WO2011029331A1 - 一种录制节目的方法、多媒体系统和网络侧设备 - Google Patents

一种录制节目的方法、多媒体系统和网络侧设备 Download PDF

Info

Publication number
WO2011029331A1
WO2011029331A1 PCT/CN2010/074232 CN2010074232W WO2011029331A1 WO 2011029331 A1 WO2011029331 A1 WO 2011029331A1 CN 2010074232 W CN2010074232 W CN 2010074232W WO 2011029331 A1 WO2011029331 A1 WO 2011029331A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
recording
task
program
scheduling
Prior art date
Application number
PCT/CN2010/074232
Other languages
English (en)
French (fr)
Inventor
徐权
王印龙
熊勤
王德超
马忠成
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP10814933.7A priority Critical patent/EP2466880A4/en
Priority to RU2012112905/07A priority patent/RU2515470C2/ru
Priority to US13/395,882 priority patent/US9282278B2/en
Publication of WO2011029331A1 publication Critical patent/WO2011029331A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/76—Television signal recording
    • H04N5/78—Television signal recording using magnetic recording
    • H04N5/782—Television signal recording using magnetic recording on tape
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
    • H04N21/23103—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion using load balancing strategies, e.g. by placing or distributing content on different disks, different memories or different servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
    • H04N21/23116—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion involving data replication, e.g. over plural servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
    • H04N21/2747—Remote storage of video programs received via the downstream path, e.g. from the server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/433—Content storage operation, e.g. storage operation in response to a pause request, caching operations
    • H04N21/4334—Recording operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
    • H04N21/4622—Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/633—Control signals issued by server directed to the network components or client
    • H04N21/6332—Control signals issued by server directed to the network components or client directed to client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/65—Transmission of management data between client and server
    • H04N21/654—Transmission by server directed to the client
    • H04N21/6543—Transmission by server directed to the client for forcing some client operations, e.g. recording

