EP2005647A1 - Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicast - Google Patents
Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicastInfo
- Publication number
- EP2005647A1 EP2005647A1 EP07731853A EP07731853A EP2005647A1 EP 2005647 A1 EP2005647 A1 EP 2005647A1 EP 07731853 A EP07731853 A EP 07731853A EP 07731853 A EP07731853 A EP 07731853A EP 2005647 A1 EP2005647 A1 EP 2005647A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- packets
- file
- receiving
- request
- mode
- 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.)
- Withdrawn
Links
Classifications
-
- 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/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
- H04L12/1868—Measures taken after transmission, e.g. acknowledgments
-
- 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
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
-
- 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
Definitions
- the invention relates to a method and a system for transmitting data packets relating to a file, said packets being cyclically transmitted in multicast mode, and a method and a device for receiving such packets.
- IP network Internet Protocol
- a non-limiting example of a data distribution system is peer-to-peer, also known as peer-to-peer, which allows the sharing of data between computers. a network.
- unicast defines a point-to-point network connection.
- unicast means making two computers communicate with each other, each identified by a unique network address. To do this, the data packets are routed on the network according to the address of the encapsulated recipient in the transmitted frame. Normally, only the recipient intercepts and decodes the packet addressed to him.
- a first disadvantage of these download mechanisms lies in the fact that, during massive transmissions, the content broadcast server can be saturated due to the large number of simultaneous connections established with users.
- connection in unicast mode implies a strong redundancy of the transferred data.
- Document US Pat. No. 6,256,673 discloses a method of broadcasting a file in multicast mode in which the contents of the file are continuously transmitted cyclically.
- the "multicast” mode unlike the "unicast” mode, makes it possible to simultaneously address a content to a plurality of recipient users, by means of a single sending.
- the broadcast server sends only once the data constituting the broadcast.
- the aforementioned data is duplicated by the routers of the network, dynamically, to reach authorized users who have requested it.
- the set of paths or paths followed by the data packets broadcast, from the server to the authorized users, form a multicast information broadcast tree whose root is the broadcast server, the various paths constituting the branches and the users constituting leaves of said tree.
- the multicast broadcasting mode uses a specific technique of multicast addressing.
- a data packet that is part of a multicast broadcast has a destination IP address, called a "multicast address”. All information carrier data packets belonging to the same broadcast bear the same destination multicast address.
- a unicast IP address identifies one and only one machine (or a user's workstation)
- a multicast IP address is used to identify a set (or group) of machines, namely all machines. able to access this broadcast.
- the content of the file is broadcast cyclically as long as a user has not been able to load all the packets allowing the reconstruction of the requested file.
- a user wants to download a file, after querying the server, it starts broadcasting the content of the file.
- the file breaks down, for its emission, in a multitude of packets. These are identified relative to their relative position in the file which allows the user to rebuild the file.
- a second user wants to get the same content, he connects to the same server.
- the file being broadcast the second user receives data upon connection to the server, but this data received is not necessarily at the beginning of the file.
- the server during the connection of the user, notes that it must issue the contents of the file again so that the second user receives all the packets forming the file.
- Stopping the broadcast occurs when all users have had the opportunity to receive all the packages forming the file.
- the use of the multicast mode and the cyclic transmission make it possible to optimize the quantity of data circulating on the network and, therefore, to reduce the saturation thereof.
- the management of the broadcast cycles to be performed is managed by an information note indicating that an additional cycle must be performed when a user connects during the broadcast of the contents of a file.
- the download must be made in its entirety over at most two broadcast cycles.
- An object of the present invention is in particular a method for receiving data packets relating to a file, the file being composed of a plurality of packets, the method comprising a step of receiving cyclically transmitted packets in multicast mode, characterized in that the method comprises the following steps: detecting packets not correctly received from the packets of the file that have been transmitted; for at least part of the packets identified as not correctly received: sending at least one request in unicast mode to obtain said packets; and o receiving said packets.
- the method of receiving data packets relating to a file according to the invention makes it possible, on the one hand, to receive these packets in multicast mode, the packets being transmitted in multicast mode and cyclically, and on the other hand, of receive packets not correctly received during multicast reception by means of a unicast connection.
- the use of multicast mode optimizes the network load since the same content is sent to a plurality of clients.
- a check of the integrity of the received data and a detection of the non received packets are carried out and allow the detection of the packets not correctly received.
- a file containing incorrect data or missing information is often unusable.
- the invention proposes to download these data by a connection in unicast mode, that is to say in point-to-point mode with a content server.
- the management of these incorrectly received packets is also performed so as to reduce the amount of information transmitted on the network and the time required to obtain all the packets forming the file for the client.
- the method further comprises a step of storing the received packets at their relative position in the file.
- the reception of the packets relating to a file can begin while the emission of the file is already in progress.
- the storage of the data contained in the packets must, however, be carried out at the actual location of these data during reception.
- the packets include information identifying the relative position in the file of the data transported by these packets.
- the packets comprise at least one data integrity verification information, said at least one data integrity verification information being able to, for example, comprise a cyclic redundancy check code.
- the integrity of the data received can be verified. This check allows the detection of erroneously received packets, also known as incorrectly received packets.
- the step of transmitting said at least one request in unicast mode is subject to a prior decision step whose realization depends on a predetermined criterion.
- the predetermined criterion is, for example, a function of the number of packets identified as not correctly received and the transmission cycle period of the file.
- the mode of reception of the packets identified as not correctly received is determined.
- the method comprises, prior to the step of receiving packets, a step of sending, to a resource manager, a request to obtain said file.
- the method comprises, prior to the step of sending a request to obtain said file, a step of establishing a connection in unicast mode with the resource manager.
- a link established in unicast mode between the client and the resource manager allows the latter to control all clients currently receiving the broadcast file.
- the method comprises a step of receiving, from the resource manager, receiving parameters of said file.
- the resource manager also manages the reception settings, including connection settings for clients in multicast mode that allow them to receive packets.
- the method further comprises a step of transmitting in unicast mode a notification informing of a current reception of said file.
- the method comprises a step of transmitting a notification of the end of reception of said file.
- This step is used to manage the number of clients currently receiving the broadcast file.
- Another object of the present invention is to provide a method for transmitting data packets relating to a file, the file being composed of a plurality of packets, said packets having previously been cyclically transmitted in multicast mode to at least one recipient, characterized in that the method comprises the following steps:
- the method of transmitting data packets relating to a file according to the invention makes it possible, on the one hand, to transmit these packets in multicast mode and cyclically, and on the other hand, to transmit, in unicast mode. , packets not correctly received by a recipient during the multicast broadcast.
- the use of multicast mode optimizes the network load since the same content is sent to a plurality of clients.
- the sending of erroneous packets via a connection in unicast mode makes it possible to reduce the amount of information transmitted on the network and the time required to obtain all the packets forming the file for the network. the customer.
- the packets comprise information identifying their relative position in the file.
- the packets furthermore comprise at least one data integrity verification information, said at least one data integrity verification information being able to, for example, comprise a cyclic redundancy check code. According to this feature, the integrity of the received data can be verified by the packet receiving client. This check allows the detection of received but erroneous packets, also called packets not correctly received.
- the method comprises a preliminary step of receiving a request to obtain the file in multicast mode.
- This request makes it possible to start the transmission of the requested file and to control the number of clients wishing to obtain the file.
- the method comprises a step of incrementing the number of recipients of the file, following the receipt of a request to obtain the file.
- the method comprises the following steps:
- the method further comprises a step of adapting the rate of transmission of the packets as a function of the charges borne by recipients.
- the step of receiving at least one request in unicast mode in order to obtain already transmitted packets to at least one recipient and not correctly received by the latter and the unicast mode transmission step of Required packages are made by a download server.
- the download server is, for example, a device for broadcasting packets in multicast mode.
- the invention also provides a device for receiving data packets relating to a file, the file being composed of a plurality of packets, the device comprising means for receiving cyclically transmitted packets transmitted in a multicast mode, characterized in that what the device comprises: means for detecting packets not correctly received from the packets of the file that have been sent;
- This device has the same advantages as the reception method briefly described above.
- Another object of the present invention is to provide a system for sending data packets relating to a file, the file being composed of a plurality of packets, said packets having previously been cyclically transmitted in multicast mode to at least one packet.
- recipient characterized in that the system comprises: means for receiving at least one request sent in unicast mode in order to obtain packets already transmitted to said at least one recipient and not correctly received by the latter; and
- the invention relates to a computer program stored on an information medium, said program containing instructions for implementing the method of receiving data packets relating to a file according to the invention, when this program is loaded and executed by a computer system.
- the invention also relates to a computer program stored on an information medium, said program containing instructions for implementing the method of transmitting data packets relating to a file according to the invention, when this program is loaded and executed by a computer system.
- Figure 1 shows, schematically, a general view of the system for broadcasting and receiving data carrier information according to the invention
- Figure 2 shows, schematically, the contents of a packet transmitted by a broadcast server according to the invention
- Figure 3 shows, schematically, the storage of packets received at the client
- Figure 4 schematically shows a general view of the support data broadcast and reception system.
- Figure 5 shows, schematically, the storage of packets received by the second client
- - Figure 6 shows, schematically, a general view of the broadcast system when disconnecting customers according to the invention
- Figure 7 illustrates an algorithm for recovering packets not correctly received according to the invention
- - Figure 8 shows, schematically, the hardware and / or software architecture of a client according to the invention
- Figure 9 shows, schematically, the hardware and / or software architecture of a transmission system according to the invention.
- the cyclic transmission of data packets in multicast mode in accordance with the invention is based on an architecture composed in particular of at least one multicast server SERV.
- This includes, in memory, a set of files that it can issue if a client machine, also called "client”, makes the request.
- Multicast broadcast mode works on UDP protocol
- UDP is a simple, unreliable, unassigned packet delivery protocol belonging to layer 4 of the OSI model, ie the "transport layer". This layer is in charge of the transport of data, their division into packets and the management of possible transmission errors, the latter feature being however not available in UDP mode.
- the above protocol is detailed in RFC 768.
- 3 WAY TCP is a connection establishment mechanism based on the sending of a connection request packet, the sending of a connection request packet an acknowledgment packet accompanied by a request for synchronization in the opposite direction and the sending by the issuer of a final acknowledgment).
- UDP uses a system of ports on which clients must connect.
- the broadcast server according to the invention is capable of transmitting, cyclically, data carrier data.
- This cyclical broadcast is also known as "carousel broadcast”.
- the architecture according to the invention also comprises a resource manager GR. It has a database of all files that the broadcast server or broadcast servers associated with it are able to broadcast. In addition, it manages the list of all customers connected to the download service. Customers therefore receive data carrier data during multicast broadcast.
- the resource manager and the broadcast server can be one and the same server.
- Another embodiment variant includes a configuration in which each of the clients is also a multicast server and all clients are managed by a single resource manager. In this way, the resource manager centralizes the availability information of the various files proposed by the customers.
- Such a configuration allows, first of all, the operator offering this service to expand its offer of available files. Then, it should be noted that the possible use of multiple servers of reduced capacity is more economical, with equal amount of information, than a large capacity server.
- This configuration also has the advantage that the resource manager is controlled by the service provider. The latter can therefore check the list of files proposed by customers and prevent his service from being used for the dissemination of illegal files. It can thus, in particular, delete these files from the list managed by the resource manager, without having to intervene on the clients' computers.
- the system comprises a resource manager GR and an associated SERV broadcast server.
- An example of hardware and / or software architecture of such a system is shown in Figure 9 and will be described later.
- the transmission and reception methods according to the invention and illustrated in FIG. 1 start with the connection of a client A to the resource manager GR in unicast mode (step 1).
- the client issues a request (step 2) in order to obtain the list of the files managed and accessible by the broadcast server SERV associated with this resource manager GR.
- the latter returns in response (step 3) the list of available files and the client selects the desired file.
- this is the file "update_login”.
- step 4 consists in the client issuing a request to the resource manager GR in order to obtain the "update_login” file.
- the resource manager determines whether this file is already being broadcast by the broadcast server SERV or not.
- the resource manager GR issues a request to the broadcast server SERV (step 5) so that the latter begins the cyclical transmission of the file requested by the client A (recipient of the file).
- This request includes, in addition, the connection parameters necessary to manage the broadcast in multicast mode, namely, the multicast address and port as well as the broadcast rate.
- the server by means of these parameters, is able to start sending the content of the file in multicast mode cyclically to the client or clients who have requested it beforehand.
- the broadcast server transmits to the resource manager GR an acknowledgment (step 6) indicating by the same that it will begin broadcasting, in multicast mode, the requested file.
- the use of the multicast transmission mode has the following advantages.
- broadcast group members are dynamic, allowing hosts to join and leave the group at any time.
- groups are not limited in size and members can be spread across multiple IP networks.
- the resource manager GR On receipt of the acknowledgment of the broadcast server, the resource manager GR sends the client A the following information (step 7).
- the subscription is made in particular according to the IGMP procedure.
- This is a protocol used to access or leave an IP multicast group. All IP hosts that support multicast mode must support IGMP, of which there are several versions. They are all subject to numerous RFCs with the W3C standardization body.
- the client upon receipt of the parameters of the resource manager GR creates an empty file, including the same name as that indicated in the parameters provided by said manager and the size also indicated by it.
- the broadcast server SERV starts multicasting the file (step 8).
- the contents of the file are developed in the form of packets and each packet is then sent over the network.
- the client makes an IGMP connection request (step 9) using the connection parameters transmitted by the GR resource manager.
- the client thus connects in multicast UDP mode in order to receive the packets of the file in question, namely the "update-software" file (step 10).
- the IGMP subscription is only acknowledged by the client broadcast server after the request to open a UDP connection point (or "socket") with parameters for an IP address in the range of multicast addresses and an IP address. port (This mechanism is intrinsic to TCP).
- the adhesion mechanism is managed by the lower layers of the ISO layers. From the developer's point of view, it's only about opening a socket with the multicast parameters defined by normalization.
- the packets broadcast by the broadcast server SERV must contain information determining the relative place of each packet in the file under consideration.
- the broadcast server transmits packets, including packets of a constant size, comprising a header (21) indicating the position of the packet to be inserted in the file at the reception at the client, the data carrier data (22) and information (23), such as a CRC code ("Cyclic Redundancy Check" in English terminology) for verifying the integrity of the data received, as shown in Figure 2.
- packets of a constant size comprising a header (21) indicating the position of the packet to be inserted in the file at the reception at the client, the data carrier data (22) and information (23), such as a CRC code ("Cyclic Redundancy Check" in English terminology) for verifying the integrity of the data received, as shown in Figure 2.
- the CRC code also called “cyclic redundancy check” is a type of hash redundancy used to produce a checksum (called “checksum” in English terminology) which is an integer calculated from a block of data for the purpose of detecting transmission or copy errors. It can also allow the repair of these errors.
- the client When the client receives the packets (step 10 of Figure 1), the latter are stored at their relative position in the file after checking the integrity of the contents of each packet received, including the CRC code contained in the packet. In case of failure during the integrity check, the position of the package in the file is stored in an error file, also called "error logs".
- the aforementioned file contains, in particular, the identifier of lost packets or received but erroneous packets. These packets are called “incorrectly received” packets.
- the error file is used later to retrieve the packets thus detected and identified as not correctly received.
- the client stores the packets relating to the requested file in the initially empty file and is created as shown in Figure 3.
- the client during the transfer of the packets from the required file, the client remains permanently connected to the resource manager GR.
- the latter performs a periodic test on the client to verify that it is still connected and is in the process of receiving broadcast packets.
- the client sends, regularly or not, an information frame (notification) to the resource manager GR to indicate that it is still receiving a file.
- This mechanism for verifying that the client is still in process when receiving the file sent in multicast mode is also called “keep alive”.
- TCP protocol defines a set of rules that allow the good communication between two computers through one or more interconnected networks.
- TCP acts in connected mode and provides simultaneous two-way communication.
- it is a reliable transport service.
- it defines the structure of the data and the acknowledgments exchanged and specifies how to detect and correct a packet loss or duplication.
- the resource manager GR updates the number of clients of the file being broadcast.
- the resource manager GR controls, upon disconnection, the deletion of the multicast connection of the corresponding client. This disconnection can mean, for example, that the client is disconnected and therefore can not receive anything.
- FIG. 4 illustrates the connection of a second client to the broadcast system, the broadcast server being issuing the file required by a first client and the latter being still receiving said file.
- the second client client B
- sends a first request step 41
- the resource manager GR containing the identifier of the file that it wishes to load
- this is the file "update_login”.
- the GR resource manager Upon receipt of this request, the GR resource manager notes that this file is already being broadcast by SERV broadcast servers.
- the resource manager GR responds to the client B by transmitting the same connection parameters as for the client A (step 44), provided, however, that the client B can support the reception of the file at flow in progress.
- the client B Upon receipt of these parameters, the client B, like the client A, creates an empty file, for example of the same name as the name of the transmitted file and the size indicated in the parameters.
- client B makes a connection request in UDP multicast mode to receive packets of the requested file (step 45).
- the first packet received by the client B (step 46) is inserted in the file in the place indicated by the packet header information, as shown in Figure 5.
- the missing part, ie the beginning of the file, will only be received at the next cycle of file transmission.
- FIG. 4 illustrates the various steps illustrated in FIG. 4, and described above, are applicable to any client wishing to download a file being broadcast by the broadcast server SERV.
- Figure 6 illustrates the management of client disconnections from the GR resource manager, and incidentally from the SERV broadcast server.
- the management of the connections and disconnections of the customers makes it possible to ask the server of diffusion the beginning and the stop of the diffusion of the file to diffuse.
- This connection management has the advantage of circulating data over the network only when the file is required, which limits the congestion of the network.
- a client when a client has finished receiving the file, it notifies the resource manager GR by issuing a message (step 61).
- the resource manager GR On receipt of such a message, the resource manager GR then decrements the number of subscribers according to the IGMP protocol on the file being broadcast.
- the resource manager GR When the resource manager GR detects that there are no more clients that are loading the transmitted file, it sends a notification to the broadcast server SERV so that the latter stops the cyclic transmission of the file (step 62). ). The broadcast server SERV therefore stops the transmission of the file
- step 63 without waiting for the end of the broadcast cycle. This file is no longer distributed in carousel.
- the resource manager GR considers that the client has abandoned the reception of the file (step 64).
- the resource manager issues a request to the clients that are connected to it in unicast mode.
- clients send information frames to the resource manager (step 65).
- a resource manager GR can manage a plurality of broadcast servers, these servers can be distributed in different locations on the network.
- the client can not disregard packets that are not correctly received, since a file containing software is not executable if parts are wrong or missing. The client must therefore handle the packets not correctly received for later retrieval.
- the algorithm starts in step 71 by handling packets not correctly received.
- step 72 which constitutes a decision step as to the mode of recovery of packets identified as not correctly received.
- the decision step depends on a criterion, the latter being in particular a function of the number of packets identified as not correctly received and the transmission cycle period of the packets of the file.
- step 73 the recovery of packets identified as not correctly received during the next file broadcast cycle.
- step 74 the client disconnects from the broadcast server and notifies the resource manager GR that the reception has ended.
- the recovery of the packets can be carried out as indicated in the following steps 75 to 79.
- the client disconnects from the broadcast server and notifies it to the resource manager GR (step 75).
- the client establishes a unicast connection with a server to retrieve packets identified as not correctly received (step 76).
- connection in unicast mode can be performed on the broadcast server or on another server, including a mirror server of the broadcast server.
- This connection is performed in particular in TCP mode to ensure the integrity of the data.
- the client sends at least one request containing the identifier of at least one packet to retrieve.
- the server upon receipt of the request or requests, responds by sending the client packets that have already been issued in multicast mode, but this time, the packets are sent in unicast mode.
- Step 78 corresponds to the reception of the packets at the client and the storage, in the file, of the information carrier data contained in the packet, in particular after verifying the integrity of the data.
- step 79 The algorithm ends in step 79 by disconnecting the server.
- connection of the client to the broadcast server or to another server for the purpose of recovering packets not correctly received can be performed according to the UDP protocol.
- the client at the end of step 78, the client must check the integrity of the data, and if the latter detects problems, he must reissue a request.
- the algorithm loops in step 77 until all the packets not correctly received are obtained.
- the connection of the client to a broadcast server or to another server for the purpose of recovering packets not correctly received is performed simultaneously with the multicast connection to the broadcast server.
- This variant has the advantage of obtaining the incorrectly received packets identified at the beginning of the reception of a file before the end of a multicast transmission cycle of the file.
- This variant is particularly interesting when receiving large files.
- This variant embodiment may require the implementation of a particular management for counting lost packets, in particular a statistical management of the number of packets lost. This management must make it possible, in particular, to determine whether the unicast connection is maintained during the entire reception of the file in multicast mode, or if the unicast connection is established several times during narrower periods.
- the broadcast server can transmit the file at a rate that can be adapted, in particular according to the maximum loads supported by each of the clients.
- a first method is to readjust the delivery rate by taking into account the lower capacity in terms of resources among the customers, provided, however, that the gap with the capacities of the other customers is not too constraining for the latter.
- a second method is to create a new multicast streaming channel with a different throughput. When a new client connects, they are assigned the most appropriate broadcast channel for their throughput capabilities.
- the resource manager GR can create a new multicast broadcast channel with a lower bit rate.
- the GR resource manager can also manage multiple rate ranges on which it assigns different clients, for example, 4Mb / s, 2Mb / s, 512kb / s, 128kb / s.
- the different ranges can be set by the GR resource manager.
- the information transmitted by the broadband broadcast server is transmitted by a lower rate broadcast server with a certain time lag.
- a client receiving a stream sent by the broadband broadcast server may also use the lower rate broadcast server and connect to it, in order to recover all or part of the packets identified as not correctly received.
- FIG. 8 represents an example of a hardware and / or software architecture of a client according to the invention and which is implemented in the manner described with reference to FIGS. 1, 4, 6 and 7.
- a client 81 in particular Client A, comprises, on the one hand, means for managing a communication 82 for receiving a file in multicast mode, and, on the other hand, means for managing a communication in communication.
- unicast mode 83 to receive packets not correctly received.
- management means 82 comprise means for establishing a connection in unicast mode with the resource manager 84 and means for transmitting a request 85 to request obtaining a given file. .
- the management means 82 also comprise means for receiving the reception parameters of the file enabling the connection to the broadcast server, and means for establishing the connection in multicast mode using the reception parameters received.
- the management means 82 furthermore comprise means for receiving and memorizing the file broadcast in multicast mode by a broadcast server and means for detecting the packets not correctly received from the packets of the file that have been sent.
- management means 82 comprise transmission means 90 of a notification of the end of receipt of the file.
- management means 82 include transmission means 91 of information frames to indicate that the client is in the process of receiving a file transmitted in multicast mode.
- the management means of the unicast communication 83 comprise, for their part, decision means 92 for sending at least one request in unicast mode to a download server.
- management means 83 comprise means for establishing a unicast connection 93 with a loading server in order to obtain the packets not correctly received, means 94 for transmitting at least one unicast request to this loading server, as well as means for receiving and storing 95 required packets.
- FIG. 9 represents an example of a hardware and / or software architecture of a data packet transmission system according to the invention and which is implemented in the manner described with reference to FIGS. 1, 4 and 6.
- the data packet sending system 100 comprises at least one broadcast server 101, at least one resource manager 102 and at least one download server 103. It will be noted that said at least one broadcast server 101, said at least one a resource manager 102 and said at least one download server 103 may be made according to a single hardware and / or software component.
- the broadcast server 101 is able to broadcast cyclically in multicast mode packets forming a file to at least one recipient. It includes, in particular, packet sending means 104, start means 105 for sending packets of a given file and stop means 106 for sending the file.
- the broadcast server 101 includes means 107 for matching the packet transmission rate as a function of the charges borne by the recipients of the packets.
- the resource manager 102 includes means 108 for receiving a request to obtain a file in multicast mode.
- the resource manager 102 includes means 109 for incrementing the number of recipients of the file being transmitted by a broadcast server associated with the resource manager.
- the manager 102 also comprises, means for determining the number of recipients 115 receiving the transmitted file, these determination means being able to decrement the number of recipients of the file on receipt of a notification of the end of receipt of the file.
- it includes means 111 for informing the broadcast server that it must stop the transmission of a file.
- the download server 103 comprises means 112 for receiving at least one request sent in unicast mode in order to obtain already transmitted packets to the addressee sending the request and means 113 for sending in unicast mode of the requested packets. .
- the download server 103 may also be a broadcast server 102.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0651160A FR2899410A1 (fr) | 2006-03-31 | 2006-03-31 | Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicast |
PCT/FR2007/051049 WO2007113447A1 (fr) | 2006-03-31 | 2007-04-02 | Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicast |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2005647A1 true EP2005647A1 (fr) | 2008-12-24 |
Family
ID=37763780
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP07731853A Withdrawn EP2005647A1 (fr) | 2006-03-31 | 2007-04-02 | Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicast |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2005647A1 (fr) |
FR (1) | FR2899410A1 (fr) |
WO (1) | WO2007113447A1 (fr) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
PL2335381T3 (pl) | 2008-09-30 | 2013-06-28 | France Telecom | Sposób przesyłania danych przez źródło przesyłania grupowego z przesyłaniem identyfikatora strategii przesyłania w kanale sygnalizacji przesyłania grupowego |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1185033A4 (fr) * | 2000-04-06 | 2004-06-23 | Ntt Docomo Inc | Procede et systeme de multidiffusion, station mobile et station de base |
US7143132B2 (en) * | 2002-05-31 | 2006-11-28 | Microsoft Corporation | Distributing files from a single server to multiple clients via cyclical multicasting |
-
2006
- 2006-03-31 FR FR0651160A patent/FR2899410A1/fr active Pending
-
2007
- 2007-04-02 EP EP07731853A patent/EP2005647A1/fr not_active Withdrawn
- 2007-04-02 WO PCT/FR2007/051049 patent/WO2007113447A1/fr active Application Filing
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2007113447A1 * |
Also Published As
Publication number | Publication date |
---|---|
FR2899410A1 (fr) | 2007-10-05 |
WO2007113447A1 (fr) | 2007-10-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2006016055A2 (fr) | Procede et serveur de referencement de diffusion poste a poste de fichiers demandes par telechargement a ce serveur | |
FR2805112A1 (fr) | Procede et unite de controle de flux d'une connexion tcp sur un reseau a debit controle | |
WO2006111635A1 (fr) | Procede et systeme de transmission d’un flux multicast en reseau d’echange de donnees | |
EP3603024B1 (fr) | Procédé de recommandation d'une pile de communication | |
FR2824930A1 (fr) | Procede de communication et/ou de partage de ressources machines, au sein d'un reseau de communication, entre une pluralite de membres d'une communaute | |
FR2949931A1 (fr) | Procedes et dispositifs de transmission d'un flux de donnees, produit programme d'ordinateur et moyen de stockage correspondants. | |
FR2870022A1 (fr) | Procede et dispositif de distribution de donnees numeriques notamment pour reseau pair-a-pair | |
WO2008087364A2 (fr) | Procede de transmission/reception en temps reel de donnees par paquets entre un serveur et un terminal client, serveur et terminal correspondants | |
FR3029376A1 (fr) | Procede de traitement d'une requete de livraison de donnees, dispositif, module proxy, terminal client et programme d'ordinateur associes | |
FR3034943A1 (fr) | Procede de lecture en continu sur un equipement client d'un contenu diffuse au sein d'un reseau pair a pair | |
FR2946164A1 (fr) | Procede de telechargement de donnees de grande taille vers un grand nombre de machines clientes en reseau a partir d'un serveur unique | |
EP2005647A1 (fr) | Procede et dispositif d'emission et de reception de paquets de donnees relatifs a un fichier emis de maniere cyclique en mode multicast | |
EP3231190B1 (fr) | Procédé et dispositifs permettant une transmission d'un flux de données selon un mode de transmission multipoint | |
WO2020193429A1 (fr) | Procédé d'obtention d'un segment de données par un dispositif client apte à communiquer avec une pluralité de réseaux de diffusion de contenu | |
WO2019220034A1 (fr) | Gestion du téléchargement progressif adaptatif d'un contenu numérique au sein d'un terminal de restitution d'un réseau de communication local | |
FR2904503A1 (fr) | Procede d'acces par un client a un service au travers d'un reseau, par utilisation combinee d'un protocole de configuration dynamique et d'un protocole point a point, equipement et programme d'ordinateur correspondants | |
EP3414873B1 (fr) | Procédé de transmission de données dans une communication multi-chemin | |
WO2020260825A1 (fr) | Procede de gestion d'une communication entre terminaux dans un reseau de communication, et dispositifs et systeme pour la mise en oeuvre du procede | |
EP1647125A1 (fr) | Description de contenu de paquets dans un reseau de communication par paquets | |
EP2446608B1 (fr) | Technique de contrôle d'accès par une entité cliente à un service | |
WO2016055645A1 (fr) | Procédé de diffusion de contenus en streaming dans un réseau pair à pair | |
EP4272449A2 (fr) | Contrôle de la transmission d'au moins un contenu depuis un equipement fournisseur vers un noeud d'ingestion | |
WO2013144494A1 (fr) | Dispositif et procede de gestion pour un service reseau | |
FR3124668A1 (fr) | Procédé de contrôle de la livraison partagée d’un contenu | |
FR2951045A1 (fr) | Procede de gestion de la taille de paquets de donnees d'un flux de donnees, produit programme d'ordinateur, moyen de stockage, et tete de tunnel correspondants. |
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: 20081021 |
|
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 IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20120210 |
|
DAX | Request for extension of the european patent (deleted) | ||
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ORANGE |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20171025 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20180306 |