CN1973514B - Module and method for file delivery session handling - Google Patents
Module and method for file delivery session handling Download PDFInfo
- Publication number
- CN1973514B CN1973514B CN200580020889.9A CN200580020889A CN1973514B CN 1973514 B CN1973514 B CN 1973514B CN 200580020889 A CN200580020889 A CN 200580020889A CN 1973514 B CN1973514 B CN 1973514B
- Authority
- CN
- China
- Prior art keywords
- timer
- receiver module
- receiving
- file delivery
- waiting timer
- 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 - Fee Related
Links
Images
Classifications
-
- 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]
-
- 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/14—Session management
-
- 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/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/28—Timers or timing mechanisms used in protocols
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
- Acyclic And Carbocyclic Compounds In Medicinal Compositions (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
Abstract
In receiving a file delivery session in which file delivery tables (FDTs) identify Transport Objects (TOs) transmitted along with the FDTs, a receiver determines whether the files of the session have been received using a number of timers. A fragment wait timer t1 is started for each new TO declared in an FTD when that FDT is received. Each timer is cancelled when at least a fragment of the corresponding TO is received. Alternatively, a single timer is cancelled when at least a fragment of all the TOs have been received. A new object wait timer t3 is started when all the TOs declared in an FDT are received, and is cancelled when a new FDT is received. One of a number of table wait timers t2 is started whenever a TO which is not declared in any received FDT is received, and is cancelled when an FDT declaring that object is received. The file delivery session is left if any timer expires. If following expiry of a timer it is deemed that the file delivery session has almost been received fully, the session is left after a short period of time, so as to allow the session to be fully received.
Description
Technical field
Relate generally to of the present invention is sent through the resource of digital communication system.The present invention relates to a kind of receiver module and a kind of method of handling file delivery session that is used for being received in the data that file delivery session transmits especially.The invention still further relates to a kind of file delivery session that is directed against and carry out network operating node and a kind of reflector of operating to file delivery session.
Background technology
FLUTE is the project of under the control of internet engineering task group (IETF), managing.FLUTE for through internet unidirectional delivery document definition agreement.This agreement is suitable for multicast network especially, but should technology likewise can be applicable to use with unicast addressed.The FLUTE standard is implemented on the asynchronous layered coding (ALC), and this ALC is the basic agreement that distributes and design for extensive scalable multicast.ALC has defined the transmission of any binary object, and in following article, drafts to some extent: Luby, M.; Gemmell, J., Vicisano; L., Rizzo, L. and J; " Aysnchronous Layered Coding (ALC) ProtocolInstantiation " of Crowcroft, RFC in December, 3450,2002.For file delivery was used, it was not enough that the object transmission is only arranged.Terminal system need know in fact object represents what.FLUTE provides following mechanism, and this mechanism is used for sending the characteristic of file with signal and this characteristic being mapped to the notion of ALC with this mode of parameter that allows those objects that are used for being received of receiver design.In FLUTE, ' file ' is relevant with ' object ', and this point is discussed in above-mentioned ALC article to some extent.
In the FLUTE file delivery session, transmitter that sends this session and a plurality of receivers that receive this session are arranged.Receiver can add session at any time.One or more abstract objects such as file are sent in this session.Number of files can change.Any file can use a plurality of groupings to send.Any grouping of in session, sending possibly lost.
FLUTE has the possibility that is used to send any kind of document and any file size.FLUTE can be applicable to use several seconds or delivery session more of a specified duration that file delivery is arrived many main frames.For example, FLUTE can be used for simultaneously large software being upgraded being delivered to many main frames.It also can be used for continuously and the data of segmentation, and such as the text of arranging by the time that is used for captions, it is essential so that come the richness of convergent-divergent session according to the congestion status of network to use it to pass in the layering of ALC and LCT thus.It also can be suitable for basic metadata transmits, and this metadata for example is to make the user use the SDP file that can visit Multimedia session.It can use with radio broadcasting system, because it is expected to be used in combination with IPDC (Internet Protocol data broadcasting) through the DVB-H (DVB-mobile phone) that is developing at present standard for it especially.
FLUTE does not allow receiver to confirm how long it need stop so that realize being provided with by transmitter the purpose of session on channel.Therefore receiver can't know when it receives whole file broadcasting.FLUTE does not have definition to lead to the semanteme of the session of receiver yet.FLUTE uses file delivery session static and that define, and promptly each file delivery session is sent fixing file set, and this document is immutable between session.
The present invention not only seeks to overcome these deficiencies, and in its related up to now any file delivery, has more wide applicability.
Summary of the invention
According to a first aspect of the invention, a kind of receiver module that is used for being received in the data that file delivery session transmits is provided, this module comprises the one or more timers in the following timer:
A) fragment waiting timer;
B) new object waiting timer; And
C) table waiting timer;
This receiver module is used for leaving file delivery session in response to detecting expiring of any timer of one or more timers.
The fragment waiting timer can be used for receiving the statement of quoting one or more objects and being activated in response to receiver module, and is used for receiving the whole of an object of one or more objects or part or receive the whole of all objects in one or more objects in response to receiver module alternatively or at least partly be cancelled at least in response to receiver module.Under this situation; Receiver module can comprise a plurality of fragment waiting timers; Each fragment waiting timer is correlated with the different objects in the object of in statement, quoting, and is used for receiving that in response to receiver module the whole of affiliated partner perhaps at least partly are cancelled.
New object waiting timer can be used for having received all objects in one or more objects that the statement of being received by receiver module is quoted and being activated in response to detecting receiver module; And be used for receiving another different statement and being cancelled in response to receiver module.
The table waiting timer can be used for receiving at all unreferenced object of any statement of receiving in response to receiver module and be activated, and is used for receiving the statement of quoting that object and being cancelled in response to receiver module.Here; Receiver module can comprise a plurality of table waiting timers; Each table waiting timer with received by receiver module and in any statement of receiving all unreferenced different objects relevant, each is shown waiting timer and is used for receiving the statement of the affiliated partner of quoting it and being cancelled in response to receiver module.
This timer or each timer can be set to have the duration of being confirmed by corresponding timer parameter.Here, one or more timer parameters can for good and all be stored in the receiver module, perhaps are stored in the receiver module with renewable mode alternatively.The part that one or more timer parameters can be used as the signal that receives through communication network receives, and for example the part as packet receives.
This receiver module can be used to receive the grouping that comprises object and statement and also comprise one or more timer parameters alternatively, for example Internet protocol packets.
This receiver module can be used for definite measurement that file delivery session is received integrality in response to timer expires; Be used for to measure with threshold value and do comparison, and be used for based on this closer like leaving session immediately or leaving session after the section in effective time.Here, effective time section have with timer or timer in expiration time half the of short timer equate the perhaps shorter duration.
This receiver module can be used for estimating in response to timer expires the time that the reception expection of file delivery session is accomplished; Be used for should the time and threshold value do comparison, and be used for based on this closer like leaving session immediately or leaving session after the section in effective time.
The present invention also provides a kind of portable, hand-held device that comprises above-mentioned receiver module.
According to a second aspect of the invention, a kind of method that receives file delivery session is provided, the one or more steps during this method may further comprise the steps:
A) start the fragment waiting timer;
B) start new object waiting timer; And
C) start the table waiting timer;
This method also comprises in response to detecting expiring of any timer in one or more timers leaves file delivery session.
According to a third aspect of the invention we; A kind of network node is provided, can have operated in order to the one or more parameters in the fragment waiting timer parameter of being used by receiver, new object waiting timer parameter and the table waiting timer parameter to be provided to file delivery session.
According to a forth aspect of the invention; A kind of reflector is provided; Can operate in order to the one or more parameters in the fragment waiting timer parameter of being used by receiver to file delivery session emission, new object waiting timer parameter and the table waiting timer parameter, these one or more parameters are launched together in company with file delivery session alternatively or are formed the part of file delivery session and launch.
Only embodiments of the invention are described referring now to accompanying drawing through example.
Description of drawings
In the accompanying drawings:
Fig. 1 carries out illustrated schematic block diagram for the mobile phone handsets that receive data from the server that connects through the internet;
Fig. 2 is the schematic block diagram of the circuit of cell phone shown in Fig. 1;
Fig. 3 and Fig. 4 are that illustrated flow chart is carried out in the operation when receiving file broadcasting as file delivery session a part of for Fig. 2 mobile phone;
Fig. 5 combines object lesson that illustrated time chart is carried out in the operation of Fig. 2; And
Fig. 6 to Fig. 8 is the state machine presentation graphs of the operation of Fig. 2 mobile phone.
Embodiment
In Fig. 1, form is that the travelling carriage of mobile phone handsets 1 receives broadcast data from DVB-H broadcasting equipment B, and this broadcasting equipment B is connected to like the internet through network 2 can be with the content server 3 of data content download to cell phone 1.Content server 3 has the association charging server 4 that is used for downloading to the subscriber content charging.
This mobile phone can have the WAP function and can for example pass through GPRS channel reception data with the speed of 40Kbit/ level second.Yet will be understood that; The invention is not restricted to any specific data rate or data transfer mechanism, and for example also can use WCDMA, CDMA, GPRS, EDGE, WLAN, BT, DVB-T, IPDC, DAB, ISDB-T, ATSC, MMS, TCP/IP, UDP/IP or IP system.
This mobile phone also comprises DVB-H receiver module 19.This module is passed through DVB antenna 20 from DVB broadcasting equipment B receiving broadcast signal.
The user of mobile phone 1 can ask from one or more servers such as server 3 data download contents, and for example the video clipping that will on display 8, replay and show etc. is downloaded in request.The video clipping of downloading like this is stored in the memory 12.Other data file that varies in size also can be downloaded and be stored in the memory 12.Can start download by the user, perhaps the setting based on mobile phone is allowed to download by the user.Can download by the Carrier Requirements data of network 2 alternatively, during particularly to software upgrading.
In FLUTE, file delivery session has the zero hour and the finish time, and relates to one or more channels.In the zero hour and the finish time one or two can that is to say that one or more moment possibly not known by receiver without limiting constantly.If in session, use a plurality of channels are arranged, then these channels can be walk abreast, the mixing of serial or parallel and serial.File delivery session transports file as transmission object.When transmission object had semanteme, this object became file.Semanteme can comprise title, position, size and type.Each file delivery session transports zero, one or more transmission object (TO).Each TO can be used as the one or more groupings that are packaged in the underlying protocol and sends.Specific cluster can occur for several times in each session.Specific T O can use a channel or use several channels to send.TO can transmit for several times.
There is the special TO of the title of file delivery table (FDT) to send the mapping of file set to TO with signal.Several FDT can be arranged.Each different FDT can be called the FDT instance.The content of different FDT instances can be overlapping or can be not overlapping.The FDT instance can be sky.FLUTE provides the concrete definition that can how to use the FDT instance.The reception that the content of TO and FDT is carried out and handle and will can be those skilled in the art and understand, so repeat no more here.
Three parameters in these embodiment of the present invention, have been defined.These parameters or their any mixing can be used to confirm whether it should leave file delivery session by receiver.Therefore, receiver can leave that session earlier when perhaps resonable degree is known all associated documents of having received delivery session assuredly assuredly.Receiver uses one or more parameters and the related timer in three parameters and the understanding of grouping of receiving and the FDT that receives is determined whether to continue to receive file delivery session.
In brief, these three parameters are:
Fragment stand-by period-this parameter relates to and is receiving FDT and reception from the maximum allowed time between at least the first fragment of the TO of that FDT.
New object stand-by period-this parameter relates to the maximum allowed time between all TO that receive FDT and the different FDT of reception.
Table stand-by period-this parameter relates to the TO that in being received in being seen up to now FDT, all not have statement and reception and states the maximum allowed time between the FDT of that TO.
For example its value can use millisecond can send to receiver with signal with any suitable mode as this parameter of unit.Alternatively, this parameter can be hardwired in the receiver during fabrication.
In one embodiment, the signal by through the broadcasting of DVB-H network B sends to mobile phone 1 with parameter with signal.During fabrication parameter is built in the mobile phone 1 alternatively.Why favourable with signal transmission parameter is because it can be in the flexibility, the particularly temporal flexibility between the transmission of some composition of session that need not to allow under the compromise situation of receiver operation file delivery session.In either case, parameter all is stored in the mobile phone 1, for example is stored in the memory 12 perhaps to form in the memory of DVB-H receiver 19 parts.
To use Fig. 3 and Fig. 4 to describe the operation of mobile phone 1 (being its DVB-H receiver 19 in a general sense) when it adds file delivery session now.In Fig. 3, operation starts from step S3.1, next in step S3.2, new object waiting timer t3 is arranged to have the value of new object stand-by period parameter and starts this timer t3.DVB-H receiver 19 receives a TO then in step S3.3.In this example, if a grouping is only arranged then when correctly receiving this grouping, if perhaps TO intersperses among a plurality of groupings then when correctly receiving all groupings, thinks and receive this TO.The two or more groupings relevant can be in turn received, but also the one or more groupings relevant maybe be in the period at intermittence, received with other TO with single TO.When receiving the last grouping of TO, just that TO has been regarded as the reception among the step S3.3.Whether relevantly confirm to divide into groups at step S3.4 with FDT.If like this, then operation proceeds to step S3.5.
Confirm at step S3.5 whether FDT is new FDT, promptly whether it be all unreceived FDT in the current file delivery session up to now.If it is new FDT, then select TO identifier (TOI) from FDT at step S3.6.Each TO has corresponding TOI, and is not used in the TOI of a plurality of TO.Confirm at step S3.7 whether this is new TOI then, the TOI that does not comprise as yet among the FDT that promptly in the current file delivery session, receives.Whether if it is new TOI, it is effective then to confirm to be used for the table waiting timer t2 (TOI N) of that TOI at step S3.8, and promptly whether this timer is just in timing.For each TOI independent table waiting timer t2 is arranged.If like this, then in step S3.9, stop this table waiting timer.If this table waiting timer t2 (TOI N) is not effectively, then will be arranged to have fragment stand-by period parameter for the fragment waiting timer t1 of that TOI and start this timer t1 at step S3.10.For each TOI independent fragment waiting timer t2 is arranged.After step S3.9 or step S3.10,, confirm at step S3.11 whether this FDT comprises more TOI according to the inquiry result of step S3.8.If more TOI are arranged, then operation turns back to step S3.6, wherein selects new TOI, i.e. still untreated TOI in active procedure.If step S3.7 is not new at the bright TOI that considers of any phase table, promptly in current sessions, received this TOI, then this operation directly proceeds to the inquiry of step S3.11, and correspondingly skips steps S3.9, S3.10 and S3.10.If show that at step S3.5 FDT is not new, promptly in current sessions, received this FDT, then skips steps S3.6 to S3.11 proceeds to step S3.12 and operate to replace.
The result of step S3.5 to S3.10 is; If new TOI is arranged in new FDT: if be used for the table waiting timer t2 of that TOI is not effective; Then be provided with and start the fragment waiting timer t1 that is used for that TOI; And if the table waiting timer t2 that is used for that TOI is effectively, then stop this timer t2.All new TOI among this process check FDT, and suitably be provided with for each TOI and start fragment waiting timer t1 or stop to show waiting timer t2.
After the follows step S3.11, perhaps follow closely after negate the confirming of step S3.5, confirm in step S3.12 whether the FDT that receives comprises any new TOI, promptly comprise and the relevant TOI of still unreceived TO in current sessions up to now.Confirm if having certainly, find that promptly FDT comprises one or more and the relevant TOI of still unreceived TO in current sessions up to now, then in step S3.13 replacement with restart new object waiting timer t3.After this step or continue after negate the confirming of step S3.12, operation turns back to step S3.3, wherein begins to handle new TO or FDT.
If confirm that at step S3.4 the TO and the FDT that receive are irrelevant, suppose that then this TO is relevant with file, and operation proceed to step S3.14.Whether the fragment waiting timer t1 of TOI that confirms to be used for this TO here is effective.If effectively, then stop fragment waiting timer t1 at step S3.15.Only be provided with just effectively owing to be used for the fragment waiting timer t1 of given TOI, so effectively new FDT has been received in this timer indication at step S3.10.Because if fragment waiting timer t1 finds effectively at step S3.14 at it; Then be stopped, so if the result does not receive corresponding TO then the fragment waiting timer t1 that is used for given TOI expires within the time set by fragment stand-by period parameter at step S3.15.If within the time set by fragment stand-by period parameter, receive TO, then this timer does not expire and just is cancelled.Therefore, if receiver do not receive each TO of FDT then will only wait for by fragment and wait for the determined time of parameter leaving before the file delivery session in order to receive those TO.
After step S3.14 and S3.15, operation proceeds to step S3.16.Here determine whether to receive statement, promptly determine whether in current sessions, to receive the FDT that comprises this TOI for TOI.If make and negate confirming, the table waiting timer t2 that then will be used for that TOI at step S3.17 is arranged to have by the determined value of table stand-by period parameter, starts timer then.Such effect is, starts the table waiting timer t2 that is used for this TOI during this TOI of without proper notice still when receiving TO.If TOI just was declared before table waiting timer t2 expires, then at this timer of step S3.9 cancellation t2.If do not receive this TO, then show waiting timer and expire.
After step S3.16 and S3.17, operation turns back to step S3.3, wherein receives another TO for processing.
Can implement to be used for new object waiting timer t3 and the fragment waiting timer t1 and table waiting timer t2 of each TOI with any suitable mode, for example use discrete timer (not shown) or use on controller 11, perhaps to be contained in the subroutine of implementing on the processor (not shown) in the DVB-H receiver 19 and implement.
Analysis according to Fig. 3 flow chart will be understood that; The table waiting timer t2 that is used for given TOI is only just effective when DVB-H receiver 19 is being waited for FDT, just can not take place when identifying this TO among the FDT that this point is only received during current sessions receiving TO.Under this situation; DVB-H receiver 19 expectation receive FDT or with all different FDT of any FDT that receives up to now, and the use of his-and-hers watches waiting timer t2 can cause the DVB-H receiver to wait for the scheduled time that is equated by the indicated time quantum of table stand-by period parameter and measuring in order to receive that table.If before the table waiting timer t2 of the TOI that is used for that TO countdown is to zero, do not receive suitable FDT, promptly comprise the FDT of that TOI, then DVB-H receiver 19 leaves this session.
Though when all that correctly receive the TO that intersperses among a plurality of groupings are divided into groups, think hereinbefore and in step 3.3, received TO, alternatively, still can not operate about independent grouping even receive all groupings of formation TO as yet.Under this situation, step S3.3 relates to the reception of single grouping, and is right after inserting step S3.18 before step S3.14.Confirm in step S3.18 whether this grouping is first grouping of receiving about TO.Confirm that if make certainly then operation proceeds to step S3.14.Otherwise operation is ignored this grouping and is turned back to step S3.3.The result of this step is if receive any fragment of that TO then stop to be used for the fragment waiting timer t1 of this TO.
Now but selection operation will be described.The inquiry that is replaced in according to step S3.12 provides step S3.13, can fully omit step S3.12, and can replace inserting step S3.13 after definite certainly branch of step S3.7.For example, step S3.13 can directly be placed on after the step S3.7 or directly be placed on before the step S3.11.But the effect of this selection operation is identical with previous embodiment, but owing to can omit step S3.12, so but confirming of relating to of this selection operation will lack one.
24a in Fig. 2,24b...24n place illustrate the fragment waiting timer.Illustrate the table waiting timer at 25a, 25b...25c place.Illustrate new object waiting timer at 26 places.
Referring now to Fig. 4 the mobile phone 1 relevant with table waiting timer t2 with fragment waiting timer t1, new object waiting timer t3 and the operation of DVB-H receiver 19 are described.This operation is carried out with the operation of Fig. 3 concurrently.This can be through using independent hardware, realizing through use subroutine and appropriate operating system software alternatively.
With reference to Fig. 4, when session is in progress, i.e. in the time of among session is receiving, this representes through beginning session step S4.1, operates in to stay among the step S4.2 in the circulation till definite timer expires.If any timer among fragment waiting timer t1, new object waiting timer t3 and the table waiting timer t2 expires, i.e. countdown is to zero, and then step S4.2 provides definite certainly, therefore causes to proceed to step S4.3.Certainly, timer can replace from the suitable timing of zero perhaps another value to predetermined value.
Step S4.2 can carry out with any suitable mode.There is no need just has notice at timer in expiring immediately, as long as fully check each timer continually timer expire and Fig. 4 in move on between the operation of step S4.3 and do not have excessive deferral.
Determine whether to receive all TO that corresponding TO I identified at step S4.3 by among the FDT that during current sessions, receives.Confirm if make certainly, confirm that then file delivery session completes successfully,, and leave this session at step S4.4 because mobile phone 1 has been received the predetermined All Files that will be sent by this session up to now.Leave session and will be understood to include the grouping that the termination reception is used for this session.As a rule, this relates at least some receiver functions of cutting off DVB-H receiver 19, but it also can keep connecting so that receive other broadcast data.In case left session, the power consumption of mobile phone can greatly reduce, and prolongs the time before battery 17 need recharge thus.
After affirming of step S4.5 confirmed, operation proceeding to optional step S4.6.This step is why optional to be because it can omit fully.Confirming at step S4.6 whether the file delivery process will be accomplished soon, is through determining whether within short predetermined amount of time, receiving or accomplishing one and omit or incomplete TO realizes in this example.This can carry out with any suitable mode.For example possible is, if current the reception with stable speed divided into groups and block length is known, this can predict and accomplish the needed time quantum of branch group of received.Can use to transmitted in packets regularly or any understanding of scheduling (for example waiting emission times without number to divide into groups) from rotating-disk memory (carousel), to the calculating of average or nearest Data Receiving speed and/or wait until the time that the file delivery session reception was calculated or estimated to accomplish to the amount of the data of reception.If forward error correction data such as Reed Solomon data form the part of TO, can confirm that then DVB-H receiver 19 does not need zero padding.Under this situation, need not receive all application datas and/or odd and even data equally, this was both because odd and even data can be corrected the mistake in the application data, again because odd and even data only just needs when wrong in application data.
The time that constitutes a little time quantum can be confirmed with any suitable mode.It can be scheduled to.It can depend on the remaining quantity of electric charge in the battery 17.Especially, high relatively charge level is arranged in the battery 17 then time quantum can be bigger, if battery does not have too many electric charge then time quantum can be less if detect.The battery charge level can be confirmed with any suitable mode.
If it is definite certainly that step S4.6 provides, then before step S74.4 receiver 19 left session, this session continued the short time at step S4.7, for example in step S4.6, was used as the scheduled time of threshold value.Can use independent timer to come implementation step S4.7.
If step S.5 with 4.6 in a step provide and negate to confirm, then under the situation of not receiving All Files, just leave session at step S4.4.This point is suitable equally when after step S4.7, not receiving All Files.Under arbitrary situation in these situation, can for example on display 8, error message be provided.The DVB-H receiver can infer in view of the above that this document delivery session is unsustained conversation type.
The multiplexing time slot of next schedule link layer (time slice burst (time sliceburst) that promptly is used for DVB-H) after timer expires perhaps refreshes (flush) till the whole slot cycle (this cycle took DVB-H maximum 41 seconds) through waiting by the time before leaving session can to allow system.
The operation of the step S3.3 to S18 of Fig. 3 can be used software implementation, for example passes through based on self-explantory following false code.
Receive grouping P with TOIM from session
If grouping P carry part or complete FDT instance
If after receiving, intactly receive the FDT instance
The complete FDT instance of receiving of If be " new " FDT instance
For each TOI N in the FDT instance of receiving, do{
IfN be " new " TOI statement
If table_wait_timer (N) effectively
Stop table_wait_timer (N)
}else{
Fragment_wait_timer (N) is set;
Start fragment_wait_timer (N)
}
}
}
If in the FDT instance, have any " new " TOI statement
Replacement global_new_table_wait_timer;
}
}
}else{
If this be by receiver see/receive be used for first of TOIM divide into groups
If fragment_wait_timer (M) effectively
Stop fragment_wait_timer (M)
}
The If receiver do not see as yet/receive the statement that is used for TOIM
Table_wait_timer (M) is set;
Start table_wait_timer (M)
}
}
}
P carries out repetition to next one grouping.
Optional enforcement as above-mentioned enforcement is following.Replaced order " replacement globa_new_table_wait_timer " shown in the setting; Same effect can realize as follows: replace this order is arranged at after " If N is " new " TOI statement " confirm, i.e. conduct is confirmed the consecutive order of step with " Iftable_wait_timer (N) is effective ".But this just has and one of above-mentioned selection operation about Fig. 3 operation identical effect.
The operation of DVB-H receiver 19 can be summed up as follows.When receiving file delivery session, wherein field descriptor table FDT has identified the TO that sends together in company with FDT, and receiver 19 uses a plurality of timers to determine whether to receive the file of this session.When receiving this FDT, start fragment waiting timer t1 for each the new TO that in this FDT, states.When receiving at least one fragment of corresponding TO, cancel each timer.When receiving all TO, cancel single timer alternatively.When receiving all TO that in FDT, state, start new object waiting timer t3, and when receiving new FDT, cancel this timer.As long as just start one of many table waiting timer t2 when receiving in any FDT that receives all unstated TO, and when receiving the FDT of that object of statement, cancel this timer.If any timer expires then leaves file delivery session.If after timer expires, think the approaching file delivery session of fully receiving, then after the short time period, leave session so that allow fully to receive this session.
The operation of Fig. 3 and Fig. 4 provides the support to the living document broadcast session, promptly this session file can and also thus TO also can in session, change.Be exactly the step S3.12 that helps to provide this support especially.
The file delivery session occasion that the operational applications of Fig. 3 is arrived expection is described referring now to Fig. 5.In Fig. 5, show in time the timetable of progress to the right, this timetable illustrates the operation of DVB-H receiver 19 during receiving file delivery session of mobile phone 1.This session starts from T
BeginningAnd end at T
Finish
At moment T1, DVB-H receiver 19 adds file delivery session.
At moment T2, receiver 19 receives the instance A (FDTA) of FDT table.This table is associated object with their semanteme (such as title, size, medium type etc.).In this example, FDTA has stated transmission object x, y, also can state some other transmission objects.First instance that this FDT that is receiver 19 is seen shows.The receiver utilization comes for each TOI among the FDT fragment waiting timer t1 to be set with the value that fragment wait moment parameter equates.Start these timers then.
Between moment T1 and moment T3, receiver 19 receives some groupings.Some groupings during these divide into groups belong to the TO that in FDTA, states.Receiver 19 stops to be used for the fragment waiting timer t1 of that TO when receiving first fragment of the TO that in FDTA, states.In this example, receive fragment from each TO that states, but if not so then leaving session.
At moment T4, receiver 19 receives the grouping that belongs to transmission object " z ", and this transmission object was not all stated in any table instance of seeing up to now.Receiver 19 value of utilization table wait parameter then comes for that divides into groups to be provided with table waiting timer t2, and starts this timer.
By moment T5, receiver 19 has been received the All Files of in the instance of the FDT table of seeing up to now, stating.Though received at least one fragment by moment T3, received all fragments that are used for each TO by moment T5 from each TO.Receiver 19 here utilizes with new object and waits for that the value that parameter equates is provided with object waiting timer t3, and starts this timer.
At moment T6, receiver 19 is received the instance B (FDTB) of FDT table.In this example, FDTB is different from FDTA, and statement TOw, v and some other TO of possibility.If any TO that in FDTB, states is that any previous instance of showing at FDT is unstated TO among the FDTA, then receiver stops the table waiting timer t2 (seeing the step S3.8 of Fig. 3) that (and also resetting alternatively) is used for these TO.In addition, if FDTB has stated transmission object " z ", then receiver 19 stops (and also resetting alternatively) object waiting timer t3 (seeing step S3.13).
File delivery session has the T finish time that receiver 19 known warps define in this example
FinishUnder this situation, arrive the T finish time of file delivery session when receiver 19
FinishThe time, it just leaves file delivery session.
The state machine 29 of Fig. 6 comprises first state, 30 to the 5th states 34.In second state 31, receiver is waited for TOI or is waited for the statement of TOI.In the third state 32, receiver is idle.In the 5th state 34, received the object of all statements fully.Can in as first state 30 of error condition or in the four condition 33 of having indicated session to accomplish, leave speech channel.
There are many incidents can trigger transformation from wait state 31.Comprise one or more new TOI when receiving, just before still unstated TOI, FDT the time trigger first and change 36.This has triggered to each new TOI setting and has started fragment waiting timer t1.Wait state 31 is gone in this transformation 36.In response to receiving that this incident of grouping that is used for following TOI triggers second and changes 37, this TOI has effective fragment waiting timer t1.This response is the fragment waiting timer t1 that stops to be used for that TOI.This changes 37 and can be only when one or more effective fragment waiting timer t1 is still arranged, just takes place.This transformation 37 turns back to wait state 31.Through receiving that this incident of FDT that comprises the statement that is used for following TOI triggers the 3rd and changes 38, this TOI has effective table waiting timer t2.This changes 38 and can be only when one or more effective table waiting timer t2 is still arranged, just takes place.Changing the effective wait list t2 that stopped to be used for that TOI at 38 o'clock.The 3rd changes 38 goes to wait state 31.Through receiving that first of the TOI that is used for not being the FDT table this incident of dividing into groups triggers the 4th and changes 39.This has triggered and has been that TOI startup table waiting timer t2.Wait state 31 is gone in this transformation.
In response to receiving that this incident of grouping that is used for following TOI carries out from wait state 31 to idle condition 32 transformation, this TIO has effective fragment waiting timer t1.Stop to be used for the fragment waiting timer t1 of that TOI.Through receiving that this incident of FDT that comprises the statement that is used for following TOI triggers the 6th and changes 41, this TOI has effective table waiting timer t2.The table waiting timer that is used for that TOI stops owing to this changes 41.The 6th to change 41 be from wait state 31 to idle condition 32.
When in idle condition 32, but three conversion of energies are arranged.In response to what receive this incident of FDT of comprising one or more new TOI is first to change 42.This has triggered to each new TOI setting and has started fragment waiting timer t1.This transformation is from idle condition 32 to wait state 31.In response to receive the TOI that is used for not being the FDT table first divide into groups and take place from idle condition 32 to wait state 31 another change 43.This has triggered and has been that TOI startup table waiting timer t2.The 3rd transformation is to be converted to object accepting state 34 from idle condition 32.This transformation is labeled as 44 in the drawings.This changes 44 and when receiving last omission file fragment, takes place.This has triggered resets and startup object waiting timer t3.
When in TO accepting state 34, three kinds of transformations are possible.The first transformation 45A goes to wait state 31 and when receiving the FDT that comprises one or more new TOI, takes place.This has triggered to each new TOI setting and has started fragment waiting timer t1.Alternatively, this transformation 45A can cause object waiting timer t3 to stop.Second changes 45B goes to wait state 31.This changes 45B this TOI all without proper notices still in any FDT instance of receiving up to now takes place when receiving the grouping with following TOI.Change 45B and triggered new TOI setting and startup table waiting timer t2 for receiving.Alternatively, this transformation 45B possibly cause object waiting timer t3 to stop.The 3rd transformation 46 is the transformations from TO accepting state 34 to session completion status 33.This changes 46 and when object waiting timer t3 expires, takes place.
30 transformation takes place when the fragment waiting timer t1 that is used for any TOI or any timer of showing waiting timer t2 expire from wait state 31 to error condition.This transformation is labeled as 47 in the drawings.Take place when receiving last omission file fragment from the transformation 48 of wait state 31 to TO accepting state 34.This replacement and startup object waiting timer t3.
To optional state machine 49 be described with reference to Fig. 7 now.In this state machine, wait state 50 relates to this state of statement of waiting for TOI or TOI.Session unfinished state 51 is provided.Be converted to this state 51 through changing 52 from wait state 50, this transformation expires in response to object waiting timer t3 and takes place.This does not only just take place when receiving the object of one or more statements as yet.In response to expiring, any fragment waiting timer t1 that is used for any TOI or any table waiting timer t2 carry out from wait state 50 to error condition 54 transformation 53.Also there are idle condition 55 and session completion status 56.
Carry out transformation 57 in response to receiving this incident of FDT that comprises new TOI (TOI that had not promptly before stated) from wait state 50 to itself.The action that produces owing to this transformation 57 is to start and fragment waiting timer t1 and replacement object waiting timer t3 be set for each the new TOI that in FDT, states.Take place in response to receiving this incident of grouping that is used for following TOI from the wait state to the itself, second to change 58, this TOI has effective fragment waiting timer t1.This causes the fragment waiting timer t1 that is used for that TOI to stop.This only just takes place when one or more effective fragment waiting timer t1 is arranged.Take place in response to receiving this incident of FDT that comprises the statement that is used for following TOI the 3rd to change 59 from wait state 50 to itself, this TOI has effective table waiting timer t2.Such result is that the table waiting event t2 that is used for that TOI stops.This only just takes place when one or more effective table waiting timer t2 is arranged.First take place when dividing into groups the 4th to change 60 when what receive the TOI that is used for not being the FDT table from wait state 50 to itself.This causes the table waiting timer t2 that is used for that TOI to start.
When receiving the grouping that is used for following TOI, carry out from wait state 50 to idle condition 55 transformation 61, this TOI has effective fragment waiting timer t1.This causes the fragment waiting timer t1 that is used for that TOI to stop.55 another transformation 62 takes place when receiving the FDT that comprises the statement that is used for following TOI from wait state 50 to idle condition, and this TOI has effective table waiting timer t2.Such result is that the table waiting timer t2 that is used for that TOI stops.
Carry out from idle condition 55 to wait state 50 transformation 63 in response to receiving this incident of FDT that comprises one or more new TOI.Changed 63 o'clock carrying out this, be provided with and start fragment waiting timer t1 and the replacement object waiting timer t3 that is used for each new TOI.When what receive the TOI that is used for not being the FDT table first 50 another transformation 64 takes place from idle condition 55 to wait state when dividing into groups.This causes the table waiting timer t2 that is used for that TOI to stop.
In the time of in session unfinished state 51, five transformations are possible.At first, in response to this incident of grouping of receiving omission for the TOI of statement, and under this condition of the object of receiving all statements, go to the transformation 67 of session completion status 56.
In response to first this incident of dividing into groups of receiving the without proper notice TOI that is used for not being FDT, two optional transformations that constitute two different embodiment are possible.The first optional transformation is 50 transformation 68A from session unfinished state 51 to wait state.This changes 68A and causes the table waiting timer t2 that is used for this TOI to start.Thereby provide transformation 68A to allow to utilize the file that does not run into as yet to replenish the file set of having received up to now.Transformation 68B from session unfinished state 51 to itself is more strict alternatively, only allows to accomplish the file that has run into.This transformation does not cause any timer to change to some extent.
Take place the 4th in response to receiving this incident of FDT that comprises one or more new TOI and change 69A.This transformation 69A is 54 transformation from session unfinished state 51 to error condition.Also for session provides the time window that defines as follows, receiver can be accomplished fetching the uncompleted file of possibility within this time window when providing the file set in the session to be sure of without certain that change for this.This is favourable especially in following the application, this be applied in transmit leg when wanting to guarantee to have enough transmission to accomplish the fetching of session content for any receiver unserviceable bottom transmit.When the 4th timer t4 expires, take place from session unfinished state 51 to error condition 54 the 5th change 69B.As long as just reset when getting into session unfinished state 51 with start timer t4, as long as and just stop this timer when withdrawing from this state.Comprise that timer t4 is in order to ensure can ad infinitum not taking the session unfinished state.
Also can have from session unfinished state 51 to error condition 54 other change (not shown).
Optional state machine 70 has been shown in Fig. 8.State machine 70 comprises wait state 71.In this pending state, state machine 70 is waiting for that TOI perhaps waits for the statement of TOI.Other state in the state machine 70 is error condition 72, idle condition 73 and session completion status 74.
When in wait state 71, state machine 70 can experience the transformation 75 of getting back to wait state 71.In response to receiving that this incident of FDT that comprises one or more new TOI changes 75.This transformation 75 has triggered to each new TOI setting and has started fragment waiting timer t1.It has also triggered replacement object waiting timer t3.Another transformation 76 from wait state 71 to itself takes place when receiving the grouping that is used for following TOI, and this TOI has effective fragment waiting timer t1.This has caused the fragment waiting timer that stops to be used for that TOI.This only just takes place when one or more effective waiting timer t1 is arranged.The 3rd transformation 78 from wait state 71 to itself takes place when receiving the FDT that comprises the statement that is used for following TOI, and this TOI has effective table waiting timer t2.This only just takes place when one or more effective table waiting timer t2 is arranged.The table waiting timer t2 of each TOI that is used for comprising at the FDT that receives is stopped.First take place when dividing into groups the 4th to change 79 when what receive the TOI that is used for not being the FDT table from wait state 71 to itself.This has triggered and has been that TOI startup table waiting timer t2.
If in wait state 71, by receiving that this incident of grouping that is used for following TOI triggers the transformation 80 of going to idle condition 73, this TOI has effective fragment waiting timer t1.Change 80 and triggered the fragment waiting timer that stops to be used for that TOI.73 another transformation 81 takes place in response to receiving the FDT that comprises the statement that is used for following TOI from wait state 71 to idle condition, and this TOI has effective table waiting timer t2.The table waiting timer t2 that is used for that TOI is stopped.
When in idle condition 73, in response to receiving that the FDT that comprises one or more new TOI goes to the transformation of wait state 71.This causes to each new TOI setting and starts fragment waiting timer t1 and replacement object waiting timer t3.When what receive the TOI that is used for not being the FDT table first 71 another transformation 83 takes place from idle condition 73 to wait state when dividing into groups.This causes and is that TOI startup table waiting timer t2.
If state machine 70 in wait state 71 and also object waiting timer t3 expire, then go to the transformation 84 of error condition 72.This only just takes place when the object of unreceived one or more statements is still arranged.Expire if in wait state 51, be used for any fragment waiting timer t1 or any table waiting timer t2 of any TOI, then go to the transformation 85 of error condition 72.
When in idle condition 73 and when object waiting timer t3 expires, go to the transformation 86 of session completion status 74.The condition of this point is to have received the object of being stated.The object of one or more statements is not received as yet if object waiting timer t3 expires, and then replaces the transformation 87 of going to error condition 72.
Fragment stand-by period, table stand-by period and object waiting event parameter can send to receiver 19 with signal aloft.The parameter that use is sent with signal is why favourable to be that promptly the file broadcasting equipment can be revised parameter according to session content because it provides the optimization by server driven.Signal sends can use any suitable mode to take place.Some examples are described below.
Can be with signal transmission parameter in LCT (hierarchical coding transmission) extension header.For example, can within the LCT of single variable-length expansion, send all parameters with signal.Here, this LCT extension header can comprise following field: HET (header extension type) successively; HEL (header extension length); Fragment stand-by period parameter; Table stand-by period parameter; And object stand-by period parameter.The order of field is unimportant.
Can in the corresponding LCT header extension of regular length, send each parameter alternatively with signal.For example, three header extension that comprise HET field and corresponding time parameter field separately can be arranged.
Any combination that can use these two options is alternatively for example used the header extension of a regular length and the header extension of two variable-lengths with signal transmission parameter.
Can replace and use the FDT extended field to realize with signal transmission parameter as the one or more attributes in the FDT instance.For FLUTE, extended field can be as follows:
<xs:attribute?name＝″tablc_wait″
type＝″xs:unsignedLong″use＝″optional″/>
<xs:attribute?name＝″fragment_wait″
type＝″xs:unsigncdLong″use＝″optional″/>
<xs:attribute?name＝″new_object″
type＝″xs:unsignedLong″use＝″optional″/>
For example, the instance of this point can be:
<Pxml?vcrsion＝″1.0″encoding＝″UTF-8″?>
<FDT-Instance?xmlns:xsi＝″http:/>/www.w3.org/2001/XMLSchema-instancc″
xmlns:fl＝″http://www.examplc.com/flute″
xsi:schcmaLocation＝″http://www.cxample.com/flutc-fdt.xsd″
Expircs＝″2890842807″
table_wait＝″100″
fragment_wait＝″50″
new_obiect＝″200″>
<File
Content-Location＝″www.example.com/menu/tracklist.html″
TOI＝″1″
Content-Type＝″text/html″/>
<File
Content-Location＝″www.example.com/tracks/trackl.mp3″
TOI＝″2″
Content-Length＝″6100″
Content-Type＝″audio/mp3″
Content-Encoding＝″gzip″
Content-MD5＝″Eth76GlkJU45sghK″
Some-Private-Extension-Tag＝″abc123″/>
</FDT-Instancc>
Can replace parameter is sent with signal as the extension header of any other protocol level such as L2, IP, UDP, TCP or RTP.
For example can replace and in (weak point) file, carry parameter through TO.Any suitable form such as XML be can use, but any free text or data file also maybe be used.File as an example is following:
<start-of-file>
table_wait＝100；fragment_wait＝200；new_object＝300
<end-of-file>
Can outside band, send this parameter alternatively with signal.An example of this point has used SDP (Session Description Protocol) description field.Field as an example is following:
a＝fragment_wait:100
a＝table_wait:200
a＝new_object:300
Alternatively:
a＝fragment_wait:100；table?wait:200；new_object300
Above-mentioned field can be the parameter of session level or media-level.
The parameter of outside band, sending can be fetched, perhaps this parameter can be on independent channel, broadcasted with signal.
Can replace parameter is embedded in the envelope, for example:
<file-envclope
table_wait＝100
fragment_wait＝200
new_object＝300
<file-body
...the?actual?file?data...
</>file-body
</>filc-envelope
Can one or more parameters be installed in the receiver in advance, and other parameter can use any suitable mode to send with signal.This can reduce signal and send expense when one or more parameters are immutable, but allows variable element to be communicated to receiver.
Many other remodeling and the distortion of said system are possible.For example, although combined mobile telecommunication handset particularly mobile phone the present invention has been described, the present invention can be applicable to can be used for being received in other device of the file in the delivery session.Transmission can be through transmission aerial, that pass through DVB or other digital system.It is perhaps to be connected to fixed network through phone that this transmission can replace, and for example is connected to the transmission of other wired connection of PC or server computer or other device through the internet multicast.
Though in conjunction with the IPDC on the DVB-H embodiment has been described, the present invention can be applied to can to support one to one divide into groups any system of transmitting of (clean culture), one-to-many (broadcasting) or multi-to-multi (multicast).Equally, the carrying of communication system can be originally unidirectional (such as DVB-T/S/C/H, DAB) or two-way (such as GPRS, UMTS, MBMS, BCMCS, WLAN etc.).Packet can be that IPv4 or IPv6 divide into groups, but the present invention and be not limited to these packet types.
Claims (26)
1. receiver module that is used for being received in the data that file delivery session transmits, said module comprises the one or more timers in the following timer:
A) fragment waiting timer is set to receive the statement of quoting one or more objects and be activated in response to said receiver module;
B) new object waiting timer is set to receive all objects in one or more objects of in the statement of being received by said receiver module, quoting and be activated in response to detecting said receiver module; And
C) table waiting timer is set to receive all unreferenced object in any statement of receiving and be activated in response to said receiver module;
Said receiver module is set to leave said file delivery session in response to detecting expiring of any timer in said one or more timer.
2. receiver module as claimed in claim 1, wherein said fragment waiting timer are set to receive the part at least of at least one object in said one or more object and be cancelled in response to said receiver module.
3. receiver module as claimed in claim 2; Comprise a plurality of fragment waiting timers; Different objects in each fragment waiting timer and the said object of in said statement, quoting are relevant, and are set to receive the part at least of related object and be cancelled in response to said receiver module.
4. receiver module as claimed in claim 1, wherein said new object waiting timer are set to receive another different statement and be cancelled in response to said receiver module.
5. receiver module as claimed in claim 1, wherein said table waiting timer are set to receive the another different statement of having quoted object all unreferenced in any statement of before having received and be cancelled in response to said receiver module.
6. receiver module as claimed in claim 5; Comprise a plurality of table waiting timers; Each table waiting timer with received by said receiver module and in any statement of receiving all unreferenced different objects relevant, each is shown waiting timer and is set to receive the said statement of quoting related object and be cancelled in response to said receiver module.
7. receiver module as claimed in claim 1, wherein each timer is set to have the duration of being confirmed by corresponding timer parameter.
8. receiver module as claimed in claim 7, wherein one or more timer parameters for good and all are stored in the said receiver module.
9. receiver module as claimed in claim 7, wherein one or more timer parameters are stored in the said receiver module with renewable mode.
10. receiver module as claimed in claim 7, wherein said receiver module are set to the part of one or more timer parameters as the signal that receives through communication network received.
11. receiver module as claimed in claim 10, wherein one or more timer parameters are as the part of packet and receive.
12. receiver module as claimed in claim 1, wherein said receiver module is set to receive the grouping that comprises object and statement.
13. receiver module as claimed in claim 12, wherein said grouping comprises Internet protocol packets.
14. receiver module as claimed in claim 1, wherein said receiver module is set to receive the grouping that comprises object, statement and one or more timer parameters.
15. receiver module as claimed in claim 14, wherein said grouping comprises Internet protocol packets.
16. receiver module as claimed in claim 1; Wherein said receiver module is set to definite tolerance that file delivery session is received integrality in response to timer expires; Should measure with threshold value and do comparison, and based on said closer like leaving said session immediately or leaving said session in effective time after the section.
17. receiver module as claimed in claim 16, section had and equated the perhaps shorter duration with the expiration time of the shortest timer half the wherein said effective time.
18. receiver module as claimed in claim 1; Wherein said receiver module is set to estimate in response to timer expires the time that the reception expection of said file delivery session is accomplished; Should the time and threshold value do comparison, and based on said closer like leaving said session immediately or leaving said session in effective time after the section.
19. a portable, hand-held device comprises receiver module as claimed in claim 1.
20. a method that receives file delivery session, the one or more steps in said method comprising the steps of:
A) start the fragment waiting timer in response to receiving the statement of quoting one or more objects;
B) receive all objects in one or more objects of in the statement of receiving, quoting and start new object waiting timer in response to detecting; And
C) the startup table waiting timer in response to receiving all unreferenced object in any statement of receiving;
Said method also comprises leaves said file delivery session in response to detecting expiring of any said timer.
21. also comprising in response to the part at least of receiving at least one object in said one or more object, method as claimed in claim 20, said method cancel said fragment waiting timer.
22. also comprising in response to receiving another statement, method as claimed in claim 20, said method cancel said new object waiting timer.
23. also comprising in response to receiving the another statement of having quoted object all unreferenced in any statement of before having received, method as claimed in claim 20, said method cancel said table waiting timer.
24. a network node comprises:
Be used for the device of following one or more parameters being provided to file delivery session:
Fragment waiting timer parameter, this parameter with receiving the file delivery table and receiving that the maximum allowed time between at least the first fragment of the object of sending table according to this document is relevant,
New object waiting timer parameter, this parameter with at all objects of receiving a file delivery table and receive that the maximum allowed time that different files sends between the table is relevant, and
File delivery table waiting timer parameter, this parameter with receiving the object that in present being seen file delivery table, do not have statement and receiving that the maximum allowed time between the file delivery table of stating this unstated object is relevant,
Wherein said one or more timer parameter is used by receiver.
25. a reflector comprises:
Be used for to file delivery session the device of one or more parameters below the emission:
Fragment waiting timer parameter, this parameter with receiving the file delivery table and receiving that the maximum allowed time between at least the first fragment of the object of sending table according to this document is relevant,
New object waiting timer parameter, this parameter with at all objects of receiving a file delivery table and receive that the maximum allowed time that different files sends between the table is relevant, and
File delivery table waiting timer parameter, this parameter with receiving the object that in present being seen file delivery table, do not have statement and receiving that the maximum allowed time between the file delivery table of stating this unstated object is relevant,
Wherein said one or more timer parameter is used by receiver.
26. a system comprises reflector and receiver, wherein said reflector comprises:
Be used for to file delivery session the device of one or more parameters below the emission:
Fragment waiting timer parameter, this parameter with receiving the file delivery table and receiving that the maximum allowed time between at least the first fragment of the object of sending table according to this document is relevant,
New object waiting timer parameter, this parameter with at all objects of receiving a file delivery table and receive that the maximum allowed time that different files sends between the table is relevant, and
File delivery table waiting timer parameter, this parameter with receiving the object that in present being seen file delivery table, do not have statement and receiving that the maximum allowed time between the file delivery table of stating this unstated object is relevant,
Said receiver comprises receiver module as claimed in claim 1.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0414334A GB2415581A (en) | 2004-06-25 | 2004-06-25 | Reception of file delivery sessions |
| GB0414334.3 | 2004-06-25 | ||
| GBGB0418484.2A GB0418484D0 (en) | 2004-06-25 | 2004-08-18 | File delivery session handling |
| GB0418484.2 | 2004-08-18 | ||
| PCT/IB2005/051921 WO2006000936A1 (en) | 2004-06-25 | 2005-06-10 | File delivery session handling |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1973514A CN1973514A (en) | 2007-05-30 |
| CN1973514B true CN1973514B (en) | 2012-09-05 |
Family
ID=32800240
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200580020889.9A Expired - Fee Related CN1973514B (en) | 2004-06-25 | 2005-06-10 | Module and method for file delivery session handling |
Country Status (7)
| Country | Link |
|---|---|
| CN (1) | CN1973514B (en) |
| AT (1) | ATE525841T1 (en) |
| ES (1) | ES2369699T3 (en) |
| GB (2) | GB2415581A (en) |
| HK (1) | HK1102883A1 (en) |
| RU (1) | RU2388164C2 (en) |
| ZA (1) | ZA200610733B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101682435B (en) * | 2007-06-01 | 2015-08-05 | 汤姆森特许公司 | For performing the apparatus and method of the power management in receiver |
| WO2016060638A1 (en) * | 2014-10-13 | 2016-04-21 | Avery Dennison Retail Information Services, Llc | Utility timers in a food freshness printer |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1110443A (en) * | 1993-10-19 | 1995-10-18 | 休斯航空公司 | Method and apparatus for confirming delivery of files in a file broadcast system |
| CN1244999A (en) * | 1996-11-12 | 2000-02-16 | 艾利森电话股份有限公司 | Channel resource management within a digital mobile communication network |
| CN1052579C (en) * | 1996-06-04 | 2000-05-17 | 彭崇恩 | Mfg. of rechargeable corpuscular accumulator |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7231404B2 (en) * | 2003-01-31 | 2007-06-12 | Nokia Corporation | Datacast file transmission with meta-data retention |
-
2004
- 2004-06-25 GB GB0414334A patent/GB2415581A/en not_active Withdrawn
- 2004-08-18 GB GBGB0418484.2A patent/GB0418484D0/en not_active Ceased
-
2005
- 2005-06-10 RU RU2006144284/09A patent/RU2388164C2/en active
- 2005-06-10 CN CN200580020889.9A patent/CN1973514B/en not_active Expired - Fee Related
- 2005-06-10 ES ES05747365T patent/ES2369699T3/en active Active
- 2005-06-10 AT AT05747365T patent/ATE525841T1/en not_active IP Right Cessation
-
2006
- 2006-12-20 ZA ZA200610733A patent/ZA200610733B/en unknown
-
2007
- 2007-10-18 HK HK07111312.1A patent/HK1102883A1/en not_active IP Right Cessation
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1110443A (en) * | 1993-10-19 | 1995-10-18 | 休斯航空公司 | Method and apparatus for confirming delivery of files in a file broadcast system |
| CN1052579C (en) * | 1996-06-04 | 2000-05-17 | 彭崇恩 | Mfg. of rechargeable corpuscular accumulator |
| CN1244999A (en) * | 1996-11-12 | 2000-02-16 | 艾利森电话股份有限公司 | Channel resource management within a digital mobile communication network |
Also Published As
| Publication number | Publication date |
|---|---|
| GB0414334D0 (en) | 2004-07-28 |
| GB0418484D0 (en) | 2004-09-22 |
| CN1973514A (en) | 2007-05-30 |
| RU2006144284A (en) | 2008-07-27 |
| ES2369699T3 (en) | 2011-12-05 |
| ZA200610733B (en) | 2008-06-25 |
| ATE525841T1 (en) | 2011-10-15 |
| GB2415581A (en) | 2005-12-28 |
| RU2388164C2 (en) | 2010-04-27 |
| HK1102883A1 (en) | 2007-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100876315B1 (en) | File Delivery Session Handling | |
| CN100579129C (en) | Grouping of session objects | |
| US9485044B2 (en) | Method and apparatus of announcing sessions transmitted through a network | |
| JP5485134B2 (en) | Robust file cast for mobile TV | |
| KR101157846B1 (en) | Scheduled downloads: enabling background processes to receive broadcast data | |
| US20070300265A1 (en) | User behavior adapted electronic service guide update | |
| WO2012125376A2 (en) | System and apparatus for using multichannel file delivery over unidirectional transport ("flute') protocol for delivering different classes of files in a broadcast network | |
| US20080101317A1 (en) | System and method for providing advanced session control of a unicast session | |
| US7827580B2 (en) | Dynamically adjustable electronic service guide | |
| CN101449496A (en) | System, method, mobile terminal and computer program product for providing push-to-talk chat in interactive mobile TV | |
| WO2007029091A1 (en) | Optimized broadcast of esg with simple fragment management scheme | |
| CN1973514B (en) | Module and method for file delivery session handling | |
| CN101536501B (en) | A method and receiving unit for fast change of services | |
| KR100902855B1 (en) | Grouping of session objects | |
| CN101371517B (en) | Enhanced digital video broadcast idle mode in wireless communication networks | |
| KR100531870B1 (en) | Broadcasting message service method | |
| KR100641892B1 (en) | Broadcasting reservation server of providing broadcasting reservation service and method for operating the broadcasting reservation server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1102883 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160112 Address after: Espoo, Finland Patentee after: NOKIA TECHNOLOGIES OY Address before: Espoo, Finland Patentee before: NOKIA Corp. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120905 |