WO2016101213A1 - 一种文件修复的方法、相关装置及系统 - Google Patents

一种文件修复的方法、相关装置及系统 Download PDF

Info

Publication number
WO2016101213A1
WO2016101213A1 PCT/CN2014/094963 CN2014094963W WO2016101213A1 WO 2016101213 A1 WO2016101213 A1 WO 2016101213A1 CN 2014094963 W CN2014094963 W CN 2014094963W WO 2016101213 A1 WO2016101213 A1 WO 2016101213A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
file data
data
repair
flute
Prior art date
Application number
PCT/CN2014/094963
Other languages
English (en)
French (fr)
Inventor
曹龙雨
余勇
李志明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201480035411.2A priority Critical patent/CN106063190B/zh
Priority to EP14908781.9A priority patent/EP3226466A4/en
Priority to PCT/CN2014/094963 priority patent/WO2016101213A1/zh
Publication of WO2016101213A1 publication Critical patent/WO2016101213A1/zh
Priority to US15/631,343 priority patent/US10516502B2/en

Links

Images

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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/637—Control signals issued by the client directed to the server or network components
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast

Definitions

  • Embodiments of the present invention relate to communication technologies, and in particular, to a file repair method, related device, and system.
  • Multimedia Broadcast/Multicast Service is a technology that transfers data from a data source to multiple receiving ends (such as user equipment) by sharing network resources, and can provide multimedia services while Efficient use of network resources to achieve higher rates of multimedia service broadcast and multicast.
  • the enhanced multimedia broadcast/multicast service (evolved MBMS, eMBMS) technology (also known as LTE broadcast) is an enhanced broadcast multicast function based on LTE technology developed on the basis of MBMS technology.
  • the eMBMS technology has made significant improvements in terms of logical architecture, transmission mode, and channel structure to support larger bandwidths and provide users with a better experience.
  • the eMBMS technology uses a point-to-multipoint transmission method of the File DeLivery over Unidirectional Transport (FLUTE) protocol defined by the Internet Task Force.
  • FLUTE File DeLivery over Unidirectional Transport
  • the point-to-multipoint transmission mode of the FLUTE protocol converts the content to be transmitted into multiple FLUTE files, and processes each file to be processed into a FLUTE packet during transmission, and transmits the FLUTE packet to multiple receiving ends through the Internet.
  • the above-mentioned service for transmitting MBMS user data on the FLUTE channel through the FLUTE communication protocol within a specified time interval may be referred to as a FLUTE session. Files corresponding to data of the same service will only be sent to multiple receivers through one FLUTE session. If the data is lost or damaged during the transmission of the FLUTE packet, the user equipment (UE) at the receiving end can request the repair data from the file repair server by using the Uniform Resource Identifier (or URI) of the file.
  • UE Uniform Resource Identifier
  • multiple FLUTE session features are proposed in the 3GPP R12 standard, that is, data of the same service that the UE is interested in/interested can be transmitted to the user in multiple FLUTE sessions, and the user can freely choose which The FLUTE session receives the FLUTE packet corresponding to the service.
  • the data loss or damage is caused.
  • the solution provided by the prior art can only be effective if the same service can only be sent to the receiving end through a FLUTE session, if at most The loss or damage of data caused by the FLUTE session feature will not be able to repair the data.
  • the embodiment of the invention provides a file repairing method, related device and system, which can perform file repairing on data loss or data corruption caused by multiple FLUTE session characteristics.
  • an embodiment of the present invention provides a method for file repair, the method comprising:
  • the broadcast multicast service center receives a file repair request message sent by the user equipment, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE session for transmitting the file data.
  • Transmission session identifier a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE session for transmitting the file data.
  • the broadcast multicast service center sends the repair data of the file data to the user equipment.
  • the repair data of the file data is data of at least one of the following: a FLUTE file corresponding to the file data, an encoded symbol of the file data, according to The coded symbols of the file data are re-encoded to obtain new code symbols and bytes corresponding to the file data.
  • the file repair request message further includes a source block number SBN of the file data, the file The coded symbol of the data identifies at least one of a range of bytes of the ESI and the file data;
  • the file repair request message is a symbol based file repair request message or a byte range based file repair request message.
  • the broadcast multicast service center determines, according to the transport session identifier and a URI corresponding to the file data, the repair data of the file data, including:
  • the broadcast multicast service center obtains a FLUTE file corresponding to the file data according to the transport session identifier and a URI corresponding to the file data, and the repair data of the file data is a FLUTE corresponding to the file data.
  • Document or,
  • the repair data of the file data is an encoded symbol of the file data
  • the broadcast multicast service center is configured according to the transmission session identifier and Determining, by the URI corresponding to the file data, the repair data of the file data, the broadcast multicast service center determining, according to the transport session identifier, a FLUTE session for transmitting the file data; the broadcast multicast service center And determining repair data of the file data according to the FLUTE session for transmitting the file data and a URI corresponding to the file data.
  • an embodiment of the present invention provides a file repair method, including:
  • the user equipment sends a file repair request message to the broadcast multicast service center, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired and a transmission of the one-way delivery file transmission FLUTE session for transmitting the file data.
  • Session identifier identifier
  • the user equipment receives repair data of the file data returned by the broadcast multicast service center according to the file repair request message.
  • the method further includes: the user equipment acquiring the transmission session identifier.
  • the repair data of the file data is data of at least one of the following types: corresponding to the file data a FLUTE file, an encoding symbol of the file data, a new encoding symbol obtained by re-encoding according to an encoding symbol of the file data, and a byte corresponding to the file data.
  • an embodiment of the present invention provides a broadcast multicast service center, including:
  • a receiving unit configured to receive a file repair request message sent by the user equipment, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE session for transmitting the file data Transmission session identifier;
  • a processing unit configured to determine, according to the transport session identifier and a URI corresponding to the file data, repair data of the file data
  • a sending unit configured to send the repair data of the file data to the user equipment.
  • the repair data of the file data is data of at least one of the following: a FLUTE file corresponding to the file data, an encoded symbol of the file data, according to The coded symbols of the file data are re-encoded to obtain new code symbols and bytes corresponding to the file data.
  • the file repair request message further includes a source block number SBN of the file data, the file The coded symbol of the data identifies at least one of a range of bytes of the ESI and the file data;
  • the file repair request message is a symbol based file repair request message or a byte range based file repair request message.
  • the processing unit is specifically configured to: according to the transmission session identifier and the file data Corresponding URI, obtaining a FLUTE file corresponding to the file data, where the repair data of the file data is a FLUTE file corresponding to the file data; or
  • the processing unit is configured to determine, according to an SBN of the file data or an ESI of the file data, a transport session identifier, and a URI corresponding to the file data, an encoded symbol of the file data, where the file data is Repair data is an encoded symbol of the file data; or,
  • the processing unit is configured to determine, according to the SBN of the file data or the ESI of the file data, the transmission session identifier, and a URI corresponding to the file data, an encoding symbol of the file data, according to the file.
  • the coded symbols of the data are re-encoded to obtain a new coded symbol, and the repaired data of the file data is an encoded symbol of the file data; or
  • the processing unit is configured to determine, according to the transport session identifier, a URI corresponding to the file data, and a byte range of the file data, a byte corresponding to the file data, and repair data of the file data.
  • the byte corresponding to the file data is configured to determine, according to the transport session identifier, a URI corresponding to the file data, and a byte range of the file data, a byte corresponding to the file data, and repair data of the file data. The byte corresponding to the file data.
  • the processing unit is specifically configured to use, according to the transmission session identifier, Determining a FLUTE session for transmitting the file data; the broadcast multicast service center determining repair data of the file data according to the FLUTE session for transmitting the file data and a URI corresponding to the file data.
  • an embodiment of the present invention provides a user equipment, including:
  • a sending unit configured to send a file repair request message to the broadcast multicast service center, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE for transmitting the file data
  • the transport session identifier of the session
  • a receiving unit configured to receive repair data of the file data returned by the broadcast multicast service center according to the file repair request message.
  • an embodiment of the present invention provides a broadcast multicast service center, including a bus, to And a processor, a memory, a transmitter, and a receiver coupled to the bus; the memory for storing computer execution instructions, the computer execution instructions being configured to be executed by the processor;
  • the receiver is configured to receive a file repair request message sent by the user equipment, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE that transmits the file data.
  • the transport session identifier of the session includes a uniform resource identifier URI corresponding to the file data to be repaired, and a one-way transfer file transmission FLUTE that transmits the file data.
  • the processor is configured to determine, according to the transport session identifier and a URI corresponding to the file data, repair data of the file data;
  • the transmitter is further configured to send repair data of the file data to the user equipment.
  • the specific information and implementation manner of the file repair request and the data repair data of the file may be specifically referred to any possible implementation manner of the third aspect; how the processor determines the file For details of the repair data of the data, reference may be made to any possible implementation of the third aspect.
  • an embodiment of the present invention provides a user equipment, including a bus, and a processor, a memory, a transmitter, and a receiver connected to the bus; the memory is configured to store a computer to execute an instruction, where the computer executes The instructions are configured to be executed by the processor;
  • the transmitter is configured to send a file repair request message to the broadcast multicast service center, where the file repair request message includes a uniform resource identifier URI corresponding to the file data to be repaired and a one-way transfer file that transmits the file data. Transmit the transport session identifier of the FLUTE session;
  • the receiver is configured to receive repair data of the file data returned by the broadcast multicast service center according to the file repair request message.
  • the processing unit is further configured to acquire the transport session identifier.
  • the specific information and implementation manners of the file repair request and the data repair data of the file may be specifically referred to any possible implementation of the fourth aspect. the way.
  • an embodiment of the present invention provides a computer readable medium, including a computer
  • the instructions When the instructions are executed by a processor of a computer to execute the instructions, the computer performs the method of file repair described in the first aspect or the method of file repair described in any of the possible implementations of the first aspect.
  • an embodiment of the present invention provides a computer readable medium, including a computer executing instruction, when the processor of the computer executes the computer to execute an instruction, where the computer performs the file repairing method according to the second aspect Or the method of file repair described in any of the possible implementations of the second aspect.
  • the embodiment of the present invention provides a file repair method.
  • the broadcast multicast service center obtains a URI corresponding to the file data to be repaired and a FLUTE session for transmitting the file data by receiving a file repair request message sent by the user equipment. Transmitting the session identifier, so that the broadcast multicast service center can use the transport session identifier to sense which FLUTE session the file data is transmitted through, and then use the URI corresponding to the file data to obtain the repair data of the file data, and implement the The file is fixed, which solves the problem that the prior art cannot handle file repair under multiple FLUTE session characteristics.
  • FIG. 1 is a schematic diagram of an eMBMS logical architecture in an LTE network
  • FIG. 2 is a schematic diagram of a FLUTE file
  • FIG. 3 is a flowchart of a method for file repair according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of still another method for file repair according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of still another method for file repair according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a broadcast multicast service center according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a user equipment according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an apparatus for file repair according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a file repair system according to an embodiment of the present invention.
  • the embodiment of the invention provides a file repairing method, a related device and a system, which can perform file repairing on data loss or data corruption caused by multiple FLUTE session characteristics.
  • FIG. 1 is a schematic diagram of an eMBMS logical architecture in an LTE network, which mainly includes: a broadcast multicast service center (BM-SC), an MBMS gateway (MBMS-GW), a mobility management network element entity (MME), and a multi-cell/multicast.
  • BM-SC broadcast multicast service center
  • MBMS-GW MBMS gateway
  • MME mobility management network element entity
  • MCE Coordination Function Entity
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network E-UTRAN.
  • the MCE is mainly used for service scheduling, that is, selecting appropriate resources (including parameters such as frequency and time) for multicast/multicast single frequency network (BSFN) transmission;
  • MME is the control plane network.
  • the meta-node is mainly used for session control;
  • the MBMS-GW acts as a node between the BM-SC and the E-UTRAN, and is the access gateway of the network, and is responsible for processing user data-related messages and session-related signaling;
  • BM- The SC belongs to the service layer network element and is the entry of the content provider. It provides aggregation and transmission of services, authorization of users, establishment and initiation of service bearers, and initiation of session control.
  • each file has its corresponding URI, and the URI can uniquely identify the file or data. source.
  • Each file is split into multiple objects before being transmitted, and each object is identified by TOI.
  • each object is further divided into at least one source block, each source block being identified by a source block number (SBN).
  • SBN source block number
  • Each source block is further divided into source symbols of the same size, and the BM-SC obtains a parity symbol of the source symbol by Forward Error Correction (FEC) algorithm.
  • FEC Forward Error Correction
  • the BM-SC will enclose the source symbol and check code symbol belonging to the same file in the FLUTE package.
  • the FLUTE session channel is transmitted to the user equipment, and the file transfer is completed.
  • the source symbol and the check code symbol are collectively referred to as an encoding symbol, and the encoded symbol may be identified by an encoding symbol identifier (ESI).
  • ESE encoding symbol identifier
  • each object is further divided into at least one byte in units of bytes, and the BM-SC encapsulates the bytes belonging to the same file in the FLUTE packet through the FLUTE session channel. Give the user device.
  • the user equipment may request repair data from the BM-SC through the file repair request message, and the file repair request includes the URI of the file, so that the BM-SC You can use the URI of the file to retransmit the relevant file or part of the data of the related file.
  • the BM-SC cannot determine which FLUTE session the file to be repaired by the UE is transmitted, and cannot obtain the correct data.
  • the embodiment of the present invention provides a file repairing method, in which a user equipment can add a transport session identifier of a FLUTE session for transmitting file data to be repaired to a file repair request message, so that the BM-SC can sense the file to be repaired.
  • the data is transmitted through which FLUTE session, so that the BM-SC can obtain the repair data of the file data according to the information such as the transport session identifier, and implement the file repair, which solves the problem that the prior art cannot handle multiple FLUTE session characteristics.
  • the problem with the file fix in which a user equipment can add a transport session identifier of a FLUTE session for transmitting file data to be repaired to a file repair request message, so that the BM-SC can sense the file to be repaired.
  • the data is transmitted through which FLUTE session, so that the BM-SC can obtain the repair data of the file data according to the information such as the transport session identifier, and implement the file repair, which solves the problem that the prior art cannot handle multiple FLUTE session characteristics.
  • the BM-SC may also be a file repair server.
  • the file repair server appears as a sub-function of the Associated Delivery functions of the network element entity BM-SC.
  • an embodiment of the present invention provides a file repair method, which is convenient for understanding.
  • a detailed process of the user equipment and the BM-SC interacting with each other for file repair is provided.
  • the file repair method provided by the embodiment of the present invention may only perform part of the steps, or may be applied only to The user equipment is only applicable to the BM-SC, and the embodiment of the present invention is not limited herein.
  • the user equipment acquires a URI corresponding to the file data to be repaired and a transport session identifier (Transport Session Identifier) of the FLUTE session that transmits the file data.
  • Transport Session Identifier Transport Session Identifier
  • the BM-SC includes at least one server, which belongs to a logical function module of the BM-SC, and each server can provide at least one service for the user equipment, and the service provided by the same server.
  • the content has the same URI. Since the content of the service to be transmitted is converted into multiple FLUTE files before the content of the service is transmitted, the files corresponding to the content of the same service have the same URI.
  • the above URI can uniquely identify the file or data source, and thus can be referred to as a URI of a file, or a URI of a server. That is, the URI corresponding to the file data to be repaired may be the URI of the file corresponding to the file data to be repaired, or may be the URI of the server providing the file data to be repaired, and the present invention The embodiment is not limited herein.
  • the user equipment may save the transport session identifier of the FLUTE session transmitting the file, and under a plurality of FLUTE session characteristics, for a given IP source address There may be multiple FLUTE sessions, and the transport session identifier is used to uniquely identify a particular FLUTE session for the given IP source address.
  • the session identifier By transmitting the session identifier, a FLUTE session can be uniquely determined, such that the user device When it is determined that there is data loss or damage in the file, the transmission session identifier can be obtained, so that the BM-SC can sense which FLUTE session the data loss or corruption occurs.
  • S300 is an optional step.
  • the user equipment sends a file repair request message to the BM-SC, where the file repair request message includes a URI corresponding to the file data and a transport session identifier of the FLUTE session that transmits the file data.
  • the user equipment may use a Hypertext Transfer Protocol (HTTP) acquisition (GET) request to send the file repair request message to the BM-SC.
  • HTTP Hypertext Transfer Protocol
  • GET Hypertext Transfer Protocol acquisition
  • the user equipment when the user equipment is found to have lost or damaged file data, the user equipment not only sends the URI corresponding to the file data to the BM-SC, but also transmits the URI.
  • the transmission session identifier of the FLUTE session of the file data is sent to the BM-SC, so that the BM-SC can identify the FLUTE session for transmitting the file data, and further acquire the repair data of the file data, and complete the repair of the file.
  • the BM-SC receives the file repair request message sent by the user equipment, and determines the repair data of the file data according to the transport session identifier included in the file repair request message and the URI corresponding to the file data.
  • the repair data of the file data may be at least one of the following forms: a FLUTE file corresponding to the file data, an encoded symbol of the file data, and a re-encoding according to an encoded symbol of the file data. The new encoding symbol and the byte corresponding to the file data. Since the repair data of the file data contains all the information of the file data, the BM-SC implements repair of the file data.
  • the file repair request message may be a symbol-based file repair request message (Symbol-Based File Repair Request Message), or may be based on a word. Byte-Range-Based File Repair Request Message.
  • the symbol-based file repair request message may be applied to a scenario that needs to be repaired for some specific coded symbols, and the URI corresponding to the file data included in the symbol-based file repair request message may be jointly transmitted.
  • the postFileRepair element of the Associated Delivery procedure fragment is determined; and the byte range based file repair request message can be applied to the file Some or all of the bytes are used for file repair, and the URI corresponding to the file data included in the byte range-based file repair request message may be "Alternate" in the File Delivery Table (FDT). Elements such as -Content-Location-1" and "Alternate-Content-Location-2" are determined.
  • the file repair request message may include the file data in addition to the URI corresponding to the file data and the transport session identifier. SBN or ESI of the file data.
  • the file repair request message may only carry the URI of the file and the transport session identifier of the FLUTE session transmitting the file; if the request is to fix the unreceived in a particular file
  • the source repair block the file repair request message may include a URI of the specific file, a transport session identifier, and a range of the SBN, where the range of the SBN may be used to indicate the first lost source block to the last one.
  • the file repair request message may include a file URI, a transport session identifier, an SBN of the particular source block, and An ESI indicating/identifying the unreceived source symbol. Therefore, the BM-SC can acquire repair data such as a specific FLUTE file, an encoded symbol of the unreceived source block, or an encoded symbol of the unreceived source symbol according to the information included in the file repair request message.
  • the file repair request message may include the URI and the transport session identifier corresponding to the file data.
  • a file data byte range, the file data byte range being a byte range corresponding to the file data to be repaired.
  • the file repair request message may only contain the URI and the transport session identifier of the FLUTE session transmitting the file; if a specific source block is requested And the file repair request message may include a URI, a transport session identifier, and a byte range to be repaired, where the byte range may be used to indicate the specific source block; if the specific to be repaired is specific Some parts of the source block, the file repair request message is also The minimum ESI value for this part can be included. Therefore, the BM-SC can acquire repair data such as a specific FLUTE file or a byte corresponding to the unreceived source block according to the information included in the file repair request message.
  • the BM-SC sends a file repair response message to the user equipment, where the file repair response message includes repair data of the file data.
  • the BM-SC may return a file repair response message to the user equipment by using an HTTP response request, and the file repair response may include repair data of the file data, and implement file repair on the file data.
  • the file repair response message may be a character based file repair response message, or may be a byte range based file repair response message.
  • the file repair request message and the file repair response message of a specific MBMS service may be transmitted through the same TCP connection according to the HTTP protocol.
  • the method may specifically be as follows:
  • the BM-SC receives a file repair request message sent by the user equipment, where the file repair request message includes a URI corresponding to the file data to be repaired and a transport session identifier of the FLUTE session that transmits the file data.
  • the file repair request message further includes at least one of an SBN of the file data, an ESI of the file data, and a byte range of the file data, where the information may identify/indicate the file data.
  • the BM-SC determines repair data of the file data according to the transport session identifier and a URI corresponding to the file data.
  • the broadcast multicast service center obtains the number of files according to the transport session identifier and a URI corresponding to the file data.
  • the repair data of the file data is a FLUTE file corresponding to the file data; or
  • Decoding by the broadcast multicast service center, an encoding symbol of the file data according to an SBN of the file data or an ESI of the file data, a transmission session identifier, and a URI corresponding to the file data, where the file data is Repair data is an encoded symbol of the file data; or,
  • the broadcast multicast service center determines, according to the transport session identifier, a URI corresponding to the file data, and a byte range of the file data, a byte corresponding to the file data, and repair data of the file data.
  • the byte corresponding to the file data is a URI corresponding to the file data.
  • the repair data of the file data is data of at least one of the following: a FLUTE file corresponding to the file data, an encoded symbol of the file data, and a re-encoding according to an encoded symbol of the file data.
  • the obtained new code symbol and the byte corresponding to the file data Since the repair data of the file data includes all the information of the file data, the repair of the file data is realized, and the problem that the prior art cannot handle file repair under multiple FLUTE session characteristics is solved.
  • the BM-SC sends the repair data of the file data to the user equipment.
  • the repair data of the file data may be sent to the user equipment by using a file repair response message.
  • S303 For details, refer to S303.
  • the method for file repair described in FIG. 3 may specifically be as follows:
  • the user equipment sends a file repair request message to the broadcast multicast service center, where the file repair request message includes a URI corresponding to the file data to be repaired and the file data is transmitted.
  • the transport session ID of the FLUTE session is a file repair request message.
  • S502 The user equipment receives repair data of the file data returned by the broadcast multicast service center according to the file repair request message. For details, refer to the corresponding embodiment of FIG. 3.
  • the method may further include:
  • S500 The user equipment acquires the transport session identifier.
  • the embodiment of the present invention provides a broadcast multicast service center 60, as shown in FIG. 6, including a receiving unit 601, a processing unit 602, and a sending unit 603.
  • the receiving unit 601 is configured to receive a file repair request message sent by the user equipment, where the file repair request message includes a URI corresponding to the file data to be repaired and a transport session identifier of the FLUTE session that transmits the file data.
  • the file repair request message may further include at least one of an SBN of the file data, an ESI of the file data, and a byte range of the file data, where the information may identify/instruct the File data.
  • the processing unit 602 is configured to determine the repair data of the file data by using the transport session identifier and a URI corresponding to the file data. Specifically, the processing unit 602 may determine, according to the transport session identifier, a FLUTE session for transmitting the file data, and determine, according to the FLUTE session for transmitting the file data and a URI corresponding to the file data. The encoded symbol of the file data repairs the data. For example, the processing unit 602 may obtain a FLUTE file corresponding to the file data according to the transport session identifier and a URI corresponding to the file data, where the repair data of the file data is corresponding to the file data.
  • the processing unit 602 may determine, according to an SBN of the file data or an ESI of the file data, the transmission session identifier, and a URI corresponding to the file data, an encoding symbol of the file data,
  • the repair data of the file data is an encoded symbol of the file data; or the processing unit 602 may be configured according to an SBN of the file data or an ESI of the file data, the transport session identifier, and the file data.
  • Corresponding URI determining an encoding symbol of the file data, re-encoding according to the encoding symbol of the file data, obtaining a new encoding symbol, the file
  • the repair data of the data is an encoded symbol of the file data; or the processing unit 602 may determine the file according to the transport session identifier, a URI corresponding to the file data, and a byte range of the file data.
  • the byte corresponding to the data, and the repair data of the file data is a byte corresponding to the file data.
  • the repair data of the file data is data of at least one of the following: a FLUTE file corresponding to the file data, an encoded symbol of the file data, and a re-encoding according to an encoded symbol of the file data.
  • the sending unit 603 is configured to send the repair data of the file data to the user equipment. Specifically, the repair data of the file data may be sent to the user equipment by using a file repair response message.
  • the receiving unit 601 may receive the file repair request message sent by the user equipment, and obtain the URI corresponding to the file data to be repaired and the transmission session identifier of the FLUTE session that transmits the file data, so that the processing unit 602 is configured according to
  • the transmission session identifier and the URI corresponding to the file data may determine the repair data of the file data
  • the sending unit 603 may send the repair data of the file data to the user equipment, and implement the file.
  • the embodiment of the present invention provides a user equipment 70, as shown in FIG. 7, including a sending unit 701 and a receiving unit 702;
  • the sending unit 701 is configured to send a file repair request message to the BM-SC, where the file repair request message includes a URI corresponding to the file data to be repaired and a transport session identifier of the FLUTE session that transmits the file data.
  • the receiving unit 702 is configured to receive, by the BM-SC, the file repair request message according to the file
  • the repair data of the returned file data is data of at least one of the following: a FLUTE file corresponding to the file data, an encoded symbol of the file data, and a re-encoding according to an encoded symbol of the file data.
  • the obtained new code symbol and the byte corresponding to the file data Since the repair data of the file data includes all the information of the file data, the repair of the file data is realized, and the problem that the prior art cannot handle file repair under multiple FLUTE session characteristics is solved.
  • the user equipment 70 may further include an obtaining unit 703, configured to acquire the transport session identifier.
  • an obtaining unit 703 configured to acquire the transport session identifier.
  • the user equipment 70 may add a transport session identifier of a FLUTE session for transmitting file data to be repaired to the file repair request message, so that the BM-SC user equipment 70 can sense the file to be repaired.
  • the data is transmitted by which FLUTE session, so that the BM-SC can obtain the repair data of the file data according to the information such as the transport session identifier and return it to the user equipment 70, thereby realizing the repair of the file and solving the prior art.
  • the sending unit for sending a message may be implemented by using a transmitter or implemented by a transceiver, and the receiving unit for receiving a message may be implemented by using a receiver or transmitting and receiving.
  • the transmitter or the transceiver may be implemented by one physical entity, or may be implemented by multiple physical entities.
  • the transmitter and the transceiver may be implemented by one physical entity or multiple physical entities. This is not a limitation.
  • Other units, such as an acquisition unit or a processing unit may be implemented by one or more processors, which are not limited in the present invention.
  • FIG. 8 is an apparatus for file repair according to an embodiment of the present invention.
  • the device may include:
  • the processor 801, the memory 802, and the communication interface 805 are connected by a bus 804 and complete communication with each other.
  • Processor 801 may be a single core or multi-core central processing unit, or a particular integrated circuit, or one or more integrated circuits configured to implement embodiments of the present invention.
  • the memory 802 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.
  • Memory 802 is used by computer to execute instructions 803. Specifically, the program code may be included in the computer execution instruction 803.
  • the processor 801 runs the computer execution instruction 803, and may execute the method flow of the method for file repair described in the method embodiment corresponding to any one of FIG. 3 to FIG.
  • the device may be a broadcast multicast service center.
  • the device may be a user equipment.
  • the embodiment of the present invention provides a computer readable medium, including a computer executing instruction, when the processor of the computer executes the computer execution instruction, the computer executes the file described in the method embodiment corresponding to FIG. 3 or FIG. The method of repair.
  • the embodiment of the present invention provides a computer readable medium, including a computer executing instructions, when the processor of the computer executes the computer execution instruction, the computer executes the file described in the method embodiment corresponding to FIG. 3 or FIG. The method of repair.
  • a file repair system includes: a broadcast multicast service center 60 and a user equipment 70; and an action performed by each of the broadcast multicast service center 60 and the user equipment 70, and interaction between them.
  • a broadcast multicast service center 60 and a user equipment 70 includes: a broadcast multicast service center 60 and a user equipment 70; and an action performed by each of the broadcast multicast service center 60 and the user equipment 70, and interaction between them.
  • the LTE network mentioned in the present invention includes an LTE A network, and may subsequently have an LTE version.
  • aspects of the present invention, or possible implementations of various aspects may be embodied as a system, method, or computer program product. Therefore, the present invention Various aspects, or possible implementations of various aspects, may be in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, etc.), or a combination of software and hardware aspects, collectively referred to herein "Circuit,” “module,” or “system.” Furthermore, aspects of the invention, or possible implementations of various aspects, may take the form of a computer program product, which is a computer readable program code stored in a computer readable medium.
  • the computer readable medium can be a computer readable signal medium or a computer readable storage medium.
  • the computer readable storage medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing, such as random access memory (RAM), read only memory (ROM), Erase programmable read-only memory (EPROM or flash memory), optical fiber, portable read-only memory (CD-ROM).
  • the processor in the computer reads the computer readable program code stored in the computer readable medium such that the processor is capable of performing the various functional steps specified in each step of the flowchart, or a combination of steps; A device that functions as specified in each block, or combination of blocks.
  • the computer readable program code can execute entirely on the user's computer, partly on the user's computer, as a separate software package, partly on the user's computer and partly on the remote computer, or entirely on the remote computer or computer.
  • the functions noted in the various steps in the flowcharts or in the blocks in the block diagrams may not occur in the order noted. For example, two steps, or two blocks, shown in succession may be executed substantially concurrently or the blocks may be executed in the reverse order.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