Definitions

  • the present invention relates to the field of multimedia services such as Internet Protocol Television (IPTV), mobile TV, mobile streaming media, and the like, and particularly relates to a recording program requiring a very high success rate for video and voice recorded programs of a multi-node layout network.
  • IPTV Internet Protocol Television
  • mobile TV mobile TV
  • mobile streaming media and the like
  • IPTV Internet Protocol Television
  • recording program requiring a very high success rate for video and voice recorded programs of a multi-node layout network.
  • the IPTV service connects the set-top box to the broadband network and uses the computer or television as the display terminal to provide users with a broadband value-added service for interactive TV experience and multimedia services.
  • the IPTV system can provide Video on Demand (VOD), Live TV and Time-shifted TV (TSTV) and TV on Demand (TVOD).
  • VOD Video on Demand
  • TSTV Live TV and Time-shifted TV
  • TVOD TV on Demand
  • the IPTV system is a multi-node architecture. In order to balance the concurrent streaming of the user watching the TV, the IPTV system sets a logical node concept management area and a service in the area.
  • the node is configured with an agent server, a magnetic array, and multiple Blades for service service functions, etc.
  • the IPTV system creates channels at the central node and then relays them to other edge nodes.
  • Live TV also known as live broadcast service
  • the live TV is implemented based on the live channel.
  • the service is like the traditional channel TV, the channel switching and the channel selection are realized by the on-screen menu form, enriching the user's video channel; for the operator, the service is attractive
  • IP Internet Protocol
  • TSTV is a kind of liberation of users from traditional program schedules, allowing users to pause and rewind programs while watching live TV programs, and to fast forward to the moment when the live TV is currently playing.
  • the media playback method completely overturns the original way of watching TV, bringing a new viewing experience to the audience.
  • TVOD is an extension of TSTV, which is to make a program on the live channel into a recorded program. After that, and displayed on the electronic program list, to meet the user's ability to randomly click on the missed programs, you can also choose the program a few days ago. Make IPTV become the real "my TV”, get rid of the shackles of time, and adapt to the faster and faster life rhythm of modern people.
  • the technical problem to be solved by the present invention is to provide a method, a multimedia system and a network side device for recording a program with extremely high success rate.
  • the recording fails, it can repair and complement each other between nodes, which greatly reduces the possibility of failure of program recording and provides users with smoother TVOD on-demand service quality.
  • the present invention provides a method for recording a program, which is applied to a multimedia system including a multi-node architecture of a network side device, the method comprising:
  • the network side device After receiving the recording request, the network side device generates a recording task, and sends the recording task to each node that stores the channel specified in the recording task in advance;
  • the node After receiving the recording task, the node performs a section directory system for the channel specified in the recording task, and returns the recording result information to the network side device.
  • the method also includes
  • the network side device When the node performs program recording, the network side device periodically checks the recording result information returned by each node. If the recording result information is found to be recording failure information, it is detected whether a node has set a temporary storage for the channel. a time shifting configuration of the program, if any, transmitting a re-recording task to a node that has a time-shifted configuration of the temporary program for the channel;
  • the node that sets the time-shift configuration of the temporary program to the channel determines whether the time period of the program that failed to record is time-shifted in the node to temporarily store the temporarily stored program. If yes, the program that is the same as the time period of the program that failed to be recorded is extracted from the program temporarily stored in the node as the recorded program of the local node, and then the recording success information is returned to the network side device.
  • the method also includes:
  • the network side device When the node performs the program recording, the network side device periodically checks the recording result information returned by each node, and if the recording result information part is found to be the recording failure information, sends a scheduling task to the node that fails the recording;
  • the node that has failed to record as the destination node schedules the program as the recording program of the local node, and returns the recording success information to the network side device.
  • the multimedia system is a multi-level node architecture, including a first-level node, a second-level node, and a third-level node.
  • the first-level node is connected to a plurality of second-level nodes, and each of the second-level nodes is connected to a plurality of third-level nodes. If the part of the recording result information is found to be a recording failure information, the step of sending a scheduling task to the node that fails to record includes:
  • the network side device first determines whether the first-level node in the recording task is successfully recorded; if the first-level node is not recorded successfully, selecting a secondary node that successfully records as a source node, and generating a program to the first-level node a scheduling task, and sending the scheduling task to the first-level node; if the secondary node is not successfully recorded, selecting a three-level node that successfully records as a source node to generate a scheduling task for scheduling a program to the first-level node And sending the scheduling task to the first level node;
  • the recording of the first-level node is successful, and then determining whether the secondary node in the recording task is successfully recorded, if the recording is not successful, selecting the primary node as the source node to generate a scheduling for scheduling the program to the secondary node a task, and sending the scheduled task to the secondary node;
  • the secondary node in the recording task is successfully recorded, and then it is determined whether the third-level node in the recording task is successfully recorded, if the recording is not successful, the secondary node connected to the tertiary node is selected as the source node. Scheduling a scheduled task of the program to the third-level node, and transmitting the scheduled task to the third-level node.
  • the method further includes: Determining whether the node stores the same program as the program to be scheduled specified in the scheduling task and whether the program size error is within the allowable range. If yes, the scheduling success information is returned to the network side device.
  • the method further includes:
  • the invention also provides a multimedia system, comprising a network side device and a plurality of nodes,
  • the network side device is configured to: generate a recording task after receiving the recording request, and send the recording task to each node that stores the channel specified in the recording task in advance;
  • Each of the nodes is configured to: after receiving the recording task, perform program recording on a channel specified in the recording task, and return recording result information to the network side device.
  • the network side device is further configured to: when the respective nodes perform program recording, periodically check the recording result information returned by each node, and if the recording result information is found to be recording failure information, detect whether there is a node pair
  • the channel sets the time shift configuration of the temporary program, and if so, sends a supplement task to the node that has set the time shift configuration of the temporary program to the channel.
  • the node that sets the time shift configuration of the temporary program to the channel is further configured to: after receiving the re-recording task, determine whether the time period of the program that failed to record is time-shifted and configured to temporarily store the program in the node In the time range, if yes, the program that is the same as the time period of the program that failed to be recorded is extracted from the program temporarily stored in the node as the recorded program of the local node, and then the recording success information is returned to the network side device.
  • the network side device is further configured to: when the respective nodes perform program recording, periodically check the recording result information returned by each node, and if the recording result information part is found to be recording failure information, send a schedule to the node that fails to record. Task
  • the node that fails to record is further configured to: after receiving the scheduled task, schedule a program as a recorded program of the local node to the node that successfully recorded, and return scheduling success information to the network side device.
  • the multimedia system is a multi-level node architecture, including a first-level node, a second-level node, and a third-level node.
  • the first-level node is connected to several second-level nodes, and each second-level node is connected to several third-level nodes.
  • the network side device is configured to: if the recording result information part is found to be recording failure information, send a scheduling task to the node that fails to record as follows:
  • the secondary node that successfully records is selected as the source node to generate a scheduling task for scheduling the program to the primary node, and the scheduling task is sent to the primary node; If the secondary node is not successfully recorded, the third-level node that successfully records is selected as the source node to generate a scheduling task for scheduling the program to the first-level node, and the scheduling task is sent to the first-level node;
  • the recording of the first-level node is successful, and then determining whether the secondary node in the recording task is successfully recorded, if the recording is not successful, selecting the primary node as the source node to generate a scheduling for scheduling the program to the secondary node a task, and sending the scheduled task to the secondary node;
  • the secondary node in the recording task is successfully recorded, and then it is determined whether the third-level node in the recording task is successfully recorded, if the recording is not successful, the secondary node connected to the tertiary node is selected as the source node. Scheduling a scheduled task of the program to the third-level node, and transmitting the scheduled task to the third-level node.
  • the network side device is a content management engine, and each of the nodes includes a media control unit and a plurality of streaming media servers controlled by the media control unit.
  • the media control unit is configured to: after receiving the recording task delivered by the content management engine, send the recording task to a streaming media server that stores a channel specified in the recording task; and receive the streaming media server Sending the result information to the content management engine after the recorded result information is sent;
  • the streaming server storing the channel specified in the recording task is configured to: after receiving the recording task, perform program recording on a channel specified in the recording task, and return recording result information to the media control unit.
  • the media control unit is further configured to: if the controlled streaming server has more than two channels stored in the recording task, send the recording task to the streaming server with the least load.
  • the present invention also provides a network side device, and the network side device is set as: Each node of the determined channel receives the recording result information after the program is recorded on the channel specified in the recording task after receiving the recording task, and returns the recording result information to the network side device.
  • the network side device is further configured to: when the respective nodes perform program recording, periodically check the recording result information returned by each node, and if the recording result information is found to be recording failure information, detect whether there is a node pair
  • the channel sets the time shift configuration of the temporary program, and if so, sends a supplement task to the node that has set the time shift configuration of the temporary program to the channel; receives the time shift configuration of the temporary program set for the channel Recording success information returned by the node;
  • the recording success information is determined by the node that has set the time shift configuration of the temporary program to the channel, and after determining whether the time period of the program that failed to be recorded is in the local time shift configuration Within the time range of the temporary program, if yes, the device that is temporarily stored in the node is extracted and returned from the network side device.
  • the network side device is further configured to: when the respective nodes perform program recording, periodically check the recording result information returned by each node, and if the recording result information part is found to be recording failure information, send a schedule to the node that fails to record. a task; receiving scheduling success information returned by the node that failed to record;
  • the node that has successfully recorded is scheduled to be a recorded program of the local node and returned to the network side device.
  • the network side device is applied to a multimedia system, where the multimedia system is a multi-level node architecture, including a first-level node, a second-level node, and a third-level node, where the first-level node is connected to several second-level nodes, and each second-level node is respectively Connect several third-level nodes,
  • the network side device is configured to: if the recording result information part is found to be recording failure information, send a scheduling task to the recording failure node as follows:
  • selecting a secondary node that successfully records as a source node generates a scheduling task for scheduling a program to the primary node, and sends the scheduling task to the primary node. If the secondary node is not successfully recorded, the third-level node that successfully records is selected as the source node to generate a scheduling task for scheduling the program to the first-level node, and the scheduling task is sent to the first-level node;
  • the recording of the first-level node is successful, and then determining whether the secondary node in the recording task is successfully recorded, if the recording is not successful, selecting the primary node as the source node to generate a scheduling for scheduling the program to the secondary node a task, and sending the scheduled task to the secondary node;
  • the secondary node in the recording task is successfully recorded, and then it is determined whether the third-level node in the recording task is successfully recorded, if the recording is not successful, the secondary node connected to the tertiary node is selected as the source node. Scheduling a scheduled task of the program to the third-level node, and transmitting the scheduled task to the third-level node.
  • the network side device is a content management engine.
  • the method for recording a program, the multimedia system, and the network side device provided by the present invention may cause recording failure for some nodes and successful recording at other nodes. It can realize automatic mutual repair of recorded programs between nodes; when the core module of the IPTV system is one-to-one, the content management engine performs switching between the active and standby servers, or the content management engine server restarts or upgrades within half an hour, and then starts up.
  • IPTV system Before and after the process, the current TVOD recording task is almost unaffected, achieving a very high recording success rate; when the media control unit of each node of the IPTV system performs the active/standby server switching, or the media control unit server restarts for a long time Or upgrade, etc., and then start the running process, can greatly prevent the streaming media server to which it belongs to lose TVOD; IPTV system generally has multiple streaming media servers under the control of the media control unit, including a stream responsible for channel codec Media server. If the streaming server responsible for the channel codec is broken, although it can be switched to another streaming server, the switching will directly cause the TVOD to be unable to record, but the method of recording the program according to the present invention can be guaranteed under the control of the media control unit.
  • TVOD which does not affect the user's on-demand service
  • TVOD recording of the IPTV system fails or misses recording TVOD
  • the TVOD recording can be supplemented within the allowable range of the channel's time-shift duration.
  • FIG. 1 is a schematic diagram of a multimedia system in accordance with an embodiment of the present invention.
  • FIG. 2 is a flow chart of a method of recording a program in accordance with an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for repairing a failure of a recorded program according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of performing TVOD scheduling repair on a central node of an IPTV system according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of performing TVOD scheduling repair on an edge node of an IPTV system according to an embodiment of the present invention
  • FIG. 6 is a process flow diagram of performing TVOD mutual repair in an IPTV system according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of processing for performing TVOD replenishment in an IPTV system according to an embodiment of the present invention.
  • the multimedia system of this embodiment may be an IPTV system, a mobile TV system, or a mobile streaming media.
  • the multimedia system in this embodiment includes a network side device and a plurality of nodes.
  • the network side device may be a content management engine (CME), and each node includes a media control unit. (Media Control Unit, MCU for short) and several Streaming Servers (SS).
  • CME content management engine
  • MCU Media Control Unit
  • SS Streaming Servers
  • One content management engine may manage multiple media control units, and one media control unit may control multiple streaming media servers.
  • the media control unit that selects the media control unit to send the recording request when the content management engine sends the recording request first needs to satisfy the condition that the channel of the program to be recorded is stored on the streaming server controlled by the media control unit, and further may be based on a strategy such as load balancing.
  • a strategy such as load balancing.
  • the smallest streaming server serves as a channel-on-demand service to handle recording tasks.
  • the streaming server that stores the channel of the program to be recorded is also selected, and may be further selected according to a strategy such as load balancing.
  • the content management engine advances the recording task in a chronological order, such as one day in advance.
  • the recording task is sent to the media control unit of each node.
  • the streaming server is responsible for channel codec and real-time recording of the program.
  • the streaming server After receiving the recording task, the streaming server performs program recording on the channel specified in the recording task, and then returns the recording result information to the media control unit, and then the recording result information is returned to the content management engine by the media control unit.
  • the program is successfully recorded, it is saved as a separate file in the corresponding directory of the recorded program.
  • the partial node fails to record, the recorded program is repaired by the mutual nodes; when all the nodes fail to record, the program's supplement is tried again.
  • the content management engine periodically checks the recording result information returned by each node during the process of recording the program in each node. If a part of the node returns the recording failure information, the content management engine sends a scheduling task to the media control unit of the node that failed the recording, and the node that failed the recording is recorded. After receiving the scheduling task, the media control unit schedules the successfully recorded program as the recorded program of the local node to the media control unit of the successfully recorded node, and returns scheduling success information to the content management engine.
  • the content management engine periodically checks the recording result information returned by each node during the process of recording the program in each node. If all the nodes return the recording failure information, the maximum probability of the problem is that the network is unreachable or the channel media stream is interrupted. When major engineering failures occur, the system should generate an alarm so that the operator can timely grasp and solve it.
  • the content management engine detects whether a node has set a time shift configuration of the temporary program for the channel to be recorded. If not, the program recording cannot be repaired, and the result is determined as a failure result; if yes, the channel to be recorded is The media control unit of the node that has set the time shift configuration of the temporary program transmits the supplement task.
  • the media control unit of the node After receiving the re-recording task, the media control unit of the node sends the re-recording task to the streaming server configured to set the time-shift configuration of the temporary program to the channel to be recorded, and then the streaming media server determines the time period of the program that failed to be recorded. Whether it is at the time Within the time range in which the temporarily stored program is configured to be transferred, if yes, the record success information is returned from the program intermediate unit temporarily stored on the streaming server, otherwise the record failure information is returned to the media control unit.
  • any environment or device in the multimedia system of this embodiment is independent, that is, if one device is broken, it does not affect other devices and is also broken.
  • the multimedia system of this embodiment is a multi-node architecture. When a program fails to record on one node, it is likely to be successful in others. When there are more than three nodes, the probability of a program failing to record on all nodes. Far less than one in ten thousand, thus greatly improving the success rate of program recording.
  • the IPTV system includes a network side device, such as a content management engine, and a plurality of nodes, each of which includes a media control unit and a plurality of streaming media servers, and the ⁇ system is a multi-level node architecture.
  • the content management engine of the IPTV system after receiving the recording request, the content management engine of the IPTV system generates a recording task of the TVOD, and sends the recording task to the media control unit in advance, and then the recording control task is sent by the media control unit of the IPTV system to the streaming media server.
  • TVOD recording The content management engine periodically checks the TVOD that failed to record. If some nodes record successfully and some of the nodes fail to record, then the nodes will be repaired according to certain policies. If all nodes fail, the nodes will be re-recorded again.
  • FIG. 2 is a flowchart of a method of recording a program according to an embodiment of the present invention. As shown in FIG. 2, the method for recording a program of the present embodiment includes the following steps:
  • the content management engine receives the recording request.
  • the recording request may be sent to the content management engine as an external system, such as an IPTV service management system or a user set top box or the like.
  • the recording request should include the program information to be recorded.
  • the recording request sent by the IPTV service management system includes the program schedule to be recorded.
  • the program schedule is expressed by the start time and the end time, but the present invention does not limit the manner in which the information is expressed.
  • the recording request may also include deletion information for the recording task, and the content management engine receives the same After the recording request, if the recording task is still in the local recording task queue, delete it and notify the media control unit. After the media control unit receives it, if the recording task is still in the local recording task queue, It is deleted.
  • the recording task may also include modification information of the recording task. After the content management engine receives such a recording request, if the recording task is still in the local recording task queue, it is modified and notified to the media control unit, and the media control is performed. After the unit receives it, if the recording task is still in the local recording task queue, it will be modified.
  • the content management engine preprocesses the recording request, converts the qualified recording request into a recording task, and then adds the recording task table to the content management engine;
  • the recording task includes: TVOD logo (Identity, abbreviated as ID), time shift channel ID, TVOD start time, TVOD end time, and TVOD name.
  • Determining the recording request compliance condition may include verifying the time period of the channel and TVOD in the recording request.
  • the content management engine determines whether the channel of the TVOD to be recorded is configured on the streaming server, and the recording time must be several minutes in advance, and the recording duration is generally within 4 hours.
  • the content management engine sends a recording task to the media control unit.
  • One content management engine may manage multiple media control units, and one media control unit may control multiple streaming media servers.
  • the media control unit selected by the content management engine when the recording request is issued first satisfies the condition that the channel of the TVOD to be recorded is stored on the streaming server controlled by the media control unit, and may be further selected according to a policy such as load balancing.
  • the streaming server selected by the media control unit when the recording task is sent should store the channel of the TVOD to be recorded, and may further be selected according to a strategy such as load balancing.
  • the content management engine advances the recording task in a chronological order, such as one day in advance.
  • the recording task is delivered to the primary server of the media control unit.
  • the media control unit only provides services from the primary server.
  • the content management engine fails, the media control unit can send the received recording task to the streaming service as usual.
  • the streaming media server can normally record TVOD according to the recording task; when the primary server of the media control unit fails, the other servers of the media control unit quickly switch to the primary server, and simultaneously synchronize the TVOD recording task to the memory of the node. Record the task queue.
  • the media control unit maintains a recording task queue of the node, inserts the recording task into the recording task queue of the node, and updates the task index table of the recording task queue of the node;
  • the recording task when the recording task is inserted, the recording task is inserted after the recording task whose time at which the start time of the time period is earlier than the start time of the time period of the recording task and the time interval of the time period of the recording task is the smallest.
  • the recording tasks in the local recording task queue are arranged in order from the front to the back according to the starting time of the TVOD, so as to conveniently select the recording tasks earlier than the current time.
  • the media control unit updates the task index table each time a new recording task is inserted to maintain the local recording task status.
  • the media control unit periodically takes the recording task of the upcoming start time from the local recording task queue (for example, about 2 seconds in advance) and sends it to the streaming server.
  • the streaming media server After receiving the recording task, the streaming media server replies to the media control unit with a response to the recording request.
  • the streaming media server processes the received recording task, and determines whether the channel, the recording start time, and the ending time of the TVOD to be recorded are stored on the streaming media server, that is, the recording start time and the end time are both later than the current time. ), if yes, perform real-time recording; otherwise, directly report the recording failure information to the media control unit.
  • the streaming media server sends the recording result information to the media control unit, and reports the recording result, where the recording result information includes the recording success information or the recording failure information (including the error information);
  • the media control unit After receiving the recording result information, the media control unit sends the recording result information to the content management engine, and periodically reports the execution result of the recording task until receiving the confirmation response of the content management engine.
  • the content management engine receives the recording result information as the recording success information, the recording task is identified as a success state, and then a record (including the full path information of the file accessible when the TVOD is requested) is saved in the TVOD table of the database. , then send the recording result to the media control unit The response confirms that the recording result information has been successfully processed.
  • the content management engine receives the recording result information as the recording failure information, the recording task is identified as a failure state, or if the media control unit is not received after a certain time (for example, 5 minutes) after the recording end time of the recording task is exceeded.
  • the recording result information the content management engine identifies the recording task as a failure state.
  • a major failure of the IPTV system such as a failure of the content management engine due to a long power outage or a media stream input to the IPTV system channel, allows the TVOD recording to fail.
  • the content management engine periodically checks the recording result information sent by the media control unit. If some of the nodes record successfully, some of the nodes fail to record, and then enter the nodes according to a certain policy. Fix; if all nodes fail, re-subscribe each node again.
  • the content management engine periodically (for example, 2 minutes) checks the recording task of the TVOD recording failure in the IPTV system and processes it.
  • the IPTV system of this embodiment is described by taking a three-level node architecture system as an example, and the IPTV system can be extended to a multi-level node architecture system.
  • the primary node is represented as the central node
  • the secondary node is represented as the regional central node
  • the tertiary node is represented as the edge node.
  • the content management engine determines whether the TVOD is successfully recorded on the central node. If the TVOD is unsuccessful, the TVOD is dispatched from other nodes to the central node. The priority of the scheduling is as shown in FIG. 4; if the central node records the task successfully, it is another node. If the recording task fails, the TVOD is hierarchically scheduled to these nodes, and the sequence of the scheduling process is as shown in FIG. 5.
  • the content management engine periodically checks whether the central node has a TVOD. If the central node has a TVOD, it can respond to a recording response to the sender of the recording request, and execute the result of the recording task (success) if the central node is on the central node. There is no TVOD until the recording task times out (for example, 2 hours), and a recording response can be responded to the sender of the recording request, and the execution result (failure) of the recording task is reported. Whether there is a TVOD decision on the central node is to ensure the consistency of the TVOD data in the IPTV system, and all the content must have one on the central node to ensure that the programs that the user can order can be accessed normally. For example, when the user of the edge node is on demand, on the node to which it belongs Missing programs can be guaranteed by redirecting policies to other nodes (at least on the central node).
  • FIG. 3 is a flowchart of a method for repairing a failure of a recorded program according to an embodiment of the present invention. As shown in FIG. 3, the basic workflow for repairing a failed program for each cycle includes the following steps:
  • the content management engine checks the recording task of the TVOD failure in the IPTV system, where the identifiers of the recording tasks in the same time period of the same channel are the same.
  • step 303 Determine the failed TVOD recording task, whether the TVOD fails to be recorded on all the nodes. If the recording fails on the part of the node and the other node records successfully, go to step 303. If all the nodes fail to record, go to step 304.
  • the content management engine first determines whether the central node of the recording task is successfully recorded. If the recording is successful, the regional center node that successfully recorded is preferentially selected. If the recording of the regional central node fails, the edge node that successfully recorded is selected, and the scheduled TVOD is generated to the center. The task of the node, and then make a repair recording;
  • the regional center node of the recording task is successfully recorded. If the recording is not successful, the task of scheduling the TVOD from the central node to the regional central node is generated, and then the repair recording is performed;
  • the edge node of the recording task is successfully recorded. If the recording is not successful, a task of scheduling TVOD from the central node of the area to which the edge node belongs is generated, and then the repair recording is performed.
  • the TVOD fails to record on all the nodes, and it is checked whether the TVOD meets the supplementary condition. If the supplementary condition is met, the process proceeds to step 305, otherwise it is not processed;
  • the re-recording condition is time-shifted configuration on the TVOD channel on the streaming server, and the configured time-shifted content includes the TVOD on the time period that was not recorded.
  • the scheduling mode may be a File Transfer Protocol (FTP), a HyperText Transfer Protocol (HTTP), or a Real Time Streaming Protocol (RTSP).
  • FTP File Transfer Protocol
  • HTTP HyperText Transfer Protocol
  • RTSP Real Time Streaming Protocol
  • the content management engine needs the scheduling of TVOD, first select the FTP download information of the streaming server of the source node, and the FTP download information includes: an IP address, a port number, a username, a password, etc., and then combines the TVOD information on the source node, including the TVOD identifier. , file name and full path of TVOD, etc., as a scheduling task. Afterwards, the content management engine periodically processes the scheduling tasks. When the destination node schedules the TVOD, the original recording task is identified as a successful state.
  • the content management engine of the embodiment processes the scheduling task periodically, and the basic workflow thereof is shown in FIG. 6, and includes the following steps:
  • the content management engine sends a scheduling content request of the TVOD to the media control unit, and sends the scheduling task to the media control unit.
  • the media control unit maintains a local scheduling task queue, and inserts the scheduling task into a local scheduling task queue.
  • the media control unit After receiving the scheduling request, the media control unit returns a response to the scheduling content request to the content management engine.
  • the media control unit selects N (eg, 10) scheduling tasks in the scheduling task queue every cycle, and sends a scheduling content request to the streaming media server of the IPTV system.
  • N eg, 10
  • the streaming media server When receiving the scheduling request of the TVOD, the streaming media server returns a response to the scheduling content request to the media control unit.
  • the streaming media server After receiving the scheduling request of the TVOD, the streaming media server performs an actual copy processing of the TVOD: first determining whether the TVOD file exists in the original TVOD directory, if the TVOD file exists and the size error of the TVOD to be scheduled is Within the allowable range (such as 2%), the TVOD file is considered to exist, and the successful scheduling result information can be directly returned; otherwise, the TVOD file is cleared first, and then the TVOD to the destination node is scheduled from the streaming server of the source node. On the media server;
  • the media control unit After receiving the scheduling result information, the media control unit sends the scheduling result information to the content management engine, and reports the execution result of the scheduling task.
  • the execution result may be that the scheduling is successful, or the scheduling may fail. If the scheduling is successful, the file path information and identification information (such as the file name) of the TVOD file are included in the execution result, and other attribute information such as size, name, and the like of the TVOD file may also be included.
  • the scheduling result information received by the content management engine is the scheduling success information
  • the recording task is identified as a successful state
  • the scheduling result information received by the content management engine is the scheduling failure information
  • the recording task of the TVOD corresponding to the scheduling task is identified as a failure status.
  • the content management engine periodically checks the recording task of the failed TVOD to determine whether to perform the TVOD mutual repair method.
  • the content management engine If TVOD is not successfully recorded on all nodes, it is likely that the content management engine fails to deliver the recording task to the media control unit of each node at some point due to restart or upgrade. At this time, the content management engine initiates the re-recording process.
  • the premise of the re-recording is that the time-shifted configuration of the channel to be recorded needs to be configured on the streaming media server, and the configured time-shifted content includes the TVOD on the time period that cannot be recorded. Copy a copy of TVOD on the content, this process is called a supplement.
  • the content management engine determines which nodes are configured with time-shifted channels, and then issues the re-recording tasks to the nodes configured with the time-shifted channels, and records the recording tasks of these nodes as the supplemental status.
  • the recording tasks of other nodes are directly marked as retry failures.
  • the original recording task is identified as a successful state. If not all nodes are successful, the TVOD inter-node mutual repair process is performed.
  • the basic workflow of the supplemental repair in this embodiment is as shown in FIG. 7, and includes the following steps:
  • the content management engine sends a supplement request to the media control unit, and sends the supplementary task to the media control unit.
  • the media control unit After receiving the replenishment request, the media control unit returns a replenishment request to the content management engine. Response
  • the media control unit assembles the supplemental task information in the supplement request, and sends a supplement request and a backup task to the streaming server of the IPTV system.
  • the streaming media server After receiving the TVOD re-recording request, the streaming media server determines, according to the start time and the ending time of the TVOD of the re-recording task, whether the recorded content of the locally stored TSTV has a recorded program to be supplemented, and if so, Copy the recorded program and make a TVOD file;
  • the streaming media server After performing the TVOD replenishment request, the streaming media server sends the supplemental result information to the media control unit to reply to the execution result of the re-recording task.
  • the media control unit After receiving the supplemental response, the media control unit sends the supplemental result information to the content management engine, and reports the execution result of the supplementary task.
  • the execution result may be a successful re-recording, or it may be a re-recording failure. If the re-recording is successful, the file path information and identification information (such as the file name) of the TVOD file should be included in the execution result, and other attribute information such as size, name, and the like of the TVOD file may also be included.
  • the supplement result information received by the content management engine is the supplement success information
  • send a response to the supplement result to the media control unit confirm that the supplement result message has been successfully processed, and then the content management engine will re-record the status.
  • the recording task of the TVOD is identified as a success status. If the information of the re-recording result received by the content management engine is the information of the re-recording failure, the recording task of the TVOD in the re-recording state is identified as a failure status.
  • the content management engine periodically checks the failed TVOD recording task to determine whether to do it.
  • the recording may fail for some reasons, and the recording may be successful at other nodes, and the automatic mutual repair of the recorded programs between the nodes may be realized;
  • the core module of the IPTV system manages the content one by one
  • the engine performs the main/slave server switchover, or the content management engine server restarts or upgrades within half an hour, and then the current TVOD recording task is almost unaffected before and after the booting process, achieving a very high recording success rate;
  • the media control unit of each node of the IPTV system performs active/standby server switching, or media control
  • the unit server can be restarted or upgraded for a long period of time, and then the process of booting up can greatly prevent the streaming media server to which it belongs from losing TVOD;
  • the IPTV system generally has a plurality of streaming media servers under the control of the media control unit, including a streaming media server responsible for channel codec. If the streaming server responsible for the channel codec is broken, although it can be switched to another streaming server, the switching will directly cause other streaming servers under TVOD to also have the TVOD, without affecting the user's on-demand service;
  • the TVOD recording of the IPTV system fails or the TVOD is missed, the TVOD recording can be supplemented within the allowable range of the time shift of the channel, which is flexible and convenient, and greatly improves the service performance of the IPTV.
  • the method of the present invention is not limited to the structure of the above IPTV system, and can be applied to other system configurations.
  • the inventive method can be applied to the content distribution of digital television,
  • the recording method of the present invention may cause recording failure for some nodes in some nodes, and automatic mutual repair of recorded programs between nodes when recording successfully at other nodes; when the core module of the IPTV system manages content one by one The engine performs the main/slave server switchover, or the content management engine server restarts or upgrades within half an hour, and then the current TVOD recording task is almost unaffected before and after the booting process, achieving a very high recording success rate; When the media control unit of each node of the IPTV system performs the active/standby server switching, or the media control unit server restarts or upgrades for a long time, and then starts the running process, the streaming media server to which it belongs can be greatly prevented. Lost TVOD. When the TVOD recording of the IPTV system fails or the TVOD is missed, the TVOD recording can be supplemented within the allowable range of the time shift of the channel, which is flexible and convenient, and greatly improves the service performance of the IPTV.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Television Signal Processing For Recording (AREA)

