WO2010075785A1 - Ims网络中文件下载方法、装置和系统 - Google Patents

Ims网络中文件下载方法、装置和系统 Download PDF

Info

Publication number
WO2010075785A1
WO2010075785A1 PCT/CN2009/076235 CN2009076235W WO2010075785A1 WO 2010075785 A1 WO2010075785 A1 WO 2010075785A1 CN 2009076235 W CN2009076235 W CN 2009076235W WO 2010075785 A1 WO2010075785 A1 WO 2010075785A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
file
service
information
negotiation
Prior art date
Application number
PCT/CN2009/076235
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
Priority claimed from CN2008101898280A external-priority patent/CN101771662B/zh
Priority claimed from CN200910082784A external-priority patent/CN101877641B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010075785A1 publication Critical patent/WO2010075785A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102Entity profiles

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a file downloading technology in an IMS network. Background technique
  • the method for downloading a file by using the FLUTTE (File Delivery over Unidirectional Transport) protocol includes: The terminal acquires a FLUTE session parameter by using a short message or a telephone, and the FLUTE session parameter, such as a transmission session identifier, a FLUTE session destination multicast address, and The source IP address of the sender of the FLUTE session, etc.; the terminal receives the data sent by the media server according to the FLUTE session parameter, where the data includes the content description information and the file to be downloaded; the terminal obtains the content description information from the received data; The content description information obtains a file to be downloaded from the received data.
  • a FLUTE session parameter such as a transmission session identifier, a FLUTE session destination multicast address, and The source IP address of the sender of the FLUTE session, etc.
  • the terminal receives the data sent by the media server according to the FLUTE session parameter, where the data includes the content description information and the file to be downloaded
  • the terminal obtains the content description information from the received data
  • the file downloading method, device and system in the IMS network provided by the embodiments of the present invention control the file downloading by using the IMS network capability, thereby improving the flexibility and controllability of file downloading.
  • the terminal negotiates with the terminal, and returns a FLUTE session parameter to the terminal according to the result of the negotiation, so that the terminal receives the media according to the FLUTE session parameter.
  • the data sent by the body server is not limited to the authorization code.
  • An embodiment of the present invention provides a file downloading system in an IMS network, where the system includes: a service control function device, configured to acquire a service identifier of a file download service of the terminal, and perform the foregoing on the terminal according to the service identifier.
  • the file download service is authorized, if the authorization is passed, the session negotiation is performed with the terminal, and the FLUTE session parameter is returned to the terminal based on the result of the negotiation, so that the terminal sends the media server according to the FLUTE session parameter.
  • the data includes: a service control function device, configured to acquire a service identifier of a file download service of the terminal, and perform the foregoing on the terminal according to the service identifier.
  • the file download service is authorized, if the authorization is passed, the session negotiation is performed with the terminal, and the FLUTE session parameter is returned to the terminal based on the result of the negotiation, so that the terminal sends the media server according to the FLUTE session parameter.
  • a media server configured to send, according to the FLUTE session parameter, a file corresponding to the file download service to the terminal.
  • the network device located in the IMS network, and includes: an authorization module, configured to acquire a service identifier of a file download service of the terminal, and perform authorization on the file download service to the terminal according to the service identifier. ;
  • a negotiation module configured to perform a session negotiation with the terminal when the authorization result of the authorization module is authorized to pass, and return a FLUTE session parameter to the terminal according to the result of the negotiation, so that the terminal according to the FLUTE session parameter Receive data sent by the media server.
  • FIG. 1 is a flowchart of a file downloading method according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart of a file downloading method according to Embodiment 2 of the present invention.
  • FIG. 3 is a flowchart of a file downloading method according to Embodiment 3 of the present invention.
  • FIG. 4 is a flowchart of a file repairing method according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic diagram of a file downloading system according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic diagram of a specific application of a file downloading system according to Embodiment 5 of the present invention.
  • FIG. 7 is a schematic diagram of a file downloading apparatus according to Embodiment 6 of the present invention.
  • FIG. 8 is a flowchart of a method for acquiring download service information in a network television architecture according to Embodiment 1 of the present invention.
  • FIG. 9 is a flowchart of a method for acquiring download service information in a network television architecture according to Embodiment 2 of the present invention
  • FIG. 10 is a flowchart of a method for acquiring download service information in a network television architecture according to Embodiment 3 of the present invention.
  • Embodiment 1 of the present invention provides a file downloading method based on the FLUTE protocol in an IMS network, and the process of the method is as shown in FIG.
  • S100 is used to obtain a service identifier of a file download service of the terminal.
  • the file download service in this embodiment is a service that is set for one or more download files that need to be provided to the terminal, and one file download service corresponds to a unique service identifier.
  • a file download service in this embodiment can be implemented by multiple transport sessions, that is, a file corresponding to a file download service can be sent through multiple transport sessions.
  • the terminal sends a download service request including the service identifier to the network side, and the service identifier may be included in the download.
  • the network side may obtain the service identifier of the file download service of the terminal from the received download service request; for example, when the file download service is initiated by the network side, the terminal performs the file in advance.
  • the network side determines the service identifier corresponding to the file download service according to the message sent by the terminal (such as a subscription message, etc.).
  • S110 Perform file download service authorization on the terminal according to the service identifier, if the authorization is passed, go to S120, otherwise, go to S130.
  • the file download service authorization for the terminal may be: determining whether the terminal has the right to perform the file download service.
  • the authorization can also be: Review other permissions, etc.
  • the authorization process may be performed according to the subscription information of the user corresponding to the terminal or the local policy or the subscription information in combination with the local policy.
  • a specific example of an authorization is: If the user subscribes to the file download service in advance, the authorization is passed, otherwise the authorization fails (that is, the authorization fails).
  • a specific example of another authorization is: In the case where the local policy is that a file download service allows all users to access, the file download service authorization is performed on the terminal according to the local policy regardless of whether the user subscribes to the file download service. The result is authorized Passed.
  • S120 Perform session negotiation with the terminal, provide a FLUTE session parameter to the terminal according to the result of the session negotiation, or provide the terminal with the FLUTE session parameter and the downloaded service information based on the result of the negotiation.
  • the foregoing session negotiation may be: when the terminal sends the FLUTE session parameter to the network side, check the FLUTE session parameter sent by the terminal, that is, determine, according to the FLUTE session parameter sent by the terminal, the network side terminal sends the FLUTE session parameters.
  • the foregoing session negotiation may also be: when the terminal does not send the FLUTE session parameter to the network side, directly send the FLUTE session parameter determined by the network side to the file download service by the terminal.
  • the result of the above negotiation is usually that the negotiation is successful, that is, the FLUTE session parameter returned to the terminal is a parameter returned to the terminal based on the negotiation success.
  • the terminal can receive the data sent by the media server according to the FLUTE session parameters it receives, thereby obtaining the file that needs to be downloaded.
  • the result of the above negotiation may also be a negotiation failure. When the negotiation fails, the negotiation failure information may be returned to the terminal, so that the terminal does not receive the FLUTE session parameter.
  • the network side may also determine downloading service information for the terminal, and send the download service information to the terminal during the session negotiation process.
  • the foregoing download service information may be any one or any of the following: address information of the content description information, address information of the file repair server, and report parameters.
  • the acquisition address information of the content description information may be the acquisition address information of the file allocation table, that is, the storage address information of the file allocation table.
  • the obtaining address information of the content description information is used by the terminal to obtain the content description information of the file corresponding to the file download service, that is, the terminal may obtain the content description of the file corresponding to the file download service from the network device indicated by the obtaining address information of the content description information. information.
  • the terminal provides another implementation manner for the terminal to obtain the content description information, and improves the flexibility of the terminal to obtain the content description information.
  • the address information of the file repair server is used by the terminal to request repair data from the file repair server indicated by the address information, so that the terminal can repair the file corresponding to the file download service; that is, the terminal can use the address information of the file repair server.
  • the repair data is obtained, so that the repair data is used to repair the file corresponding to the file download service received.
  • the file repair service The device can be set up with the above media server, or can be set independently from the above media server. In an actual application, the file repair server can be set according to specific needs.
  • the file repair server indicated by the address information may directly provide repair data to the terminal, and the file repair server indicated by the address information may also redirect the terminal to another server capable of providing repair data to the terminal, so that the terminal is Get repair data at the server.
  • a specific example in which the file repair server indicated by the address information can directly provide repair data to the terminal is: the file repair server indicated by the address information is received based on the received terminal
  • the repair data is provided to the terminal directly based on the HTTP connection.
  • the file repair server indicated by the address information can directly provide the repair data for the terminal is: the file repair server indicated by the address information receives the HTTP-based repair request sent by the terminal, and provides the terminal with the unicast Or transmitting the FLUTE session parameter of the repair data in a multicast or broadcast manner, so that the terminal receives the repair data according to the FLUTE session parameter of the received repair data.
  • the network device indicated by the address information may use the FLUTE protocol to provide repair data to the terminal by using unicast or multicast or broadcast mode; for example, after receiving the HTTP-based repair request, the file repair server is based on HTTP.
  • the repair response provides unicast or multicast or broadcast mode to provide the terminal with the FLUTE session information corresponding to the repair data
  • the repair response may be an HTTP Redirect message.
  • the FLUTE session information corresponding to the repair data may be sent to the terminal in the HTTP Redirect message in the SDP mode or the XML mode, so that the terminal can initiate a SIP session according to the FLUTE session information carried in the HTTP Redirect message, and modify the data with the service control function device.
  • the session negotiation and then receiving the repair data according to the FLUTE session information of the modified data in the negotiation result.
  • the terminal may not perform session negotiation for the repair data, but directly receive the repair data according to the FLUTE session information carried in the HTTP Redirect message.
  • the implementation manner of obtaining the address information of the file repair server by the terminal is clarified, which provides a specific implementation manner for the terminal to repair the file, and improves the content description of the terminal.
  • the flexibility of information is provided.
  • the reporting parameter is used to instruct the terminal to report the file downloading information, for example, the statistical information indicating that the terminal successfully reports the file being downloaded.
  • the above reported parameters can be: whether to report, report the delay time and report Any one or more of the server's address information.
  • the reporting delay time is used to indicate the delay time for the terminal to report the file downloading information, and the reporting delay time can be implemented by the reporting timer; for example, triggering the reporting at the end of the file downloading process
  • the timer reports the file download information when the count value of the report timer reaches a predetermined value.
  • the address information of the reporting server is used to indicate the destination address of the terminal to send the file download information, that is, where the terminal sends the file download information. It should be noted that the address information of the reporting server may be the address information of the media server, the address information of the file repair server, or the address information independent of the media server and the file repair server.
  • the terminal By providing the reporting parameters for the terminal during the session negotiation process, the terminal obtains the implementation mode of the reporting parameters, and provides a specific implementation manner for the terminal to report the file downloading information, and improves the flexibility of the terminal to report the file downloading information.
  • the information transmitted between the terminal and the network side in the foregoing session negotiation process may be transmitted through a Session Initiation Protocol (SIP)-based message, and the information transmitted between the terminal and the network side in the session negotiation process may be a Session Description Protocol (SDP).
  • SIP Session Initiation Protocol
  • SDP Session Description Protocol
  • the method is carried in the message, and can also be carried in the message by using Extensible Markup Language (XML), and part of the information can be carried in the SDP mode and another part of the information is carried in the message by using XML; for example, FLUTE
  • XML Extensible Markup Language
  • the session parameters are in the SDP manner, and the downloaded service information is carried in the download service response message in XML.
  • the failure indication here may be an indication that the authorization is not passed, or an indication that the terminal is prohibited from downloading the file.
  • the executor of the first embodiment may be a service control function device on the network side.
  • the service control function device may exist independently or may be set in a network device on the network side, such as a network device where the media server is located.
  • the result of the session negotiation may be sent to the media server.
  • the service control function device sends the FLUTE session parameter provided to the terminal to the media server, so that the media server can receive the The FLUTE session parameter provides the file corresponding to the file download service to the terminal.
  • the file downloading service is performed through the file I, so that the network side can conveniently manage the file downloading (such as billing management, authorization management, and transmission management); and download the file to the terminal by using the service identifier of the file download service.
  • the service authorization enables the network side to further strengthen the management of the file downloading.
  • the session negotiation enables the network side to provide the downloaded file to the terminal in multiple ways.
  • the IMS network capability is introduced in the file downloading process. The method for downloading the service information such as the acquisition address information of the content description information of the terminal is clarified, the flexibility and controllability of the file downloading are improved, and the file downloading process is further improved.
  • the second embodiment of the present invention provides a file downloading method based on a terminal initiated file download service.
  • the flow of the method is shown in Figure 2.
  • step 2-1 the terminal sends a download service request.
  • the download service request may be a SIP-based download service request, for example, the download service request may be a SIP Invite message.
  • the download service request carries the FLUTE session parameters, such as the transport session identifier, the FLUTE session destination multicast address information (which may include port information), the source IP address of the FLUTE session sender, and the service identifier.
  • the service identifier may be represented by a service identifier obtained from the service selection discovery information or by using a Temporary Mobile Group Identity (TMGI).
  • TMGI Temporary Mobile Group Identity
  • the above FLUTE session parameters can be carried in the download service request through SDP or XML.
  • the request URI Uniform Resource Identifier
  • PSI Public Service Identity
  • a specific example of a FLUTE session parameter carried in the SDP offer in the SDP offer in the download service request is:
  • Step 2-2 After receiving the download service request, the IMS core forwards the download service request to the service control function device, that is, the IMS core performs the routing function, and routes the download service request to the service control function device.
  • the service control function device can be set in a network device as needed, for example, in 3GPP/TISPAN/OIPF (3rd Generation Partnership Project/Telecommunications and Internet Converged Services and Protocols for Advanced Networking/Open IPTV Forum, 3rd Generation Partnership Project/
  • the service control function device can be represented as an SCF (Service Control Function), that is, the service control function device in this embodiment can be set in 3GPP/TISPAN/OIPF.
  • SCF Service Control Function
  • Step 2-3 The service control function device obtains the service identifier from the download service request, authorizes the file downloading of the terminal according to the service identifier, and performs session negotiation with the terminal after the authorization is passed, for example, carrying the request for downloading the service.
  • the FLUTE session parameter is checked (or authorized), and the service control function device returns a download service response to the terminal.
  • the download service response may carry the authorized FLUTE session parameters and download service information.
  • the download service response can be a SIP based download service response. In the case that the download service request is a SIP Invite message, the download service response may be a SIP 200 OK message.
  • the service control function device may modify the FLUTE session parameters carried in the download service request according to the predetermined policy, or may not modify the FLUTE session parameters carried in the download service request; That is to say, the FLUTE session parameter carried in the download service response may be the same as the FLUTE session parameter carried in the download service request, or may be the same as the FLUTE session parameter carried in the download service request.
  • the download service information carried in the download service response may include: the address information of the content description information, the address information of the file repair server, and the reporting parameters. Reporting parameters such as whether to report, delay reporting time, and address information of the reporting server.
  • the service control function is performed.
  • the device can return an error indication message to the terminal, so that the terminal knows that the authorization has failed.
  • a specific example of the error indication information returned by the service control function device to the terminal is:
  • the service control function device returns a SIP 401 (Unauthorized) message or a SIP 403 (Forbidden) message to the terminal.
  • the above-mentioned FLUTE session parameters and the download service information may be carried in the download service response in the SDP mode or the XML mode.
  • the FLUTE session parameters may be carried in the download service response in one of the SDP mode and the XML mode, and the download service is performed.
  • the information can be carried in the download service response in another way in the SDP mode and the XML mode.
  • a report-indication: TRUE/FALSE //Report indication (that is, whether it is reported)
  • a backofF-time:value ⁇ Report delay time
  • the above FDT (file allocation table) file address is the acquisition address information of the content description information, that is, the FDT acquisition address information.
  • the attribute value of the above report-server-address can be either an HTTP URI or a SIP URI.
  • the above repair-server-address (address of the file repair server ⁇
  • the address information of the server directly providing the repair data may be the address information of the server providing the repair description information (ie, pointing to the repair description information), and the terminal may obtain the repair data according to the repair description information.
  • a specific example of downloading business information in XML to be carried in the download service response is:
  • the carrying method of downloading service information is defined by different XML elements.
  • the acquisition address information of the content description information is defined by CondentDescAdress
  • the address information of the repair server is defined by RepairServerAddress.
  • the indication of whether to report is defined by Reportlndication, the reporting delay time is defined by BackoffTime, and the address information of the reporting server is defined by ReportServerAddress.
  • Step 2-4 After receiving the download service response, the IMS core forwards the download service response to the terminal.
  • Step 2-5 The terminal acquires content description information according to the obtained address information (such as the HTTP URI address of the FDT file) of the content description information in the received download service response.
  • the terminal acquires content description information according to the acquired address information of the content description information to the download information providing function device.
  • the download information providing function device may be set in an SSF (Service Selection Function) entity of the 3GPP/TISPAN network, or may be set in other network devices, or may be set independently.
  • SSF Service Selection Function
  • the terminal may obtain the obtained address information, such as the preset address information of the preset content description information.
  • the content description information obtains the address information, or the terminal may obtain the content description information (such as obtaining the content description information from the data transmitted from the media server) by other means.
  • Step 2-6 The terminal starts the file receiving process according to the FLUTE session information carried in the received download service response, and receives the data corresponding to the FLUTE session.
  • step 2-5 there may be no sequential execution order between step 2-5 and step 2-6.
  • step 2-7 After the terminal completes the receiving operation of the data corresponding to the FLUTE session, it is judged whether there is missing data, and if there is missing data, it proceeds to step 2-7.
  • Step 2-7 The terminal acquires the repair data from the file repair server according to the address information of the file repair server carried in the received download service response. For example, the terminal sends a repair data request to the file repair server, and the repair data request carries the lost information. The information of the data, the file repair server sends the repair data to the terminal according to the information of the lost data carried in the modified data request. It should be noted that the file repair server may further send the content description information of the repair data or the acquisition address information of the content description information of the modified data to the terminal, so that the terminal may obtain the content description information of the repair data, and describe the content according to the repair data. Information for data repair.
  • Step 2-8 The terminal reports the file download information to the server.
  • the terminal determines that the file downloading information needs to be reported according to the reported report of the received download service response, the terminal reaches a predetermined value when the count value corresponding to the report delay time in the report parameter carried in the download service response reaches a predetermined value. Report the file download information to the server.
  • the file download information reported by the terminal can be: a list of successfully received files, a download duration, and the like.
  • the reporting delay time can be implemented by using a reporting timer.
  • the reporting timer can start timing after the terminal completes the receiving operation of the data corresponding to the FLUTE session, or can start timing when it is determined that no data is lost.
  • the terminal starts timing after completing the timing operation of repairing data.
  • the timing value of the reporting timer reaches the reporting delay time, the terminal reports the file downloading information to the server. This embodiment does not limit the timing for starting the counting of the delay time.
  • the file downloading information is reported to the service control function device as an example. That is, the reporting server and the service control function device in the embodiment are combined.
  • the escalation server can also be set separately.
  • the reporting server can be independent of the service control function device.
  • the reporting server can be combined with the media server.
  • the file downloading service is introduced, so that the network side can conveniently manage the file download initiated by the terminal (such as charging management, authorization management, transmission management, etc.); downloading the file to the terminal by using the service identifier of the file download service
  • the service authorization enables the service control function device to control and manage the file downloading;
  • the session negotiation between the service control function device and the terminal enables the media server to provide the downloaded file to the terminal in a plurality of manners;
  • the IMS network capability is introduced in the file downloading process, and the implementation manner of downloading the service information such as the acquisition address information of the terminal to obtain the content description information is clarified, the flexibility and controllability of the file downloading are improved, and the file downloading process is further improved.
  • the third embodiment of the present invention provides a file downloading method for starting a file download service based on a network side.
  • the flow of the method is shown in Figure 3.
  • step 3-1 the service control function device sends a download service request.
  • the service control function device can send a download service request according to the subscription of the terminal.
  • the service control function device can obtain the service of the subscribed download service by using the content subscribed by the terminal in the terminal subscription process. logo.
  • the service control function device downloads the service according to the subscription trigger file
  • the file download service authorization is performed on the terminal according to the service identifier in the subscription information, and when the authorization is passed, the service control function device sends a download service request.
  • the service control function device in the third embodiment can be configured in a network device as needed.
  • the service control function device in the 3GPP/TISPAN/OIPF network, can be represented as an SCF, that is, the service control function device in this embodiment can be Set in the service control function entity of the 3GPP/TISPAN/OIPF network.
  • the download service request in this embodiment may be a SIP-based download service request.
  • the download service request may be a SIP Invite message.
  • the download service request in this embodiment carries the FLUTE session parameters and the download service information.
  • the FLUTE session parameters carried in the service request such as the transport session identifier, the multicast address information of the FLUTE session (which may contain port information), and the source IP address information of the FLUTE session sender.
  • the download service information carried in the download service request may include: the address information of the content description information, the address information of the file repair server, and the report parameters. Report parameters such as whether to report, delay the report, and report the address information of the server.
  • the above-mentioned FLUTE session parameters and the download service information may be carried in the download service request in the SDP mode or the XML mode.
  • the FLUTE session parameter may be carried in the download service request in one of the SDP mode and the XML mode, and the download service is performed.
  • the information can be carried in the download service request in another way in the SDP mode and the XML mode.
  • Step 3-2 After receiving the download service request, the IMS core forwards the download service request to the terminal, that is, the IMS core performs a routing function, and routes the download service request to the terminal.
  • Step 3-3 After receiving the download service request, the terminal returns a download service response to the service control function device.
  • the download service response can be a SIP based download service response.
  • the download service response may be a SIP 200 OK message.
  • the download service response may carry the FLUTE session parameter carried in the download service request, or The download service response may carry the FLUTE session parameter and the download service information carried in the download service request.
  • the above-mentioned FLUTE session parameters and the download service information may be carried in the download service response in the SDP mode or the XML mode.
  • the FLUTE session parameters may be carried in the download service response in one of the SDP mode and the XML mode, and the download service is performed.
  • the information can be carried in the download service response in another way in the SDP mode and the XML mode.
  • Step 3-4 After receiving the download service response, the IMS core forwards the download service response to the service control function device.
  • Step 3-5 The terminal acquires content description information according to the obtained address information (such as the HTTP URI address of the FDT file) of the content description information in the received download service request. For example, the terminal acquires the content description information according to the acquired address information of the content description information to the download information providing function device.
  • the download information providing function device may be set in the SSF entity of the 3GPP/TISPAN network, or may be set in other network devices, or set independently.
  • the terminal may obtain the obtained address information of the content description information by using other methods, such as pre-setting the content description information, or the like, or The terminal may also obtain content description information (such as obtaining content description information from data transmitted from the media server) by other means.
  • Step 3-6 The terminal starts the file receiving process according to the FLUTE session information carried in the received download service request, and receives the data corresponding to the FLUTE session.
  • the terminal After the terminal completes the receiving operation of the data corresponding to the FLUTE session, the terminal determines whether there is missing data. If there is missing data, it goes to step 3-7.
  • Step 3-7 The terminal obtains the repair data from the file repair server according to the address information of the file repair server carried in the received download service request. For example, the terminal sends a repair data request to the file repair server, where the repair data request carries a loss. The information of the data, the file repair server sends the repair data to the terminal according to the information of the lost data carried in the modified data request. It should be noted that the file repair server may also send content description information of the repair data or modify the data to the terminal. The content description information acquires the address information, so that the terminal can obtain the content description information of the repair data, and perform data repair according to the content description information of the repair data.
  • step 3-8 If there is a report trigger condition, when the report trigger condition is satisfied, go to step 3-8.
  • Step 3-8 The terminal reports the file download information to the server.
  • the terminal determines that the file download information needs to be reported according to the received report of the received download service request, the terminal reaches a predetermined value when the count value corresponding to the report delay time in the report parameter carried in the download service request reaches a predetermined value.
  • Report file download information to the service control function device The file download information reported by the terminal may be: a list of successfully received files, a download duration, and the like.
  • the reporting delay time in the third embodiment can be implemented by using a reporting timer.
  • the reporting timer can start timing after the terminal completes the receiving operation of the data corresponding to the FLUTE session, and can also determine that no data is lost. The timing starts or the timing starts after the terminal completes the timing operation of repairing the data.
  • the terminal reports the file downloading information to the server. This embodiment does not limit the timing for starting the counting of the delay time.
  • the file downloading information is reported to the service control function device as an example, that is, the reporting server in the specific embodiment may be combined with the service control function device.
  • the escalation server can also be set separately.
  • the reporting server can be independent of the service control function device.
  • the reporting server can also be combined with the media server or the like.
  • the file downloading service is introduced, so that the network side can conveniently manage the file downloading initiated by the terminal (such as charging management, authorization management, and transmission management), and perform file processing on the terminal by using the service identifier of the file download service.
  • Downloading the service authorization enabling the service control function device to control and manage the file downloading; performing the session negotiation with the terminal through the service control function device, so that the media server can provide the downloaded file to the terminal in various manners;
  • the IMS network capability is introduced in the file downloading process, and the implementation method of downloading the service information such as the acquisition address information of the content description information is clarified, and the flexibility and controllability of the file downloading are improved, and the file downloading process is further improved. .
  • Embodiment 4 of the present invention provides a file repair implementation method.
  • the flow of the method is shown in Figure 4.
  • the file repair server and the media server in the fourth embodiment are combined, and the file repair service is combined.
  • the server and the media server are externally represented as a media server in FIG.
  • the terminal After the FLUTE session is established for the file download service, and the terminal uses the FLUTE session to receive the downloaded data (that is, after the FLUTE session established for the file download service ends), the terminal finds that the received file download data is incomplete, and the terminal responds according to the download service (That is, the address information (such as the HTTP URI address information) of the file repair server carried in the download service request based on the terminal initiated file download service or the download service request (that is, the download service request based on the network side initiated file download service) sends an HTTP request to the server.
  • the file repair server ie, the media server in FIG. 4) sends an HTTP request. If the file repair server sends repair data to the terminal according to the received HTTP request, the subsequent steps are not performed, if the file repair server sends the terminal to the terminal.
  • To repair the FLUTE session information corresponding to the data go to step 4-1.
  • Step 4-1 The terminal sends a SIP Re-invite message, and performs FLUTE session information negotiation with the service control function device.
  • the SDP Offer in the SIP Re-invite message may be set according to the FLUTE session information corresponding to the repair data obtained from the file repair server, that is, the terminal needs to respond according to the download service (that is, the download service response based on the terminal initiated file download service) or download.
  • the service request that is, the download service request based on the network side initiates the file download service
  • the address information of the file repair server carried by the repair server is requested by the repair server for the FLUTE session information corresponding to the repair data, and then the SIP Re-invite message is sent.
  • the request URI in the SIP Re-invite message may be set to the PSI of the FLUTE session.
  • the port portion of the m line of the SDP in the SIP Re-invite message may be set as the FLUTE media transmission channel of the terminal local.
  • SDP c line can be set to the local IP address information of the terminal.
  • Step 4-2 After receiving the SIP Re-invite message, the IMS core receives the message The SIP Re-invite message is forwarded to the service control function device. If the service control function device determines to provide the terminal with the repair data in the FLUTE unicast mode, then to step 4-3; if the service control function device determines to provide the terminal with the repair data in FLUTE multicast or broadcast mode, then go to step 4-5.
  • Step 4-3 The service control function device selects a file repair server, and sends a SIP Invite message to the file repair server as a B2B UA (back-to-back user agent).
  • the setting file repair server is set in the media server entity. Go to step 4-4.
  • Step 4-4 After receiving the SIP invite message, the file repair server returns a SIP 200 OK message to the service control function device, and goes to step 4-5.
  • 81? 200 0 The message carries 80? ⁇ 8 ⁇ 61".
  • SDP Answer carries the IP address information and port information of the file repair server.
  • SDP Answer carries a specific address of the IP address information and port information of the file repair server.
  • Step 4-5 The service control function device checks the FLUTE session information in the SIP Re-invite message (ie, authorizes), and returns a SIP 200 OK message to the terminal according to the check result, and the SIP 200 OK message sent by the service control function device Carry SDP Answer.
  • SDP Answer carries files to repair the server's IP address information and port information.
  • Step 4-6 After receiving the SIP 200 OK message, the IMS core forwards the SIP 200 OK message to the terminal, that is, the IMS core performs a routing function, and routes the SIP 200 OK message to the terminal.
  • Step 4-7 The terminal receives the repair data according to the information in the SDP Answer of the received SIP 200 OK message.
  • the channel established between the terminal and the file repair server is a FLUTE unicast channel, and the terminal receives the repair data sent by the media server based on the FLUTE unicast channel.
  • the terminal When the terminal provides the repair data by using the FLUTE multicast mode or the FLUTE broadcast mode, the terminal receives the repair data sent by the media server according to the FLUTE session information in the SDP Answer.
  • the fourth embodiment described above can be applied to the file repair process of the first to third embodiments.
  • the fourth embodiment provides the terminal with a specific implementation manner for obtaining the repair data, so that the repair data can be obtained in multiple manners, and the FLUTE-based file download process is improved.
  • Embodiment 5 of the present invention provides a file downloading system in an IMS network.
  • the structure of the system is shown in Figure 5.
  • the system of Figure 5 includes: a service control function device 500, a media server 510, and an IMS core 520.
  • the system may further include: downloading one or both of the information providing function device 530, the file repair server, and the reporting server.
  • the file repair server and the report server are not shown in FIG. Both the file repair server and the report server in this embodiment can be disposed in the media server 510.
  • the service control function device 500 is configured to obtain a service identifier of the file download service of the terminal, and perform file download service authorization on the terminal according to the service identifier. If the authorization is passed, the service control function device 500 performs session negotiation with the terminal, and is based on the negotiation. The result provides the terminal with the FLUTE session parameter, or provides the terminal with the FLUTE session parameter and the downloaded service information based on the result of the negotiation. Optionally, if the authorization fails, the service control function device 500 sends a failure indication to the terminal, and the file download process ends.
  • the service control function device 500 may perform the file download service authorization for the terminal.
  • the service control function device 500 determines whether the terminal has the right to perform the file download service.
  • the authorization can also be: Review other permissions, etc.
  • the service control function device 500 can perform file download service authorization according to the subscription information of the user corresponding to the terminal and/or the local policy.
  • a specific example of authorization by a service control function device 500 is: if the service control function device 500 determines that the user has previously subscribed to the file download service, the service control function device 500 determines that the authorization is passed; otherwise, the service control function device 500 determines that the authorization has failed ( That is, the authorization does not pass).
  • a specific example of authorization by another service control function device 500 is: In the case where the local policy is that a file download service allows all users to access, the service control function device 500 according to the local whether the user subscribes to the file download service or not. The result of the policy authorizing the terminal to download the file is authorized.
  • the service control function device 500 receives the terminal. After the sent FLUTE session parameters, the FLUTE session parameters sent by the terminal are checked, that is, the service control function 500 determines the FLUTE session parameters sent to the terminal based on the FLUTE session parameters sent by the terminal.
  • the service control function device 500 When the service control function device 500 initiates the file download service, the service control function device 500 does not receive the FLUTE session parameter sent by the terminal, and the service control function device 500 directly sends the FLUTE session determined by the terminal for the file download service. parameter.
  • the result of the negotiation of the session negotiation performed by the service control function device 500 with the terminal is usually a negotiation success, that is, the FLUTE session parameter returned by the service control function device 500 to the terminal is a parameter returned to the terminal based on the successful negotiation.
  • the terminal can receive the data sent by the media server according to the FLUTE session parameters it receives, thereby obtaining the file that needs to be downloaded.
  • the negotiation result of the negotiation between the service control function device 500 and the terminal may also be a negotiation failure. When the negotiation fails, the service control function device 500 may return the negotiation failure information to the terminal, so that the terminal does not Will receive the FLUTE session parameters.
  • the service control function device 500 can also determine the download service information for the terminal, and during the session negotiation process, the service control function device 500 sends the download service information to the terminal.
  • the foregoing download service information may be any one or any of a plurality of content description information acquisition address information, a file repair server address information, and a report parameter.
  • the reporting parameter may be: whether any one or any of the reporting, reporting delay, and address information of the reporting server.
  • the information transmitted between the terminal and the service control function device 500 can be transmitted through the SIP-based message, and the information transmitted between the terminal and the service control function device 500 can be carried in the message by using the SDP, or can be carried in the XML manner.
  • a part of the information may be in the SDP manner and another part of the information is carried in the message in the manner of XML; the specific example is as described in the foregoing embodiment.
  • the service control function device 500 can send the authorization result and/or the session negotiation result to the media server 510 to control whether the media server 510 provides files for the terminal and how to provide the terminal. File.
  • the service control function device 500 may perform session negotiation with the terminal, and send a FLUTE session parameter of the repair data to the terminal according to the result of the negotiation, so that the terminal negotiates according to the session.
  • the FLUTE session parameter of the repair data in the result receives the repair data.
  • the service control function device 500 is an execution point for controlling the file download service, and the service control function device 500 performs file download service control, such as file download service for the terminal, and session negotiation (including media server selection, etc.). Wait for control.
  • file download service control such as file download service for the terminal, and session negotiation (including media server selection, etc.). Wait for control.
  • the media server 510 is configured to send a file corresponding to the file download service to the terminal based on the result of the negotiation.
  • the media server 510 can obtain the results of the session negotiation from the service control function device 500 and/or the terminal. For example, after receiving the FLUTE session parameter sent by the service control function device 500, the media server 510 provides the file corresponding to the file download service to the terminal according to the FLUTE session parameter. For example, after receiving the notification information of the authorization failure sent by the service control function device 500, the media server 510 does not provide the file corresponding to the file download service to the terminal according to the notification.
  • the media server 510 also receives the FLUTE session parameters of the repair data sent by the service control function device 500. At this time, the media server 510 can send the repair data to the terminal according to the FLUTE session parameters of the repair data.
  • the IMS core 520 is configured to route information transmitted between the service control function device 500 and the terminal. For example, the IMS core 520 routes SIP signaling transmitted between the terminal and the service control function.
  • the download information providing function device 530 is configured to send content description information of the file to the terminal.
  • the download information providing function device 530 can transmit the content description information of the file to the terminal after receiving the request from the terminal.
  • file repair server configured to provide repair data to the terminal based on the HTTP connection after receiving the HTTP-based repair request sent by the terminal; or provide the terminal with the FLUTE session parameter of the repair data, so that the terminal receives the parameter according to the FLUTE session parameter Fix the data. That is, file repair
  • the server can directly provide repair data to the terminal, and can also redirect the terminal to other servers that can provide repair data to the terminal, so that the terminal can obtain repair data from other servers.
  • a specific example of the file repair server directly providing repair data to the terminal is: After receiving the HTTP-based repair request sent by the terminal, the file repair server directly provides repair data to the terminal based on the HTTP connection.
  • a specific example of the file repair server redirecting the terminal to provide repair data for the terminal is: After receiving the HTTP-based repair request sent by the terminal, the file repair server provides the terminal with the FLUTE session parameter of the repair data, so that the terminal receives the The FLUTE session parameter of the repair data receives the repair data sent by the media server.
  • the terminal may directly receive the repair data sent by the media server through unicast, multicast, or broadcast according to the FLUTE session parameter of the repair data, or may also receive the repair data according to the received data.
  • the repair data sent by the media server by unicast, multicast or broadcast is received according to the FLUTE session parameter in the result of the session negotiation.
  • the reporting server is configured to receive file download information sent by the terminal.
  • the reporting server can manage the downloaded file by using the received file download information, for example, statistics on data that cannot be successfully downloaded during the file downloading process to determine whether there is a problem with the downloaded file.
  • Embodiments of the present invention do not limit the specific application of file download information.
  • a specific example of the interface between the service control function device 500, the media server 510, the IMS core 520, and the download information providing function device 530 is as follows:
  • the interface between the terminal and the media server 510 can be an II interface.
  • the II interface is used for the terminal to obtain media content (data corresponding to the file of the file download service) from the media server 510, and the media content can be streamed through the II interface by unicast or multicast or broadcast.
  • the II interface is also used to transmit repair data to the terminal in unicast HTTP, unicast FLUTE, or multicast FLUTE mode.
  • the interface between the terminal and the IMS core 520 can be 12 interfaces, and the 12 interface is used for receiving and receiving SIP signaling by the terminal.
  • the interface between the terminal and the download information providing function device 530 may be a 13 interface, and the B interface is used for The content description information is transmitted to the terminal in a unicast manner.
  • the interface between the IMS core 520 and the service control function device 500 may be a 14 interface for forwarding SIP signaling between the IMS core 520 and the service control function device 500.
  • the interface between the IMS core 520 and the media server 510 may be a 15 interface, and the 15 interface is used to forward SIP signaling between the IMS core 520 and the media server 510.
  • the service control function device 500 When the service control function device 500, the media server 510, the IMS core 520, and the download information providing function device 530 are applied in different networks, they may be set in different network entities as needed.
  • One specific example is shown in FIG. 6:
  • Figure 6 is a 3GPP MTV architecture diagram.
  • the service control function device 500 can be set in the SCF/receipt report, the media server 510 is set in the MDF (media distribution function), and the download information providing function device 530 is set in the SSF (service selection function).
  • the file repair server and the escalation server can also be set in the MDF (Media Distribution Function).
  • the configuration of the service control function device 500 in this embodiment may be the configuration of the network device described in the sixth embodiment.
  • the fifth embodiment of the present invention introduces the file download service in the file downloading by setting the service control function device 500, so that the file download process can be controlled by the service control function device 500.
  • the service control function device 500 uses the service identifier of the file download service to the terminal.
  • the file download service authorization is performed, and the management of the file download is further enhanced.
  • the service control function device 500 enables the media server to provide the downloaded file to the terminal in various manners through session negotiation with the terminal.
  • the IMS network capability was introduced in the process, and the operations of downloading information providing functions, reporting servers, and file repair servers in the network were clarified, which improved the flexibility and controllability of file downloading, and further improved the file downloading process.
  • Embodiment 6 of the present invention provides a network device, which is located in an IMS network, and the structure of the network device is as shown in FIG.
  • the network device in FIG. 7 includes: an authorization module 700 and a negotiation module 710.
  • the authorization module 700 is configured to obtain a service identifier of the file download service of the terminal, and perform the file download service authorization on the terminal according to the service identifier, optionally, when the authorization result is an authorization failure, The terminal returns a failure indication.
  • the authorization module 700 authorizes the file download service to the terminal.
  • the authorization module 700 determines whether the terminal has the right to perform the file download service.
  • the authorization can also be: Review other permissions, etc.
  • the authorization module 700 can perform file download service authorization according to the subscription information of the user corresponding to the terminal and/or the local policy.
  • a specific example of authorization by an authorization module 700 is: if the authorization module 700 determines that the user has previously subscribed to the file download service, the authorization module 700 determines that the authorization is passed; otherwise, the authorization module 700 determines that the authorization has failed (ie, the authorization fails).
  • a specific example of authorization by another authorization module 700 is as follows: In the case that the local policy is that a certain file download service allows all users to access, the authorization module 700 performs the terminal according to the local policy regardless of whether the user subscribes to the file download service. The result of the file download service authorization is authorized.
  • the negotiation module 710 is configured to perform session negotiation with the terminal when the authorization result of the authorization module 700 is authorized to pass, and return a FLUTE session parameter to the terminal according to the result of the session negotiation, so that the terminal receives the content sent by the media server according to the received FLUTE session parameter. data.
  • the network device where the negotiation module 710 is located receives the FLUTE session parameter sent by the terminal, and the negotiation module 710 checks the FLUTE session parameter sent by the terminal, that is, the negotiation module 710 sends the message to the terminal. Based on the FLUTE session parameters, determine the FLUTE session parameters sent to the terminal.
  • the network device where the negotiation module 710 is located does not receive the FLUTE session parameter sent by the terminal, and the negotiation module 710 directly determines the FLUTE session parameter for the file download service of the terminal.
  • the negotiation result of the negotiation between the negotiation module 710 and the terminal is usually successful, that is, the FLUTE session parameter returned by the negotiation module 710 to the terminal is a parameter returned to the terminal based on the negotiation success.
  • the terminal can receive the data sent by the media server according to the FLUTE session parameters it receives, thereby obtaining the file that needs to be downloaded.
  • the negotiation result of the negotiation between the negotiation module 710 and the terminal may also be a negotiation failure. When the negotiation fails, the negotiation module 710 may return the negotiation failure information to the terminal, so that the terminal does not receive the FLUTE. Session parameters.
  • the negotiation module 710 may further determine download service information for the terminal. During the session negotiation process, the negotiation module 710 sends the download service information to the terminal. At this time, the negotiation module 710 can include: a first negotiation sub-module 711 and a first transmission sub-module 712.
  • the first negotiation sub-module 711 is configured to perform session negotiation with the terminal when the authorization result of the authorization module 700 is authorized.
  • the session negotiation may be a session negotiation in a case where the terminal initiates a file download service, that is, a session negotiation performed on the basis of the FLUTE session parameter sent by the terminal, and the session negotiation may also be performed when the network device initiates a file download service. Session negotiation, that is, session negotiation based on the FLUTE session parameters sent by the terminal.
  • the specific negotiation process may be as described in the above embodiment, and the description is not repeated here.
  • the first sending sub-module 712 is configured to return a FLUTE session parameter and download service information to the terminal according to the result negotiated by the first negotiation sub-module 711.
  • the foregoing download service information may be any one or any of a plurality of content description information acquisition address information, a file repair server address information, and a report parameter.
  • the reporting parameter may be: whether any one or any of the reporting, reporting delay time, and address information of the reporting server.
  • the information transmitted between the terminal and the network device of the embodiment may be transmitted by using a SIP-based message, and the information transmitted between the terminal and the network device may be carried in the message by using an SDP, or may be carried in an XML manner.
  • a part of the information may be in the SDP manner and another part of the information is carried in the message in an XML manner; the specific example is as described in the foregoing embodiment.
  • the authorization module 700 and the negotiation module 710 can send the authorization result and/or the session negotiation result to the media server to control whether the media server provides the file for the terminal and how to provide the terminal with the file.
  • the negotiation module 710 can also include: a second negotiation sub-module 713 and a second transmission sub-module 714.
  • the second negotiation sub-module 713 is configured to perform session negotiation for the repair data with the terminal according to the FLUTE session parameter of the received repair data after the network device where the network device is located receives the FLUTE session parameter of the repair data.
  • the second sending sub-module 714 is configured to send, according to a result of the negotiation of the second negotiation sub-module 713, a FLUTE session parameter of the repair data to the terminal, so that the terminal repairs the data according to the result of the session negotiation.
  • the FLUTE session parameter receives the repair data.
  • the repair data at this time may be sent by the media server through FLUTE unicast mode, multicast mode or broadcast mode.
  • the network device in this embodiment may include: a first negotiation sub-module 711, a first transmission sub-module 712, a second negotiation sub-module 713, and a second transmission sub-module 714.
  • the network device in this embodiment is an execution point for controlling a file download service, and the network device performs file download service control, such as performing file download service on the terminal, and session negotiation (including media server selection, etc.), etc., to improve The flexibility and controllability of file downloading further improved the file download process.
  • the present invention also provides another set of embodiments.
  • the device naming and the meaning of the nouns in the embodiments of the present invention may be different from the previous set of embodiments, but do not affect the implementation and protection scope of the present invention.
  • Embodiment 1 The service control function entity obtains download service information from the download function entity.
  • the method for obtaining download service information in the network television architecture provided by the first embodiment of the present invention enables the service control function entity to control the download service.
  • the user terminal corresponds to the UE (User Equipment);
  • the service control function entity corresponds to the SCF (Service Control Function);
  • the BMSC corresponding to the download function entity (Broadcast) Multicast Service Centre, Broadcast Multicast Service Center);
  • the user terminal corresponds to the UE (User Equipment); the service control function entity corresponds to the IPTV SCF (Service Control Function); and the download function entity corresponds to the IPTV MF ( Media Functions, or IPTV MDF (Media Delivery Functions);
  • the user terminal corresponds to an OITF (Open IPTV Terminal Function);
  • the service control function entity corresponds to an IPTV control entity; and
  • the download function entity corresponds to a CDF (Content Delivery Function) );
  • the download service information in this embodiment may be a receiving report of the download service, such as the success of the download file, the failure information; or the status information of the download service, such as starting the download, downloading the suspension, and downloading the recovery. Complex, download completed, etc.;
  • the entire process adopts a hypertext transfer protocol, which is not limited to the hypertext transfer protocol, and may also be implemented by RTSP (Real Time Streaming Protocol), Diameter protocol, or SIP (Session Initiation Protocol). Waiting for the way.
  • RTSP Real Time Streaming Protocol
  • Diameter protocol Diameter protocol
  • SIP Session Initiation Protocol
  • the S80 user terminal sends an HTTP POST message to the download function entity, and carries the download service information of the download service, where the information includes information indicating the service control function entity corresponding to the user terminal;
  • the download function entity receives an HTTP POST message from the user terminal, and returns an HTTP 200 OK confirmation.
  • the download function entity extracts the download service information from the HTTP POST message, and parses the information indicating the service control function entity from the information, such as: the identity information of the service control function entity, or the user terminal and the service control function entity are established. Identification information of the service session, etc., the download function entity determines the service control function entity that provides the service for the user terminal according to the information, or the download function entity determines the service control function entity that provides the service for the user according to the locally configured rule;
  • the download function entity sends an HTTP POST message, or a SIP INFO message, or a SIP MESSAGE message to the determined service control function entity by using the download service information transmission channel, and carries the download service information of the download service.
  • the service control function entity receives an HTTP POST message, or a SIP INPO message, or a SIP MESSAGE message, which carries the downloaded service information from the download function entity, and returns an HTTP 200 OK or SIP 200 OK confirmation.
  • the service control function entity can obtain the information of the download status, and can perform flexible service control on the download service, such as performing statistics on the downloaded file, adjusting the download time, adjusting the download fee, and the like.
  • the embodiment applies to the Mobile IPTV architecture and TISPAN IPTV The architecture and OIPF architecture, and the ability to use multiple protocols, expand its scope of application.
  • Embodiment 2 The service control function entity obtains the downloaded service information from the user terminal.
  • the method for obtaining the download service information in the network television architecture provided by the second embodiment of the present invention enables the service control function entity to control the download service.
  • the user terminal corresponds to the UE (User
  • SCF Service Control Functions
  • the user terminal corresponds to the UE (User
  • IPTV SCF Service Control
  • the user terminal corresponds to OITF (Open IPTV)
  • Terminal Function open IPTV terminal function
  • service control function entity corresponds to the IPTV control entity
  • the download service information in this embodiment may be a receiving report of the download service, such as receiving the file successfully, failing the information; or downloading the status information of the service, such as starting the download, downloading the pause, downloading the restore, downloading, and the like;
  • the entire process uses a SIP (Session Initiation Protocol).
  • SIP Session Initiation Protocol
  • S900 firstly, a download service information transmission channel between the user terminal and the service control function entity that is routed through the IMS Core, so that the channel supports the user terminal to send the service information function to the service control function entity;
  • the S90 user terminal sends a SIP INPO message or a SIP MESSAGE message to the IMS Core, and the message carries the download service information of the download service.
  • the IMS Core route sends a SIP INPO message or a SIP MESSAGE message to the service control function entity, where the message carries the download service information of the download service.
  • the service control function entity receives the SIP INPO message SIP MESSAGE message, extracts the download service information, and returns a SIP 200 OK message to the IMS Core route; S904.
  • the IMS Core route returns a SIP 200 OK message to the user terminal.
  • the service control function entity may carry the address of the file repair server in the returned SIP 200 OK message, and the service information providing entity may repair the file.
  • the server initiates a repair file request.
  • the service control function entity directly receives the SIP message from the user terminal through the IMS Core route, and extracts the download service information therefrom. Therefore, the service control function entity can obtain the information of the download status, and can perform flexible service control on the download service, such as performing statistics on the downloaded file, adjusting the download time, adjusting the download fee, and the like. Applicable to Mobile IPTV architecture and TISPAN IPTV architecture and OIPF architecture.
  • Embodiment 3 The service control function entity obtains download service information from the user terminal.
  • the method for obtaining download service information in the network television architecture provided by the third embodiment of the present invention enables the service control function entity to control the download service.
  • the user terminal corresponds to a UE (User Equipment);
  • the service control function entity corresponds to an SCF (Service Control Function);
  • the user terminal corresponds to the UE (User Equipment);
  • the service control function entity corresponds to the IPTV SCF (Service Control Functions);
  • the user terminal corresponds to an OITF (Open IPTV Terminal Function);
  • the service control function entity corresponds to an IPTV control entity;
  • the download service information in this embodiment may be a receiving report of the download service, such as receiving the file successfully, failing the information; or downloading the status information of the service, such as starting the download, downloading the pause, downloading the restore, downloading, and the like;
  • the entire process adopts a hypertext transfer protocol.
  • the specific steps of the method are as follows: S1000. Establish a download service information transmission channel between the user terminal and the service control function entity, so that the channel supports the user terminal to send the service information function to the service control function entity.
  • the S100 user terminal sends an HTTP POST message to the service control function entity by using the download service information transmission channel, where the message carries the download service information of the download service;
  • the service control function entity receives an HTTP POST message from the user terminal, extracts the download service information, and returns an HTTP 200 OK message to the user terminal.
  • the service control function entity may carry the address of the file repair server in the returned HTTP 200 OK message, and the service information providing entity may repair the file.
  • the server initiates a repair file request.
  • the service control function entity receives an HTTP message from the user terminal, and extracts the download service information therefrom. Therefore, the service control function entity can obtain the information of the download status, and can perform flexible service control on the download service, such as statistics on the downloaded file, adjustment of the download time, adjustment of the download fee, and the like. Applicable to Mobile IPTV architecture and TISPAN IPTV architecture and OIPF architecture.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Description

IMS网络中文件下载方法、 装置和系统 本申请要求 2008年 12月 30日递交的申请号为 200810189828.0、以及 2009 年 4月 29日递交的申请号为 200910082784.6的中国专利申请的优先权, 其全 部内容通过引用结合在本申请中。 技术领域
本发明涉及网络通讯技术领域, 具体涉及 IMS网络中文件下载技术。 背景技术
采用 FLUTE (File Delivery over Unidirectional Transport, 文件单向传送) 协议进行文件下载的方法包括: 终端通过短信息或电话等方式获取 FLUTE会话 参数, FLUTE会话参数如传输会话标识、 FLUTE会话目的组播地址以及 FLUTE 会话发送者的源 IP地址等; 之后, 终端根据 FLUTE会话参数接收媒体服务器发 送的数据, 该数据中包括内容描述信息和需要下载的文件; 终端从接收的数据 中获取内容描述信息; 终端根据该内容描述信息从接收到的数据中获得需要下 载的文件。
发明人发现上述现有技术至少存在如下问题: 在 IMS ( IP Multimedia Subsystem, IP多媒体子系统) 中, 文件下载的灵活性和可控性差。 发明内容
本发明实施方式提供的 IMS网络中文件下载方法、 装置和系统, 利用 IMS 网络能力对文件下载进行控制, 提高了文件下载的灵活性和可控性。
本发明实施方式提供的一种 IMS网络中文件下载方法, 包括:
获取终端的文件下载业务的业务标识, 并根据所述业务标识对所述终端进 行所述文件下载业务授权;
如果所述授权通过, 则与所述终端进行会话协商, 并基于所述协商的结果 向所述终端返回 FLUTE会话参数,使所述终端根据所述 FLUTE会话参数接收媒 体服务器发送的数据。
本发明实施方式提供的一种 IMS网络中文件下载系统, 所述系统包括: 业务控制功能装置, 用于获取终端的文件下载业务的业务标识, 并根据所 述业务标识对所述终端进行所述文件下载业务授权, 如果所述授权通过, 则与 所述终端进行会话协商, 并基于所述协商的结果向所述终端返回 FLUTE会话参 数, 使所述终端根据所述 FLUTE会话参数接收媒体服务器发送的数据;
媒体服务器, 用于基于所述 FLUTE会话参数向所述终端发送所述文件下 载业务对应的文件。
本发明实施方式提供的一种网络设备, 位于 IMS网络中, 包括: 授权模块, 用于获取终端的文件下载业务的业务标识, 并根据所述业务标 识对所述终端进行所述文件下载业务授权;
协商模块, 用于在所述授权模块授权结果为授权通过时, 与所述终端进行 会话协商, 基于所述协商的结果向所述终端返回 FLUTE会话参数, 使所述终端 根据所述 FLUTE会话参数接收媒体服务器发送的数据。 附图说明
图 1是本发明实施例一的文件下载方法流程图;
图 2是本发明实施例二的文件下载方法流程图;
图 3是本发明实施例三的文件下载方法流程图;
图 4是本发明实施例四的文件修复方法流程图;
图 5是本发明实施例五的文件下载系统示意图;
图 6是本发明实施例五的文件下载系统的具体应用示意图;
图 7是本发明实施例六的文件下载装置示意图;
图 8为本发明实施例一提供的网络电视架构中下载业务信息的获取方法的 流程图示意图;
图 9为本发明实施例二提供的网络电视架构中下载业务信息的获取方法的 流程图示意图; 图 10为本发明实施例三提供的网络电视架构中下载业务信息的获取方法 的流程图示意图。 具体实施方式
本发明实施例一提供一种 IMS网络中基于 FLUTE协议的文件下载方法, 该 方法的流程如附图 1所示。
图 1中, S100、 获取终端的文件下载业务的业务标识。
本实施例中的文件下载业务是指针对需要向终端提供的一个或者多个下 载文件而设置的业务, 一个文件下载业务对应一个唯一的业务标识。 本实施例 中的一个文件下载业务可以通过多个传输会话来实现, 即一个文件下载业务对 应的文件可以通过多个传输会话发送。
获取终端的文件下载业务的业务标识的方式有多种, 例如, 在由终端发起 文件下载业务时, 终端会向网络侧发送包括有业务标识在内的下载业务请求, 该业务标识可以包括在下载业务请求的 FLUTE会话参数中, 此时, 网络侧可以 从接收到的下载业务请求中获取终端的文件下载业务的业务标识; 再例如, 在 由网络侧发起文件下载业务时, 终端会事先进行文件下载的订阅操作, 这样, 可以在终端订阅文件下载业务对应的文件过程中, 网络侧根据终端发送来的消 息 (如订阅消息等) 确定文件下载业务对应的业务标识。
S110、 根据上述业务标识对终端进行文件下载业务授权, 如果授权通过, 到 S120, 否则, 到 S130。
对终端进行文件下载业务授权可以为: 判断终端是否有权限进行该文件下 载业务。 当然, 该授权也可以为: 对其他权限等进行审核。 该授权过程可以根 据终端对应的用户的签约信息或者本地策略或者签约信息结合本地策略进行。 一个授权的具体例子为: 如果用户事先签约了该文件下载业务, 则授权通过, 否则授权失败 (即授权未通过) 。 另一个授权的具体例子为: 在本地策略是某 个文件下载业务允许所有的用户访问的情况下, 则不论用户是否签约了该文件 下载业务, 则根据该本地策略对终端进行该文件下载业务授权的结果均为授权 通过。
S120、 与终端进行会话协商, 基于会话协商的结果向终端提供 FLUTE会话 参数, 或者基于协商的结果向终端提供 FLUTE会话参数和下载业务信息。
上述会话协商可以为: 在终端向网络侧发送了 FLUTE会话参数的情况下, 对终端发送来的 FLUTE会话参数进行检查,即在终端发送来的 FLUTE会话参数 的基础上确定网络侧向终端发送的 FLUTE会话参数。 上述会话协商也可以为: 在终端没有向网络侧发送 FLUTE会话参数的情况下,直接向终端发送网络侧为 终端进行文件下载业务而确定的 FLUTE会话参数。
上述协商的结果通常为协商成功, 即上述向终端返回的 FLUTE会话参数是 基于协商成功而向终端返回的参数。终端可以根据其接收到的 FLUTE会话参数 接收媒体服务器发送的数据, 从而获取到其需要下载的文件。 在某些特殊情况 下, 上述协商的结果也可以为协商失败, 在协商失败时, 可以向终端返回协商 失败的信息, 从而使终端不会接收到 FLUTE会话参数。
在会话协商过程中, 网络侧还可以为终端确定下载业务信息, 并在会话协 商过程中, 向终端发送下载业务信息。 上述下载业务信息可以为: 内容描述信 息的获取地址信息、 文件修复服务器的地址信息和上报参数中的任意一个或任 意多个。 上述内容描述信息的获取地址信息可以为文件分配表的获取地址信 息, 即文件分配表的存储地址信息。
上述内容描述信息的获取地址信息用于终端获取文件下载业务对应的文 件的内容描述信息, 即终端可以从该内容描述信息的获取地址信息指示的网络 设备处获取文件下载业务对应的文件的内容描述信息。 通过在会话协商过程中 为终端提供内容描述信息的获取地址信息, 为终端获得内容描述信息提供了另 一种实现方式, 且提高了终端获得内容描述信息的灵活性。
上述文件修复服务器的地址信息用于终端向该地址信息指示的文件修复 服务器请求修复数据, 以使终端能够对文件下载业务对应的文件进行修复; 也 就是说, 终端可以利用文件修复服务器的地址信息获取到修复数据, 从而利用 该修复数据对其接收到的文件下载业务对应的文件进行修复。 该文件修复服务 器可以和上述媒体服务器合设, 也可以与上述媒体服务器独立设置, 在实际应 用中, 可以根据具体需求来设置文件修复服务器。
另外, 该地址信息所指示的文件修复服务器可以为终端直接提供修复数 据, 该地址信息所指示的文件修复服务器也可以将终端重定向到能够为终端提 供修复数据的其他服务器处, 使终端从其他服务器处获取修复数据。
该地址信息所指示的文件修复服务器可以为终端直接提供修复数据的一 个具体例子为: 该地址信息所指示的文件修复服务器在接收到终端发送的基于
HTTP的修复请求后, 直接基于 HTTP连接为终端提供修复数据。
该地址信息所指示的文件修复服务器可以为终端直接提供修复数据的另 一个具体例子为: 该地址信息所指示的文件修复服务器接收终端发送的基于 HTTP的修复请求后, 为该终端提供通过单播或者组播或者广播方式发送修复 数据的 FLUTE会话参数,使终端根据接收到的修复数据的 FLUTE会话参数接收 修复数据。 也就是说, 该地址信息所指示的网络设备可以利用 FLUTE协议、 采 用单播或者组播或者广播方式为终端提供修复数据; 例如, 文件修复服务器在 接收到基于 HTTP的修复请求后, 在基于 HTTP的修复响应中提供单播或者组播 或者广播方式为终端提供修复数据对应的 FLUTE会话信息, 该修复响应可以为 HTTP Redirect消息。 修复数据对应的 FLUTE会话信息可以采用 SDP方式或者 XML方式携带在 HTTP Redirect消息中发送给终端, 使终端可以根据 HTTP Redirect消息中携带的 FLUTE会话信息发起 SIP会话, 以与业务控制功能装置进 行修改数据的会话协商,进而根据协商结果中的修改数据的 FLUTE会话信息接 收修复数据。另外, 终端也可以不针对修复数据进行会话协商, 而是根据 HTTP Redirect消息中携带的 FLUTE会话信息直接接收修复数据。 通过在会话协商过 程中为终端提供文件修复服务器的地址信息, 明确了终端获得文件修复服务器 的地址信息的实现方式, 为终端修复文件提供了一种具体的实现方式, 且提高 了终端获得内容描述信息的灵活性。
上报参数用于指示终端上报文件下载信息, 例如, 指示终端上报文件成功 下载的统计情况信息。 上述上报参数可以为: 是否上报、 上报延迟时间和上报 服务器的地址信息中的任意一个或任意多个。
是否上报用于指示终端是否上报文件下载信息; 上报延迟时间用于指示终 端上报文件下载信息的延迟时间, 上报延迟时间可以通过上报定时器来实现; 例如, 在本次文件下载流程结束时触发上报定时器, 在上报定时器的计数值达 到预定值时, 终端上报文件下载信息。
上报服务器的地址信息用于指示终端发送文件下载信息的目的地址, 即指 示终端将文件下载信息发送到哪里。 需要说明的是, 上报服务器的地址信息可 以是媒体服务器的地址信息, 也可以是文件修复服务器的地址信息, 还可以是 独立于媒体服务器和文件修复服务器的地址信息。
通过在会话协商过程中为终端提供上报参数, 明确了终端获得上报参数的 实现方式, 为终端上报文件下载信息提供了一种具体的实现方式, 且提高了终 端上报文件下载信息的灵活性。
上述会话协商过程中终端与网络侧之间传输的信息可以通过基于会话发 起协议 (SIP) 的消息传输, 且上述会话协商过程中终端与网络侧之间传输的 信息可以采用会话描述协议 (SDP) 的方式携带在消息中, 也可以采用可扩展 标记语言(XML) 的方式携带在消息中, 还可以将一部分信息采用 SDP的方式 且另一部分信息采用 XML的方式携带在消息中; 例如, 将 FLUTE会话参数以 SDP的方式、 且将下载业务信息以 XML的方式携带在下载业务应答消息中。
S130、 向终端发送失败指示, 本次文件下载流程结束。 这里的失败指示可 以为授权未通过的指示信息, 也可以为禁止终端进行文件下载的指示信息。
上述实施例一的执行主体可以为网络侧的业务控制功能装置, 业务控制功 能装置可以独立存在, 也可以设置在网络侧的某一网络设备中, 如设置在媒体 服务器所在网络设备中等。
另外需要说明的是, 在实施例一中, 还可以将会话协商的结果发送给媒体 服务器, 例如, 业务控制功能装置将向终端提供的 FLUTE会话参数发送给媒 体服务器, 使媒体服务器可以根据接收到的 FLUTE会话参数向终端提供文件 下载业务对应的文件。 在授权失败时可以通知媒体服务器, 也可以不通知媒体 服务器。 如果通知了媒体服务器, 则媒体服务器会根据该通知明确获知不向终 端提供文件下载业务对应的文件。
本发明实施例一通过弓 I入文件下载业务, 使网络侧便于对文件下载进行管 理 (如计费管理、 授权管理、 以及传输管理等); 通过利用文件下载业务的业 务标识对终端进行文件下载业务授权, 使网络侧进一步加强了对文件下载的管 理; 通过进行会话协商, 使网络侧能够通过多种方式为终端提供下载的文件; 本发明实施例一在文件下载过程中引入了 IMS网络能力,且明确了终端获取内 容描述信息的获取地址信息等下载业务信息的实现方式, 提高了文件下载的灵 活性和可控性, 进一步完善了文件下载过程。
本发明实施例二提供一种基于终端发起文件下载业务的文件下载方法。 该 方法的流程如附图 2所示。
图 2中, 步骤 2-1、 终端发送下载业务请求。 下载业务请求可以为基于 SIP 的下载业务请求, 例如, 下载业务请求可以为 SIP Invite消息。
该下载业务请求中携带有 FLUTE会话参数, 如传输会话标识、 FLUTE会 话目的组播地址信息(可以包含有端口信息)、 FLUTE会话发送者的源 IP地址 、 以及业务标识等。 业务标识可以采用从业务选择发现信息中获取的业务 标识, 或者使用临时移动组标识(Temporary Mobile Group Identity, TMGI)来 表示。 上述 FLUTE会话参数可以通过 SDP方式或者通过 XML方式携带在下 载业务请求中。下载业务请求中的请求 URI (Uniform Resource Identifier, 通用 资源标志符) 可以设置为该 FLUTE会话的 PSI (Public Service Identity, 公共 业务标识)。
下载业务请求中以 SDP方式携带在 SDP Offer (SDP提供) 中的 FLUTE 会话参数的一个具体的例子为:
m=application 12345 FLUTE/UDP 0 //Port部分可能携带目的端口信息 c=IN IP6 <destination multicast address> //FLUTE会话目的组播地址
a=source-filter: <sender unicast address> //FLUTE会话发送者源 IP地址 a=flute tsi:123 //FLUTE会话 Transmission Session ID a=service— id: service— d //业务标识, 具体值参见上面描述 上述 m=application 12345 FLUTE/UDP 0中的 12345即为 Port部分。
步骤 2-2、 IMS核心 (IMS Core) 接收到下载业务请求后, 将下载业务请 求转发给业务控制功能装置, 即 IMS核心执行路由功能,将下载业务请求路由 到业务控制功能装置。 业务控制功能装置可以根据需要设置在某网络设备中, 例 如 , 在 3GPP/TISPAN/OIPF ( 3rd Generation Partnership Project/ Telecommunications and Internet Converged Services and Protocols for Advanced Networking/ Open IPTV Forum,第三代合作伙伴计划 /电信和互联网融合业务及 高级网络协议 /开放式 IPTV论坛) 网络中, 业务控制功能装置可以表现为 SCF (业务控制功能), 即本实施例中的业务控制功能装置可以设置在 3GPP/TISPAN/OIPF网络的业务控制功能实体中。
步骤 2-3、 业务控制功能装置从下载业务请求中获取业务标识, 根据该业 务标识对终端进行文件下载进行授权,并在授权通过后,与终端进行会话协商, 例如, 对下载业务请求中携带的 FLUTE会话参数进行检查(或称授权), 业务 控制功能装置向终端返回下载业务应答。 该下载业务应答中可以携带授权后的 FLUTE会话参数以及下载业务信息。该下载业务应答可以为基于 SIP的下载业 务应答。在下载业务请求为 SIP Invite消息的情况下, 下载业务响应可以为 SIP 200 OK消息。
在对下载业务请求中携带的 FLUTE会话参数进行授权过程中, 业务控制 功能装置可以根据预定策略修改下载业务请求中携带的 FLUTE会话参数, 也 可以不修改下载业务请求中携带的 FLUTE会话参数; 也就是说, 下载业务应 答中携带的 FLUTE会话参数有可能与下载业务请求中携带的 FLUTE会话参数 相同, 也可能与下载业务请求中携带的 FLUTE会话参数相同。
上述下载业务应答中携带的下载业务信息可以包括: 内容描述信息的获取 地址信息、 文件修复服务器的地址信息和上报参数等。 上报参数如是否上报、 上报延迟时间和上报服务器的地址信息等。
如果上述对终端进行文件下载进行授权的结果为授权失败, 则业务控制功 能装置向终端返回错误指示信息, 以使终端获知授权失败。 本实施例中, 业务 控制功能装置向终端返回的错误指示信息的一个具体例子为: 业务控制功能装 置向终端返回 SIP 401 (Unauthorized,未授权)消息,或者 SIP 403 (Forbidden, 禁止) 消息。
上述 FLUTE会话参数以及下载业务信息可以采用 SDP方式或者 XML方 式携带在下载业务应答中; 另外, 上述 FLUTE会话参数可以采用 SDP方式和 XML方式中的一种方式携带在下载业务应答中,而下载业务信息可以采用 SDP 方式和 XML方式中的另一种方式携带在下载业务应答中。
下载业务信息采用 SDP方式携带在下载业务应答中的一个具体例子为: a=content-desc:<URI> //FDT文件地址
a=repair-server-address:<URI> 〃修复 Server地址信息
a=report-indication:TRUE/FALSE //上报指示 (即是否上报) a=backofF-time:value 〃上报延迟时间
a=report-server-address: :<URI> //上报 Server地址,默认为 SCF a=recvonly
上述 FDT (文件分配表)文件地址即内容描述信息的获取地址信息, 也即 FDT的获取地址信息。
上述 report-server-address (上报服务器地址信息) 的属性值可以为 HTTP URI, 也可以为 SIP URI。 上述 repair-server-address (文件修复服务器的地址俨
、, 息)可以是直接提供修复数据的服务器的地址信息, 也可以是提供修复描述 息的服务器的地址信息 (即指向修复描述信息), 终端可以根据该修复描述信 息来获取修复数据。
下载业务信息采用 XML方式携带在下载业务应答中的一个具体例子为:
<?xml version="1.0" encoding="UTF-8"?>
<xs: schema
targetNamespace="urn:3GPP:metadata:2008:IMS-PSS-MBMS:FluteInfon xmlns:xs="http:〃 www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:simpleType name="CondentDescAdress">
<xs:restriction base="xs:string"/>
</xs: simpleType>
<xs:simpleType name="RepairServerAddress">
<xs:restriction
Figure imgf000012_0001
</xs: simpleType>
<xs: simpleType name="ReportIndication">
<xs:restriction base="xs:boolean"/>
</xs: simpleType> <xs: element name="Backof Time" t pe="xs:restriction'7>
<xs:restriction base="xs:integer">
<xs:minLength value="0"/>
<xs:maxLength value="3600"/>
</xs:restriction>
<xs: simpleType name="ReportServerAddress">
<xs:restriction base="xs: string"/>
</xs: simpleType> </xs:schema>
上述 XML Schema (XML模式) 中, 分别通过不同的 XML元素定义了下 载业务信息的携带方式。 具体而言, 通过 CondentDescAdress定义了内容描述 信息的获取地址信息,通过 RepairServerAddress定义了修复服务器的地址信息。 通过 Reportlndication定义了是否上报的指示, 通过 BackoffTime定义了上报延 迟时间, 通过 ReportServerAddress定义了上报服务器的地址信息。 步骤 2-4、 IMS核心接收到下载业务应答后, 将下载业务应答转发给终端。 步骤 2-5、 终端根据接收到的下载业务应答中的内容描述信息的获取地址 信息(如 FDT文件的 HTTP URI地址)获取内容描述信息。例如, 终端根据该 内容描述信息的获取地址信息到下载信息提供功能装置处获取内容描述信息。 下载信息提供功能装置可以设置于 3GPP/TISPAN网络的 SSF(Service Selection Function, 业务选择功能) 实体中, 也可以设置于其他网络设备中, 或者独立 设置。
需要说明的是, 步骤 2-5是可选的, 如果下载业务应答中没有包括内容描 述信息的获取地址信息, 则终端也可以通过其他方式 (如预设置内容描述信息 的获取地址信息等)获得内容描述信息的获取地址信息, 或者终端也可以通过 其他方式获得内容描述信息(如从媒体服务器传输来的数据中获得内容描述信 息)。
步骤 2-6、终端根据接收到的下载业务应答中携带的 FLUTE会话信息启动 文件接收流程, 接收 FLUTE会话对应的数据。
需要说明的是, 步骤 2-5和步骤 2-6之间可以没有先后执行顺序。
在终端完成 FLUTE会话对应的数据的接收操作后, 判断是否存在丢失数 据, 如果存在丢失数据, 则到步骤 2-7。
步骤 2-7、 终端根据接收到的下载业务应答中携带的文件修复服务器的地 址信息从文件修复服务器处获取修复数据, 例如, 终端向文件修复服务器发送 修复数据请求, 修复数据请求中携带有丢失数据的信息, 文件修复服务器根据 修改数据请求中携带的丢失数据的信息向终端发送修复数据。 需要说明的是, 文件修复服务器还可以向终端发送修复数据的内容描述信息或者修改数据的 内容描述信息的获取地址信息, 以便终端可以获取到修复数据的内容描述信 息, 并根据修复数据的内容描述信息进行数据修复。
如果存在上报触发条件 (如上报参数中包含有上报指示和上报延迟时间), 则在上报触发条件满足时(如上报指示表示为上报, 且上报延迟时间的计时值 达到预定值), 到步骤 2-8。 步骤 2-8、 终端向上报服务器上报文件下载信息。
例如, 终端根据接收到的下载业务应答携带的上报参数中的是否上报判断 出需要上报文件下载信息后, 在下载业务应答携带的上报参数中的上报延迟时 间对应的计数值达到预定值时, 终端向上报服务器上报文件下载信息。 终端上 报的文件下载信息可以为: 成功接收的文件列表、 下载时长等。
需要说明的是, 上报延迟时间可以通过上报定时器来实现, 例如, 上报定 时器可以在终端完成 FLUTE会话对应的数据的接收操作后开始计时, 也可以 在判断出没有丢失数据时开始计时或者在终端完成修复数据的计时操作后开 始计时。 在上报定时器的计时值达到上报延迟时间时, 终端向上报服务器上报 文件下载信息。 本实施例不限制针对上报延迟时间开始计时的时刻。
本实施例是以向业务控制功能装置上报文件下载信息为例进行说明的, 即 本实施例中的上报服务器与业务控制功能装置合设。 当然, 也可以单独设置上 报服务器。 上报服务器可以独立于业务控制功能装置, 例如, 上报服务器可以 与媒体服务器等合设。
本发明实施例二通过引入文件下载业务, 使网络侧便于对终端发起的文件 下载进行管理 (如计费管理、 授权管理、 传输管理等); 通过利用文件下载业 务的业务标识对终端进行文件下载业务授权, 使业务控制功能装置能够对文件 下载进行控制管理; 通过业务控制功能装置与终端进行会话协商, 使媒体服务 器能够通过多种方式为终端提供下载的文件; 由此可知, 本发明实施例二在文 件下载过程中引入了 IMS网络能力,明确了终端获取内容描述信息的获取地址 信息等下载业务信息的实现方式, 提高了文件下载的灵活性和可控性, 进一步 完善了文件下载过程。
本发明实施例三提供一种基于网络侧发起文件下载业务的文件下载方法。 该方法的流程如附图 3所示。
图 3中, 步骤 3-1、 业务控制功能装置发送下载业务请求。
业务控制功能装置可以根据终端的订阅发送下载业务请求。 业务控制功能 装置在终端订阅过程中可以利用终端订阅的内容获取订阅的下载业务的业务 标识。
业务控制功能装置在根据订阅触发文件下载业务时, 根据订阅信息中的业 务标识对终端进行文件下载业务授权, 并在授权通过时, 业务控制功能装置发 送下载业务请求。
实施例三中的业务控制功能装置可以根据需要设置在某网络设备中, 例 如, 在 3GPP/TISPAN/OIPF网络中, 业务控制功能装置可以表现为 SCF, 即本 实施例中的业务控制功能装置可以设置在 3GPP/TISPAN/OIPF网络的业务控制 功能实体中。
本实施例中的下载业务请求可以为基于 SIP的下载业务请求, 例如, 下载 业务请求可以为 SIP Invite消息。 本实施例中的下载业务请求中携带有 FLUTE 会话参数和下载业务信息。
下载业务请求中携带的 FLUTE会话参数如传输会话标识、 FLUTE会话目 的组播地址信息(可以包含有端口信息) 以及 FLUTE会话发送者的源 IP地址 信息等。
下载业务请求中携带的下载业务信息可以包括: 内容描述信息的获取地址 信息、 文件修复服务器的地址信息和上报参数等。 上报参数如是否上报、 上报 延迟时间和上报服务器的地址信息等。
上述 FLUTE会话参数以及下载业务信息可以采用 SDP方式或者 XML方 式携带在下载业务请求中; 另外, 上述 FLUTE会话参数可以采用 SDP方式和 XML方式中的一种方式携带在下载业务请求中,而下载业务信息可以采用 SDP 方式和 XML方式中的另一种方式携带在下载业务请求中。
步骤 3-2、 IMS核心接收到下载业务请求后, 将下载业务请求转发给终端, 即 IMS核心执行路由功能, 将下载业务请求路由到终端。
步骤 3-3、 终端接收到下载业务请求后, 向业务控制功能装置返回下载业 务应答。 该下载业务应答可以为基于 SIP的下载业务应答。 在下载业务请求为 SIP Invite消息的情况下, 下载业务响应可以为 SIP 200 OK消息。
下载业务应答中可以携带有下载业务请求中携带的 FLUTE会话参数, 或 者下载业务应答中可以携带有下载业务请求中携带的 FLUTE会话参数和下载 业务信息。
上述 FLUTE会话参数以及下载业务信息可以采用 SDP方式或者 XML方 式携带在下载业务应答中; 另外, 上述 FLUTE会话参数可以采用 SDP方式和 XML方式中的一种方式携带在下载业务应答中,而下载业务信息可以采用 SDP 方式和 XML方式中的另一种方式携带在下载业务应答中。
步骤 3-4、 IMS核心接收到下载业务应答后, 将下载业务应答转发给业务 控制功能装置。
步骤 3-5、 终端根据接收到的下载业务请求中的内容描述信息的获取地址 信息(如 FDT文件的 HTTP URI地址)获取内容描述信息。例如, 终端根据该 内容描述信息的获取地址信息到下载信息提供功能装置处获取内容描述信息。 下载信息提供功能装置可以设置于 3GPP/TISPAN网络的 SSF实体中, 也可以 设置于其他网络设备中, 或者独立设置。
需要说明的是, 如果下载业务请求中没有包括内容描述信息的获取地址信 息, 则终端也可以通过其他方式 (如预设置内容描述信息的获取地址信息等) 获得内容描述信息的获取地址信息, 或者终端也可以通过其他方式获得内容描 述信息 (如从媒体服务器传输来的数据中获得内容描述信息)。
步骤 3-6、终端根据接收到的下载业务请求中携带的 FLUTE会话信息启动 文件接收流程, 接收 FLUTE会话对应的数据。
需要说明的是, 步骤 3-5和步骤 3-6之间可以没有先后执行顺序。
在终端完成 FLUTE会话对应的数据的接收操作后, 终端判断是否存在丢 失数据, 如果存在丢失数据, 则到步骤 3-7。
步骤 3-7、 终端根据接收到的下载业务请求中携带的文件修复服务器的地 址信息从文件修复服务器处获取修复数据, 例如, 终端向文件修复服务器发送 修复数据请求, 修复数据请求中携带有丢失数据的信息, 文件修复服务器根据 修改数据请求中携带的丢失数据的信息向终端发送修复数据。 需要说明的是, 文件修复服务器还可以向终端发送修复数据的内容描述信息或者修改数据的 内容描述信息的获取地址信息, 以便终端可以获取到修复数据的内容描述信 息, 并根据修复数据的内容描述信息进行数据修复。
如果存在上报触发条件, 则在上报触发条件满足时, 到步骤 3-8。
步骤 3-8、 终端向上报服务器上报文件下载信息。
例如, 终端根据接收到的下载业务请求携带的上报参数中的是否上报判断 出需要上报文件下载信息后, 在下载业务请求携带的上报参数中的上报延迟时 间对应的计数值达到预定值时, 终端向业务控制功能装置上报文件下载信息。 终端上报的文件下载信息可以为: 成功接收的文件列表、 下载时长等。
需要说明的是, 实施例三中的上报延迟时间可以通过上报定时器来实现, 例如, 上报定时器可以在终端完成 FLUTE会话对应的数据的接收操作后开始 计时, 也可以在判断出没有丢失数据时开始计时或者在终端完成修复数据的计 时操作后开始计时。 在上报定时器计时值达到上报延迟时间时, 终端向上报服 务器上报文件下载信息。 本实施例不限制针对上报延迟时间开始计时的时刻。
本实施例是以向业务控制功能装置上报文件下载信息为例进行说明的, 即 具体的本实施例中的上报服务器可以与业务控制功能装置合设实体。 当然, 也 可以单独设置上报服务器。 上报服务器可以独立于业务控制功能装置, 例如, 上报服务器也可以与媒体服务器等合设。
本发明实施例三通过引入文件下载业务, 使网络侧便于对终端发起的文件 下载进行管理 (如计费管理、 授权管理、 以及传输管理等); 通过利用文件下 载业务的业务标识对终端进行文件下载业务授权, 使业务控制功能装置能够对 文件下载进行控制管理; 通过业务控制功能装置与终端进行会话协商, 使媒体 服务器能够通过多种方式为终端提供下载的文件; 由此可知, 本发明实施例二 在文件下载过程中引入了 IMS网络能力,明确了终端获取内容描述信息的获取 地址信息等下载业务信息的实现方式, 提高了文件下载的灵活性和可控性, 进 一步完善了文件下载过程。
本发明实施例四提供一种文件修复实现方法。该方法的流程如附图 4所示。 本实施例四中的文件修复服务器与媒体服务器合设, 且合设的文件修复服 务器与媒体服务器在图 4中对外表现为媒体服务器。
针对文件下载业务建立 FLUTE会话,且终端利用该 FLUTE会话接收完成 下载数据后(即针对文件下载业务建立的 FLUTE会话结束后), 终端发现接收 到的文件下载数据不完整, 终端根据下载业务应答(即基于终端发起文件下载 业务的下载业务应答)或下载业务请求(即基于网络侧发起文件下载业务的下 载业务请求) 中携带的文件修复服务器的地址信息 (如 HTTP URI地址信息) 发送 HTTP请求向文件修复服务器(即图 4中的媒体服务器)发送 HTTP请求, 如果文件修复服务器根据接收到的 HTTP请求向终端发送修复数据, 则不再进 行后续描述的步骤, 如果文件修复服务器向终端发送的是修复数据对应的 FLUTE会话信息, 则到步骤 4-1。
步骤 4-1、 终端发送 SIP Re-invite消息, 与业务控制功能装置进行 FLUTE 会话信息协商。 SIP Re-invite消息中的 SDP Offer可以根据从文件修复服务器处 获取的修复数据对应的 FLUTE会话信息设置, 即终端需要先根据下载业务应 答(即基于终端发起文件下载业务的下载业务应答) 或下载业务请求(即基于 网络侧发起文件下载业务的下载业务请求) 中携带的文件修复服务器的地址信 息向修复服务器请求了修复数据对应的 FLUTE 会话信息之后, 再发送 SIP Re-invite消息。
需要说明的是, 如果终端从文件修复服务器处获取的是以组播或广播方式 发送修复数据对应的 FLUTE会话信息时, 则 SIP Re-invite消息中的请求 URI 可以设置为 FLUTE会话的 PSI。如果终端从文件修复服务器处获取的是以单播 方式发送修复数据对应的 FLUTE会话信息时, 则 SIP Re-invite消息中的 SDP 的 m行的端口部分可以设置为终端本地的 FLUTE媒体传送通道的端口, SDP 的 c行可以设置为终端本地的 IP地址信息, 一个具体的例子为:
m=application 12345 FLUTE/UDP 0 //Port携带 UE本地的端口信息 c=IN IP6 <destination multicast address> //FLUTE会话 UE的 IP地址信息 步骤 4-2、 IMS核心接收到 SIP Re-invite消息后,将 SIP Re-invite消息转发 给业务控制功能装置。 如果业务控制功能装置确定以 FLUTE单播方式为终端提供修复数据, 则 到步骤 4-3;如果业务控制功能装置确定以 FLUTE组播或广播方式为终端提供 修复数据, 则到步骤 4-5。
步骤 4-3、业务控制功能装置选择文件修复服务器, 并作为 B2B UA (背靠 背用户代理) 向文件修复服务器发送 SIP Invite消息。 在本实施例中, 设定文 件修复服务器设置在媒体服务器实体中。 到步骤 4-4。
步骤 4-4、 文件修复服务器接收到 SIP invite消息后, 向业务控制功能装置 返回 SIP 200 OK消息, 到步骤 4-5。 81? 200 0 消息中携带有80? ^8\¥61"。 SDP Answer中携带文件修复服务器的 IP地址信息和端口信息。 SDP Answer中 携带有文件修复服务器的 IP地址信息和端口信息的一个具体例子为: m=application 23457 FLUTE/UDP 0 //Port携带文件修复服务器本地的端口信息 c=IN IP6 <destination multicast address> //FLUTE会话文件修复服务器的 IP地址 信息
步骤 4-5、 业务控制功能装置对 SIP Re-invite消息中的 FLUTE会话信息进 行检查 (即授权), 并基于检查结果向终端返回 SIP 200 OK消息, 业务控制功 能装置发送的 SIP 200 OK消息中携带有 SDP Answer。 SDP Answer中携带文件 修复服务器的 IP地址信息和端口信息。
步骤 4-6、 IMS核心接收到 SIP 200 OK消息后, 将 SIP 200 OK消息转发给 终端, 即 IMS核心执行路由功能, 将 SIP 200 OK消息路由到终端。
步骤 4-7、 终端根据接收到的 SIP 200 OK消息的 SDP Answer中的信息接 收修复数据。
在采用 FLUTE单播方式为终端提供修复数据时, 终端和文件修复服务器 之间建立的通道为 FLUTE单播通道,终端基于该 FLUTE单播通道接收媒体服 务器发送的修复数据。
在采用 FLUTE组播方式或者 FLUTE广播方式为终端提供修复数据时,终 端通过根据 SDP Answer中的 FLUTE会话信息,接收媒体服务器发送的修复数 据。 上述实施例四可以应用于上述实施例一至三的文件修复过程中。 上述实施例四为终端提供了获取修复数据的具体实现方式, 使获取修复数 据可以通过多种方式实现, 完善了基于 FLUTE的文件下载过程。
本发明实施例五提供一种 IMS网络中的文件下载系统。该系统的结构如附 图 5所示。
图 5中的系统包括: 业务控制功能装置 500、 媒体服务器 510和 IMS核心 520。 可选的, 该系统还可以包括: 下载信息提供功能装置 530、 文件修复服务 器和上报服务器中的任意一个或两个。 图 5中没有示出文件修复服务器和上报 服务器。 本实施例中的文件修复服务器和上报服务器都可以设置在媒体服务器 510中。
业务控制功能装置 500, 用于获取终端的文件下载业务的业务标识, 并根 据业务标识对终端进行文件下载业务授权, 如果授权通过, 则业务控制功能装 置 500与终端进行会话协商,并基于协商的结果向终端提供 FLUTE会话参数, 或者基于协商的结果向终端提供 FLUTE会话参数和下载业务信息。 可选的, 如果授权不通过, 则业务控制功能装置 500向终端发送失败指示, 本次文件下 载过程结束。
业务控制功能装置 500对终端进行文件下载业务授权可以为: 业务控制功 能装置 500判断终端是否有权限进行该文件下载业务。当然,该授权也可以为: 对其他权限等进行审核。 业务控制功能装置 500可以根据终端对应的用户的签 约信息和 /或者本地策略进行文件下载业务授权。一个业务控制功能装置 500授 权的具体例子为: 如果业务控制功能装置 500判断出用户事先签约了该文件下 载业务,则业务控制功能装置 500确定授权通过,否则,业务控制功能装置 500 确定授权失败 (即授权不通过)。 另一个业务控制功能装置 500授权的具体例 子为: 在本地策略是某个文件下载业务允许所有的用户访问的情况下, 则不论 用户是否签约了该文件下载业务, 业务控制功能装置 500根据该本地策略对终 端进行该文件下载业务授权的结果均为授权通过。
在终端发起文件下载业务的情况下, 业务控制功能装置 500在接收到终端 发送来的 FLUTE会话参数后, 对终端发送来的 FLUTE会话参数进行检查, 即业 务控制功能 500在终端发送来的 FLUTE会话参数的基础上确定向终端发送的 FLUTE会话参数。
在业务控制功能装置 500发起文件下载业务的情况下, 业务控制功能装置 500不会接收到终端发送的 FLUTE会话参数,业务控制功能装置 500直接向终端 发送为终端进行文件下载业务而确定的 FLUTE会话参数。
业务控制功能装置 500与终端进行的会话协商的协商结果通常为协商成 功, 即业务控制功能装置 500向终端返回的 FLUTE会话参数是基于协商成功而 向终端返回的参数。终端可以根据其接收到的 FLUTE会话参数接收媒体服务器 发送的数据, 从而获取到其需要下载的文件。 在某些特殊情况下, 业务控制功 能装置 500与终端进行的会话协商的协商结果也可以为协商失败, 在协商失败 时, 业务控制功能装置 500可以向终端返回协商失败的信息, 从而使终端不会 接收到 FLUTE会话参数。
另外, 在会话协商过程中, 业务控制功能装置 500还可以为终端确定下载 业务信息, 并在会话协商过程中, 业务控制功能装置 500向终端发送下载业务 信息。 上述下载业务信息可以为: 内容描述信息的获取地址信息、 文件修复服 务器的地址信息和上报参数中的任意一个或任意多个。 上报参数可以为: 是否 上报、 上报延迟时间和上报服务器的地址信息中的任意一个或任意多个。 内容 描述信息的获取地址信息、 文件修复服务器的地址信息和上报参数的具体作用 如上述实施例中的描述, 在此不再重复说明。
终端与业务控制功能装置 500之间传输的信息可以通过基于 SIP的消息传 输,且终端与业务控制功能装置 500之间传输的信息可以采用 SDP的方式携带在 消息中, 也可以采用 XML的方式携带在消息中, 还可以将一部分信息采用 SDP 的方式且另一部分信息采用 XML的方式携带在消息中;具体例子如上述实施例 的描述。
业务控制功能装置 500 可以将授权结果和 /或会话协商结果发送给媒体服 务器 510, 以控制媒体服务器 510是否为终端提供文件、 以及如何为终端提供 文件。
需要说明的是,业务控制功能装置 500还可以在接收到修复数据的 FLUTE 会话参数后, 与终端进行会话协商, 并基于协商的结果向终端发送修复数据的 FLUTE会话参数, 使终端根据会话协商的结果中的修复数据的 FLUTE会话参 数接收修复数据。
从上述描述可知, 业务控制功能装置 500是对文件下载业务进行控制的执 行点, 业务控制功能装置 500执行文件下载业务控制, 如对终端进行文件下载 业务、 以及会话协商 (包括媒体服务器选择等) 等进行控制。
媒体服务器 510, 用于基于协商的结果向终端发送文件下载业务对应的文 件。媒体服务器 510可以从业务控制功能装置 500和 /或终端处获得会话协商的 结果。例如,媒体服务器 510在接收到业务控制功能装置 500发送来的 FLUTE 会话参数后, 根据该 FLUTE会话参数向终端提供文件下载业务对应的文件。 再例如, 媒体服务器 510在接收到业务控制功能装置 500发送来的授权失败的 通知信息后, 媒体服务器 510根据该通知不向终端提供文件下载业务对应的文 件。
上述媒体服务器 510还会接收到业务控制功能装置 500发送来的修复数据 的 FLUTE会话参数, 此时, 媒体服务器 510可以根据修复数据的 FLUTE会话 参数向终端发送修复数据。
IMS核心 520, 用于对业务控制功能装置 500与终端之间传输的信息进行 路由。 例如, IMS核心 520对终端与业务控制功能之间传输的 SIP信令进行路 由。
下载信息提供功能装置 530, 用于向终端发送文件的内容描述信息。 下载 信息提供功能装置 530可以在接收到终端的请求后, 向终端发送文件的内容描 述信息。
文件修复服务器, 用于在接收终端发送的基于 HTTP的修复请求后, 基于 HTTP连接为终端提供修复数据; 或者, 为终端提供修复数据的 FLUTE会话参 数, 使所述终端根据所述 FLUTE会话参数接收修复数据。 也就是说, 文件修复 服务器可以为终端直接提供修复数据, 也可以将终端重定向到能够为终端提供 修复数据的其他服务器处, 使终端从其他服务器处获取修复数据。
文件修复服务器为终端直接提供修复数据的一个具体例子为: 文件修复服 务器在接收到终端发送的基于 HTTP的修复请求后, 直接基于 HTTP连接为终端 提供修复数据。 文件修复服务器将终端重定向到能够为终端提供修复数据的一 个具体例子为: 文件修复服务器接收终端发送的基于 HTTP的修复请求后, 为 该终端提供修复数据的 FLUTE会话参数, 使终端根据接收到的修复数据的 FLUTE会话参数接收媒体服务器发送的修复数据。
需要说明的是, 终端接收到修复数据的 FLUTE会话参数后, 可以直接根据 修复数据的 FLUTE会话参数接收媒体服务器通过单播、组播或广播方式发送的 修复数据,也可以根据接收到的修复数据的 FLUTE会话参数与业务控制功能装 置 500进行会话协商后, 根据会话协商的结果中的 FLUTE会话参数接收媒体服 务器通过单播、 组播或广播方式发送的修复数据。
上报服务器, 用于接收终端发送来的文件下载信息。 上报服务器可以利用 接收到的文件下载信息对被下载的文件进行管理, 例如, 对文件下载过程中不 能成功下载的数据进行统计, 以判断是否被下载的文件存在问题。 本发明实施 例不限制文件下载信息的具体应用。
上述业务控制功能装置 500、 媒体服务器 510、 IMS核心 520和下载信息 提供功能装置 530之间的接口的一个具体例子为:
终端与媒体服务器 510之间的接口可以为 II接口。 II接口用于终端从媒体 服务器 510处获取媒体内容 (文件下载业务的文件对应的数据), 媒体内容可 以通过单播或组播或广播的方式通过 II接口进行流式传输。当文件修复服务器 设置于媒体服务器中时, II接口还用于以单播 HTTP、 单播 FLUTE、 或者组播 FLUTE方式向终端传输修复数据。
终端与 IMS核心 520之间的接口可以为 12接口, 12接口用于终端收发 SIP 信令。
终端与下载信息提供功能装置 530之间的接口可以为 13接口, B接口用于 以单播方式向终端传输内容描述信息。
IMS核心 520与业务控制功能装置 500之间的接口可以为 14接口, 14接口 用于转发 IMS核心 520和业务控制功能装置 500之间的 SIP信令。
IMS核心 520与媒体服务器 510之间的接口可以为 15接口, 15接口用于转 发 IMS核心 520和媒体服务器 510之间的 SIP信令。
上述业务控制功能装置 500、 媒体服务器 510、 IMS核心 520和下载信息 提供功能装置 530应用在不同的网络中时, 可以根据需要设置在不同的网络实 体中, 一个具体例子如附图 6所示:
图 6为 3GPP MTV架构图。 可以将业务控制功能装置 500设置于 SCF/接 收上报中, 将媒体服务器 510设置于 MDF (媒体分发功能) 中, 将下载信息 提供功能装置 530设置于 SSF (业务选择功能) 中。 另外, 文件修复服务器和 上报服务器也可以设置于 MDF (媒体分发功能) 中。
本实施例中业务控制功能装置 500的结构可以为实施例六中记载的网络设 备的结构。
本发明实施例五通过设置业务控制功能装置 500, 在文件下载中引入文件 下载业务, 使文件下载过程能够被业务控制功能装置 500控制; 业务控制功能 装置 500通过利用文件下载业务的业务标识对终端进行文件下载业务授权, 进 一步加强了对文件下载的管理; 业务控制功能装置 500通过与终端进行会话协 商, 使媒体服务器能够通过多种方式为终端提供下载的文件; 本发明实施例五 在文件下载过程中引入了 IMS 网络能力, 且明确了网络中的下载信息提供功 能、 上报服务器、 以及文件修复服务器等执行的操作, 提高了文件下载的灵活 性和可控性, 进一步完善了文件下载过程。
本发明实施例六提供一种网络设备, 位于 IMS网络中, 该网络设备的结构 如附图 7所示。
图 7中的网络设备包括: 授权模块 700和协商模块 710。
授权模块 700, 用于获取终端的文件下载业务的业务标识, 并根据业务标 识对终端进行所述文件下载业务授权, 可选的, 在授权结果为授权失败时, 向 终端返回失败指示。
授权模块 700对终端进行文件下载业务授权可以为: 授权模块 700判断终 端是否有权限进行该文件下载业务。 当然, 该授权也可以为: 对其他权限等进 行审核。授权模块 700可以根据终端对应的用户的签约信息和 /或者本地策略进 行文件下载业务授权。一个授权模块 700授权的具体例子为:如果授权模块 700 判断出用户事先签约了该文件下载业务,则授权模块 700确定授权通过,否则, 授权模块 700确定授权失败 (即授权不通过)。 另一个授权模块 700授权的具 体例子为: 在本地策略是某个文件下载业务允许所有的用户访问的情况下, 则 不论用户是否签约了该文件下载业务, 授权模块 700根据该本地策略对终端进 行该文件下载业务授权的结果均为授权通过。
协商模块 710, 用于在授权模块 700的授权结果为授权通过时, 与终端进 行会话协商, 基于会话协商的结果向终端返回 FLUTE会话参数, 使终端根据 接收到的 FLUTE会话参数接收媒体服务器发送的数据。
在终端发起文件下载业务的情况下, 协商模块 710所在的网络设备会接收 到终端发送来的 FLUTE会话参数, 协商模块 710对终端发送来的 FLUTE会话参 数进行检查, 即协商模块 710在终端发送来的 FLUTE会话参数的基础上确定向 终端发送的 FLUTE会话参数。
在业务控制功能装置发起文件下载业务的情况下, 协商模块 710所在的网 络设备不会接收到终端发送的 FLUTE会话参数, 协商模块 710直接为终端进行 文件下载业务确定 FLUTE会话参数。
协商模块 710与终端进行的会话协商的协商结果通常为协商成功, 即协商 模块 710向终端返回的 FLUTE会话参数是基于协商成功而向终端返回的参数。 终端可以根据其接收到的 FLUTE会话参数接收媒体服务器发送的数据,从而获 取到其需要下载的文件。 在某些特殊情况下, 协商模块 710与终端进行的会话 协商的协商结果也可以为协商失败, 在协商失败时, 协商模块 710可以向终端 返回协商失败的信息, 从而使终端不会接收到 FLUTE会话参数。
另外, 在会话协商过程中, 协商模块 710还可以为终端确定下载业务信息, 并在会话协商过程中, 协商模块 710向终端发送下载业务信息。 此时, 协商模 块 710可以包括: 第一协商子模块 711和第一发送子模块 712。
第一协商子模块 711, 用于在授权模块 700的授权结果为授权通过时, 与 终端进行会话协商。 这里的会话协商可以是在终端发起文件下载业务情况下的 会话协商, 即在终端发送来的 FLUTE会话参数的基础上进行的会话协商, 该 会话协商也可以是在网络设备发起文件下载业务情况下的会话协商, 即在没有 终端发送来的 FLUTE会话参数的基础上进行的会话协商。 具体协商过程可以 如上述实施例中的描述, 在此不再重复说明。
第一发送子模块 712, 用于根据第一协商子模块 711协商的结果向终端返回 FLUTE会话参数和下载业务信息。
上述下载业务信息可以为: 内容描述信息的获取地址信息、 文件修复服务 器的地址信息和上报参数中的任意一个或任意多个。 上报参数可以为: 是否上 报、 上报延迟时间和上报服务器的地址信息中的任意一个或任意多个。 内容描 述信息的获取地址信息、 文件修复服务器的地址信息和上报参数的具体作用如 上述实施例中的描述, 在此不再重复说明。
终端与本实施例的网络设备之间传输的信息可以通过基于 SIP的消息传输, 且终端与该网络设备之间传输的信息可以采用 SDP的方式携带在消息中, 也可 以采用 XML的方式携带在消息中, 还可以将一部分信息采用 SDP的方式且另一 部分信息采用 XML的方式携带在消息中; 具体例子如上述实施例的描述。
授权模块 700和协商模块 710可以将授权结果和 /或会话协商结果发送给媒 体服务器,以控制媒体服务器是否为终端提供文件、以及如何为终端提供文件。
协商模块 710还可以包括: 第二协商子模块 713和第二发送子模块 714。 第二协商子模块 713, 用于在其所在的网络设备接收到修复数据的 FLUTE 会话参数后, 根据接收到的修复数据的 FLUTE会话参数与终端进行针对修复 数据的会话协商。
第二发送子模块 714, 用于基于第二协商子模块 713的协商的结果向终端 发送修复数据的 FLUTE会话参数, 使终端根据会话协商的结果中的修复数据 的 FLUTE会话参数接收修复数据。 此时的修复数据可以是媒体服务器通过 FLUTE单播方式、组播方式或广播方式发送的。需要说明的是, 本实施例中的 网络设备可以同时包括: 第一协商子模块 711、 第一发送子模块 712、 第二协 商子模块 713和第二发送子模块 714。
本实施例中的网络设备是对文件下载业务进行控制的执行点, 该网络设备 执行文件下载业务控制, 如对终端进行文件下载业务、 以及会话协商 (包括媒 体服务器选择等) 等进行控制, 提高了文件下载的灵活性和可控性, 进一步完 善了文件下载过程。
本发明还提供另一组实施例, 本组实施例中的装置命名以及名词的含义等 都有可能与前一组实施例不同, 但并不影响本发明的实施和保护范围。
实施例一: 业务控制功能实体从下载功能实体获取下载业务信息
本发明实施例一提供的网络电视架构中下载业务信息的获取方法, 能使业 务控制功能实体对下载业务进行控制。
本实施例提供的方法, 在 Mobile IPTV架构中, 用户终端对应 UE (User Equipment,用户终端);业务控制功能实体对应 SCF (Service Control Functions, 业务控制功能实体); 下载功能实体对应的 BMSC (Broadcast Multicast Service Centre, 广播多播服务中心);
本实施例提供的方法, 在 TISPAN IPTV架构中, 用户终端对应 UE (User Equipment, 用户终端); 业务控制功能实体对应 IPTV SCF ( Service Control Functions,业务控制功能实体);下载功能实体对应 IPTV MF (Media Functions, 媒体功能实体), 或者其中的 IPTV MDF (Media Delivery Functions, 媒体分发 功能实体);
本实施例提供的方法, 在 OIPF架构中, 用户终端对应 OITF (Open IPTV Terminal Function,开放 IPTV终端功能);业务控制功能实体对应 IPTV控制实 体; 下载功能实体对应 CDF (Content Delivery Function, 内容传送实体);
本实施例中的下载业务信息可以为下载业务的接收报告, 如下载文件接收 成功, 失败信息; 或是下载业务的状态信息, 如开始下载, 下载暂停, 下载恢 复, 下载完成等;
本实施例中整个过程采用超文本传输协议方式, 当然不仅限于超文本传输 协议, 也可以通过 RTSP (Real Time Streaming Protocol, 实时流传输协议)、 Diameter协议或 SIP (Session Initiation Protocol, 会话初始协议)等方式。 如图
8所示, 该方法具体步骤为:
S800、 首先建立下载功能实体与业务控制功能实体之间的下载业务信息传 送通道, 使该通道支持下载功能实体向业务控制功能实体发送下载业务信息的 能力;
S80 用户终端向下载功能实体发送 HTTP POST消息, 并携带下载业务 的下载业务信息, 该信息中含有指示该用户终端对应的业务控制功能实体的信 息;
5802、下载功能实体接收来自用户终端的 HTTP POST消息,返回 HTTP 200 OK确认;
5803、 下载功能实体从 HTTP POST消息中解出下载业务信息, 并从该信 息中解析出指示业务控制功能实体的信息,如:业务控制功能实体的标识信息, 或用户终端与业务控制功能实体建立业务会话的标识信息等, 下载功能实体根 据这个信息确定为用户终端提供服务的业务控制功能实体, 或者下载功能实体 根据本地配置的规则确定为用户提供服务的业务控制功能实体;
5804、 下载功能实体通过下载业务信息传送通道向已经确定的业务控制功 能实体发送 HTTP POST消息、 或 SIP INFO消息、 或 SIP MESSAGE消息, 并 携带下载业务的下载业务信息;
5805、 业务控制功能实体接收来自下载功能实体的携带有下载业务信息的 HTTP POST消息、 或 SIP INPO消息、 或 SIP MESSAGE消息, 返回 HTTP 200 OK或 SIP 200 OK确认。
本实施例中, 业务控制功能实体能够获取下载状态的信息, 进而能够对下 载业务进行灵活的业务控制, 如对下载的文件进行统计, 下载时间的调整, 下 载资费的调整等,另外,本发明实施例适用于 Mobile IPTV架构和 TISPAN IPTV 架构以及 OIPF架构, 且能够使用多种协议方式, 扩大了其适用范围。 实施例二: 业务控制功能实体从用户终端获取下载业务信息
本发明实施例二提供的网络电视架构中下载业务信息的获取方法, 能使业 务控制功能实体对下载业务进行控制。
本实施例提供的方法, 在 Mobile IPTV架构中, 用户终端对应 UE (User
Equipment,用户终端);业务控制功能实体对应 SCF (Service Control Functions, 业务控制功能实体);
本实施例提供的方法, 在 TISPAN IPTV架构中, 用户终端对应 UE (User
Equipment, 用户终端); 业务控制功能实体对应 IPTV SCF ( Service Control
Functions, 业务控制功能实体);
本实施例提供的方法, 在 OIPF架构中, 用户终端对应 OITF (Open IPTV
Terminal Function,开放 IPTV终端功能);业务控制功能实体对应 IPTV控制实 体;
本实施例中的下载业务信息可以为下载业务的接收报告, 如下载文件接收 成功, 失败信息; 或是下载业务的状态信息, 如开始下载, 下载暂停, 下载恢 复, 下载完成等;
本实施例中整个过程采用 SIP ( Session Initiation Protocol, 会话初始协议) 方式。 如图 9所示, 该方法具体步骤为:
S900、 首先建立经过 IMS Core路由的, 用户终端与业务控制功能实体之 间的下载业务信息传送通道, 使该通道支持用户终端向业务控制功能实体发送 下载业务信息的能力;
S90 用户终端向 IMS Core路由发送 SIP INPO消息或 SIP MESSAGE消 息, 该消息携带下载业务的下载业务信息;
5902、 IMS Core 路由向业务控制功能实体发送 SIP INPO 消息或 SIP MESSAGE消息, 该消息携带下载业务的下载业务信息;
5903、业务控制功能实体收到 SIP INPO消息 SIP MESSAGE消息, 从中取 出下载业务信息, 向 IMS Core路由返回 SIP 200 OK消息; S904、 IMS Core路由向用户终端返回 SIP 200 OK消息。
本实施例中的下载业务信息, 如果是下载业务信息中含有接收失败的文 件,则业务控制功能实体可以在返回的 SIP 200 OK消息中携带文件修复服务器 的地址, 业务信息提供实体可以向文件修复服务器发起修复文件请求。
本发明实施例二提供的网络电视架构中下载业务信息的获取方法, 业务控 制功能实体通过 IMS Core路由直接接收来自用户终端的 SIP消息, 并从中取 出下载业务信息。 因此, 业务控制功能实体就能够获取下载状态的信息, 进而 能够对下载业务进行灵活的业务控制, 如对下载的文件进行统计, 下载时间的 调整, 下载资费的调整等, 另外, 本发明实施例适用于 Mobile IPTV架构和 TISPAN IPTV架构以及 OIPF架构。
实施例三: 业务控制功能实体从用户终端获取下载业务信息
本发明实施例三提供的网络电视架构中下载业务信息的获取方法, 能使业 务控制功能实体对下载业务进行控制。
本实施例提供的方法, 在 Mobile IPTV架构中, 用户终端对应 UE (User Equipment,用户终端);业务控制功能实体对应 SCF (Service Control Functions, 业务控制功能实体);
本实施例提供的方法, 在 TISPAN IPTV架构中, 用户终端对应 UE (User Equipment, 用户终端); 业务控制功能实体对应 IPTV SCF (Service Control Functions, 业务控制功能实体);
本实施例提供的方法, 在 OIPF架构中, 用户终端对应 OITF (Open IPTV Terminal Function,开放 IPTV终端功能);业务控制功能实体对应 IPTV控制实 体;
本实施例中的下载业务信息可以为下载业务的接收报告, 如下载文件接收 成功, 失败信息; 或是下载业务的状态信息, 如开始下载, 下载暂停, 下载恢 复, 下载完成等;
本实施例中整个过程采用超文本传输协议方式。 如图 10所示, 该方法具 体步骤为: S1000、 建立用户终端与业务控制功能实体之间的下载业务信息传送通道, 使该通道支持用户终端向业务控制功能实体发送下载业务信息的能力;
S100 用户终端通过下载业务信息传送通道向业务控制功能实体发送 HTTP POST消息, 该消息携带下载业务的下载业务信息;
S1002、业务控制功能实体接收来自用户终端的 HTTP POST消息, 从中取 出下载业务信息, 向用户终端返回 HTTP 200 OK消息。
本实施例中的下载业务信息, 如果是下载业务信息中含有接收失败的文 件,则业务控制功能实体可以在返回的 HTTP 200 OK消息中携带文件修复服务 器的地址, 业务信息提供实体可以向文件修复服务器发起修复文件请求。
本发明实施例三提供的网络电视架构中下载业务信息的获取方法, 业务控 制功能实体接收来自用户终端的 HTTP消息,并从中取出下载业务信息。因此, 业务控制功能实体就能够获取下载状态的信息, 从而能够对下载业务进行灵活 的业务控制,如对下载的文件进行统计,下载时间的调整,下载资费的调整等, 另外, 本发明实施例适用于 Mobile IPTV架构和 TISPAN IPTV架构以及 OIPF 架构。
通过以上的实施方式的描述, 本领域的技术人员可以清楚地了解到本发明 可借助软件加必需的硬件平台的方式来实现, 当然也可以全部通过硬件来实 施, 但很多情况下前者是更佳的实施方式。 基于这样的理解, 本发明的技术方 案对背景技术做出贡献的全部或者部分可以以软件产品的形式体现出来, 该计 算机软件产品可以存储在存储介质中, 如 ROM/RAM、 磁碟、 光盘等, 包括若 干指令用以使得一台计算机设备(可以是个人计算机, 服务器, 或者网络设备 等) 执行本发明各个实施例或者实施例的某些部分所述的方法。
虽然通过实施例描绘了本发明, 本领域普通技术人员知道, 本发明有许多 变形和变化而不脱离本发明的精神, 本发明的申请文件的权利要求包括这些变 形和变化。

Claims

权利要求
1、 一种 IMS网络中文件下载方法, 其特征在于, 包括:
获取终端的文件下载业务的业务标识, 并根据所述业务标识对所述终端进 行所述文件下载业务授权;
如果所述授权通过, 则与所述终端进行会话协商, 并基于所述协商的结果 向所述终端返回 FLUTE会话参数,使所述终端根据所述 FLUTE会话参数接收媒 体服务器发送的数据。
2、 如权利要求 1 所述的方法, 其特征在于, 所述获取终端的文件下载业 务的业务标识包括:
接收终端发送来的携带有业务标识的下载业务请求。
3、 如权利要求 1 所述的方法, 其特征在于, 所述获取终端的文件下载业 务的业务标识包括:
从所述终端的订阅信息中获取所述业务标识。
4、 如权利要求 1所述的方法, 其特征在于, 所述方法还包括:
在所述会话协商过程中, 向所述终端发送内容描述信息的获取地址信息。
5、 如权利要求 4所述的方法, 其特征在于, 所述内容描述信息的获取地 址信息包括: 文件分配表的获取地址信息。
6、 如权利要求 1所述的方法, 其特征在于, 所述方法还包括:
在所述会话协商过程中, 向所述终端发送文件修复服务器的地址信息。
7、 如权利要求 7所述的方法, 其特征在于, 所述方法还包括:
所述文件修复服务器使用 HTTP连接为所述终端提供修复数据; 或者 所述文件修复服务器向所述终端发送修复数据的 FLUTE会话参数, 使所 述终端根据所述修复数据的 FLUTE会话参数接收修复数据。
8、 如权利要求 1至 7中任一权利要求所述的方法, 其特征在于, 所述方 法还包括:
接收所述终端发送来的修复数据的 FLUTE会话参数;
根据所述修复数据的 FLUTE会话参数与所述终端进行针对修复数据的会 话协商, 并基于所述针对修复数据的会话协商的结果向所述终端返回 FLUTE 会话参数, 使所述终端根据接收到的所述 FLUTE会话参数接收修复数据。
9、 如权利要求 1所述的方法, 其特征在于, 所述方法还包括:
在所述会话协商过程中, 向所述终端发送上报参数。
10、 一种 IMS网络中文件下载系统, 其特征在于, 所述系统包括: 业务控制功能装置, 用于获取终端的文件下载业务的业务标识, 并根据所 述业务标识对所述终端进行所述文件下载业务授权, 如果所述授权通过, 则与 所述终端进行会话协商, 并基于所述协商的结果向所述终端返回 FLUTE会话 参数, 使所述终端根据所述 FLUTE会话参数接收媒体服务器发送的数据; 媒体服务器, 用于基于所述 FLUTE会话参数向所述终端发送所述文件下 载业务对应的文件。
11、 如权利要求 10所述的系统, 其特征在于, 所述系统还包括: 下载信息提供功能装置, 用于向所述终端发送所述文件的内容描述信息。
12、 如权利要求 10或 11所述的系统, 其特征在于, 所述系统还包括: 文件修复服务器, 用于在接收所述终端发送的基于 HTTP的修复请求后, 使用 HTTP连接为所述终端提供修复数据; 或者, 向所述终端发送修复数据的 FLUTE会话参数。
13、 一种网络设备, 位于 IMS网络中, 其特征在于, 所述网络设备包括: 授权模块, 用于获取终端的文件下载业务的业务标识, 并根据所述业务标 识对所述终端进行所述文件下载业务授权;
协商模块, 用于在所述授权模块授权结果为授权通过时, 与所述终端进行 会话协商, 基于所述协商的结果向所述终端返回 FLUTE会话参数, 使所述终 端根据所述 FLUTE会话参数接收媒体服务器发送的数据。
14、 如权利要求 13所述的网络设备, 其特征在于, 所述协商模块包括: 第一协商子模块, 用于在所述授权模块授权结果为授权通过时, 与所述终 端进行会话协商;
第一发送子模块, 用于根据所述第一协商子模块协商的结果向终端返回 FLUTE会话参数和下载业务信息;所述下载业务信息包括: 内容描述信息的获 取地址信息、 文件修复服务器的地址信息和上报参数中的任意一个或多个。
15、 如权利要求 13或 14所述的网络设备, 其特征在于, 所述协商模块包 括:
第二协商子模块, 用于在其所在的网络设备接收到终端发送来的修复数据 的 FLUTE会话参数后,根据所述修复数据的 FLUTE会话参数与所述终端进行 针对修复数据的会话协商;
第二发送子模块, 用于根据所述第二协商子模块协商的结果向所述终端返 回 FLUTE会话参数,使所述终端根据接收到的所述 FLUTE会话参数接收修复数 据。
PCT/CN2009/076235 2008-12-30 2009-12-30 Ims网络中文件下载方法、装置和系统 WO2010075785A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200810189828.0 2008-12-30
CN2008101898280A CN101771662B (zh) 2008-12-30 2008-12-30 网络电视架构中下载业务信息的获取方法、装置及系统
CN200910082784A CN101877641B (zh) 2009-04-29 2009-04-29 Ims网络中文件下载方法、装置和系统
CN200910082784.6 2009-04-29

Publications (1)

Publication Number Publication Date
WO2010075785A1 true WO2010075785A1 (zh) 2010-07-08

Family

ID=42309827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/076235 WO2010075785A1 (zh) 2008-12-30 2009-12-30 Ims网络中文件下载方法、装置和系统

Country Status (1)

Country Link
WO (1) WO2010075785A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107196986A (zh) * 2016-03-15 2017-09-22 中国移动通信集团江苏有限公司 一种重定向方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155353A (zh) * 2006-05-13 2008-04-02 华为技术有限公司 一种用于多媒体广播和组播业务中的下载分发方法
CN101232502A (zh) * 2008-03-03 2008-07-30 华为技术有限公司 一种媒体流下载方法、系统及装置
CN101243675A (zh) * 2005-06-27 2008-08-13 诺基亚公司 用于动态丰富媒体场景的传送机制
US20080253545A1 (en) * 2000-12-29 2008-10-16 Cisco Technology, Inc. Method and System for Real-Time Insertion of Services During a Call Session Over a Communication Network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080253545A1 (en) * 2000-12-29 2008-10-16 Cisco Technology, Inc. Method and System for Real-Time Insertion of Services During a Call Session Over a Communication Network
CN101243675A (zh) * 2005-06-27 2008-08-13 诺基亚公司 用于动态丰富媒体场景的传送机制
CN101155353A (zh) * 2006-05-13 2008-04-02 华为技术有限公司 一种用于多媒体广播和组播业务中的下载分发方法
CN101232502A (zh) * 2008-03-03 2008-07-30 华为技术有限公司 一种媒体流下载方法、系统及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107196986A (zh) * 2016-03-15 2017-09-22 中国移动通信集团江苏有限公司 一种重定向方法及装置
CN107196986B (zh) * 2016-03-15 2021-04-27 中国移动通信集团江苏有限公司 一种重定向方法及装置

Similar Documents

Publication Publication Date Title
US10277651B2 (en) Session control for media stream transmission
CN101573943B (zh) 媒体频道管理
KR101809124B1 (ko) Http 서버들을 이용하는 mbms 파일 수리를 위한 ip 멀티미디어 서브시스템 및 방법
US8307049B2 (en) Method and device for obtaining media description information of IPTV services
JP4932906B2 (ja) Imsアーキテクチャ・ネットワークにおけるipサービスに渡ってテレビジョンにアクセスするためのシステム
EP2091182A1 (en) Method and system for providing multicast service
WO2009117919A1 (zh) 一种内容点播业务的建立方法、系统和装置
WO2009024092A1 (fr) Procédé et système permettant la commande d&#39;autorisation de ressource de service
US20090244255A1 (en) Method, system and apparatus for multi-terminal communication
WO2008037220A1 (fr) Procédé, système et dispositif pour autoriser une émission de télévision en direct sur un canal par un réseau
WO2007098682A1 (fr) Procédé permettant d&#39;obtenir un guide de programmes électronique, système pour guide de programmes électronique et unité de mise en service
WO2008098500A1 (fr) Procédé et appareil pour découvrir un service de flux de données multimédia et appareil pour découvrir un service
US9531816B2 (en) Method and apparatus for media transfer between user equipment
WO2011015015A1 (zh) 内容上行方法及内容交付功能实体
WO2009155770A1 (zh) 交互式网络电视系统及其内容推播方法
WO2010028601A1 (zh) 以文件方式传输媒体内容的方法、系统及设备
WO2009049518A1 (fr) Procédé, système et entité d&#39;établissement de session de système de télévision par internet ip
WO2011137718A1 (zh) 控制内容报告行为的方法、装置和系统
WO2010075785A1 (zh) Ims网络中文件下载方法、装置和系统
Shibeshi et al. Using an RTSP Proxy to implement the IPTV Media Function via a streaming server
WO2010022603A1 (zh) 附着到对等网络及获取iptv内容的方法、系统和装置
WO2009024053A1 (fr) Procédé et système pour transférer un message de découverte d&#39;opération et entité fonctionnelle pour une découverte d&#39;opération
WO2008098504A1 (fr) Procédé et système pour fournir un service multidiffusion et dispositif pour fournir un paramètre de service multidiffusion
CN101877641B (zh) Ims网络中文件下载方法、装置和系统
WO2008122246A1 (fr) Procédé et système servant à découvrir des affaires multimédias en mode continu

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: 09836072

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09836072

Country of ref document: EP

Kind code of ref document: A1