在本发明实施例提供了一种文件修复的方法，广播多播业务中心接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识，根据所述传输会话标识，确定传输所述文件数据的FLUTE会话，根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的修复数据，实现了文件的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。

Description

一种文件修复的方法、相关装置及系统 技术领域
本发明实施例涉及通信技术，特别涉及一种文件修复的方法、相关装置及系统。
背景技术
多媒体广播/多播业务(Multimedia Broadcast/Multicast Service，MBMS)是一种通过共享网络资源，从一个数据源向多个接收端(如用户设备)传送数据的技术，能够在提供多媒体业务的同时能有效地利用网络资源，实现较高速率的多媒体业务广播和组播。而增强型多媒体广播/多播业务(evolved MBMS，eMBMS)技术(也被称为LTE广播)是在MBMS技术基础上发展的一种基于LTE技术的增强型广播组播功能。eMBMS技术在逻辑架构、传输方式和信道结构等方面进行了重大改进，能支持更大的带宽，为用户提供更好的体验。
eMBMS技术中使用了因特网工作任务组定义的单向传递文件传输(File deLivery over Unidirectional Transport，FLUTE)协议的点对多点传输方式。FLUTE协议的点对多点传输方式会将需要传输的内容转换成多个FLUTE文件，在传输时对每个文件做一定处理后封装成FLUTE包，将FLUTE包通过互联网传送至多个接收端上。上述在一段指定的时间区间内，通过FLUTE通信协议在FLUTE频道上传送MBMS用户数据的服务可以称为FLUTE会话(FLUTE session)。相同业务的数据所对应的文件只会通过一个FLUTE会话发送给多个接收端。如果在FLUTE包的传输过程中，造成了数据的丢失或损坏，接收端的用户设备(UE)可以利用文件的统一资源标识符(Uniform Resource Identifier，或URI)向文件修复服务器请求修复数据。
随着eMBMS技术的发展，在3GPP R12标准中提出了多个FLUTE会话特性，即UE关注的/感兴趣的同一个业务的数据可以在多个FLUTE会话中传送给用户，用户可以自由选择在哪个FLUTE会话接收该业务对应的FLUTE包。 然而，针对FLUTE包的传输过程中造成了数据的丢失或损坏的问题，现有技术提供的解决方案，仅能在同一个业务只能通过一个FLUTE会话发送给接收端的情况下有效，如果在多个FLUTE会话特性下造成了数据的丢失或损坏，将无法修复数据。
发明内容
本发明实施例提供了一种文件修复的方法、相关装置及系统，能够针对多个FLUTE会话特性下造成的数据丢失或数据损坏问题，进行文件修复。
一方面，本发明实施例提供了一种文件修复的方法，该方法包括：
广播多播业务中心接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据；
所述广播多播业务中心将所述文件数据的修复数据发送给所述用户设备。
结合第一方面，在第一种可能的实现方式中，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。
结合第一方面，或者第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述文件修复请求消息还包括所述文件数据的来源区块编号SBN、所述文件数据的编码符号标识ESI和所述文件数据的字节范围中的至少一种信息；
和/或，所述文件修复请求消息为基于符号的文件修复请求消息或者基于字节范围的文件修复请求消息。
结合第一方面，或者第一方面的第一种或者第二种可能的实现方式，在 第三种可能的实现方式中，所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据包括：
所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，
所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述广播多播业务中心根据所述所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。
结合第一方面，或者第一方面的第一种或者第二种或者第三种可能的实现方式，在第四种可能的实现方式中，所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据包括：所述广播多播业务中心根据所述传输会话标识，确定传输所述文件数据的FLUTE会话；所述广播多播业务中心根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的修复数据。
第二方面，本发明实施例提供了一种文件修复的方法，包括：
用户设备向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
所述用户设备接收所述广播多播业务中心根据所述文件修复请求消息返回的所述文件数据的修复数据。
结合第二方面，在第一种可能的实现方式中，所述方法还包括：所述用户设备获取所述传输会话标识。
结合第二方面，或者第二方面的第一种可能的实现方式，在第二种可能的实现方式中，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。
第三方面，本发明实施例提供了一种广播多播业务中心，包括：
接收单元，用于接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
处理单元，用于根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据；
发送单元，用于将所述文件数据的修复数据发送给所述用户设备。
结合第三方面，在第一种可能的实现方式中，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。
结合第三方面，或者第三方面的第一种可能的实现方式，在第二种可能的实现方式中，所述文件修复请求消息还包括所述文件数据的来源区块编号SBN、所述文件数据的编码符号标识ESI和所述文件数据的字节范围中的至少一种信息；
和/或，所述文件修复请求消息为基于符号的文件修复请求消息或者基于字节范围的文件修复请求消息。
结合第三方面，或者第三方面的第一种或者第二种可能的实现方式，在第三种可能的实现方式中，所述处理单元具体用于根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，
所述处理单元具体用于根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述处理单元具体用于根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述处理单元具体用于根据所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。
结合第三方面，或者第三方面的第一种或者第二种或者第三种可能的实现方式，在第四种可能的实现方式中，所述处理单元具体用于根据所述传输会话标识，确定传输所述文件数据的FLUTE会话；所述广播多播业务中心根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的修复数据。
第四方面，本发明实施例提供了一种用户设备，包括：
发送单元，用于向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
接收单元，用于接收所述广播多播业务中心根据所述文件修复请求消息返回的所述文件数据的修复数据。
第五方面，本发明实施例提供了一种广播多播业务中心，包括总线，以 及连接到所述总线的处理器、存储器、发射器和接收器；所述存储器用于存储计算机执行指令，所述计算机执行指令被配置成由所述处理器执行；
其中，所述接收器用于接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
所述处理器用于根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据；
所述发射器还用于将所述文件数据的修复数据发送给所述用户设备。
在第五方面中，关于所述文件修复请求以及所述文件的数据修复数据的具体信息和实现方式具体可以参考第三方面的任一可能的实现方式；关于所述处理器如何确定所述文件数据的修复数据具体可以参考第三方面的任一可能的实现方式。
第六方面，本发明实施例提供了一种用户设备，包括总线，以及连接到所述总线的处理器、存储器、发射器和接收器；所述存储器用于存储计算机执行指令，所述计算机执行指令被配置成由所述处理器执行；
其中，所述发射器用于向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
所述接收器用于接收所述广播多播业务中心根据所述文件修复请求消息返回的所述文件数据的修复数据。
结合第六方面，在第一种可能的实现方式中，所述处理单元还用于获取所述传输会话标识。
在第六方面或者第六方面的第一种可能的实现方式中，关于所述文件修复请求以及所述文件的数据修复数据的具体信息和实现方式具体可以参考第四方面的任一可能的实现方式。
第七方面，本发明实施例提供了一种计算机可读介质，包括计算机执行 指令，以供计算机的处理器执行所述计算机执行指令时，所述计算机执行第一方面所述的文件修复的方法或者第一方面的任一种可能的实现方式所述的文件修复的方法。
第八方面，本发明实施例提供了一种计算机可读介质，包括计算机执行指令，以供计算机的处理器执行所述计算机执行指令时，所述计算机执行第二方面所述的文件修复的方法或者第二方面的任一种可能的实现方式所述的文件修复的方法。
在本发明实施例提供了一种文件修复的方法，广播多播业务中心通过接收用户设备发送的文件修复请求消息，获取待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识，从而广播多播业务中心利用所述传输会话标识可以感知所述文件数据是通过哪个FLUTE会话传输的，再利用文件数据所对应的URI，可以获取该文件数据的修复数据，实现了文件的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对现有技术或实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为一种LTE网络中的eMBMS逻辑架构的示意图；
图2为一种FLUTE文件的示意图；
图3为本发明实施例提供的一种文件修复的方法的流程图；
图4为本发明实施例提供的又一种文件修复的方法的流程图；
图5为本发明实施例提供的又一种文件修复的方法的流程图；
图6为本发明实施例提供的一种广播多播业务中心的示意图；
图7为本发明实施例提供的一种用户设备的示意图；
图8为本发明实施例提供的一种用于文件修复的装置的组成示意图；
图9为本发明实施例提供了一种文件修复系统的示意图。
具体实施方式
本发明实施例提供了一种文件修复的方法、相关装置及系统，能够针对多个FLUTE会话特性下，造成的数据丢失或数据损坏问题，进行文件修复。
如图1所示为LTE网络中eMBMS逻辑架构示意图，主要包括：广播多播业务中心(BM-SC)、MBMS网关(MBMS-GW)、移动管理网元实体(MME)、多小区/多播协调功能实体(MCE)、演进型通用陆地无线接入网E-UTRAN。其中，MCE主要用于业务的调度，即选择合适的资源(包括频率、时间等参数)进行多播/组播单频网络(Multimedia Broadcast multicast service Single Frequency Network,BSFN)传输；MME是控制面网元节点，主要用于会话控制；MBMS-GW作为BM-SC和E-UTRAN之间的一个节点，是网络的接入网关，负责处理用户数据相关的报文和会话相关的信令；BM-SC属于业务层网元，是内容提供者的入口，提供业务的汇聚和发送、用户的授权、业务承载的建立和发起、会话控制的发起等。
通常，BM-SC在传输业务的内容之前，需要将传输的业务的内容转换成多个FLUTE文件，如图2所示，每个文件具有其相应地URI，该URI可以唯一标识该文件或者数据源。每个文件在传送前，会被分割成多个对象，每个对象用TOI标识。在基于符号传输FLUTE文件的机制中，每个对象又会被分割成至少一个来源区块(source block)，每个来源区块用来源区块编号(source block number，SBN)标识。而每一个来源区块又会被分割成大小相同的来源符号(source symbol)，BM-SC再通过前向纠错(Forward Error Correction,FEC)算法得到该来源符号的检查码符号(parity symbol)，最后BM-SC将属于同一个文件的来源符号与检查码符号封装在FLUTE包中通过 FLUTE会话频道传送给用户设备，完成了文件的传输。其中，来源符号与检查码符号又被统称为编码符号(encoding symbol)，编码符号可以用编码符号标识(encoding symbol identifier，ESI)来标识。在基于字节传输FLUTE文件的机制中，每个对象又会以字节为单位被分割成至少一个字节，BM-SC将属于同一个文件的字节封装在FLUTE包中通过FLUTE会话频道传送给用户设备。
然而，在FLUTE包的传输过程中，可能造成了数据的丢失或损坏，此时用户设备可以通过文件修复请求消息向BM-SC请求修复数据，该文件修复请求包含文件的URI，从而BM-SC可以利用文件的URI等信息，重传相关的文件或者相关文件的部分数据。经发明人分析发现，由于在多个FLUTE会话特性下，同一个业务的内容可以在多个FLUTE会话中传输，在所述多个FLUTE会话中传输的文件虽然并不同，但是文件的URI却是相同的。因此，采用现有技术的方案，BM-SC无法判断UE待修复的文件是通过哪个FLUTE会话传输，无法获得正确的数据。
本发明实施例提供了一种文件修复的方法，用户设备可以将用于传输待修复的文件数据的FLUTE会话的传输会话标识添加到文件修复请求消息中，使得BM-SC可以感知待修复的文件数据是通过哪个FLUTE会话传输的，，从而BM-SC可以根据该传输会话标识等信息，获取该文件数据的修复数据，实现了文件的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。需要注意的是，本发明各实施例中，BM-SC也可以是文件修复服务器(file repair server)。通常情况下，文件修复服务器是作为网元实体BM-SC的联合传输功能(Associated Delivery functions)的子功能的形式出现的。
如图3所示，本发明实施例提供了一种文件修复的方法，为了便于理解， 在本发明实施例中，提供了用户设备与BM-SC相互交互进行文件修复的详细流程，在实际应用中，本发明实施例提供的文件修复的方法可以只执行部分步骤，或者可以只应用于用户设备或者只应用于BM-SC中，本发明实施例在此不作限定。
S300：用户设备获取待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识(Transport Session Identifier)。
在本发明实施例中，BM-SC中包含至少一个服务器(Server)，该服务器属于BM-SC的逻辑功能模块，每个服务器可以为用户设备提供至少一种业务，由相同服务器提供的业务的内容具有相同的URI。由于在传输业务的内容之前，待传输的业务的内容会被转换成多个FLUTE文件，因而同一个业务的内容所对应的文件具有相同的URI。上述URI可以唯一地标识该文件或者数据源，因此可以称为文件的URI(URI of file)，也可以称为服务器的URI(Server URI)。也即所述待修复的文件数据所对应的URI即可以是指所述待修复的文件数据所对应的文件的URI，也可以是指提供所述待修复的文件数据的服务器的URI，本发明实施例在此不作限定。
BM-SC通过FLUTE会话将文件传输给所述用户设备时，所述用户设备可以保存传输所述文件的FLUTE会话的传输会话标识，在多个FLUTE会话特性下，对于一个给定的IP源地址，会有多个FLUTE会话，而所述传输会话标识用于唯一标识这个给定IP源地址的某个特定的FLUTE会话，通过传输会话标识，可以唯一确定一个FLUTE会话，从而当所述用户设备确定所述文件中有数据丢失或损坏时，可以获取所述传输会话标识，使得BM-SC能够感知数据丢失或损坏是发生在哪个FLUTE会话。
在本发明实施例中，S300为可选步骤。
S301：所述用户设备向BM-SC发送文件修复请求消息，所述文件修复请求消息包含所述文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识。
所述用户设备可以利用超文本传送协议(Hypertext transfer protocol，HTTP)获取(GET)请求，向所述BM-SC发送所述文件修复请求消息。
不同于现有技术，本发明实施例中所述用户设备在发现有文件数据丢失或损坏时，不仅会将所述文件数据所对应的URI发送给所述BM-SC，还会将传输所述文件数据的FLUTE会话的传输会话标识发送给所述BM-SC，从而所述BM-SC可以识别传输所述文件数据的FLUTE会话，进而获取所述文件数据的修复数据，完成了文件的修复。
S302：BM-SC接收用户设备发送的文件修复请求消息，根据所述文件修复请求消息包含的所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据。
所述BM-SC可以根据所述传输会话标识，确定传输所述文件数据的FLUTE会话，根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的修复数据。其中，所述文件数据的修复数据可为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。由于所述文件数据的修复数据包含了所述文件数据的全部信息，从而所述BM-SC实现了对所述文件数据的修复。
具体地，由于进行文件数据修复的粒度不同，在本发明实施例中，所述文件修复请求消息即可以是基于符号的文件修复请求消息(Symbol-Based File Repair Request Message)，也可以是基于字节范围的文件修复请求消息(Byte-Range-Based File Repair Request Message)。其中，所述基于符号的文件修复请求消息可以应用于针对某些特定的编码符号需要修复的场景，所述基于符号的文件修复请求消息中包含的所述文件数据所对应的URI可以由联合传输程序片段(Associated Delivery procedure fragment)的postFileRepair元素确定；而所述基于字节范围的文件修复请求消息可以应用于针对文件中 的部分或者所有的字节来进行文件修复，所述基于字节范围的文件修复请求消息中包含的所述文件数据所对应的URI可以是由文件传输表(File Delivery Table，FDT)中"Alternate-Content-Location-1"和"Alternate-Content-Location-2"等元素确定。
如果所述文件修复请求消息是基于符号的文件修复请求消息，则所述文件修复请求消息中除了包含所述文件数据所对应的URI和所述传输会话标识之外，还可以包括所述文件数据的SBN或者所述文件数据的ESI等。例如，如果某个文件完全丢失或损坏，则所述文件修复请求消息中可以只携带该文件的URI和传输该文件的FLUTE会话的传输会话标识；如果请求修复某个特定文件中的未接收到的来源区块，则所述文件修复请求消息中可以包含该特定文件的URI、传输会话标识以及SBN的范围，所述SBN的范围可以用于指示第一个丢失的来源区块到最后一个丢失的来源区块；如果需要请求修复某个特定来源区块的未接收到的来源符号，则所述文件修复请求消息中可以包含文件的URI、传输会话标识、该特定来源区块的SBN以及用于指示/标识该未接收到的来源符号的ESI。从而所述BM-SC根据上述文件修复请求消息中包含的信息可以获取某个特定的FLUTE文件、未接收到的来源区块的编码符号或者未接收到的来源符号的编码符号等修复数据。
如果所述文件修复请求消息是基于字节范围的文件修复请求消息，则所述文件修复请求消息中除了包含所述文件数据所对应的URI和所述传输会话标识之外，还可以包含所述文件数据字节范围(byte range)，所述文件数据字节范围为待修复的所述文件数据所对应的字节范围。例如，如果请求的是某个文件的所有来源区块，则所述文件修复请求消息中可以只包含URI和传输该文件的FLUTE会话的传输会话标识；如果请求的是某些特定的来源区块，则所述文件修复请求消息中可以包含URI、传输会话标识以及待修复的字节范围(byte range)，所述字节范围可以用于指示该特定的来源区块；如果待修复的是特定来源区块中的某些部分，则所述文件修复请求消息中还 可以包含该部分的最小的ESI的值。从而所述BM-SC根据上述文件修复请求消息中包含的信息可以获取某个特定的FLUTE文件或者未接收到的来源区块所对应的字节等修复数据。
S303：所述BM-SC向所述用户设备发送文件修复响应消息，所述文件修复响应消息包含所述文件数据的修复数据。
所述BM-SC可以利用HTTP响应(HTTP response)请求，向所述用户设备返回文件修复响应消息，所述文件修复响应可以包含所述文件数据的修复数据，实现了对文件数据的文件修复。所述文件修复响应消息可以是基于字符的文件修复响应消息，还可以是基于字节范围的文件修复响应消息。在本发明实施例中，一个特定的MBMS业务的文件修复请求消息及文件修复响应消息都可以按照HTTP协议通过相同的TCP连接进行传输。
对应于图3所述实施例，如果将图3所述的文件修复的方法应用于BM-SC中，该方法具体可以如下：
S401：BM-SC接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识。
可选地，所述文件修复请求消息还包括所述文件数据的SBN、所述文件数据的ESI和所述文件数据的字节范围中的至少一种信息，上述信息可以标识/指示所述文件数据。
S402：所述BM-SC根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据。
所述BM-SC可以根据所述传输会话标识，确定传输所述文件数据的FLUTE会话，再根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的修复数据。具体地，所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数 据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，
所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
所述广播多播业务中心根据所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。
可选地，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。由于所述文件数据的修复数据包含了所述文件数据的全部信息，实现了对文件数据的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
S403：所述BM-SC将所述文件数据的修复数据发送给所述用户设备。具体地可以通过文件修复响应消息将所述文件数据的修复数据发送给所述用户设备，具体可以参考S303。
对应于图3所述实施例，如果图3所述的文件修复的方法应用于用户设备中，该方法具体可以如下：
S501：用户设备向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的URI和传输所述文件数据的 FLUTE会话的传输会话标识。
S502：所述用户设备接收所述广播多播业务中心根据所述文件修复请求消息返回的文件数据的修复数据。具体可以参考图3对应的实施例。
可选地，在发送所述文件修复请求消息之前，所述方法还可以包括：
S500：所述用户设备获取所述传输会话标识。
本发明实施例提供了一种广播多播业务中心60，如图6所示，包括接收单元601、处理单元602和发送单元603。
所述接收单元601，用于接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识。可选地，所述文件修复请求消息还可以包括所述文件数据的SBN、所述文件数据的ESI和所述文件数据的字节范围中的至少一种信息，上述信息可以标识/指示所述文件数据。
所述处理单元602，用于所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据。具体地，所述处理单元602可以根据所述传输会话标识，确定传输所述文件数据的FLUTE会话，根据所述传输所述文件数据的FLUTE会话和所述文件数据所对应的URI，确定所述文件数据的编码符号修复数据。例如，所述处理单元602可以根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，所述处理单元602可以根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，所述处理单元602可以根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件 数据的修复数据为所述文件数据的编码符号；或者，所述处理单元602可以根据所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。可选地，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节
所述发送单元603，用于将所述文件数据的修复数据发送给所述用户设备。具体地可以通过文件修复响应消息将所述文件数据的修复数据发送给所述用户设备。
本发明实施例所述的广播多播业务中心60实现文件修复的具体方式，还可以参考图3所述的方法实施例，本发明实施例在此不再赘述。
本发明实施例中，接收单元601可以通过接收用户设备发送的文件修复请求消息，获取待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识，从而处理单元602根据所述传输会话标识和所述文件数据所对应的URI，可以确定所述文件数据的修复数据，所述发送单元603，可以将所述文件数据的修复数据发送给所述用户设备，实现了文件的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
本发明实施例提供了一种用户设备70，如图7所示，包括发送单元701和接收单元702；
其中，所述发送单元701，用于向BM-SC发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的URI和传输所述文件数据的FLUTE会话的传输会话标识；
所述接收单元702，用于接收所述BM-SC根据所述文件修复请求消息 返回的所述文件数据的修复数据。可选地，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。由于所述文件数据的修复数据包含了所述文件数据的全部信息，实现了对文件数据的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
可选地，所述用户设备70还可以包括获取单元703，用于获取所述传输会话标识。本发明实施例所述的用户设备70实现文件修复的具体方式，还可以参考图3所述的方法实施例，本发明实施例在此不再赘述。
在本发明实施例中，所述用户设备70可以将用于传输待修复的文件数据的FLUTE会话的传输会话标识添加到文件修复请求消息中，使得BM-SC用户设备70可以感知待修复的文件数据是通过哪个FLUTE会话传输的，，从而BM-SC可以根据该传输会话标识等信息，获取该文件数据的修复数据并返回给所述用户设备70，实现了文件的修复，解决了现有技术无法处理多个FLUTE会话特性下的文件修复的问题。
本领域技术人员能够理解，上述图6和图7的实施例中，用于发送消息发送单元可以采用发送器实现或者采用收发器实现，用于接收消息的接收单元可以采用接收器实现或者采用收发器实现。在物理实现上，发送器或者收发器可以用一个物理实体实现，也可采用多个物理实体实现，发送器和收发器可以采用一个物理实体实现，也可以采用多个物理实体实现，本发明对此不做限制。其他单元，如获取单元或处理单元可以采用一个或多个处理器实现，本发明对此不做限制。
如图8，为本发明实施例提供的一种用于文件修复的装置，所述装置可以包括：
处理器801、存储器802、总线804和通信接口805。处理器801、存储器802和通信接口805之间通过总线804连接并完成相互间的通信。
处理器801可能为单核或多核中央处理单元，或者为特定集成电路，或者为被配置成实施本发明实施例的一个或多个集成电路。
存储器802可以为高速RAM存储器，也可以为非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
存储器802用于计算机执行指令803。具体的，计算机执行指令803中可以包括程序代码。
当所述装置运行时，处理器801运行计算机执行指令803，可以执行图3至图5任意之一对应的方法实施例所述的文件修复的方法的方法流程。当执行图3或图4对应的方法实施例所述的文件修复的方法的方法流程时，所述装置可以为广播多播业务中心。当执行图3或图5对应的方法实施例所述的文件修复的方法的方法流程时，所述装置可以为用户设备。
本发明实施例提供了一种计算机可读介质，包括计算机执行指令，以供计算机的处理器执行所述计算机执行指令时，所述计算机执行图3或图4对应的方法实施例所述的文件修复的方法。
本发明实施例提供了一种计算机可读介质，包括计算机执行指令，以供计算机的处理器执行所述计算机执行指令时，所述计算机执行图3或图5对应的方法实施例所述的文件修复的方法。
参阅图9，本发明实施例提供的一种文件修复系统包括：广播多播业务中心60和用户设备70；广播多播业务中心60和用户设备70各自执行的动作以及它们之间的交互，可以参见图3至图5对应的方法实施例的描述，也可以参考图6和图7对应的装置实施例的描述，此处不再赘述。
本发明中所提到的LTE网络，包括LTE A网络、以及后续可能出现LTE版本。
本领域普通技术人员将会理解，本发明的各个方面、或各个方面的可能实现方式可以被具体实施为系统、方法或者计算机程序产品。因此，本发明 的各方面、或各个方面的可能实现方式可以采用完全硬件实施例、完全软件实施例(包括固件、驻留软件等等)，或者组合软件和硬件方面的实施例的形式，在这里都统称为“电路”、“模块”或者“系统”。此外，本发明的各方面、或各个方面的可能实现方式可以采用计算机程序产品的形式，计算机程序产品是指存储在计算机可读介质中的计算机可读程序代码。
计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质包含但不限于电子、磁性、光学、电磁、红外或半导体系统、设备或者装置，或者前述的任意适当组合，如随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或者快闪存储器)、光纤、便携式只读存储器(CD-ROM)。
计算机中的处理器读取存储在计算机可读介质中的计算机可读程序代码，使得处理器能够执行在流程图中每个步骤、或各步骤的组合中规定的功能动作；生成实施在框图的每一块、或各块的组合中规定的功能动作的装置。
计算机可读程序代码可以完全在用户的计算机上执行、部分在用户的计算机上执行、作为单独的软件包、部分在用户的计算机上并且部分在远程计算机上，或者完全在远程计算机或者计算机上执行。也应该注意，在某些替代实施方案中，在流程图中各步骤、或框图中各块所注明的功能可能不按图中注明的顺序发生。例如，依赖于所涉及的功能，接连示出的两个步骤、或两个块实际上可能被大致同时执行，或者这些块有时候可能被以相反顺序执行。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限 于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (13)

  1. 一种文件修复的方法，其特征在于，包括：
    广播多播业务中心接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
    所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据；
    所述广播多播业务中心将所述文件数据的修复数据发送给所述用户设备。
  2. 根据权利要求1所述的方法，其特征在于，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。
  3. 根据权利要求1或2所述的方法，其特征在于，所述文件修复请求消息还包括所述文件数据的来源区块编号SBN、所述文件数据的编码符号标识ESI和所述文件数据的字节范围中的至少一种信息。
  4. 根据权利要求3所述的方法，其特征在于，所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据包括：
    所述广播多播业务中心根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，
    所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
    所述广播多播业务中心根据所述文件数据的SBN或所述文件数据的ESI、所述所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
    所述广播多播业务中心根据所述所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。
  5. 一种文件修复的方法，其特征在于，包括：
    用户设备向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
    所述用户设备接收所述广播多播业务中心根据所述文件修复请求消息返回的所述文件数据的修复数据。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述用户设备获取所述传输会话标识。
  7. 一种广播多播业务中心，其特征在于，包括：
    接收单元，用于接收用户设备发送的文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
    处理单元，用于根据所述传输会话标识和所述文件数据所对应的URI，确定所述文件数据的修复数据；
    发送单元，用于将所述文件数据的修复数据发送给所述用户设备。
  8. 根据权利要求7所述的广播多播业务中心，其特征在于，所述文件数据的修复数据为以下至少一种形式的数据：所述文件数据所对应的FLUTE文件、所述文件数据的编码符号、根据所述文件数据的编码符号进行重新编码所获得的新的编码符号和所述文件数据所对应的字节。
  9. 根据权利要求7所述的广播多播业务中心，其特征在于，所述文件修复请求消息还包括所述文件数据的来源区块编号SBN、所述文件数据的编码符号标识ESI和所述文件数据的字节范围中的至少一种信息。
  10. 根据权利要求9所述的广播多播业务中心，其特征在于，所述处理单元具体用于根据所述传输会话标识和所述文件数据所对应的URI，获得所述文件数据所对应的FLUTE文件，所述文件数据的修复数据为所述文件数据所对应的FLUTE文件；或者，
    所述处理单元具体用于根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
    所述处理单元具体用于根据所述文件数据的SBN或所述文件数据的ESI、所述传输会话标识以及所述文件数据所对应的URI，确定所述文件数据的编码符号，根据所述文件数据的编码符号进行重新编码，获得新的编码符号，所述文件数据的修复数据为所述文件数据的编码符号；或者，
    所述处理单元具体用于根据所述传输会话标识、所述文件数据所对应的URI以及所述文件数据的字节范围，确定所述文件数据所对应的字节，所述文件数据的修复数据为所述文件数据所对应的字节。
  11. 一种用户设备，其特征在于，包括：
    发送单元，用于向广播多播业务中心发送文件修复请求消息，所述文件修复请求消息包含待修复的文件数据所对应的统一资源标识符URI和传输所述文件数据的单向传递文件传输FLUTE会话的传输会话标识；
    接收单元，用于接收所述广播多播业务中心根据所述文件修复请求消息返回的所述文件数据的修复数据。。
  12. 根据权利要求11所述的用户设备，其特征在于，还包括：
    获取单元，用于获取所述传输会话标识。
  13. 一种文件修复系统，其特征在于，包括如权利要求7-10任一项所 述的广播多播业务中心和如权利要求11或12所述的用户设备。