Abstract

本发明提供一种录制节目的方法、多媒体系统和网络侧设备。该多媒体系统包括网络侧设备和多个节点，网络侧设备设置为：收到录制请求后生成录制任务, 并将所述录制任务提前下发给存储有所述录制任务中指定的频道的各个节点；各个节点设置为：收到所述录制任务后对所述录制任务中指定的频道进行节目录制，并向所述网络侧设备返回录制结果信息。根据本发明的录制方法，当出现录制失败时，能够在节点间进行互修复和补录，极大的降低了节目录制的失败可能性，提供给用户更流畅的录制节目点播（TVOD）点播服务质量。

Description

一种录制节目的方法、 多媒体系统和网络侧设备
技术领域
本发明涉及交互式网络电视（Internet Protocol Television, IPTV ) 、 手机 电视、移动流媒体等多媒体业务领域， 尤其涉及对于多节点布局网络的视频、 语音的录制节目的需要极高成功率的录制节目的方法、 多媒体系统和网络侧 设备。
背景技术
IPTV业务是将机顶盒接入到宽带网络， 以电脑或者电视机为显示终端， 从而为用户提供一种交互式电视体验和多媒体服务的宽带增值业务。 IPTV系 统可以提供视频点播（ Video on Demand, 简称 VOD )、 直播电视（ Live TV ) 和时移电视（ Time-shifted TV, 简称 TSTV )和录制节目点播（ TV on Demand, 简称 TVOD ) 。 IPTV系统是多节点架构， IPTV系统为了均衡用户收看电视 的并发流， 设置逻辑上的节点概念管理区域和负责区域内的服务， 节点下配 置主备代理（Agent )服务器、 磁阵及多个可供服务服务功能的刀片等。 IPTV 系统在中心节点创建通道， 然后中继到其他边缘节点上。
直播电视， 又称直播服务， 是 IPTV业务地基本业务形式之一。 直播电 视是基于直播频道而实现的， 对用户而言， 该业务如同传统频道电视， 频道 切换和频道选择通过屏幕菜单形式实现， 丰富了用户的收视频道； 对运营商 而言， 该业务是吸引传统电视用户的有效手段， 其运营关键是频道特色； 从 技术实现角度看， 该业务一般釆用互联网协议（ Internet Protocol , IP )组播技 术在 IP网络上传送电视节目信息。
TSTV是一种将用户从传统的节目时刻表中解放出来， 能够让用户在看 直播电视节目的时候， 实现对节目的暂停和后退等操作， 并能够快进到当前 直播电视正在播放的时刻的媒体播放方式， 彻底颠覆了原有看电视的方式， 给观众带来全新的收视体验。
TVOD是 TSTV的扩充， 该业务是将直播频道上一段节目做成录制节目 后， 并在电子节目单上显示， 以满足用户能够随意点播错过的精彩节目， 还 可以选择几天前的节目。使得 IPTV成为真正的"我的电视"，摆脱了时间的束 缚， 顺应现代人越来越快的生活节奏。
目前对节目 （例如， TVOD ) 的录制， 成功率很高， 但也有失败的情况。 对于电信级运营要求， 除频道本身问题或录制节目制作本身不当处， 录制节 目录制失败是不能接受的。排除重大故障， 如掉电、人为停止 IPTV系统的服 务器或流媒体刀片服务或频道无信号等外，在 IPTV正常运行下，在如下情况 下需要尽可能的保证录制节目的成功， 不影响业务： 部分节点由于频道丟码 率过高、 发生较短时间的主备服务器的切换或短时间内的网络故障等。
发明内容
本发明要解决的技术问题是提供一种极高成功率的录制节目的方法、 多 媒体系统和网络侧设备。 当出现录制失败时， 能够在节点间进行互修复和补 录， 极大的降低了节目录制的失败可能性， 提供给用户更流畅的 TVOD点播 服务质量。
为了解决上述技术问题， 本发明提供了一种录制节目的方法， 应用于包 括网络侧设备的多节点架构的多媒体系统， 该方法包括：
网络侧设备收到录制请求后生成录制任务， 并将所述录制任务提前下发 给存储有所述录制任务中指定的频道的各个节点； 以及
所述节点收到所述录制任务后对所述录制任务中指定的频道进行节目录 制， 并向所述网络侧设备返回录制结果信息。
该方法还包括，
在所述节点进行节目录制时， 所述网络侧设备定时检查各个节点返回的 录制结果信息， 若发现所述录制结果信息均为录制失败信息， 则检测是否有 节点对所述频道设置了暂存节目的时移配置， 若有， 则向对所述频道设置了 暂存节目的时移配置的节点发送补录任务； 以及
所述对所述频道设置了暂存节目的时移配置的节点收到所述补录任务 后， 判断录制失败的节目的时间段是否在本节点时移配置所暂存节目的时间 范围内， 若是， 则从本节点暂存的节目中提取与所述录制失败的节目的时间 段相同的节目作为本节点的录制节目， 然后向所述网络侧设备返回录制成功 信息。
该方法还包括：
在所述节点进行节目录制时， 所述网络侧设备定时检查各个节点返回的 录制结果信息， 若发现所述录制结果信息部分为录制失败信息， 则向录制失 败的节点发送调度任务； 以及
作为目的节点的所述录制失败的节点收到所述调度任务后向作为源节点 的录制成功的节点调度节目作为本节点的录制节目， 并向所述网络侧设备返 回录制成功信息。
所述多媒体系统为多级节点架构， 包括一级节点、二级节点和三级节点， 一级节点连接若干个二级节点， 各个二级节点分别连接若干个三级节点， 所述网络侧设备若发现所述录制结果信息部分为录制失败信息， 则向录 制失败的节点发送调度任务的步骤包括：
所述网络侧设备先判断所述录制任务中的一级节点是否录制成功； 若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
所述目的节点收到所述调度任务后， 该方法还包括： 判断本节点是否存储有与所述调度任务中指定的待调度的节目相同的节 目且节目大小误差是否在允许范围内， 若是， 则向所述网络侧设备返回调度 成功信息。
所述各个节点收到所述录制任务后， 该方法还包括：
所述节点将收到的所述录制任务插入到本地录制任务队列中时间段开始 时刻比该录制任务的时间段开始时刻早并且与该录制任务的时间段开始时刻 的时间间隔最小的录制任务之后。
本发明还提供一种多媒体系统， 包括网络侧设备和多个节点，
所述网络侧设备设置为： 收到录制请求后生成录制任务， 并将所述录制 任务提前下发给存储有所述录制任务中指定的频道的各个节点；
所述各个节点设置为： 收到所述录制任务后对所述录制任务中指定的频 道进行节目录制， 并向所述网络侧设备返回录制结果信息。
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息，若发现所述录制结果信息均为录制失败信息， 则检测是否有节点对所述频道设置了暂存节目的时移配置， 若有， 则向对所 述频道设置了暂存节目的时移配置的节点发送补录任务，
所述对所述频道设置了暂存节目的时移配置的节点还设置为： 收到所述 补录任务后， 判断录制失败的节目的时间段是否在本节点时移配置所暂存节 目的时间范围内， 若是， 则从本节点暂存的节目中提取与所述录制失败的节 目的时间段相同的节目作为本节点的录制节目， 然后向所述网络侧设备返回 录制成功信息。
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息 , 若发现所述录制结果信息部分为录制失败信 息， 则向录制失败的节点发送调度任务；
所述录制失败的节点还设置为： 收到所述调度任务后， 向录制成功的节 点调度节目作为本节点的录制节目，并向所述网络侧设备返回调度成功信息。
所述多媒体系统为多级节点架构， 包括一级节点、二级节点和三级节点， 一级节点连接若干个二级节点， 各个二级节点分别连接若干个三级节点， 所述网络侧设备是设置为： 若发现所述录制结果信息部分为录制失败信 息， 则按如下方式向录制失败的节点发送调度任务：
先判断所述录制任务中的一级节点是否录制成功，
若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
所述网络侧设备为内容管理引擎， 所述各个节点分别包括一个媒体控制 单元和若干个由该媒体控制单元控制的流媒体服务器，
所述媒体控制单元设置为： 接收所述内容管理引擎下发的录制任务后将 所述录制任务发送给存储有所述录制任务中指定的频道的流媒体服务器； 收 到所述流媒体服务器发来的录制结果信息后将所述录制结果信息发送给所述 内容管理引擎；
所述存储有所述录制任务中指定的频道的流媒体服务器设置为： 收到所 述录制任务后对所述录制任务中指定的频道进行节目录制， 向所述媒体控制 单元返回录制结果信息。
所述媒体控制单元还设置为： 若所控制的流媒体服务器有两个以上存储 有所述录制任务中指定的频道， 则将所述录制任务发送给负荷最小的流媒体 服务器。
本发明还提供了一种网络侧设备， 所述网络侧设备设置为： 收到录制请 定的频道的各个节点； 接收所述各个节点收到所述录制任务后对所述录制任 务中指定的频道进行节目录制后， 向所述网络侧设备返回录制结果信息。
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息，若发现所述录制结果信息均为录制失败信息， 则检测是否有节点对所述频道设置了暂存节目的时移配置， 若有， 则向对所 述频道设置了暂存节目的时移配置的节点发送补录任务； 接收对所述频道设 置了暂存节目的时移配置的节点返回的录制成功信息；
其中， 所述录制成功信息由所述对所述频道设置了暂存节目的时移配置 的节点收到所述补录任务后， 判断录制失败的节目的时间段是否在本节点时 移配置所暂存节目的时间范围内， 若是， 则从本节点暂存的节目中提取与所 网络侧设备返回。
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息 , 若发现所述录制结果信息部分为录制失败信 息， 则向录制失败的节点发送调度任务； 接收所述录制失败的节点返回的调 度成功信息；
其中， 所述调度成功信息由所述录制失败的节点收到所述调度任务后， 向录制成功的节点调度节目作为本节点的录制节目， 并向所述网络侧设备返 回。
所述网络侧设备应用于多媒体系统， 所述多媒体系统为多级节点架构， 包括一级节点、 二级节点和三级节点， 所述一级节点连接若干个二级节点， 各个二级节点分别连接若干个三级节点，
所述网络侧设备是设置为： 若发现所述录制结果信息部分为录制失败信 息， 则按如下方式向录制失败的节点发送调度任务：
先判断所述录制任务中的一级节点是否录制成功，
若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
所述网络侧设备为内容管理引擎。
综上， 本发明提供的一种录制节目的方法、 多媒体系统和网络侧设备， 才艮据本发明实施例的录制方法，在部分节点可能因为某种原因导致录制失败， 而在其他节点录制成功， 可以实现节点间录制节目的自动互修复； 当 IPTV 系统的最核心模块一一内容管理引擎进行主备服务器切换， 或内容管理引擎 服务器在半个小时内的重启或升级等， 然后开机运行的过程前后， 当前的 TVOD的录制任务， 几乎不受影响， 达到非常高的录制成功率； 当 IPTV 系 统的各节点的媒体控制单元进行主备服务器切换， 或媒体控制单元服务器较 长时间内的重启或升级等， 然后开机运行的过程后， 能极大防止其所属的流 媒体服务器丟失 TVOD; IPTV系统一般是在媒体控制单元控制下有多个流媒 体服务器， 其中包括一个负责频道编解码的流媒体服务器。 如果负责频道编 解码的流媒体服务器坏了， 虽然可以切换到其他的流媒体服务器上， 切换期 间会直接导致 TVOD不能录制， 但根据本发明的录制节目的方法可以保证在 此媒体控制单元控制下的其他流媒体服务器也具有该 TVOD, 从而不影响用 户的点播服务； 此外， 当 IPTV系统的 TVOD录制失败或错过录制 TVOD, 可以在频道的时移时长允许范围内， 可以补做 TVOD的录制， 灵活方便， 极 大地提高了 IPTV的服务性能。 附图概述
图 1是根据本发明实施例的多媒体系统的示意图；
图 2是根据本发明实施例的录制节目的方法的流程图；
图 3是根据本发明实施例的对录制节目失败的修复方法的流程图； 图 4 为根据本发明实施例的对 IPTV系统的中心节点进行 TVOD调度修 复的示意图；
图 5 为根据本发明实施例的对 IPTV系统的边缘节点进行 TVOD调度修 复的示意图；
图 6为根据本发明实施例在 IPTV系统中进行 TVOD互修复的处理流程 图；
图 7为根据本发明实施例在 IPTV系统中进行 TVOD补录的处理流程图。
本发明的较佳实施方式
下面结合附图及实施例对本发明的技术方案进行更详细的说明。
图 1是根据本发明实施例的多媒体系统的示意图， 本实施例的多媒体系 统可以是 IPTV系统， 手机电视系统或者移动流媒体等。 如图 1所示， 本实施 例的多媒体系统包括网络侧设备和多个节点， 在本实施例中网络侧设备可以 是内容管理引擎（ Content Management Engine, 简称 CME ) , 各个节点分别 包括媒体控制单元（Media Control Unit, 简称 MCU )和若干个流媒体服务器 ( Streaming Server, 简称 SS ) 。 一个内容管理引擎可能管理多个媒体控制单 元， 一个媒体控制单元可能控制多个流媒体服务器。 内容管理引擎在下发录制请求时选择要下发录制请求的媒体控制单元首 先要满足的条件是该媒体控制单元控制的流媒体服务器上存储有待录制的节 目的频道， 进一步可根据负荷均衡等策略来选择， 比如， 现在一个媒体控制 单元下， 一个频道在只在一个流媒体服务器上进行服务， 也可以考虑一个频 道在多个（两个以上） 流媒体服务器上进行服务， 每个流媒体服务器都定时 上报其性能状态， 例如 CPU使用、 用户点播的并发流等， 然后根据该性能状 态， 通过加权方法， 计算出剩余服务能力值最大的流媒体服务器， 即选择负 荷最小的流媒体服务器来做频道点播的服务， 来处理录制任务。 相似地， 媒 体控制单元下发录制任务时也要选择存储有待录制节目的频道的流媒体服务 器， 进一步也可根据负荷均衡等策略来选择。
考虑到在内容管理引擎的服务器或媒体控制单元的服务器短时间内的重 启或主备切换过程中尽量减少对录制任务的影响， 内容管理引擎按录制任务 开始的时间顺序，提前一定时间 (如一天)将录制任务下发给各个节点的媒体控 制单元。 制的频道的流媒体服务器。 流媒体服务器负责频道编解码， 进行节目的实时 录制。 流媒体服务器收到所述录制任务后对所述录制任务中指定的频道进行 节目录制， 然后向媒体控制单元返回录制结果信息， 然后由媒体控制单元将 录制结果信息返回给内容管理引擎。 节目录制成功后， 以单独的文件保存在 录制节目对应的目录下。 当部分节点录制失败后， 通过在节点间互修复录制 的节目； 当全部节点录制失败后， 再次尝试节目的补录。
内容管理引擎在各个节点进行节目录制的过程中定时检查各个节点返回 的录制结果信息， 若发现部分节点返回录制失败信息， 则向录制失败的节点 的媒体控制单元发送调度任务， 录制失败的节点的媒体控制单元收到所述调 度任务后向录制成功的节点的媒体控制单元调度录制成功的节目作为本节点 的录制节目， 并向所述内容管理引擎返回调度成功信息。
此外， 内容管理引擎在各个节点进行节目录制的过程中定时检查各个节 点返回的录制结果信息， 若发现所有节点均返回录制失败信息， 说明此问题 极大概率是网络不通或此频道媒体流断流等重大工程故障，系统应产生告警， 以便及时让运营商及时掌握和解决。 接下来内容管理引擎检测是否有节点对 要录制的频道设置了暂存节目的时移配置， 若没有， 则此节目录制无法修复， 直接判定为失败结果； 若有， 则向对要录制的频道设置了暂存节目的时移配 置的节点的媒体控制单元发送补录任务。 该节点的媒体控制单元收到补录任 务后将补录任务发送给对要录制的频道设置了暂存节目的时移配置的流媒体 服务器， 然后该流媒体服务器判断录制失败的节目的时间段是否处于所述时 移配置所暂存节目的时间范围内， 若是， 则从流媒体服务器上暂存的节目中 单元返回补录成功信息， 否则向媒体控制单元返回补录失败信息。
本实施例的多媒体系统中的任何环境或设备都是独立的， 即一个设备坏 掉不影响到其他设备也坏掉。 而且本实施例的多媒体系统是多节点架构的， 一个节目在一个节点上录制失败时， 很可能在其他是成功的， 当节点多达三 个以上时， 一个节目在所有节点上录制失败的概率远低于万分之一， 因此大 大提高节目录制的成功率。
IPTV系统包括网络侧设备， 例如内容管理引擎， 和多个节点， 各个节点 包括媒体控制单元和若干个流媒体服务器等， 并且 ιρτν 系统为多级节点架 构。 本实施例中， IPTV系统的内容管理引擎接收到录制请求后， 生成 TVOD 的录制任务，提前下发给各媒体控制单元，之后由 IPTV系统的媒体控制单元 将录制任务下发给流媒体服务器进行 TVOD的录制。 内容管理引擎定时检查 录制失败的 TVOD, 如果是部分节点录制成功， 部分节点录制失败， 则才艮据 一定的策略进入节点间互修复； 如果全部节点都失败， 则对各节点再次补录。
图 2是根据本发明实施例的录制节目的方法的流程图， 如图 2所示， 本 实施例的录制节目的方法包括下面步骤：
201、 内容管理引擎接收到录制请求；
向内容管理引擎发送录制请求的可以是外部系统， 例如， IPTV业务管理 系统或者用户机顶盒等等。 录制请求中应包含需要录制的节目信息， 例如， IPTV 业务管理系统发送的录制请求包括需要录制的节目时间表。 本实施例 中， 节目时间表是以开始时间和结束时间来表示， 但本发明对于这些信息的 表示方式不做限制。
录制请求中还可以包括对录制任务的删除信息， 内容管理引擎收到这样 的录制请求后， 如该录制任务还在本地的录制任务队列中， 则将其删除并通 知媒体控制单元， 媒体控制单元收到后， 如该录制任务还在本地的录制任务 队列中， 则将其删除。
录制任务中还可以包括对录制任务的修改信息， 内容管理引擎收到这样 的录制请求后， 如该录制任务还在本地的录制任务队列中， 则对其进行修改 并通知媒体控制单元， 媒体控制单元收到后， 如该录制任务还在本地的录制 任务队列中， 则对其进行修改。
202、 内容管理引擎对该录制请求进行预处理， 将符合条件的录制请求转 化为录制任务， 然后添加到内容管理引擎的录制任务表；
录制任务中包含： TVOD标识 （Identity,简写为 ID)、时移频道 ID、 TVOD 开始时间、 TVOD结束时间和 TVOD名称等信息。 内容管理引擎在判断录制 请求符合条件后，可以向录制请求的发送方返回一个录制请求已接受的响应。
判断录制请求符合条件可以包括对录制请求中的频道和 TVOD的时间段 的校验。内容管理引擎判断是否在流媒体服务器配置了待录制 TVOD的频道， 开始录制时间必须提前几分钟， 录制时长一般为 4小时之内。
203、 内容管理引擎向媒体控制单元发送录制任务；
一个内容管理引擎可能管理多个媒体控制单元 , 一个媒体控制单元可能 控制多个流媒体服务器。 内容管理引擎在下发录制请求时选择的媒体控制单 元首先要满足的条件是该媒体控制单元控制的流媒体服务器上存储有待录制 TVOD的频道， 进一步可根据负荷均衡等策略来选择。 相似地， 媒体控制单 元在下发录制任务时选择的流媒体服务器应当存储有待录制 TVOD的频道， 进一步也可根据负荷均衡等策略来选择。 考虑到内容管理引擎的服务器或媒体控制单元的服务器短时间内的重启 或主备切换过程中尽量减少对录制任务的影响， 内容管理引擎按录制任务开 始的时间顺序，提前一定时间 (如一天)将录制任务下发给媒体控制单元的主服 务器。 正常情况下， 媒体控制单元只有主服务器提供服务。 当内容管理引擎 发生故障时， 媒体控制单元可以照常将已接收到的录制任务发送给流媒体服 务器， 这样流媒体服务器可以按照录制任务进行正常录制 TVOD; 当媒体控 制单元的主服务器发生故障时， 媒体控制单元的其他服务器迅速切换为主服 务器， 同时将 TVOD录制任务同步到本节点内存的录制任务队列中。
204、媒体控制单元维护本节点的录制任务队列， 将录制任务插入到本节 点的录制任务队列， 并更新本节点的录制任务队列的任务索引表；
本实施例在插入录制任务时， 将该录制任务插入到时间段的开始时刻比 该录制任务的时间段的开始时刻早且与该录制任务的时间段的开始时刻的时 间间隔最小的录制任务之后， 使得本地录制任务队列中的录制任务是按 TVOD的开始时间的先后顺序从前到后依次排列， 以方便选择早于当前时间 的录制任务。 所述媒体控制单元每插入一个新的录制任务的同时更新任务索 引表， 以维护本地录制任务状态。
205、媒体控制单元成功将录制任务插入到本地录制任务队列之后， 向内 容管理引擎回复录制请求的应答。
206、媒体控制单元定时从本地的录制任务队列中取出即将到达开始时间 的录制任务（例如提前 2秒左右） ， 下发给流媒体服务器。
207、流媒体服务器收到录制任务后立即向媒体控制单元回复录制请求的 应答。
208、 流媒体服务器对收到的录制任务进行处理， 判断流媒体服务器上是 否存储有待录制的 TVOD的频道、 录制开始时间和结束时间是否正确 （即录 制开始时间和结束时间均应晚于当前时间） ， 若是， 则进行实时录制； 否则 直接向媒体控制单元回复录制失败信息。
209、 流媒体服务器向媒体控制单元发送录制结果信息， 上报录制结果， 所述录制结果信息包括录制成功信息或录制失败信息 （包含错误信息） ；
210、媒体控制单元收到录制结果信息后， 向内容管理引擎发送录制结果 信息， 定时上报录制任务的执行结果， 直到收到内容管理引擎的确认响应；
211、若内容管理引擎收到录制结果信息为录制成功信息， 则将录制任务 标识为成功状态， 然后在数据库的 TVOD表中保存一条记录（包含点播此 TVOD时可访问的文件的全路径信息） ， 然后向媒体控制单元发送录制结果 的应答， 确认录制结果信息已经成功处理。
若内容管理引擎收到录制结果信息为录制失败信息， 则将录制任务标识 为失败状态，或者若在超过录制任务的录制结束时间一定时间 (如 5分钟)后一 直未收到媒体控制单元发送来的录制结果信息， 则内容管理引擎将该录制任 务标识为失败状态。
IPTV系统重大故障， 如内容管理引擎因长时间掉电或输入到 IPTV系统 频道的媒体流失败等， 允许 TVOD的录制失败。 除此之外， 在 IPTV正常运 行下， 允许短时间 （如半小时） 内重启或升级内容管理引擎、 依次升级媒体 控制单元或流媒体服务器等的情况下需要尽可能的保证录制节目的业务成 功。 为了进一步保证 TVOD的录制成功， 在步骤 211后， 内容管理引擎定时 地检查媒体控制单元发送来的录制结果信息， 如果是部分节点录制成功， 部 分节点录制失败， 则根据一定的策略进入节点间互修复； 如果全部节点都失 败， 则对各节点再次补录。
内容管理引擎周期地（例如 2分钟 )检查 IPTV系统中 TVOD录制失败 的录制任务并处理。 本实施例的 IPTV 系统以三级节点架构系统为例进行说 明， IPTV系统可扩展到多级节点架构系统。 为了便于表述， 一级节点表示为 中心节点， 二级节点表示为区域中心节点， 三级节点表示为边缘节点。 首先 内容管理引擎判断此 TVOD在中心节点上是否录制成功， 如不成功， 则从其 他节点调度 TVOD到中心节点上， 调度的优先顺序如图 4所示； 如果中心节 点录制任务成功， 是其他节点的录制任务失败， 则将 TVOD分级调度到这些 节点上， 调度的流程顺序如图 5所示。
在步骤 210后， 内容管理引擎定时检查中心节点是否有 TVOD, 如果中 心节点有 TVOD, 可以向录制请求的发送方回应一个录制响应， 上^艮录制任 务的执行结果 (成功），如果中心节点上一直没有 TVOD,直到录制任务超时 (如 2小时)， 可以向录制请求的发送方回应一个录制响应， 上报录制任务的执行 结果 (失败)。所述中心节点上有否有 TVOD的判定，是 IPTV系统中为了保存 TVOD数据的一致性， 所有的内容必须在中心节点上要有一份， 保证用户能 点播的节目都可以正常访问。 如： 边缘节点的用户点播时， 在其所属节点上 未命中节目，可以通过重定向策略到其他节点上 (至少中心节点上有节目）， 以 服务保证。
图 3是根据本发明实施例的对录制节目失败的修复方法的流程图， 如图 3所示， 每个周期的对录制节目失败的修复方法基本工作流程包括下面步骤：
301、 内容管理引擎检查出 IPTV系统中 TVOD失败的录制任务， 其中同 一频道同一时段的录制任务的标识相同。
302、 对失败的 TVOD录制任务进行判断， 此 TVOD是否在所有节点上 录制失败， 如果部分节点上录制失败， 其他节点录制成功， 则执行步骤 303 , 如果所有节点都录制失败， 则执行步骤 304。
303、 进入节点间互修复流程。
本实施例的节点间互修复流程大体是：
内容管理引擎首先判断此录制任务的中心节点是否录制成功， 如果未录 制成功， 则优先选择录制成功的区域中心节点， 如果区域中心节点录制失败， 则选择录制成功的边缘节点， 产生调度 TVOD到中心节点的任务， 然后进行 修复录制；
再判断录制任务的区域中心节点是否录制成功， 如果未录制成功， 则产 生从中心节点调度 TVOD到区域中心节点的任务， 然后进行修复录制；
最后判断录制任务的边缘节点是否录制成功， 如果未录制成功， 则产生 从该边缘节点所属的区域中心节点调度 TVOD的任务， 然后进行修复录制。
304、 此时 TVOD在所有节点上都录制失败， 检查此 TVOD是否满足补 录条件， 如果满足补录条件， 则进入步骤 305, 否则不处理；
补录条件为流媒体服务器上在该 TVOD频道上做了时移配置， 并且配置 的时移内容包含未能录制的时间段上的 TVOD。
305、 进入补录流程。
从一个节点 A调度到另一个节点 B的关系，本实施例中称为 TVOD的调 度任务， 其中， 节点 A称为源节点， 节点 B称为目的节点。 调度方式可以为 文件传输协议 ( File Transfer Protocol, FTP ) 、 超文本传输协议（HyperText Transfer Protocol, HTTP )或实时流传输协议（ Real Time Streaming Protocol, RTSP )等， 本实施例以 FTP下载为调度方式为例。 内容管理引擎需要 TVOD 的调度时， 首先选择源节点的流媒体服务器的 FTP下载信息， FTP下载信息 包括： IP地址、端口号、用户名和密码等， 然后结合源节点上的 TVOD信息， 包括 TVOD标识、 文件名和 TVOD的全路径等， 作为一个调度任务。 之后内 容管理引擎周期处理这些调度任务， 当目的节点调度完 TVOD后， 将原先的 录制任务标识为成功状态。
本实施例的内容管理引擎周期处理调度任务， 其基本工作流程如图 6所 示， 包括下面步骤：
601、 内容管理引擎向媒体控制单元发送 TVOD 的调度内容请求， 同时 将调度任务发送给媒体控制单元；
602、媒体控制单元维护本地的调度任务队列， 将调度任务插入到本地的 调度任务队列；
603、媒体控制单元收到调度请求后， 向所述内容管理引擎回复调度内容 请求的应答；
604、 媒体控制单元每周期在调度任务队列中选择 N (如 10)个调度任务， 向 IPTV系统的流媒体服务器发送调度内容请求；
605、 所述流媒体服务器收到 TVOD 的调度请求时， 向所述媒体控制单 元回复调度内容请求的应答；
606、 所述流媒体服务器收到 TVOD的调度请求后， 进行实际的 TVOD 的拷贝处理： 首先判断在原 TVOD目录下是否存在该 TVOD文件， 如果存在 该 TVOD文件且与待调度的 TVOD的大小误差在允许范围（如 2%)之内， 则 认为该 TVOD文件已经存在， 可以直接返回成功的调度结果信息； 否则先清 除该 TVOD文件，再从源节点的流媒体服务器上调度 TVOD到目的节点的流 媒体服务器上；
607、 流媒体服务器执行 TVOD 的调度任务完毕后， 向媒体控制单元发 送调度结果信息， 以回复所述调度任务的执行结果；
608、媒体控制单元收到调度结果信息后， 向内容管理引擎发送调度结果 信息， 上报调度任务的执行结果；
上述步骤 607和 608中， 执行结果可能是调度成功， 也可能是调度失败。 如果是调度成功， 执行结果中要包括 TVOD文件的文件路径信息和标识信息 (如文件名），还可以包含该 TVOD文件的其他属性信息如大小、名称等等。
609、若内容管理引擎收到的调度结果信息是调度成功信息， 则向媒体控 制单元发送调度内容结果的应答， 确认调度结果消息已经成功处理， 然后， 内容管理引擎将该调度任务对应的 TVOD的录制任务标识为成功状态；
若内容管理引擎收到的调度结果信息是调度失败信息， 将该调度任务对 应的 TVOD的录制任务标识为失败状态。
此后内容管理引擎再周期性检查失败 TVOD的录制任务， 判断是否要做 TVOD互修复方法。
如果 TVOD在所有节点都未录制成功， 很可能内容管理引擎在某时刻因 为重启或是升级等原因， 未能成功下发录制任务到各节点的媒体控制单元。 此时内容管理引擎发起补录处理， 补录的前提是需要在流媒体服务器上对所 要录制的频道进行时移配置， 并且配置的时移内容包含未能录制的时间段上 的 TVOD, 从时移内容上复制一份 TVOD, 此过程叫做补录。
当 TVOD在所有节点都未录制成功时， 内容管理引擎判断哪些节点上配 置了时移频道， 然后对配置了时移频道的节点下发补录任务， 对这些节点的 录制任务标记为补录状态， 其他节点的录制任务直接标记为补录失败。 当补 录成功后， 将原先的录制任务标识为成功状态， 如果不是所有节点都成功， 再进行 TVOD的节点间互修复流程处理。
本实施例的补录修复的基本工作流程如图 7所示， 包括下面步骤：
701、 内容管理引擎向媒体控制单元发送补录请求， 同时将补录任务发送 给媒体控制单元；
702、媒体控制单元收到补录请求后， 向所述内容管理引擎回复补录请求 的应答；
703、 媒体控制单元将补录请求中的补录任务信息组装后， 向 IPTV系统 的流媒体服务器发送补录请求和补录任务；
704、 所述流媒体服务器收到 TVOD 的补录请求后， 根据其中补录任务 的 TVOD的开始时间和结束时间， 判断本地存储的 TSTV的录制内容是否有 要补录的录制节目， 如果有， 复制该录制节目并做成 TVOD的文件；
如果 TSTV的录制内容中没有要补录的节目段， 则补录失败。
705、 流媒体服务器执行 TVOD 的补录请求完毕后， 向媒体控制单元发 送补录结果信息， 以回复所述补录任务的执行结果；
706、媒体控制单元收到补录响应后，向内容管理引擎发送补录结果信息， 上报补录任务的执行结果；
上述两个步骤中， 执行结果可能是补录成功， 也可能是补录失败。 如果 是补录成功， 执行结果中要包括 TVOD文件的文件路径信息和标识信息（如 文件名） ， 还可以包含该 TVOD文件的其他属性信息如大小、 名称等等。
707、若内容管理引擎收到的补录结果信息为补录成功信息， 则向媒体控 制单元发送补录结果的应答， 确认补录结果消息已经成功处理， 然后， 内容 管理引擎将补录状态的 TVOD的录制任务标识为成功状态； 若内容管理引擎 收到的补录结果信息为补录失败信息， 则将补录状态的 TVOD的录制任务标 识为失败状态。
此后内容管理引擎再周期性检查失败 TVOD的录制任务， 判断是否要做
TVOD互修复方法。
根据本发明实施例的录制方法， 在部分节点可能因为某种原因导致录制 失败， 而在其他节点录制成功， 可以实现节点间录制节目的自动互修复； 当 IPTV 系统的最核心模块一一内容管理引擎进行主备服务器切换， 或 内容管理引擎服务器在半个小时内的重启或升级等， 然后开机运行的过程前 后， 当前的 TVOD的录制任务， 几乎不受影响， 达到非常高的录制成功率； 当 IPTV 系统的各节点的媒体控制单元进行主备服务器切换， 或媒体控 制单元服务器较长时间内的重启或升级等， 然后开机运行的过程后， 能极大 防止其所属的流媒体服务器丟失 TVOD;
IPTV系统一般是在媒体控制单元控制下有多个流媒体服务器，其中包括 一个负责频道编解码的流媒体服务器。 如果负责频道编解码的流媒体服务器 坏了， 虽然可以切换到其他的流媒体服务器上， 切换期间会直接导致 TVOD 下的其他流媒体服务器也具有该 TVOD, 从而不影响用户的点播服务；
此外， 当 IPTV系统的 TVOD录制失败或错过录制 TVOD, 可以在频道 的时移时长允许范围内， 可以补做 TVOD的录制， 灵活方便， 极大地提高了 IPTV的服务性能。
从本发明方法的实现来说， 也不局限于上述 IPTV 系统的结构， 对于其 他的系统构成同样可以应用。如此发明方法可以应用于数字电视的内容发布、
TVOD的录制等。
例， 不应当理解为对本发明的限制， 根据本发明的技术方案及其较佳实施例 的描述， 可以做出各种可能的等同改变或替换， 而所有这些改变或替换都应 属于本发明的权利要求的保护范围。
工业实用性 本发明的录制方法， 在部分节点可能因为某种原因导致录制失败， 而在 其他节点录制成功，可以实现节点间录制节目的自动互修复； 当 IPTV系统的 最核心模块一一内容管理引擎进行主备服务器切换， 或内容管理引擎服务器 在半个小时内的重启或升级等， 然后开机运行的过程前后， 当前的 TVOD的 录制任务， 几乎不受影响， 达到非常高的录制成功率； 当 IPTV系统的各节点 的媒体控制单元进行主备服务器切换， 或媒体控制单元服务器较长时间内的 重启或升级等， 然后开机运行的过程后， 能极大防止其所属的流媒体服务器 丟失 TVOD。 当 IPTV系统的 TVOD录制失败或错过录制 TVOD, 可以在频 道的时移时长允许范围内， 可以补做 TVOD的录制， 灵活方便， 极大地提高 了 IPTV的服务性能。

Claims

权 利 要 求 书
1、 一种录制节目的方法， 应用于包括网络侧设备的多节点架构的多媒体 系统， 该方法包括：
网络侧设备收到录制请求后生成录制任务， 并将所述录制任务提前下发 给存储有所述录制任务中指定的频道的各个节点； 以及
所述节点收到所述录制任务后， 对所述录制任务中指定的频道进行节目 录制， 并向所述网络侧设备返回录制结果信息。
2、 如权利要求 1所述的方法， 该方法还包括：
在所述节点进行节目录制时， 所述网络侧设备定时检查各个节点返回的 所述录制结果信息， 若发现所述录制结果信息均为录制失败信息， 则检测是 否有节点对所述频道设置了暂存节目的时移配置， 若有， 则向对所述频道设 置了暂存节目的时移配置的节点发送补录任务； 以及
所述对所述频道设置了暂存节目的时移配置的节点收到所述补录任务 后， 判断录制失败的节目的时间段是否在本节点时移配置所暂存节目的时间 范围内， 若是， 则从本节点暂存的节目中提取与所述录制失败的节目的时间 段相同的节目作为本节点的录制节目， 然后向所述网络侧设备返回录制成功 信息。
3、 如权利要求 1或 2所述的方法， 该方法还包括：
在所述节点进行节目录制时， 所述网络侧设备定时检查各个节点返回的 所述录制结果信息， 若发现所述录制结果信息部分为录制失败信息， 则向录 制失败的节点发送调度任务； 以及
作为目的节点的所述录制失败的节点收到所述调度任务后向作为源节点 的录制成功的节点调度节目作为本节点的录制节目， 并向所述网络侧设备返 回录制成功信息。
4、 如权利要求 3所述的方法， 其中， 所述多媒体系统为多级节点架构， 包括一级节点、 二级节点和三级节点， 所述一级节点连接若干个二级节点， 各个二级节点分别连接若干个三级节点， 所述网络侧设备若发现所述录制结果信息部分为录制失败信息， 则向录 制失败的节点发送调度任务的步骤包括：
所述网络侧设备先判断所述录制任务中的一级节点是否录制成功； 若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
5、如权利要求 3所述的方法，其中，所述目的节点收到所述调度任务后， 该方法还包括：
判断本节点是否存储有与所述调度任务中指定的待调度的节目相同的节 目且节目大小误差是否在允许范围内， 若是， 则向所述网络侧设备返回调度 成功信息。
6、如权利要求 1所述的方法，其中，所述各个节点收到所述录制任务后， 该方法还包括：
所述节点将收到的所述录制任务插入到本地录制任务队列中时间段开始 时刻比该录制任务的时间段开始时刻早， 并且与该录制任务的时间段开始时 刻的时间间隔最小的录制任务之后。
7、 一种多媒体系统， 包括网络侧设备和多个节点，
所述网络侧设备设置为： 收到录制请求后生成录制任务， 并将所述录制 任务提前下发给存储有所述录制任务中指定的频道的各个节点； 所述各个节点设置为： 收到所述录制任务后对所述录制任务中指定的频 道进行节目录制， 并向所述网络侧设备返回录制结果信息。
8、 如权利要求 7所述的多媒体系统， 其中，
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息，若发现所述录制结果信息均为录制失败信息， 则检测是否有节点对所述频道设置了暂存节目的时移配置， 若有， 则向对所 述频道设置了暂存节目的时移配置的节点发送补录任务，
所述对所述频道设置了暂存节目的时移配置的节点还设置为： 收到所述 补录任务后， 判断录制失败的节目的时间段是否在本节点时移配置所暂存节 目的时间范围内， 若是， 则从本节点暂存的节目中提取与所述录制失败的节 目的时间段相同的节目作为本节点的录制节目 , 然后向所述网络侧设备返回 录制成功信息。
9、 如权利要求 7所述的多媒体系统， 其中，
所述网络侧设备还设置为： 在所述各个节点进行节目录制时， 定时检查 各个节点返回的录制结果信息 , 若发现所述录制结果信息部分为录制失败信 息， 则向录制失败的节点发送调度任务；
所述录制失败的节点还设置为： 收到所述调度任务后， 向录制成功的节 点调度节目作为本节点的录制节目，并向所述网络侧设备返回调度成功信息。
10、 如权利要求 9所述的多媒体系统， 其中， 所述多媒体系统为多级节 点架构， 包括一级节点、 二级节点和三级节点， 所述一级节点连接若干个二 级节点， 各个二级节点分别连接若干个三级节点，
所述网络侧设备是设置为： 若发现所述录制结果信息部分为录制失败信 息， 则按如下方式向录制失败的节点发送调度任务：
先判断所述录制任务中的一级节点是否录制成功，
若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
11、 如权利要求 7所述的多媒体系统， 其中， 所述网络侧设备为内容管 理引擎， 所述各个节点分别包括一个媒体控制单元和若干个由该媒体控制单 元控制的流媒体服务器，
所述媒体控制单元设置为： 接收所述内容管理引擎下发的录制任务后将 所述录制任务发送给存储有所述录制任务中指定的频道的流媒体服务器； 收 到所述流媒体服务器发来的录制结果信息后将所述录制结果信息发送给所述 内容管理引擎；
所述存储有所述录制任务中指定的频道的流媒体服务器设置为： 收到所 述录制任务后对所述录制任务中指定的频道进行节目录制， 向所述媒体控制 单元返回录制结果信息。
12、 如权利要求 11所述的多媒体系统， 其中，
所述媒体控制单元还设置为： 若所控制的流媒体服务器有两个以上存储 有所述录制任务中指定的频道， 则将所述录制任务发送给负荷最小的流媒体 服务器。
13、 一种网络侧设备， 所述网络侧设备设置为： 收到录制请求后生成录 各个节点； 接收所述各个节点收到所述录制任务后对所述录制任务中指定的 频道进行节目录制后， 向所述网络侧设备返回录制结果信息。
14、 如权利要求 13所述的网络侧设备， 所述网络侧设备还设置为： 在所 述各个节点进行节目录制时， 定时检查各个节点返回的录制结果信息， 若发 现所述录制结果信息均为录制失败信息， 则检测是否有节点对所述频道设置 了暂存节目的时移配置， 若有， 则向对所述频道设置了暂存节目的时移配置 的节点发送补录任务； 接收对所述频道设置了暂存节目的时移配置的节点返 回的录制成功信息；
其中， 所述录制成功信息由所述对所述频道设置了暂存节目的时移配置 的节点收到所述补录任务后， 判断录制失败的节目的时间段是否在本节点时 移配置所暂存节目的时间范围内， 若是， 则从本节点暂存的节目中提取与所 网络侧设备返回。
15、 如权利要求 13所述的网络侧设备， 所述网络侧设备还设置为： 在所 述各个节点进行节目录制时， 定时检查各个节点返回的录制结果信息， 若发 现所述录制结果信息部分为录制失败信息， 则向录制失败的节点发送调度任 务； 接收所述录制失败的节点返回的调度成功信息；
其中， 所述调度成功信息由所述录制失败的节点收到所述调度任务后， 向录制成功的节点调度节目作为本节点的录制节目， 并向所述网络侧设备返 回。
16、如权利要求 15所述的网络侧设备， 所述网络侧设备应用于多媒体系 统， 所述多媒体系统为多级节点架构， 包括一级节点、 二级节点和三级节点， 所述一级节点连接若干个二级节点，各个二级节点分别连接若干个三级节点， 所述网络侧设备是设置为： 若发现所述录制结果信息部分为录制失败信 息， 则按如下方式向录制失败的节点发送调度任务：
先判断所述录制任务中的一级节点是否录制成功，
若所述一级节点未录制成功， 则选择录制成功的二级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点； 若所述二级节点未录制成功， 则选择录制成功的三级节点作为源节点产 生向所述一级节点调度节目的调度任务， 并将该调度任务发送给所述一级节 点；
若所述一级节点录制成功， 再判断所述录制任务中的二级节点是否录制 成功， 若未录制成功， 则选择所述一级节点作为源节点产生向所述二级节点 调度节目的调度任务， 并将该调度任务发送给所述二级节点； 以及
若所述录制任务中的二级节点录制成功， 然后判断所述录制任务中的三 级节点是否录制成功， 若未录制成功， 则选择与所述三级节点连接的二级节 点作为源节点产生向所述三级节点调度节目的调度任务， 并将该调度任务发 送给所述三级节点。
17、如权利要求 13所述的网络侧设备，所述网络侧设备为内容管理引擎。
PCT/CN2010/074232 2009-09-14 2010-06-22 一种录制节目的方法、多媒体系统和网络侧设备 WO2011029331A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP10814933.7A EP2466880A4 (en) 2009-09-14 2010-06-22 METHOD, MULTIMEDIA SYSTEM, AND NETWORK SIDE DEVICE FOR RECORDING AN EMISSION
RU2012112905/07A RU2515470C2 (ru) 2009-09-14 2010-06-22 Способ, мультимедийная система и оконечное сетевое устройство для записи программы
US13/395,882 US9282278B2 (en) 2009-09-14 2010-06-22 Method, multimedia system and network side device for recording program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009101736007A CN101656861B (zh) 2009-09-14 2009-09-14 一种录制节目的方法和多媒体系统
CN200910173600.7 2009-09-14

Publications (1)

Publication Number Publication Date
WO2011029331A1 true WO2011029331A1 (zh) 2011-03-17

Family

ID=41710914

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/074232 WO2011029331A1 (zh) 2009-09-14 2010-06-22 一种录制节目的方法、多媒体系统和网络侧设备

Country Status (5)

Country Link
US (1) US9282278B2 (zh)
EP (1) EP2466880A4 (zh)
CN (1) CN101656861B (zh)
RU (1) RU2515470C2 (zh)
WO (1) WO2011029331A1 (zh)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101656861B (zh) 2009-09-14 2012-07-18 中兴通讯股份有限公司 一种录制节目的方法和多媒体系统
EP2792157B1 (en) * 2011-12-12 2020-06-03 Samsung Electronics Co., Ltd. Method and apparatus for experiencing a multimedia service
WO2013086707A1 (zh) * 2011-12-14 2013-06-20 华为技术有限公司 内容分发网络cdn路由方法、设备和系统
CN102724583A (zh) * 2012-05-30 2012-10-10 中兴通讯股份有限公司 一种节目单录制方法及系统
US9424229B2 (en) * 2013-02-13 2016-08-23 Advanced Micro Devices, Inc. Parallel torus network interconnect
CN103227934B (zh) * 2013-04-19 2017-07-28 深圳Tcl新技术有限公司 对电视节目进行录像的方法及服务器
CN105635746B (zh) * 2014-11-07 2019-10-25 南京中兴软件有限责任公司 Tvod录制任务的录制处理、录制方法及装置、系统
US9819972B1 (en) * 2014-12-10 2017-11-14 Digital Keystone, Inc. Methods and apparatuses for a distributed live-on-demand (LOD) origin
CN106303666A (zh) * 2015-06-24 2017-01-04 中兴通讯股份有限公司 一种iptv节目的处理方法及装置、iptv系统
US9942578B1 (en) * 2015-12-07 2018-04-10 Digital Keystone, Inc. Methods and apparatuses for a distributed live-on-demand (LOD) origin
CN107730011A (zh) * 2017-10-10 2018-02-23 通辽霍林河坑口发电有限责任公司 信息检测方法及装置
CN110062251A (zh) * 2019-04-19 2019-07-26 视联动力信息技术股份有限公司 一种直播发布方法、系统及装置
CN111462725B (zh) * 2020-04-17 2021-01-12 北京灵伴即时智能科技有限公司 录音编辑管理方法及系统
CN112383792B (zh) * 2020-11-12 2023-04-18 咪咕视讯科技有限公司 直播内容同步处理方法、电子设备及存储介质
CN113573080B (zh) * 2021-06-28 2023-09-29 北京百度网讯科技有限公司 直播的录制方法、装置、电子设备及存储介质
CN114339380B (zh) * 2022-01-06 2024-06-11 厦门亿联网络技术股份有限公司 基于aa模式的录制方法、装置、服务器和可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070118857A1 (en) * 2005-11-18 2007-05-24 Sbc Knowledge Ventures, L.P. System and method of recording video content
CN101179702A (zh) * 2007-12-03 2008-05-14 中兴通讯股份有限公司 一种iptv直播电视的实时录制方法
CN101489103A (zh) * 2009-01-16 2009-07-22 中兴通讯股份有限公司 一种录制节目点播的录制方法及归档方法
CN101656861A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 一种录制节目的方法和多媒体系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001313688A (ja) * 2000-04-28 2001-11-09 Canon Inc データ伝送システム、データ伝送方法、通信端末、通信方法、及びコンピュータ読み取り可能な記憶媒体
US7783956B2 (en) * 2006-07-12 2010-08-24 Cronera Systems Incorporated Data recorder
US20080046954A1 (en) * 2006-08-03 2008-02-21 Kulvir Singh Bhogal Coordinated Recording System
RU61971U1 (ru) * 2006-10-20 2007-03-10 Общество с ограниченной ответственностью "Норт Телеком" Система для предоставления услуг iptv
JP2008147759A (ja) * 2006-12-06 2008-06-26 Toshiba Corp 配信システムとそのレコーダ装置、端末装置及び番組録画・配信方法
US20080282312A1 (en) * 2007-05-08 2008-11-13 Yahoo! Inc. System and method for allocating tuner and/or recording resources
US8705944B2 (en) * 2007-07-06 2014-04-22 At&T Intellectual Property I, L.P. System and method of recording media content
JP2009182420A (ja) * 2008-01-29 2009-08-13 Panasonic Corp 代理録画システム及び映像受信装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070118857A1 (en) * 2005-11-18 2007-05-24 Sbc Knowledge Ventures, L.P. System and method of recording video content
CN101179702A (zh) * 2007-12-03 2008-05-14 中兴通讯股份有限公司 一种iptv直播电视的实时录制方法
CN101489103A (zh) * 2009-01-16 2009-07-22 中兴通讯股份有限公司 一种录制节目点播的录制方法及归档方法
CN101656861A (zh) * 2009-09-14 2010-02-24 中兴通讯股份有限公司 一种录制节目的方法和多媒体系统

Also Published As

Publication number Publication date
US9282278B2 (en) 2016-03-08
EP2466880A1 (en) 2012-06-20
RU2515470C2 (ru) 2014-05-10
CN101656861B (zh) 2012-07-18
US20120174175A1 (en) 2012-07-05
RU2012112905A (ru) 2013-10-27
CN101656861A (zh) 2010-02-24
EP2466880A4 (en) 2013-11-20

Similar Documents

Publication Publication Date Title
WO2011029331A1 (zh) 一种录制节目的方法、多媒体系统和网络侧设备
JP4884460B2 (ja) 瞬時のメディア・オン・デマンド
KR101606940B1 (ko) 풀 및 푸시 모드를 조합하는 시스템 및 방법
US8154988B2 (en) Delivery of streams to repair errored media streams in periods of insufficient resources
EP2792123B1 (en) Remote storage digital video recorder and related operating methods
JP5718977B2 (ja) 要求応答並列ビデオサーバにおける負荷分散及び受付予定管理
US20140259057A1 (en) IPTV Server and Method for Playing Recorded Content
US8631270B2 (en) Method, device for running internet protocol television service system, and internet protocol television service system
WO2013170823A2 (zh) 交互式网络电视预约系统及预约计划管理方法、设备
WO2011103837A2 (zh) 服务器故障时的报文处理方法及路由器
WO2010051059A1 (en) System and method for distributing media content
US8145778B2 (en) Method and system for transitioning streamed digital video content between stream servers in a digital video network
US20100111504A1 (en) System and method for recording and distributing media content
US8214855B2 (en) Delivery of streams to repair errored media streams in periods of unrecoverable errors
US20070239879A1 (en) Method and apparatus for router recovery
WO2011018051A1 (zh) 网络个人视频录制处理方法和设备及系统
EP1988669A1 (en) Information distribution system, terminal apparatus used in such system, recording medium on which program is recorded, and loop connection avoidance method
US8370426B2 (en) Content-on-demand method and network therefor
WO2011012027A1 (zh) 一种录像恢复的方法及系统
RU2654369C1 (ru) Способ управления полосой пропускания, терминальное устройство IPTV и система связи
US20100040073A1 (en) Apparatus and method for managing a network
US20150010292A1 (en) Method and system for fail-safe program recording in personal video recorders
WO2008074225A1 (fr) Procédé de remplacement de modèle, système et périphérique
CN113163270B (zh) 用于修复视频信号的方法及系统
JP2011130277A (ja) コンテンツ配信システム，コンテンツ配信方法及びプログラム

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13395882

Country of ref document: US

Ref document number: 2010814933

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: A20120441

Country of ref document: BY

WWE Wipo information: entry into national phase

Ref document number: 2012112905

Country of ref document: RU