PCT/CN2014/094963 2014-12-25 2014-12-25 一种文件修复的方法、相关装置及系统 WO2016101213A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201480035411.2A CN106063190B (zh) 2014-12-25 2014-12-25 一种文件修复的方法、相关装置及系统
EP14908781.9A EP3226466A4 (en) 2014-12-25 2014-12-25 File repair method, and related apparatus and system
PCT/CN2014/094963 WO2016101213A1 (zh) 2014-12-25 2014-12-25 一种文件修复的方法、相关装置及系统
US15/631,343 US10516502B2 (en) 2014-12-25 2017-06-23 File repair method, related apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/094963 WO2016101213A1 (zh) 2014-12-25 2014-12-25 一种文件修复的方法、相关装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/631,343 Continuation US10516502B2 (en) 2014-12-25 2017-06-23 File repair method, related apparatus, and system

Publications (1)

Publication Number Publication Date
WO2016101213A1 true WO2016101213A1 (zh) 2016-06-30

Family

ID=56148943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/094963 WO2016101213A1 (zh) 2014-12-25 2014-12-25 一种文件修复的方法、相关装置及系统

Country Status (4)

Country Link
US (1) US10516502B2 (zh)
EP (1) EP3226466A4 (zh)
CN (1) CN106063190B (zh)
WO (1) WO2016101213A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022006850A1 (en) * 2020-07-10 2022-01-13 Qualcomm Incorporated Transmitting encoding symbol identifier of raptor codes using control channel coding

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10721287B2 (en) * 2018-03-23 2020-07-21 Verizon Patent And Licensing, Inc. Real-time file repair

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1957554A (zh) * 2004-03-29 2007-05-02 诺基亚公司 用于多播/广播数据分布的数据修复增强
CN101877641A (zh) * 2009-04-29 2010-11-03 华为技术有限公司 Ims网络中文件下载方法、装置和系统
WO2014063730A1 (en) * 2012-10-24 2014-05-01 Huawei Technologies Co., Ltd. Communication receiver
CN103780405A (zh) * 2004-08-30 2014-05-07 诺基亚公司 在点对多点传输系统中确认数据的方法和设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7536622B2 (en) 2004-03-29 2009-05-19 Nokia Corporation Data repair enhancements for multicast/broadcast data distribution
US7376150B2 (en) * 2004-07-30 2008-05-20 Nokia Corporation Point-to-point repair response mechanism for point-to-multipoint transmission systems
US7590922B2 (en) 2004-07-30 2009-09-15 Nokia Corporation Point-to-point repair request mechanism for point-to-multipoint transmission systems
TWI325732B (en) * 2006-07-31 2010-06-01 Ind Tech Res Inst File repair mechanism for mbms and umts network
WO2008119673A1 (en) * 2007-03-30 2008-10-09 Thomson Licensing Robust file casting for mobile tv
US9215084B2 (en) * 2008-06-04 2015-12-15 Telefonaktiebolaget L M Ericsson (Publ) Method and device for content personalisation using file repair requests
US9213605B2 (en) * 2012-01-23 2015-12-15 Intel Corporation IP multimedia subsystem and method for MBMS file repair using HTTP servers
AT513277B1 (de) 2012-10-24 2014-03-15 Plasser Bahnbaumasch Franz Maschine zum Unterstopfen eines Gleises
US20150270978A1 (en) * 2014-03-20 2015-09-24 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for data repair in a data communication network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1957554A (zh) * 2004-03-29 2007-05-02 诺基亚公司 用于多播/广播数据分布的数据修复增强
CN103780405A (zh) * 2004-08-30 2014-05-07 诺基亚公司 在点对多点传输系统中确认数据的方法和设备
CN101877641A (zh) * 2009-04-29 2010-11-03 华为技术有限公司 Ims网络中文件下载方法、装置和系统
WO2014063730A1 (en) * 2012-10-24 2014-05-01 Huawei Technologies Co., Ltd. Communication receiver

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3226466A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022006850A1 (en) * 2020-07-10 2022-01-13 Qualcomm Incorporated Transmitting encoding symbol identifier of raptor codes using control channel coding

Also Published As

Publication number Publication date
CN106063190B (zh) 2019-06-28
EP3226466A4 (en) 2018-01-10
US20170302403A1 (en) 2017-10-19
CN106063190A (zh) 2016-10-26
US10516502B2 (en) 2019-12-24
EP3226466A1 (en) 2017-10-04

Similar Documents

Publication Publication Date Title
CN107948762B (zh) 直播视频的传输方法、装置和系统
KR101495369B1 (ko) 모바일 ｔｖ를 위한 로버스트 파일 캐스팅
TWI508584B (zh) Video service transmission method and device
US10470000B2 (en) Methods and apparatus for enhanced MBMS content provisioning and content ingestion
JP2016528763A5 (zh)
WO2015042913A1 (zh) 业务内容获取方法、提供方法、设备及系统
JP2018515960A (ja) マルチメディアブロードキャストマルチキャストサービスに基づくフレキシブルブロードキャストサービスのための方法及び装置
US10412151B2 (en) Method and system for on-demand file repair
WO2015113206A1 (zh) 多媒体广播多播业务获取方法、装置和通信系统
US20140215292A1 (en) Lt staircase fec code
BR112018001046B1 (pt) Método de distribuição de vídeo e função de exposição de capacidade de serviço
KR20170124551A (ko) 부분 세그먼트에 대한 표시
KR102446256B1 (ko) 부분 세그먼트에 대한 표시
WO2016101213A1 (zh) 一种文件修复的方法、相关装置及系统
EP2878098B1 (en) User equipment node, server node and methods performed in such nodes for performing file repair procedure
US20160226672A1 (en) Seamless connection handshake for a reliable multicast session
US10182089B2 (en) Method and broadcast multicast service center, BM-SC, node for providing an on-request service
WO2014131199A1 (zh) 一种前向纠错码码字同步的方法、设备与系统
Noh et al. Energy-efficient HTTP Adaptive Streaming System over SDN-enabled Wi-Fi APs
CN109196870B (zh) 用于发射和接收mmtp分组的方法和装置
TWI495320B (zh) Data confidentiality method and system using forward error correction mechanism
WO2016206159A1 (zh) 一种处理embms业务的方法、设备、系统及存储介质
WO2018068262A1 (zh) 一种获取视频码率的方法、装置及网络侧设备
KR20080055202A (ko) Ｉｐ멀티캐스트를 이용한 대용량 디지털 콘텐트 다지점전송 시스템 및 그 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14908781

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014908781

Country of ref document: EP