WO2010028591A1 - 实现客户端录制的方法、系统及录制控制实体 - Google Patents

实现客户端录制的方法、系统及录制控制实体 Download PDF

Info

Publication number
WO2010028591A1
WO2010028591A1 PCT/CN2009/073821 CN2009073821W WO2010028591A1 WO 2010028591 A1 WO2010028591 A1 WO 2010028591A1 CN 2009073821 W CN2009073821 W CN 2009073821W WO 2010028591 A1 WO2010028591 A1 WO 2010028591A1
Authority
WO
WIPO (PCT)
Prior art keywords
recording
client
scf
entity
identifier
Prior art date
Application number
PCT/CN2009/073821
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 华为技术有限公司
Publication of WO2010028591A1 publication Critical patent/WO2010028591A1/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
    • 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/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
    • 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/47—End-user applications
    • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • H04N21/47214—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content for content reservation or setting reminders; for requesting event notification, e.g. of sport results or stock market

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, system, and recording control entity for implementing client recording.
  • IPTV Internet Protocol Television
  • the line TV network integrates technologies such as Internet, multimedia, and communication to provide home users with a variety of interactive services including digital TV. Users can use IPTV services in combination with PCs via PCs (Personal Computers) or set-top boxes, or they can use IPTV services through mobile terminals.
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • IMS Whether for fixed network users or mobile network users, IMS enables peer-to-peer IP communication between various types of clients.
  • the IMS-based IPTV architecture now directly reuses the relevant functional entities of IMS, and implements IMS support for IPTV services by appropriately adding new functional entities and expanding existing functional entities.
  • Figure 1 it is a schematic diagram of the IMS-based IPTV architecture:
  • the functional entities of IMS that are directly reused by IPTV include NASS (Network Attachment).
  • NASS Network Attachment Subsystem
  • RACS Resource and Admission Control Sub-System
  • NASS completes the management of the access network to which the user is attached, including user authentication and network address allocation. Location management, etc.
  • RACS completes resource scheduling and allocation, and implements QoS (Quality of Service) control.
  • SDF Service
  • the Service Selection Functions is used to provide the UE with available services that can be browsed and selected. List.
  • Each IPTV service consists of a pair of IPTV SCF (Service Control Functions) and IPTV MF (Media Functions).
  • COD Content On Demand, content on demand
  • COD-SCF COD service control function
  • COD-MCF COD media control function
  • COD-MDF COD media delivery function
  • BC Broadcast, broadcast
  • BC-SCF BC Service Control Function
  • BC-MCF BC Media Control Function
  • BC-MDF BC Media Delivery Function
  • PVR-SCF Personal Recording Service Control Function
  • PVR-MCF Recording Media Control Function
  • PVR-MDF Recording Media Delivery Function
  • the inventor found in the process of research on the prior art that although the main tasks of each entity are given in the IMS-based IPTV architecture, there is no description of how to exchange information between entities in the client device or in the network. Storage device.
  • An object of the embodiments of the present invention is to provide a method, system, and recording control entity for implementing client recording, so that a user can record media content.
  • a method for realizing client recording which is applied to an Internet Protocol television IPTV system based on an IP multimedia subsystem, including:
  • the recording task includes an identifier of the recorded content and/or a client recording party
  • a recording initiating entity configured to send a recording task to the recording control entity, where the recording task includes an identifier of the recorded content and/or a client recording party identifier;
  • the recording control entity after receiving the recording task, controls the client recording party to record the media content according to the identifier of the recorded content and/or the client recording party identifier.
  • a recording control entity including: a receiving unit, configured to receive a recording task, where the recording task includes an identifier of the recorded content and/or a client recording party identifier;
  • control unit configured to control the recording content of the media by the client recording entity according to the identifier of the recorded content and/or the client recording party identifier.
  • FIG. 1 is a schematic diagram of an existing IMS-based IPTV architecture
  • FIG. 2 is a flowchart of a first embodiment of a method for implementing client recording according to the present invention
  • FIG. 3 is a flowchart of a second embodiment of a method for implementing client recording according to the present invention.
  • FIG. 4 is a flowchart of a third embodiment of a method for implementing client recording according to the present invention.
  • FIG. 5 is a flowchart of a fourth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 6 is a flowchart of a fifth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 7 is a flowchart of a sixth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 8 is a flowchart of a seventh embodiment of a method for implementing client recording according to the present invention.
  • FIG. 9 is a flowchart of an eighth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 10 is a flowchart of a ninth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 11 is a flowchart of a tenth embodiment of a method for implementing client recording according to the present invention.
  • FIG. 12 is a flowchart of an eleventh embodiment of a method for implementing client recording according to the present invention.
  • FIG. 13 is a block diagram of an embodiment of a system for implementing client recording according to the present invention.
  • FIG. 14 is a block diagram of a first embodiment of a recording control entity for implementing client recording according to the present invention.
  • FIG. 15 is a block diagram of a second embodiment of a recording control entity for implementing client recording according to the present invention.
  • FIG. 16 is a block diagram of a third embodiment of a recording control entity for implementing client recording according to the present invention
  • FIG. 17 is a block diagram of a fourth embodiment of a recording control entity for implementing client recording according to the present invention.
  • An embodiment of the present invention provides a method, a system, and a recording control entity for implementing client recording, receiving an identifier including a recorded content and/or a recording party identifier of a client, and controlling recording of the client recording entity according to the recording task.
  • the media content includes
  • the recording initiating entity is configured to submit a recording task to the recording control entity, and the recording control entity performs business contract checking and recording on the recording task, and completes the process of establishing the recording task.
  • the recording task may be submitted by the user equipment or may be configured by the network;
  • the recording initiating entity may be a user equipment or a network entity that configures data for the storage network;
  • the recording control entity may be a PVR-SCF or other Control entity.
  • the user to which the recording initiating entity belongs is a recording initiating user; the recording initiating entity and the recording initiating user may be collectively referred to as a recording initiating party.
  • the recording control entity can control the client recording entity to record the media content according to the received recording task.
  • the media providing entity is used to provide media content to the client recording entity, either as a media server or as a user device.
  • the client recording entity receives and records the media stream from the media providing entity; the user to which the client recording entity belongs records the user for the client; the client recording entity and the client recording user can be collectively referred to as the client recording party.
  • FIG. 2 The flow of the first embodiment of the method for implementing client recording according to the present invention is as shown in FIG. 2:
  • Step 201 Receive a recording task including an identifier of the recorded content and a client recording party identifier.
  • the recording task can be a recording task sent by the user equipment or a recording task sent by the network entity.
  • the recording task may further include recording time information, recording initiator identifier, recording parameter information, or recording capability information, etc.
  • the client recording party identifier may be a client recording entity or a user identifier
  • the recording initiator identifier may be Record the identity of the originating entity or user.
  • Step 202 Record the media content according to the recording task control client recording entity.
  • a content delivery channel is established based on the identification of the recorded content in the recording task, and/or the identity of the client recording entity or user, and the client recording entity controls receiving and recording the media content through the content delivery channel.
  • the embodiment of the present invention implements the recording system of the client through interaction between entities in the network, and improves the user experience when using the IMS-based IPTV service.
  • the flow of the second embodiment of the method for implementing client recording is as shown in FIG. 3 .
  • the recording initiation entity and the client recording entity are both UEs, and the recording service control entity is a PVR-SCF.
  • the embodiment shows in detail a process in which a user submits a recording task through the UE, and requests to record a recording task of a certain program content being watched or about to start by the UE:
  • Step 301 The UE submits a recording task to the PVR-SCF.
  • the UE When submitting a recording task, the UE may register the recording task by HTTP (Hypertext Transport Protocol) and submit it to the PVR-SCF.
  • the recording task may also be carried in the message and submitted to the PVR-SCF.
  • the message may be It is a SIP (Session Initiation Protocol) MESSAGE message, INVITE message, SUBSCRIBE message, INFO message or REFER message.
  • SIP Session Initiation Protocol
  • messages between the UE and the PVR-SCF can be transmitted through an entity route in the IMS system, such as a P-CSCF (Call Session Control) Function, a call session control function, or an S-CSCF. .
  • P-CSCF Call Session Control
  • the recording task must include the recording content identifier and the identifier of the client recording party, and the recording content identifier is used to indicate the content, channel, program, or service that the user wants to record; the client recording party identifier indicates the user or device that stores the content, this embodiment
  • the user of the client recording party is the same as the user of the recording initiator, and the device storing the recorded program is the UE device owned by the user, and the client recording party identifier) may be the identifier of the user, such as IMPU (IP Multimedia Public Identity). , public user identity).
  • the recording task may further include recording time information, recording initiator user identifier, CPVR (Client-Personal Video Recorder) content identifier, channel information, recording terminal capability information, recording parameter information, and the like.
  • the recording time information includes the start time, the end time, or the recording duration of the recording. For example, when recording the program being watched from the current time, the starting time is "NOW", and the recording end time or recording duration may not be set.
  • the recording initiator identifier indicates the identifier of the terminal or the home subscriber that initiated the recording; the CPVR content identifier indicates the recorded media content, and the user can view the program content through the identifier;
  • the channel information includes at least one of the following or a combination thereof: the user desires to record The multicast address, port information, and media parameter information corresponding to the BC channel;
  • the recording terminal capability information includes information indicating the actual capacity of the remaining storage space of the recording terminal; and the recording parameter information indicates the media information of the recorded content, such as the codec type or format. And other information.
  • Step 302 The PVR-SCF performs a service contract check after receiving the recording task.
  • the PVR-SCF After reading the information in the recording task, the PVR-SCF judges according to the information of the recording initiating user and the client recording user: The recording initiating user only has the right to control the client recording terminal; the client recording Whether the user has permission to record the requested media content. Further, the PVR-SCF can also obtain the storage space required for recording the content according to the recording time information and the recording parameter information, or judge whether the recording storage terminal has enough space for media recording according to the recording capability information, and when there is no recording task When recording parameter information is provided, other entities are queried and the recording parameter information is obtained. After the service subscription check is completed, the PVR-SCF can record the recording task.
  • Step 303 After the recording task is established, the PCR-SCF returns a recording task submission response to the UE. If the PVR-SCF obtains the space information for recording in step 302, the response in the step further carries the storage space reservation indication information, where the information includes: an indication of the reserved storage space, and the size of the reserved space.
  • the flow of the third embodiment of the method for implementing client recording in the present invention is as shown in FIG. 4, in which the recording initiating entity is UE1, the client recording entity is UE2, and the recording service control entity is PVR-SCF.
  • the process of submitting a recording task by the UE through the UE1, requesting to record the recording task of a certain program content being watched or about to start by the remote device UE2 is shown in detail:
  • Step 401 UE1 submits a recording task to the PVR-SCF.
  • UE1 and UE2 in this embodiment may belong to the same user or may belong to different users.
  • Step 402 The PVR-SCF performs a service contract check after receiving the recording task.
  • the PVR-SCF mainly checks whether the recording initiator user has the right to control the storage terminal of the client recording party.
  • the specific service contract check process is similar to the description of step 302, and details are not described herein again.
  • the PVR-SCF may also obtain the storage space required to record the content according to the recording time information given by the UE in the recording task and the recording parameter information. If the recording parameter information is not provided in the recording task, the PVR-SCF may dynamically initiate a query to other entities and obtain parameter information (such as a code type). After the check is passed, the PVR-SCF records the recording task.
  • Step 403 The PVR-SCF interacts with the UE2 to perform remote management of the recording terminal.
  • the PVR-SCF initiates a remote management request to the UE2 according to the client recording party identifier in the recording task, and the operation can complete the following functions: 1) reserve the space required for recording in the remote recording terminal UE2, and the usage policy of the space, for example, PVR-SCF can include a reservation in the remote management request
  • the indication of the storage space and the size information of the reserved storage space may also include an indication of the space usage policy, such as overwriting the original content when the storage space is insufficient; 2) the recording task is delivered, that is, the PVR-SCF is submitted when the recording task is submitted.
  • the recording task is sent to the recording storage terminal, and the terminal manages the task and starts recording.
  • the PVR-SCF may also query the entity that stores the user terminal information to obtain the state information of the UE2, such as the Presence Server, check whether the UE2 is online, or whether there is enough storage space for recording the program on the UE2.
  • entity that stores the user terminal information such as the Presence Server
  • step 403 is optional.
  • Step 404 After the recording task is established, the PCR-SCF returns a recording task submission response to the UE. Required) It is to be noted that step 404 is optional.
  • the flow of the fourth embodiment of the method for implementing client recording in the present invention is as shown in FIG. 5.
  • the recording initiating entity and the client recording entity are both UEs, and the recording service control entity is a PVR-SCF.
  • the process of establishing a recording task by the user using the UE to submit a recording task through the BC-SCF and requesting recording of a certain program content being watched by the UE is performed:
  • Step 501 The UE submits a recording task to the BC-SCF.
  • BC-SCF in this embodiment may also be a COD-SCF.
  • Step 502 The BC-SCF forwards the recording task to the PVR-SCF.
  • the BC-SCF can forward the recording task through a SIP MESSAGE message, an INVITE message, or an INFO message.
  • Step 503 The PVR-SCF performs a service contract check after receiving the recording task.
  • the business contract check process is similar to the description of step 302.
  • Step 504 After the recording task is established, the PCR-SCF returns a recording task submission response to the BC-SCF.
  • Step 505 The BC-SCF forwards the recording task submission response to the UE.
  • the client recording entity is the UE
  • the media providing entity is a multicast replication point
  • the recording service control entity is PVR-SCF 0
  • This embodiment details the detailed process of the PVR-SCF triggering the interaction between the BC-SCF and the UE according to the established recording task, so that the UE negotiates with the BC-SCF to establish a content delivery channel: Step 601: PVR- The SCF sends a recording start request to the BC-SCF.
  • the PVR-SCF sends a recording start request to the BC-SCF according to the recording content identifier and the client recording party identifier in the recording task, and the message is used to trigger the BC-SCF to negotiate with the UE to establish a content delivery channel.
  • the recording start request may be a REFER message or a MESSAGE message in the SIP.
  • the recording start request can carry one or more of the following information: Record the storage terminal or the user's ID.
  • the UE identifier, or the identifier of the user to which the UE belongs, and the PVR-SCF identifier may be the service identifier generated by the PVR-SCF or the identifier of the PVR-SCF entity.
  • the recording content identification recording time information and the recording initiation user identification are consistent with the information included in the recording task;
  • the CPVR service indication information is used to indicate that the UE is a CPVR service, and needs to record and store the received media content.
  • Step 602 The BC-SCF sends a session establishment request to the UE.
  • the BC-SCF determines that the user has the service of watching the BC channel according to one or more of the client recording party user identifier, the recording initiator user identifier, and the PVR-SCF identifier included in the recording start request message sent by the PVR-SCF. After the authentication is passed, the INVITE request is initiated to the recording storage terminal UE according to the recording storage user identifier or the recording storage terminal identifier obtained from the PVR-SCF, and the content delivery channel is negotiated.
  • the BC-SCF may carry the pre-stored multicast copy point information in the INVITE message, where the information is specifically a multicast address or a multicast address and a port for providing the recorded content, and the message may also be carried.
  • Step 603 The UE returns a session establishment response message to the BC-SCF.
  • the UE may obtain the information of the multicast replication point, and then return a response message (for example, 200 OK) to the BC-SCF, where the response message may carry the negotiation response.
  • a response message for example, 200 OK
  • Step 604 The content delivery channel is established.
  • the BC-SCF is replaced with the COD-SCF
  • the media providing entity is replaced by the multicast copy point with the COD-MF.
  • FIG. 7 A sixth embodiment of the method for implementing client recording according to the present invention is shown in FIG. 7.
  • the client recording entity is the UE
  • the recording service control entity is the PVR-SCF.
  • This embodiment details the detailed process of the PVR-SCF triggering the interaction between the UE and the BC-SCF according to the established recording task, so that the UE negotiates with the BC-SCF to establish a content delivery channel:
  • Step 701 The PVR-SCF sends a recording start request to the UE.
  • the PVR-SCF passes the recording identification and the client recording party identifier in the recording task.
  • the IMS system sends a recording start request to the UE, and the request is used to trigger the UE to negotiate with the BC-SCF to establish a content delivery channel.
  • the recording start request may be a REFER message or a MESSAGE message in the SIP.
  • the PVR-SCF carries the recording task information (including the recording time information), the recording content identifier, and the like in the recording start request, and may also carry the CPVR service indication information.
  • the PVR-SCF may perform remote management operations on the recording terminal of the UE, such as reserving storage space, indicating a space usage policy, and issuing a recording task, as described in Embodiment 3.
  • Step 702 The UE sends a session establishment request to the BC-SCF.
  • the recording task information obtained by the UE from the PVR-SCF (including the recording content identifier, the channel information, the recording parameter information, etc., refer to the description of the recording task information in the second embodiment), extracts the corresponding network parameter, and initiates a session to the BC-SCF. Establish an INVITE request and negotiate to establish a content transmission channel. This process is consistent with the establishment process of the BC service.
  • the session establishment request may also carry one or more of the following identifiers: a recording initiation user identifier, a client recording user identifier, and a PVR-SCF identifier.
  • the UE may also actively request to obtain network parameters from a server (for example, SCF, SSF) in which the corresponding channel network parameter is stored in the network.
  • a server for example, SCF, SSF
  • Step 703 The BC-SCF receives a session establishment request from the UE, and the BC-SCF may determine, according to one or more of a recording storage user identifier, a client recording user identifier, and a PVR-SCF identifier obtained from the INVITE message.
  • the user has the service right to watch the BC channel, and returns a session establishment response message to the UE.
  • Step 704 The content delivery channel is established.
  • Step 705 The UE sends a join multicast group request, the multicast replication point starts to send a media stream to the UE, and the UE records the received media content.
  • Step 706 The UE determines, according to the recording time information, that the recording end time arrives, and therefore sends a session end request to the BC-SCF.
  • Step 707 The BC-SCF returns a response, the session is terminated, and the content delivery channel is removed. It should be noted that if the COD service is recorded by the above embodiment, the BC-SCF is replaced by COD-SCF, and the media providing entity is correspondingly COD-MF.
  • the flow of the seventh embodiment of the method for implementing client recording in the present invention is as shown in FIG. 8.
  • the client recording entity is a UE
  • the media providing entity is a multicast replication point
  • the recording service control entity is a PVR-SCF.
  • This embodiment shows a detailed process in which the PVR-SCF interacts with the UE and the BC-SCF according to the established recording task, establishes a content delivery channel, and removes the channel after the recording ends: Step 801: PVR-SCF to BC-SCF Send a session establishment request.
  • the PVR-SCF sends a session establishment INVITE request to the BC-SCF according to the recording content identifier included in the recording task, and is used to request the multicast replication point information, and the message may also carry the recording initiation user identifier and the client recording user identifier, PVR- SCF logo, recording time information, etc.
  • Step 802 The BC-SCF returns a session establishment response message to the PVR-SCF.
  • the BC-SCF After receiving the INVITE message, the BC-SCF determines one or more of the PVR-SCF identifiers based on the received recording user ID, the client recording user identifier, and the PVR-SCF identifier. After the authentication is passed, the BC-SCF determines the user to view the BC channel.
  • the response message (for example, 200 OK) is returned to the PVR-SCF, and the response message may carry multicast copy point information, which is specifically a multicast address or a multicast address and a port for providing the recorded content.
  • Step 803 The PVR-SCF sends a session establishment request to the UE.
  • the PVR-SCF obtains the multicast replication point information from the received response message, and sends a session establishment request INVITE message to the UE according to the client recording party identifier in the recording task.
  • the INVITE message includes multicast replication point information, and may also include CPVR service indication information, and recording time information, etc., so that the UE can control the start and end of the recording according to the recording time.
  • Step 804 The UE returns a session establishment response message to the PVR-SCF.
  • the UE may obtain the information of the multicast replication point, and then return a response message (for example, 200 OK) to the PVR-SCF, where the response message may carry the negotiation response.
  • a response message for example, 200 OK
  • Step 805 The content delivery channel is established.
  • Step 806 The UE records the media stream from the multicast replication point.
  • the UE initiates a request to join the multicast group to the multicast replication point according to the obtained multicast group address, and records the media stream from the multicast replication point after the UE joins the multicast group.
  • Step 807 The PVR-SCF sends a session end request to the UE.
  • the PVR-SCF When the PVR-SCF judges that the recording end time is reached according to the information in the recording task, it sends a session end request BYE message to the UE, and the message is used to request the UE to terminate the recording.
  • Step 808 The PVR-SCF sends a session end request to the BC-SCF.
  • Step 809 The UE tears down the content delivery channel.
  • the UE sends a request to leave the multicast group to the multicast replication point according to the multicast group address. After the UE leaves the host, the content delivery channel is removed and the recording is terminated.
  • the flow of the eighth embodiment of the method for implementing the client recording of the present invention is as shown in FIG. 9.
  • the client recording entity is the UE
  • the media providing entity is the COD-MF
  • the recording service control entity is the PVR-SCF.
  • This embodiment shows the detailed process of the PVR-SCF interacting with the UE and the COD-SCF according to the established recording task, so that the content delivery channel is established between the UE and the COD-MF, and the channel is removed after the recording ends:
  • Step 901 The PVR-SCF sends a session establishment request to the COD-SCF.
  • the PVR-SCF sends a session establishment INVITE request to the COD-SCF according to the recording content identifier included in the recording task, and the message may also carry a recording initiation user identifier, a client recording user identifier, a PVR-SCF identifier, a recording time information, or The content delivery channel information or the control channel information provided by the recording parameter information; the COD-SCF initiates the user identification, the client according to the received recording, the recording user identifier, one or more of the PVR-SCF identifiers, and determines that the user has the BC. After the service authority of the channel is passed, step 902 is performed.
  • Step 902 The COD-SCF forwards the session establishment request to the COD-MF.
  • Step 903 The COD-MF returns a session establishment response message to the COD-SCF.
  • the COD-MF returns a response message (for example, 200 OK) to the COD-SCF according to the session establishment request INVITE message, where the message carries a response of the content delivery channel or the control channel, and the response may include at least one or a combination of the following information: The sending address of the content delivery channel and the address and port of the control channel.
  • Step 904 The COD-SCF forwards the session establishment response message to the PVR-SCF.
  • Step 905 The PVR-SCF sends a session establishment request to the UE.
  • the PVR-SCF obtains the information of the content delivery channel or the control channel from the response message or both, and the PVR-SCF sends a session establishment request INVITE message to the UE according to the client recording party identifier in the recording task, where the message includes the above
  • the acquired content delivery channel or control channel information or both are carried.
  • the PVR-SCF may also carry the CPVR service indication information in the INVITE message, and the recording time information obtained from the PVR-SCF.
  • the PVR-SCF may carry the control channel information in the INVITE message, so as to establish a control channel between the PVR-SCF and the UE, and the subsequent PVR-SCF sends a message according to the recording time information in the recording task, and controls the UE pair.
  • the media stream is recorded, and the PVR-SCF can also use the control channel to instruct the UE to record and store the received media stream.
  • Step 906 The UE returns a session establishment response message to the PVR-SCF.
  • the UE After obtaining the information from the session establishment request INVITE message, the UE returns a 200 OK response message to the PVR-SCF.
  • the UE may carry the content delivery channel information or the control channel information of the response COD-MF or both in the response message, or carry the control channel information that answers the PVR-SCF.
  • Step 907 The PVR-SCF sends a session establishment request to the COD-SCF.
  • the PVR-SCF obtains the content delivery channel information or the control channel information of the UE response COD-MF from the response message returned by the UE or both, and sends a session establishment request containing the above information to the COD-SCF.
  • Step 908 The COD-SCF forwards the session establishment request to the COD-MF.
  • Step 909 to step 910 Similar to step 903 to step 904, and details are not described herein again.
  • Step 911 A content delivery channel is established between the UE and the COD-MF.
  • Step 912 A control channel is established between the UE and the COD-MF.
  • the UE can establish a control channel with the PVR-SCF.
  • Step 913 The UE records the media stream from the COD-MF.
  • the UE uses the control channel to directly send a message (for example, PLAY) to the COD-MF to instruct the COD-MF to send the media stream; or the UE initiates recording according to the recording start time information or the PVR-SCF through the control channel.
  • the control message sends a start recording message to the COD-MF through the established control channel, instructing the COD-MF to send the media stream.
  • Step 914 The UE sends a session end request to the PVR-SCF.
  • the UE determines to send a session end request to the PVR-SCF after the recording is terminated according to the recording termination time information in the recording task, or according to the control message of the PVR-SCF being terminated by the control channel, or when the user wants to immediately terminate the recording,
  • the control channel sends a message to the COD-MF to terminate the recording, instructing the COD-MF to terminate the transmission of the media stream.
  • the UE sends a session end request BYE message to the PVR-SCF.
  • Step 915 The PVR-SCF forwards the session end request to the COD-SCF.
  • Step 916 The COD-SCF forwards the session end request to the COD-MF.
  • Step 917 The UE tears down the content delivery channel with the COD-MF.
  • Step 918 The UE removes the control channel between the COD and the MF.
  • the flow of the ninth embodiment of the method for implementing client recording according to the present invention is as shown in FIG. 10.
  • the client recording entity is the UE
  • the media providing entity is the COD-MF
  • the recording service control entity is the PVR-SCF 0.
  • the eighth embodiment of FIG. 9 is different in that, in this embodiment, another PVR-SCF interacts with the UE and the COD-SCF according to the established recording task, so that a content delivery channel is established between the UE and the COD-MF. And the detailed process of removing the channel after the recording ends:)
  • Step 1001 The PVR-SCF sends a session establishment request to the UE.
  • the PVR-SCF initiates a session establishment request INVITE message to the UE according to the client recording party identifier in the recording task, requesting to establish a session.
  • the INVITE message may include recording parameter information, content delivery channel information, or control channel information or both.
  • the PVR-SCF may also carry CPVR service indication information in the INVITE message.
  • the PVR-SCF may perform remote management operations on the recording terminal of the UE, such as reserving storage space, indicating a space usage policy, and issuing a recording task, as described in Embodiment 3.
  • Step 1002 The UE returns a session establishment response message to the PVR-SCF.
  • the UE After obtaining the information from the session establishment request INVITE message, the UE returns a 200 OK response message to the PVR-SCF.
  • the 200 OK response message carries content delivery channel information or control channel information provided by the UE or both.
  • Step 1003 The PVR-SCF sends a session establishment request to the COD-SCF.
  • the PVR-SCF sends a session establishment request INVITE message to the COD-SCF through the IMS system according to the recording content identifier in the recording task, where the INVITE message includes content delivery channel information or control channel information provided by the UE or both.
  • the message may also carry one of the following identifiers One or more types: recording initiation user ID, client recording user ID, PVR-SCF identifier.
  • the COD-SCF determines one or more of the PVR-SCF identifiers according to the received recording user ID, the client recording user identifier, and the PVR-SCF identifier. After the authentication is passed, step 1004 is performed.
  • Step 1004 The COD-SCF forwards the session establishment request to the COD-MF.
  • Step 1005 The COD-MF returns a session establishment response message to the COD-SCF.
  • the COD-MF After receiving the session establishment request INVITE message, the COD-MF returns a 200 OK response message to the COD-SCF, where the 200 OK response message carries the COD-MF negotiation response or both of the content delivery channel information or the control channel information, for example, Controls the address and port of the channel, the sending address and port of the content delivery channel.
  • Step 1006 The COD-SCF forwards the session establishment response message to the PVR-SCF.
  • Step 1007 The PVR-SCF sends a session establishment request to the UE.
  • the PVR-SCF obtains the response of the content delivery channel information and/or the control channel information provided by the COD-MF from the 200 OK response message, and sends an INVITE request to the UE according to the response, and the INVITE request includes the response information.
  • the PVR-SCF can carry control channel information in the INVITE message to establish
  • the received media stream is recorded and stored.
  • Step 1008 The UE returns a session establishment response message to the PVR-SCF.
  • Steps 1009 to 1011 Similar to steps 911 to 913, and details are not described herein again.
  • Step 1012 The COD-MF sends a session end request to the COD-SCF.
  • Step 1013 The COD-SCF forwards the session end request to the PVR-SCF.
  • Step 1014 The PVR-SCF sends a session end request to the UE.
  • Steps 1015 to 1016 Similar to steps 917 to 918, and details are not described herein again.
  • the process of the tenth embodiment of the method for implementing the client recording of the present invention is as shown in FIG. 11.
  • the client recording entity is the UE
  • the media providing entity is the multicast recording point
  • the recording service control entity is the PVR-SCF 0.
  • This embodiment shows the detailed process of the PVR-SCF controlling the establishment of the content delivery channel when the UE submits the recording task to the BC-SCF:
  • Step 1101 The UE submits a recording task to the BC-SCF.
  • the manner of submitting the recording task and the information carried by the recording task are similar to those described in step 301, and are not described here.
  • Step 1102 The BC-SCF sends a session establishment request to the PVR-SCF.
  • the BC-SCF After receiving the recording task, the BC-SCF sends a session establishment request INVITE message to the PVR-SCF.
  • the INVITE message carries the information of the multicast replication point and the recording task obtained from the UE.
  • Step 1103 The PVR-SCF performs a service subscription check after receiving the session establishment request.
  • Step 1104 The PVR-SCF sends a session establishment request to the UE.
  • the session establishment request sent by the PVR-SCF to the UE may include the multicast replication point information and the recording task information in the INVITE message.
  • Step 1105 The UE returns a session establishment response message to the PVR-SCF.
  • Step 1106 The PVR-SCF returns a session establishment response message to the BC-SCF.
  • Step 1107 The UE establishes a content delivery channel according to the obtained multicast replication point information and the multicast replication point.
  • the subsequent UE obtains the media content from the multicast replication point and records the content, and the content is removed after the recording is completed.
  • the process of the delivery channel is similar to the description of the foregoing embodiment, and details are not described in this embodiment.
  • Step 1201 The UE sends a session change request to the PVR-SCF.
  • the UE sends a session change request to the PVR-SCF when it is found that the storage space is insufficient or other reasons, and the request contains the control and content delivery channel information.
  • Step 1202 The PVR-SCF sends a session change request to the BC-SCF.
  • the session change request sent by the PVR-SCF to the BC-SCF contains the control and content delivery channel information obtained from the UE.
  • Step 1203 The BC-SCF sends a session establishment request to the MF.
  • the BC-SCF selects the MF to buffer the content that has not been recorded by the UE, and therefore sends a session establishment request to the MF, where the request carries control and content delivery channel information.
  • Step 1204 The MF returns a session establishment response message to the BC-SCF.
  • the response message returned by the MF to the BC-SCF carries the control of the MF response and the content delivery channel information.
  • Step 1205 The BC-SCF returns a session change response to the PVR-SCF.
  • the session change response returned by the BC-SCF carries the control of the MF response and the content delivery channel information.
  • Step 1206 The PVR-SCF returns a session change response to the UE.
  • the session change response returned by the PVR-SCF to the UE carries the control of the MF response and the content delivery channel information.
  • Step 1207 The UE sends a request to leave the multicast group to the multicast replication point.
  • Step 1208 Establish a content delivery and control channel between the UE and the MF.
  • the UE can control the recording of the media stream through the control channel, or can send a pause recording or terminate the recording command.
  • the PVR-SCF and the BC-SCF, the PVR-SCF and the COD-SCF may be combined into the same entity or an independent entity.
  • the combination is a unified SCF, all the PVRs in the above embodiment process.
  • the interaction between SCF and BC-SCF, or PVR-SCF and COD-SCF is an internal interaction of the entity.
  • the recording of the client is realized through the interaction between the entities in the network, and the user experience when using the IMS-based IPTV service is improved.
  • the present invention also provides an embodiment of a system and recording control entity that implements client recording.
  • FIG. 13 A block diagram of an embodiment of a system for implementing client recording of the present invention is shown in FIG. 13, which includes: a recording originating entity 1310, a recording control entity 1320, a client recording entity 1330, and a media providing entity 1340.
  • the recording initiating entity 1310 is configured to send a recording task to the recording control entity 1320, where the recording task includes an identifier of the recorded content, and/or a client recording entity 1330 or an identifier of the user; and the recording control entity 1320 is configured to receive After the recording task, the client recording entity 1330 is controlled to record the media provided by the media providing entity 1340 according to the recording task. Further, the recording control entity 1320 may be further configured to: after the receiving the recording task, determine that the recording initiating entity 1310 has the right to control the client recording entity 1330 to record the media content, and/or determine the client recording When the entity 1330 has the right to record the media content, the operation of controlling the media recording entity 1330 to record the media content according to the recording task is performed.
  • FIG. 14 A block diagram of a first embodiment of a recording control entity that implements client recording is shown in FIG. 14, and the recording control entity includes: a receiving unit 1410 and a control unit 1420.
  • the receiving unit 1410 is configured to receive a recording task, where the recording task includes an identifier of the recorded content, and/or an identifier of the client recording entity or the user;
  • the control unit 1420 is configured to control the recording media of the client recording entity according to the recording task.
  • FIG. 15 A block diagram of a second embodiment of a recording control entity for implementing client recording is shown in FIG. 15.
  • the recording control entity includes: a receiving unit 1510, a determining unit 1520, an executing unit 1530, and a control unit 1540.
  • the receiving unit 1510 is configured to receive a recording task, where the recording task includes an identifier of the recorded content, and/or an identifier of the client recording entity or the user;
  • the determining unit 1520 is configured to determine whether the recording initiating entity has the right to control the recording of the media content by the client recording entity;
  • the determining unit 1520 is further configured to determine whether the client recording entity has permission to record the media content
  • the executing unit 1530 is configured to trigger the control unit 1540 to perform the performing when the recording initiating entity has the right to control the client recording entity to record the media content, or the client recording entity has permission to record the media content. control function;
  • the control unit 1540 is configured to control the client recording entity to record the media content according to the recording task.
  • FIG. 16 A block diagram of a third embodiment of the recording control entity for implementing client recording is shown in FIG. 16.
  • the recording control entity includes: a receiving unit 1610 and a control unit 1620.
  • the receiving unit 1610 is configured to receive a recording task, where the recording task includes an identifier of the recorded content, and/or an identifier of the client recording entity or the user;
  • the control unit 1620 includes:
  • the establishing unit 1621 is configured to trigger the establishment of the content delivery channel according to the identifier of the recorded content in the recording task and/or the identifier of the client recording entity or the user; the recording unit 1622 is configured to control the client recording by using the content delivery channel The entity receives and records the media content; an ending unit) 1623, configured to delete the content delivery channel when the recording ends.
  • FIG. 17 A block diagram of a fourth embodiment of a recording control entity for implementing client recording is shown in FIG. 17, and the recording control entity includes: a receiving unit 1710 and a control unit 1720.
  • the receiving unit 1710 is configured to receive a recording task, where the recording task includes an identifier of the recorded content and/or an identifier of the client recording entity or the user;
  • the control unit 1720 includes:
  • the establishing unit 1721 is configured to trigger to establish a delivery channel according to the identifier of the recorded content in the recording task and/or the identifier of the client recording entity or the user; the recording unit 1722 is configured to control, by the content delivery channel, the client recording entity to receive and Recording the media content; an abnormality unit 1723, configured to delete the content delivery channel when the recording is abnormal; the establishing unit 1721 is further configured to establish a transmission channel between the client recording entity and the media cache entity
  • the buffer unit 1724 is configured to control, by using the transmission channel, the media cache entity to cache the media content or receive a recording command sent by the client recording entity.
  • a recording task including an identifier of a recorded content and/or an identifier of a client recording entity is received, and the client is recorded according to the recording task to record the medium. content.
  • the recording of the client is realized through interaction between entities in the network, and the user experience when using the IMS-based IPTV service is improved.
  • the method includes the following steps: collecting user service information, and obtaining physical layer target parameters according to QOE parameters corresponding to each service information; receiving line operation information of the user, where the line operation information includes test parameters and pre-stored lines Target parameter; using the physical layer target parameter and the line operation information as input parameters of a minimum power algorithm, and obtaining an optimized power spectrum by a minimum power algorithm.
  • the storage medium is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like. While the invention has been described by the embodiments of the present invention, it will be understood that

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Television Signal Processing For Recording (AREA)

Description

实现客户端录制的方法、 系统及录制控制实体
本申请要求于 2008 年 9 月 9 日提交中国专利局、 申请号为 200810212006.X, 发明名称为"实现客户端录制的方法、 系统及录制控制实体" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
) 技术领域
本发明涉及通信技术领域，特别涉及一种实现客户端录制的方法、 系统及 录制控制实体。
背景技术
IPTV ( Internet Protocol Television, 互联网协议电视）是一种利用宽带有
) 线电视网， 集互联网、 多媒体、 通讯等技术于一体， 向家庭用户提供包括数字 电视在内的多种交互式服务的技术。 用户可以通过 PC ( Personal Computer, 个人计算机）或机顶盒与电视结合的方式使用 IPTV业务， 也可以通过移动终 端使用 IPTV业务。 IMS ( IP Multimedia Subsystem, IP多媒体子系统 )是独立 于接入技术的基于 IP的标准体系， 其与现存的语音和数据网络都可以互通，
) 无论对于固定网络用户还是移动网络用户， IMS都能使通过各种类型的客户端 之间建立对等的 IP通信。
现在基于 IMS的 IPTV架构直接重用 IMS 的相关功能实体， 通过适当增 加新的功能实体以及对现有功能实体的扩充， 实现 IMS对 IPTV业务的支持。 如图 1所示， 为基于 IMS的 IPTV架构示意图：
) 图 1中， IPTV直接重用的 IMS的功能实体包括 NASS( Network Attachment
Sub-System, 网络附着子系统） 和 RACS ( Resource and Admission Control Sub-System, 资源与接纳控制子系统）， NASS 完成对用户附着于的接入网络 的管理， 包括用户验证和网络地址的分配和位置管理等； RACS完成资源的调 度和分配， 实现 QoS ( Quality of Service,服务质量 )控制。其中， SDF ( Service
) Detect Functions, 业务发现功能）用于为 UE ( User Equipment, 用户设备 )选 择一个 IPTV业务提供必要的信息， SSF ( Service Select Functions, 业务选择 功能）用于向 UE提供可以浏览和选择的可用服务列表。
每一个 IPTV业务均由一对 IPTV SCF ( Service Control Functions , 业务控 制功能）和 IPTV MF( Media Functions,媒体功能）组成。图 1中， COD( Content On Demand, 内容点播 )是 IPTV的业务功能， 分为 COD-SCF ( COD业务控 制功能）、 COD-MCF ( COD媒体控制功能）和 COD-MDF ( COD媒体递交功 能 ); BC ( Broadcast, 广播 )是 IPTV的业务功能， 分为 BC-SCF ( BC业务控 制功能）、 BC-MCF ( BC媒体控制功能）和 BC-MDF ( BC媒体递交功能）； PVR
) ( Personal Video Recorder , 个人录制 )用于实现 IPTV业务的录制功能， 分为 PVR-SCF (个人录制业务控制功能）、 PVR-MCF (录制媒体控制功能） 和 PVR-MDF (录制媒体递交功能）。 上述三种功能中的 SCF通过 IMS Core (核 心功能）与 UE进行信息交互， MCF与 UE之间的媒体控制消息通过 Xc，参考 点进行交互， MDF与 UE之间的媒体数据通过 Xc"参考点进行交互。
) 发明人在对现有技术研究的过程中发现，虽然基于 IMS的 IPTV架构中给 出了各个实体的主要任务，但是没有描述如何在各个实体之间进行信息交互以 客户端设备或位于网络中的存储设备。
发明内容
) 本发明实施例的目的在于提供一种实现客户端录制的方法、系统及录制控 制实体， 以使用户能够对媒体内容进行录制。
一种实现客户端录制的方法， 应用于基于 IP多媒体子系统的互联网协议 电视 IPTV系统中， 包括：
接收录制任务， 所述录制任务中包括录制内容的标识和 /或客户端录制方
) 标识；
根据所述录制内容的标识和 /或所述客户端录制方标识控制客户端录制方 录制媒体内容。
一种实现客户端录制的系统， 基于 IP 多媒体子系统的互联网协议电视 IPTV, 包括： 录制发起实体和录制控制实体，
) 所述录制发起实体， 用于向所述录制控制实体发送录制任务， 所述录制任 务中包括录制内容的标识和 /或客户端录制方标识；
所述录制控制实体， 用于接收到所述录制任务后，根据所述录制内容的标 识和 /或所述客户端录制方标识控制客户端录制方录制媒体内容。
一种录制控制实体， 包括： 接收单元， 用于接收录制任务， 所述录制任务中包括录制内容的标识和 / 或客户端录制方标识；
控制单元， 用于根据所述录制内容的标识和 /或所述客户端录制方标识控 制客户端录制实体录制媒体内容。
) 附图说明
图 1为现有基于 IMS的 IPTV架构示意图；
图 2为本发明实现客户端录制的方法的第一实施例流程图；
图 3为本发明实现客户端录制的方法的第二实施例流程图；
图 4为本发明实现客户端录制的方法的第三实施例流程图；
) 图 5为本发明实现客户端录制的方法的第四实施例流程图；
图 6为本发明实现客户端录制的方法的第五实施例流程图；
图 7为本发明实现客户端录制的方法的第六实施例流程图；
图 8为本发明实现客户端录制的方法的第七实施例流程图；
图 9为本发明实现客户端录制的方法的第八实施例流程图；
) 图 10为本发明实现客户端录制的方法的第九实施例流程图；
图 11为本发明实现客户端录制的方法的第十实施例流程图；
图 12为本发明实现客户端录制的方法的第十一实施例流程图；
图 13为本发明实现客户端录制的系统的实施例框图；
图 14为本发明实现客户端录制的录制控制实体的第一实施例框图；
) 图 15为本发明实现客户端录制的录制控制实体的第二实施例框图；
图 16为本发明实现客户端录制的录制控制实体的第三实施例框图； 图 17为本发明实现客户端录制的录制控制实体的第四实施例框图。
具体实施方式
本发明实施例提供了一种实现客户端录制的方法、 系统及录制控制实体， ) 接收包括录制内容的标识和 /或客户端录制方标识， 根据所述录制任务控制所 述客户端录制实体录制所述媒体内容。
下面介绍一下本发明的几个基本概念：
录制发起实体， 用于向录制控制实体提交录制任务， 录制控制实体对录制 任务进行业务签约检查并记录， 完成录制任务的建立过程。 需要说明的是， 录制任务可以是用户设备提交的， 也可以是网络配置的； 录制发起实体可以为用户设备， 也可以为存储网络配置数据的网络实体； 录制 控制实体可以是 PVR-SCF或其他控制实体。
在本发明实施例中， 录制发起实体所归属的用户为录制发起用户； 录制发 ) 起实体和录制发起用户可以统称为录制发起方。
录制控制实体可以根据所接收到的录制任务控制客户端录制实体录制媒 体内容。
媒体提供实体用于向客户端录制实体提供媒体内容， 既可以是媒体服务 器， 也可以是用户设备。
) 客户端录制实体对来自媒体提供实体的媒体流进行接收并录制；客户端录 制实体所归属的用户为客户端录制用户；客户端录制实体和客户端录制用户可 以统称为客户端录制方。
本发明实现客户端录制的方法的第一实施例流程如图 2所示：
步骤 201 : 接收包括录制内容的标识和客户端录制方标识的录制任务。 ) 其中，录制任务可以为用户设备发送的录制任务或网络实体发送的录制任 务。
进一步， 录制任务还可以包括录制时间信息、 录制发起方标识、 录制参数 信息、或录制能力信息等； 其中的客户端录制方标识可以是客户端录制实体或 用户的标识； 录制发起方标识可以是录制发起实体或用户的标识。
) 步骤 202: 根据录制任务控制客户端录制实体录制该媒体内容。
根据录制任务中录制内容的标识， 和 /或客户端录制实体或用户的标识， 建立内容交付通道，所述客户端录制实体通过所述内容交付通道控制接收并录 制所述媒体内容。
应用本发明实施例， 通过网络中各个实体之间的交互实现了客户端的录 ) 制， 提高了使用基于 IMS的 IPTV业务时的用户体验。
下面通过几个实施例详细描述本发明实现客户端录制的方法中建立录制 任务的详细过程。
本发明实现客户端录制的方法的第二实施例流程如图 3所示，该实施例中 录制发起实体和客户端录制实体均为 UE, 录制业务控制实体为 PVR-SCF, 该 实施例详细示出了用户通过 UE提交录制任务， 并请求通过该 UE录制正在收 看或即将开始的某个节目内容的录制任务建立的过程：
步骤 301 : UE向 PVR-SCF提交录制任务。
在提交录制任务时， UE可以通过 HTTP ( Hypertext Transport Protocol, 超 ) 文本传输协议） 方式登记录制任务， 并提交给 PVR-SCF; 也可以将录制任务 携带在消息中提交给 PVR-SCF, 消息可以为 SIP ( Session Initiation Protocol, 会话初始协议） MESSAGE消息、 INVITE消息、 SUBSCRIBE消息、 INFO 消息或 REFER消息等。 当通过 SIP消息提交录制任务时， UE与 PVR-SCF之 间的消息都可以通过 IMS体系中的实体路由，如 P-CSCF ( Call Session Control ) Function, 呼叫会话控制功能）或 S-CSCF来传送。
录制任务中必要包含录制内容标识和客户端录制方的标识，录制内容标识 用于表示用户希望录制的内容、 频道、 节目或业务； 客户端录制方标识表示存 储内容的用户或设备，本实施例中客户端录制方的用户与录制发起方的用户相 同， 存储录制节目的设备为该用户所拥有的 UE设备， 此时客户端录制方标识 ) 可以为用户的标识， 如 IMPU ( IP Multimedia Public Identity, 公共用户身份标 识）。
可选的， 录制任务中还可以包括录制时间信息、 录制发起方用户标识、 CPVR (客户端个人视频录像， Client-Personal Video Recorder ) 内容标识、 频 道信息、 录制终端能力信息、 录制参数信息等。 其中， 录制时间信息包括录制 ) 的起始时间、 终止时间或录制时长， 例如， 从当前时刻开始录制正在收看的节 目， 则起始时间为 "NOW" , 录制终止时间或录制时长也可不做设置； 录制发 起方标识表示发起录制的终端或所归属用户的标识； CPVR内容标识表示录制 的媒体内容， 用户可以通过该标识查看节目内容； 频道信息包括至少如下之一 或其组合： 用户期望录制的 BC频道对应的组播地址、 端口信息、 媒体参数信 ) 息； 录制终端能力信息包括录制终端剩余存储空间等表示其实际能力的信息； 录制参数信息表示录制内容媒体信息， 例如编解码类型或格式等信息。
步骤 302: PVR-SCF接收到录制任务后进行业务签约检查。
PVR-SCF读取录制任务中的信息后， 根据录制发起用户和客户端录制用 户的信息判断： 录制发起用户只否有权限控制客户端录制终端； 客户端录制用 户是否有权限录制所请求的媒体内容。 进一步， PVR-SCF还可以根据录制时 间信息和录制参数信息得出录制该内容所需的存储空间大小，或者根据录制能 力信息判断录制存储终端是否有足够空间进行媒体录制，并且当录制任务中没 有提供录制参数信息时向其它实体查询并获取录制参数信息。当业务签约检查 ) 完成后， PVR-SCF可以记录该录制任务。
步骤 303: 录制任务建立后 PCR-SCF向 UE返回录制任务提交响应。 如 果步骤 302中 PVR-SCF得到录制所需空间信息， 则在本步响应中还携带存储 空间预留指示信息， 信息中包含： 一个预留存储空间的指示， 以及所需预留空 间的大小。
) 本发明实现客户端录制的方法的第三实施例流程如图 4所示，该实施例中 录制发起实体为 UE1 ,客户端录制实体为 UE2,录制业务控制实体为 PVR-SCF, 该实施例详细示出了用户通过 UE1提交录制任务， 请求通过远端设备 UE2录 制正在收看或即将开始的某个节目内容的录制任务建立的过程：
步骤 401 : UE1向 PVR-SCF提交录制任务。
) 提交录制任务的方式和录制任务携带的信息与步骤 301 中描述类似， 在 此不再赘述。
需要说明的是， 本实施例中的 UE1和 UE2可以属于同一用户， 也可以属 于不同用户。
步骤 402: PVR-SCF接收到录制任务后进行业务签约检查。
) PVR-SCF主要检查录制发起方用户是否有权限控制客户端录制方的存储 终端。 具体的业务签约检查过程与步骤 302描述类似， 在此不再赘述。
PVR-SCF还可能根据 UE在录制任务中给出的录制时间信息以及录制参数 信息得出录制该内容所需的存储空间大小。如果录制任务中没有提供录制参数 信息， 则 PVR-SCF还可能动态向其他实体发起查询并获得参数信息 （如编解 ) 码类型）； 检查通过后， PVR-SCF记录录制任务。
步骤 403: PVR-SCF与 UE2交互， 进行录制终端远程管理。
PVR-SCF根据录制任务中的客户端录制方标识向 UE2发起远程管理请 求，该操作可以完成以下功能： 1 )在远程录制终端 UE2中预留录制所需空间， 以及空间的使用策略等， 例如 PVR-SCF可以在远程管理请求中包含一个预留 存储空间的指示， 以及预留存储空间的大小信息，还可能包含空间使用策略的 指示， 如存储空间不足时覆盖原有内容等； 2 ) 录制任务下发， 即 PVR-SCF 在录制任务提交时就将录制任务下发给录制存储终端，后续由终端管理任务并 启动录制。
) PVR-SCF还可能向保存用户终端信息的实体查询获取 UE2的状态信息， 如 Presence Server, 检查 UE2是否在线， 或 UE2上是否有足够录制该节目的 存储空间等。
需要说明的是， 步骤 403是可选的。
步骤 404: 录制任务建立后 PCR-SCF向 UE返回录制任务提交响应。 需 ) 要说明的是， 步骤 404是可选的。
本发明实现客户端录制的方法的第四实施例流程如图 5所示，该实施例中 录制发起实体和客户端录制实体均为 UE, 录制业务控制实体为 PVR-SCF, 该 实施例详细示出了用户使用 UE通过 BC-SCF提交录制任务， 并请求通过该 UE录制正在收看的某个节目内容的录制任务建立的过程：
) 步骤 501 : UE向 BC-SCF提交录制任务。
提交录制任务的方式和录制任务携带的信息与步骤 301 中描述类似， 在 此不再赘述。
需要说明的是， 本实施例中的 BC-SCF也可以为 COD-SCF。
步骤 502: BC-SCF向 PVR-SCF转发录制任务。
) BC-SCF可以通过 SIP MESSAGE消息、 INVITE消息或 INFO消息转发录 制任务。
步骤 503: PVR-SCF接收到录制任务后进行业务签约检查。
业务签约检查过程与步骤 302描述类似。
步骤 504: 录制任务建立后 PCR-SCF向 BC-SCF返回录制任务提交响应。 ) 步骤 505: BC-SCF向 UE转发录制任务提交响应。
下面通过几个实施例详细描述本发明实现客户端录制的方法中根据录制 任务控制客户端录制实体录制该媒体内容的详细过程。
本发明实现客户端录制的方法的第五实施例流程如图 6所示， 该实施例 中客户端录制实体为 UE、 媒体提供实体为组播复制点、 录制业务控制实体为 PVR-SCF0该实施例详细示出了 PVR-SCF根据已建立的录制任务触发 BC-SCF 与 UE之间交互， 使得 UE与 BC-SCF协商建立内容交付通道的详细过程： 步骤 601 : PVR-SCF向 BC-SCF发送录制启动请求。
PVR-SCF根据录制任务中的录制内容标识和客户端录制方标识， 通过 ) IMS体系向 BC-SCF发送录制启动请求， 该消息用于触发 BC-SCF与 UE协商 建立内容交付通道。 在具体实现时， 录制启动请求可以是 SIP中的 REFER消 息或 MESSAGE消息等。
录制启动请求中可以携带如下信息中的一种或多种： 录制存储终端 或用 户的标识。 本实施例中为 UE标识， 或 UE所归属的用户的标识； PVR-SCF标 ) 识， 可以是 PVR-SCF生成的业务标识或 PVR-SCF实体的标识。 录制内容标 识录制时间信息以及录制发起用户标识， 均与录制任务中包含的该信息一致；
CPVR业务指示信息， 用于指示 UE此为 CPVR业务， 需要对收到的媒体内容 进行录制存储。
步骤 602: BC-SCF向 UE发送会话建立请求。
) BC-SCF根据 PVR-SCF发送的录制启动请求消息中包含的客户端录制方 用户标识、 录制发起方用户标识以及 PVR-SCF标识中的一种或多种， 判断用 户有收看 BC频道的业务权限， 鉴权通过后根据从 PVR-SCF处获得的录制存 储用户标识或者录制存储终端标识（也可以两者都获取 ),向录制存储终端 UE 发起会话建立 INVITE请求， 协商建立内容交付通道。
) BC-SCF可以在该 INVITE消息中携带预先保存的组播复制点信息， 该信 息具体为提供录制内容的组播地址或者组播地址和端口，该消息中还可以携带
CPVR业务指示信息， 以及从 PVR-SCF获取的录制时间信息等。
步骤 603: UE向 BC-SCF返回会话建立响应消息。
UE接收到 INVITE 消息后， 可以从中获取组播复制点的信息， 然后向 ) BC-SCF返回响应消息 （例如， 200OK ), 该响应消息中可以携带协商应答。
步骤 604: 内容交付通道建立完毕。
需要说明的是， 如果通过上述实施例录制 COD业务， 则将 BC-SCF替换 为 COD-SCF, 媒体提供实体相应由组播复制点替换为 COD-MF。
本发明实现客户端录制的方法的第六实施例流程如图 7 所示， 该实施例 中客户端录制实体为 UE、 录制业务控制实体为 PVR-SCF。 该实施例详细示出 了 PVR-SCF根据已建立的录制任务触发 UE与 BC-SCF之间交互， 使得 UE 与 BC-SCF协商建立内容交付通道的详细过程：
步骤 701： PVR-SCF向 UE发送录制启动请求。
) PVR-SCF根据录制任务中的录制内容标识和客户端录制方标识， 通过
IMS体系向 UE发送录制启动请求， 该请求用于触发 UE与 BC-SCF协商建立 内容交付通道。 在具体实现时， 录制启动请求可以是 SIP中的 REFER消息或 MESSAGE消息等。
其中， PVR-SCF在录制启动请求中携带录制任务信息 （包含录制时间信 ) 息、 录制内容标识等）， 以及还可能携带 CPVR业务指示信息。
此外 PVR-SCF还可能对 UE进行录制终端远程管理操作， 例如预留存储 空间， 指示空间使用策略， 以及下发录制任务等， 参见实施例三中描述。
步骤 702: UE向 BC-SCF发送会话建立请求。
UE从 PVR-SCF处获得的录制任务信息（包括录制内容标识、 频道信息、 ) 录制参数信息等， 参考实施例二中录制任务信息的描述）中提取相应的网络参 数， 向 BC-SCF发起会话建立 INVITE请求， 协商建立内容传输通道， 此流程 与 BC业务的建立流程一致。
会话建立请求中还可能携带以下标识中的一种或多种： 录制发起用户标 识、 客户端录制用户标识以及 PVR-SCF标识。 参数， UE还可能主动向网络中存储有相应频道网络参数的服务器（例如 SCF、 SSF )请求获取网络参数。
步骤 703: BC-SCF接收来自 UE的会话建立请求， BC-SCF可能根据从 INVITE消息中获取的录制存储用户标识、客户端录制用户标识以及 PVR-SCF ) 标识中的一种或多种， 判断用户有收看 BC频道的业务权限， 向 UE返回会话 建立响应消息。
步骤 704: 内容交付通道建立完毕。
步骤 705: UE发送加入组播组请求， 组播复制点开始向 UE发送媒体流， UE对收到的媒体内容进行录制。 步骤 706: UE根据录制时间信息判定录制结束时间到达， 故向 BC-SCF 发送会话结束请求。
步骤 707: BC-SCF返回响应， 会话终止， 内容交付通道拆除。 需要说明的是， 如果通过上述实施例录制 COD业务， 则将 BC-SCF替换 ) 为 COD-SCF, 媒体提供实体相应为 COD-MF。
本发明实现客户端录制的方法的第七实施例流程如图 8 所示， 该实施例 中客户端录制实体为 UE、 媒体提供实体为组播复制点、 录制业务控制实体为 PVR-SCF。 本实施例示出了 PVR-SCF根据建立的录制任务分别与 UE 和 BC-SCF交互， 建立内容交付通道， 并在录制结束后拆除该通道的详细过程： ) 步骤 801 : PVR-SCF向 BC-SCF发送会话建立请求。
PVR-SCF根据录制任务中包含的录制内容标识向 BC-SCF发送会话建立 INVITE请求， 用于请求组播复制点信息， 该消息中还可以携带录制发起用户 标识、 客户端录制用户标识， PVR-SCF标识， 录制时间信息等。
步骤 802: BC-SCF向 PVR-SCF返回会话建立响应消息。
) BC-SCF接收到 INVITE消息后， 根据收到的录制发起用户标识、 客户端 录制用户标识， PVR-SCF标识的一种或多种， 判断用户有收看 BC频道的业 务权限， 鉴权通过后向 PVR-SCF返回响应消息（例如， 200OK ), 该响应消息 中可以携带组播复制点信息，该信息具体为提供录制内容的组播地址或者组播 地址和端口。
) 步骤 803: PVR-SCF向 UE发送会话建立请求。
PVR-SCF从接收到的响应消息中获取组播复制点信息， 并根据录制任务 中的客户端录制方标识向 UE发送会话建立请求 INVITE消息。
INVITE消息中包含组播复制点信息， 还可能包含 CPVR业务指示信息， 以及录制时间信息等， 使得 UE可以根据录制时间控制录制的开始和结束。 ) 步骤 804: UE向 PVR-SCF返回会话建立响应消息。
UE接收到 INVITE 消息后， 可以从中获取组播复制点的信息， 然后向 PVR-SCF返回响应消息 （例如， 200 OK ), 该响应消息中可以携带协商应答。
步骤 805: 内容交付通道建立完毕。
步骤 806: UE对来自组播复制点的媒体流进行录制。 UE根据获取的组播组地址向组播复制点发起加入该组播组的请求， 当 UE加入该组播组后对来自该组播复制点的媒体流进行录制。
步骤 807: PVR-SCF向 UE发送会话结束请求。
PVR-SCF根据录制任务中的信息判断到达录制结束时间时， 则向 UE发 ) 送会话结束请求 BYE消息， 该消息用于请求 UE终止录制。
步骤 808: PVR-SCF向 BC-SCF发送会话结束请求。
步骤 809: UE拆除内容交付通道。
UE根据组播组地址向组播复制点发送离开该组播组的请求， 当 UE离开 该主不住后则内容交付通道拆除完毕， 录制终止。
) 本发明实现客户端录制的方法的第八实施例流程如图 9所示， 该实施例 中客户端录制实体为 UE、 媒体提供实体为 COD-MF、 录制业务控制实体为 PVR-SCF。 本实施例示出了 PVR-SCF根据建立的录制任务分别与 UE 和 COD-SCF交互， 使得 UE与 COD-MF之间建立内容交付通道， 并在录制结束 后拆除该通道的详细过程：
) 步骤 901： PVR-SCF向 COD-SCF发送会话建立请求。
PVR-SCF根据录制任务中包含的录制内容标识向 COD-SCF发送会话建 立 INVITE请求， 该消息中还可以携带录制发起用户标识、 客户端录制用户标 识， PVR-SCF标识， 录制时间信息、 或根据录制参数信息提供的内容交付通 道信息或控制通道信息等； COD-SCF根据收到的录制发起用户标识、 客户端 ) 录制用户标识， PVR-SCF标识的一种或多种， 判断用户有收看 BC频道的业 务权限， 鉴权通过后执行步骤 902。
步骤 902: COD-SCF向 COD-MF转发会话建立请求。
步骤 903: COD-MF向 COD-SCF返回会话建立响应消息。
COD-MF根据会话建立请求 INVITE消息，向 COD-SCF返回响应消息（例 ) 如， 200OK ), 该消息中携带内容交付通道或控制通道的应答， 应答中可以至 少包括如下信息之一或者组合：内容交付通道的发送地址和端口或控制通道的 地址和端口。
步骤 904: COD-SCF向 PVR-SCF转发会话建立响应消息。
步骤 905: PVR-SCF向 UE发送会话建立请求。 PVR-SCF从响应消息中获取内容交付通道或控制通道的信息或两者都携 带， PVR-SCF根据录制任务中的客户端录制方标识向 UE发送会话建立请求 INVITE消息， 该消息中包含上述已经获取的内容交付通道或控制通道的信息 或两者都携带。 PVR-SCF还可以在 INVITE消息中携带 CPVR业务指示信息， ) 以及从 PVR-SCF获取的录制时间信息等。
或者， PVR-SCF可以在 INVITE 消息中携带控制通道信息， 以便建立 PVR-SCF与 UE之间的控制通道， 后续 PVR-SCF通过该控制通道根据录制任 务中的录制时间信息发送消息， 控制 UE对媒体流进行录制， PVR-SCF也可 以利用该控制通道指示 UE对接收到的媒体流进行录制存储。
) 步骤 906: UE向 PVR-SCF返回会话建立响应消息。
UE从会话建立请求 INVITE消息中获取信息后，向 PVR-SCF返回 200OK 响应消息。 UE可以在该响应消息中携带应答 COD-MF的内容交付通道信息或 控制通道信息或两者都携带， 或者携带应答 PVR-SCF的控制通道信息。
步骤 907: PVR-SCF向 COD-SCF发送会话建立请求。
) PVR-SCF从 UE返回的响应消息中获取该 UE应答 COD-MF的内容交付 通道信息或控制通道信息或两者都携带， 向 COD-SCF发送包含上述信息的会 话建立请求。
步骤 908: COD-SCF向 COD-MF转发会话建立请求。
步骤 909至步骤 910: 与步骤 903至步骤 904类似， 在此不再赘述。
) 步骤 911： UE与 COD-MF之间建立内容交付通道。
步骤 912: UE与 COD-MF之间建立控制通道。
UE除了与 COD-MF之间建立控制通道外还可以与 PVR-SCF之间建立控 制通道。
步骤 913: UE对来自 COD-MF的媒体流进行录制。
) UE利用控制通道直接向 COD-MF发送启动录制的消息 （例如， PLAY ), 指示 COD-MF发送媒体流； 或者， UE根据录制起始时间信息， 或 PVR-SCF 通过控制通道发送的启动录制的控制消息， 通过建立的控制通道向 COD-MF 发送启动录制的消息， 指示 COD-MF发送媒体流。
步骤 914: UE向 PVR-SCF发送会话结束请求。 UE根据录制任务中的录制终止时间信息， 或根据 PVR-SCF由控制通道 发送的终止录制的控制消息，判定录制终止后向 PVR-SCF发送会话结束请求； 或者当用户希望立即终止录制时， 利用控制通道向 COD-MF发送终止录制的 消息， 指示 COD-MF终止传送媒体流。 COD-MF终止传送媒体流后， UE向 ) PVR-SCF发送会话结束请求 BYE消息。
步骤 915: PVR-SCF向 COD-SCF转发会话结束请求。
步骤 916: COD-SCF向 COD-MF转发会话结束请求。
步骤 917: UE拆除与 COD-MF之间的内容交付通道。
步骤 918: UE拆除与 COD-MF之间的控制通道。
) 本发明实现客户端录制的方法的第九实施例流程如图 10所示， 该实施例 中客户端录制实体为 UE、 媒体提供实体为 COD-MF、 录制业务控制实体为 PVR-SCF 0 与图 9 所示的实施例八的不同之处在于， 本实施例是另一种 PVR-SCF根据建立的录制任务分别与 UE和 COD-SCF 交互， 使得 UE 与 COD-MF之间建立内容交付通道， 并在录制结束后拆除该通道的详细过程： ) 步骤 1001 : PVR-SCF向 UE发送会话建立请求。
PVR-SCF根据录制任务中的客户端录制方标识向 UE发起会话建立请求 INVITE消息， 请求建立会话。 该 INVITE消息中可以包含录制参数信息、 内 容交付通道信息或控制通道信息或两者都携带。 PVR-SCF还可能在 INVITE 消息中携带 CPVR业务指示信息。
) 此外 PVR-SCF还可能对 UE进行录制终端远程管理操作， 例如预留存储 空间， 指示空间使用策略， 以及下发录制任务等， 详见实施例三中描述。
步骤 1002: UE向 PVR-SCF返回会话建立响应消息。
UE从会话建立请求 INVITE消息中获取信息后，向 PVR-SCF返回 200OK 响应消息。 该 200OK响应消息中携带 UE提供的内容交付通道信息或控制通 ) 道信息或两者都携带。
步骤 1003: PVR-SCF向 COD-SCF发送会话建立请求。
PVR-SCF根据录制任务中的录制内容标识， 通过 IMS 系统向 COD-SCF 发送会话建立请求 INVITE消息， 该 INVITE消息中包含了 UE提供的内容交 付通道信息或控制通道信息或两者都携带，该消息中还可能携带以下标识的一 种或多种：录制发起用户标识、客户端录制用户标识， PVR-SCF标识。 COD-SCF 根据收到的录制发起用户标识、 客户端录制用户标识， PVR-SCF标识的一种 或多种， 判断用户有收看 BC频道的业务权限， 鉴权通过后执行步骤 1004。
步骤 1004: COD-SCF将会话建立请求转发至 COD-MF。
) 步骤 1005: COD-MF向 COD-SCF返回会话建立响应消息。
COD-MF接收到会话建立请求 INVITE消息后，向 COD-SCF返回 200OK 响应消息，该 200OK响应消息中携带了 COD-MF对内容交付通道信息或控制 通道信息的协商应答或两者都携带， 例如控制通道的地址和端口、 内容交付通 道的发送地址和端口。
) 步骤 1006: COD-SCF将会话建立响应消息转发到 PVR-SCF。
步骤 1007: PVR-SCF向 UE发送会话建立请求。
PVR-SCF从 200OK响应消息中获取 COD-MF提供的内容交付通道信息 和 /或控制通道信息的应答， 根据该应答向 UE发送 INVITE请求， 该 INVITE 请求中包含了上述应答信息。
) 或者， PVR-SCF可以在 INVITE 消息中携带控制通道信息， 以便建立
PVR-SCF与 UE之间的控制通道， 后续 PVR-SCF通过该控制通道根据录制任 务中的录制时间信息发送消息， 控制 UE对媒体流进行录制， PVR-SCF也可 以利用该控制通道指示 UE对接收到的媒体流进行录制存储。
步骤 1008: UE向 PVR-SCF返回会话建立响应消息。
) 步骤 1009至步骤 1011 : 与步骤 911至步骤 913类似， 在此不再赘述。
步骤 1012: COD-MF向 COD-SCF发送会话结束请求。
步骤 1013: COD-SCF向 PVR-SCF转发会话结束请求。
步骤 1014: PVR-SCF向 UE发送会话结束请求。
步骤 1015至步骤 1016: 与步骤 917至步骤 918类似， 在此不再赘述。 ) 本发明实现客户端录制的方法的第十实施例流程如图 11所示， 该实施例 中客户端录制实体为 UE、 媒体提供实体为组播录制点、 录制业务控制实体为 PVR-SCF0 本实施例示出了 UE向 BC-SCF提交录制任务时， PVR-SCF控制 建立内容交付通道的详细过程：
步骤 1101 : UE向 BC-SCF提交录制任务。 提交录制任务的方式和录制任务携带的信息与步骤 301 中描述类似， 在 此不再赘述。
步骤 1102: BC-SCF向 PVR-SCF发送会话建立请求。
BC-SCF接收到录制任务后向 PVR-SCF发送会话建立请求 INVITE消息， ) 该 INVITE消息中携带组播复制点的信息， 以及从 UE处获取的录制任务。
步骤 1103: PVR-SCF接收到会话建立请求后进行业务签约检查。 步骤 1104: PVR-SCF向 UE发送会话建立请求。
PVR-SCF向 UE发送的会话建立请求 INVITE消息中可以包含组播复制 点信息和录制任务信息。
) 步骤 1105: UE向 PVR-SCF返回会话建立响应消息。
步骤 1106: PVR-SCF向 BC-SCF返回会话建立响应消息。
步骤 1107: UE根据获取的组播复制点信息与组播复制点之间建立内容交 付通道。
后续 UE从组播复制点获取媒体内容并录制，以及在录制完成后拆除内容 ) 交付通道的过程与前述实施例的描述类似， 本实施例不再赘述。
下面通过一个实施例详细描述本发明实现客户端录制的方法中当出现异 常情况时的过程。
本发明实现客户端录制的方法的第十一实施例流程如图 12所示， 该实施 例在第七实施例的基础上， 示出了当录制过程出现异常时， UE与组播复制点 ) 之间交互的详细过程， 本实施例步骤 1201之前的过程与图 8中所示的一致： 步骤 1201 : UE向 PVR-SCF发送会话更改请求。
UE在录制过程中， 当发现存储空间不足或其它原因等需要暂停录制时， 则向 PVR-SCF发送会话更改请求， 请求中包含控制和内容交付通道信息。
步骤 1202: PVR-SCF向 BC-SCF发送会话更改请求。
) PVR-SCF向 BC-SCF发送的会话更改请求中包含从 UE处获得的控制和 内容交付通道信息。
步骤 1203: BC-SCF向 MF发送会话建立请求。
BC-SCF选择 MF为 UE未录制完的内容进行緩存， 因此向 MF发送会话 建立请求， 该请求中携带控制和内容交付通道信息。 步骤 1204: MF向 BC-SCF返回会话建立响应消息。
MF向 BC-SCF返回的响应消息中携带了 MF应答的控制和内容交付通道 信息。
步骤 1205: BC-SCF向 PVR-SCF返回会话更改响应。
) BC-SCF返回的会话更改响应中携带 MF应答的控制和内容交付通道信 息。
步骤 1206: PVR-SCF向 UE返回会话更改响应。
PVR-SCF向 UE返回的会话更改响应中携带 MF应答的控制和内容交付 通道信息。
) 步骤 1207: UE向组播复制点发送离开组播组的请求。
步骤 1208: UE与 MF之间建立内容交付和控制通道。
UE可以通过控制通道控制媒体流的录制， 也可以发送暂停录制或终止录 制命令等。
以上所有实施例中， PVR-SCF与 BC-SCF, PVR-SCF与 COD-SCF可能 ) 合设为同一实体或为独立的实体， 当合设为统一的 SCF时， 以上实施例流程 中所有 PVR-SCF与 BC-SCF, 或 PVR-SCF与 COD-SCF之间的交互为实体内 部交互。
应用本发明实施例， 通过网络中各个实体之间的交互实现了客户端的录 制， 提高了使用基于 IMS的 IPTV业务时的用户体验。
) 与本发明实现客户端录制的方法的实施例相对应， 本发明还提供了实现 客户端录制的系统和录制控制实体的实施例。
本发明实现客户端录制的系统的实施例框图如图 13所示， 该系统包括： 录制发起实体 1310、 录制控制实体 1320、客户端录制实体 1330和媒体提供实 体 1340。
) 录制发起实体 1310用于向所述录制控制实体 1320发送录制任务，所述录 制任务中包括录制内容的标识， 和 /或客户端录制实体 1330或用户的标识； 录制控制实体 1320用于在接收到所述录制任务后， 根据所述录制任务控 制所述客户端录制实体 1330录制所述媒体提供实体 1340提供的所述媒体内 进一步， 录制控制实体 1320还可以用于在接收到录制任务后， 当判断所 述录制发起实体 1310有权限控制所述客户端录制实体 1330录制所述媒体内 容， 和 /或判断所述客户端录制实体 1330有权限录制所述媒体内容时， 再执行 所述根据所述录制任务控制所述客户端录制实体 1330录制所述媒体内容的操 ) 作。
本发明实现客户端录制的录制控制实体的第一实施例框图如图 14所示， 该录制控制实体包括： 接收单元 1410和控制单元 1420。
其中， 接收单元 1410用于接收录制任务， 所述录制任务中包括录制内容 的标识， 和 /或客户端录制实体或用户的标识；
) 控制单元 1420 用于根据所述录制任务控制客户端录制实体录制媒体内 谷。
本发明实现客户端录制的录制控制实体的第二实施例框图如图 15所示， 该录制控制实体包括： 接收单元 1510、 判断单元 1520、 执行单元 1530和控制 单元 1540。
) 其中， 接收单元 1510用于接收录制任务， 所述录制任务中包括录制内容 的标识， 和 /或客户端录制实体或用户的标识；
判断单元 1520用于判断录制发起实体是否有权限控制所述客户端录制实 体录制媒体内容；
判断单元 1520还可以用于判断所述客户端录制实体是否有权限录制所述 ) 媒体内容；
执行单元 1530用于在当录制发起实体有权限控制所述客户端录制实体录 制所述媒体内容， 或所述客户端录制实体有权限录制所述媒体内容时， 触发所 述控制单元 1540执行所述控制功能；
控制单元 1540用于根据所述录制任务控制所述客户端录制实体录制所述 ) 媒体内容。
本发明实现客户端录制的录制控制实体的第三实施例框图如图 16所示， 该录制控制实体包括： 接收单元 1610、 控制单元 1620。
其中， 接收单元 1610用于接收录制任务， 所述录制任务中包括录制内容 的标识， 和 /或客户端录制实体或用户的标识； 控制单元 1620包括：
建立单元 1621 , 用于根据录制任务中录制内容的标识和 /或客户端录制实 体或用户的标识， 触发建立内容交付通道； 录制单元 1622, 用于通过所述内 容交付通道控制所述客户端录制实体接收并录制所述媒体内容； 结束单元 ) 1623 , 用于当录制结束时， 删除内容交付通道。
本发明实现客户端录制的录制控制实体的第四实施例框图如图 17所示， 该录制控制实体包括： 接收单元 1710、 控制单元 1720。
其中， 接收单元 1710用于接收录制任务， 所述录制任务中包括录制内容 的标识和 /或客户端录制实体或用户的标识；
) 控制单元 1720包括：
建立单元 1721 , 用于根据录制任务中录制内容的标识和 /或客户端录制实 体或用户的标识， 触发建立交付通道； 录制单元 1722, 用于通过内容交付通 道控制所述客户端录制实体接收并录制所述媒体内容； 异常单元 1723 , 用于 当录制异常时， 删除所述内容交付通道； 所述建立单元 1721还用于， 在所述 ) 客户端录制实体与媒体緩存实体之间建立传输通道； 緩存单元 1724, 用于通 过所述传输通道控制所述媒体緩存实体緩存所述媒体内容或接收所述客户端 录制实体发送的录制命令。
通过本发明实施例的描述可知，本发明实施例中接收包括录制内容的标识 和 /或客户端录制实体的标识的录制任务， 根据所述录制任务控制所述客户端 ) 录制实体录制所述媒体内容。应用本发明实施例， 通过网络中各个实体之间的 交互实现了客户端的录制， 提高了使用基于 IMS的 IPTV业务时的用户体验。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤 是可以通过程序来指令相关的硬件来完成，所述的程序可以存储于一计算机可 读取存储介质中， 该程序在执行时， 包括如下步骤： 收集用户的业务信息， 根 ) 据各个业务信息对应的 QOE参数获取物理层目标参数； 接收所述用户的线路 运行信息， 所述线路运行信息包括测试参数和预先存储的线路目标参数； 将所 述物理层目标参数和所述线路运行信息作为最小功率算法的输入参数，通过最 小功率算法获取优化功率谱。 所述的存储介质， 如： ROM/RAM、 磁碟、 光盘 等。 虽然通过实施例描绘了本发明， 本领域普通技术人员知道， 本发明有许多 变形和变化而不脱离本发明的精神，希望所附的权利要求包括这些变形和变化 而不脱离本发明的精神。

Claims

权 利 要 求
1、一种实现客户端录制的方法， 应用于基于 IP多媒体子系统的互联网协 议电视 IPTV系统中， 其特征在于， 包括：
接收录制任务， 所述录制任务中包括录制内容的标识和 /或客户端录制方
) 标识；
根据所述录制内容的标识和 /或所述客户端录制方标识控制所述客户端录 制方录制媒体内容。
2、 根据权利要求 1所述的方法， 其特征在于， 所述接收录制任务包括： 接收用户设备发送的录制任务， 或接收网络实体发送的录制任务。
)
3、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括：
判断所述客户端录制方是否有权限录制所述媒体内容。
4、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 判断录制发起方是否有权限控制所述客户端录制方录制所述媒体内容。
5、 根据权利要求 1所述的方法， 其特征在于， 所述根据录制内容的标识 ) 和 /或所述客户端录制方标识控制客户端录制方录制所述媒体内容包括：
根据所述录制内容的标识和 /或所述客户端录制方标识， 触发建立内容交 付通道；
所述客户端录制方通过所述内容交付通道接收并录制所述媒体内容。
6、 根据权利要求 5所述的方法， 其特征在于， 所述触发建立内容交付通 ) 道包括：
向客户端录制方发送携带 CPVR业务指示信息的请求，所述指示信息用于 指示客户端录制方存储接收到的媒体内容。
7、 根据权利要求 5所述的方法， 其特征在于， 所述录制任务中包括录制 时间信息， 所述方法还包括：
) 向客户端录制方发送包含所述录制任务的消息；
客户端录制实体根据所述录制任务， 发起协商建立内容交付通道。
8、 根据权利要求 1至 7任意一项所述的方法， 其特征在于， 所述录制任 务中还包括至少一种下述信息： 录制时间信息、发送所述录制任务的录制发起 方标识、 录制参数信息、 录制能力信息。
9、 根据权利要求 1至 7任意一项所述的方法， 其特征在于， 所述方法还 包括：
根据所述客户端录制方标识向所述客户端录制方发起远程管理请求， 所 述远程管理请求中包含用于指示所述客户端录制方预留存储空间的指示。
)
10、 一种基于 IP多媒体子系统的互联网协议电视 IPTV系统中实现客户 端录制的系统， 其特征在于， 包括： 录制发起实体和录制控制实体，
所述录制发起实体， 用于向所述录制控制实体发送录制任务， 所述录制任 务中包括录制内容的标识和 /或客户端录制方标识；
所述录制控制实体， 用于接收到所述录制任务后，根据所述录制内容的标 ) 识和 /或所述客户端录制方标识控制所述客户端录制方录制媒体内容。
11、 一种录制控制实体， 其特征在于， 包括：
接收单元， 用于接收录制任务， 所述录制任务中包括录制内容的标识和 / 或客户端录制方标识；
控制单元， 用于根据所述录制内容的标识和 /或所述客户端录制方标识控 ) 制所述客户端录制实体录制媒体内容。
12、 根据权利要求 11所述的录制控制实体， 其特征在于， 还包括： 判断单元，用于判断录制发起实体是否有权限控制所述客户端录制实体录 制所述媒体内容。
13、 根据权利要求 12所述的录制控制实体， 其特征在于， 所述判断单元 ) 还用于判断所述客户端录制实体是否有权限录制所述媒体内容。
14、 根据权利要求 11所述的录制控制实体， 其特征在于， 所述控制单元 包括：
建立单元， 用于根据所述录制内容的标识和 /或所述客户端录制方标识， 触发建立内容交付通道；
) 录制单元，用于使所述客户端录制实体通过所述内容交付通道接收并录制 所述媒体内容。
15、 根据权利要求 14所述的录制控制实体， 其特征在于， 所述控制单元 还包括：
结束单元， 用于当所述媒体内容录制结束时， 释放所述内容交付通道。
16、 根据权利要求 14所述的录制控制实体， 其特征在于， 所述控制单元 还包括：
暂停单元，用于当需要暂停录制所述媒体内容时，释放所述内容交付通道； 所述建立单元还用于， 触发建立传输通道；
緩存单元， 用于通过所述传输通道控制媒体緩存实体緩存所述媒体内容， 或接收所述客户端录制实体发送的录制命令。
PCT/CN2009/073821 2008-09-09 2009-09-09 实现客户端录制的方法、系统及录制控制实体 WO2010028591A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810212006.X 2008-09-09
CN200810212006XA CN101674470B (zh) 2008-09-09 2008-09-09 实现客户端录制的方法、系统及录制控制实体

Publications (1)

Publication Number Publication Date
WO2010028591A1 true WO2010028591A1 (zh) 2010-03-18

Family

ID=42004809

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073821 WO2010028591A1 (zh) 2008-09-09 2009-09-09 实现客户端录制的方法、系统及录制控制实体

Country Status (2)

Country Link
CN (1) CN101674470B (zh)
WO (1) WO2010028591A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885187A (zh) * 2022-06-23 2022-08-09 深圳市必提教育科技有限公司 一种在线教育直播回放方法和系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102256166A (zh) * 2011-07-19 2011-11-23 中兴通讯股份有限公司 一种iptv个人录制业务个性化权限控制的实现方法和系统
AU2012384782B2 (en) 2012-07-04 2016-01-28 Huawei Technologies Co., Ltd. Method, device and system for recording multimedia data
CN104918101B (zh) * 2015-06-01 2019-09-13 天脉聚源(北京)传媒科技有限公司 一种自动录制节目的方法、播放终端及系统
CN107094268B (zh) * 2017-03-27 2021-02-26 海信视像科技股份有限公司 节目预约录制控制方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022524A (zh) * 2006-02-14 2007-08-22 华为技术有限公司 一种通过h.248协议实现多媒体录制的方法及系统
WO2007096001A1 (en) * 2006-02-24 2007-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Ims-enabled control channel for iptv
CN101179702A (zh) * 2007-12-03 2008-05-14 中兴通讯股份有限公司 一种iptv直播电视的实时录制方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006041888A (ja) * 2004-07-27 2006-02-09 Sony Corp 情報処理装置および方法、記録媒体、並びにプログラム
CN100512424C (zh) * 2005-09-09 2009-07-08 华为技术有限公司 视频录像的实现方法及机顶盒

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022524A (zh) * 2006-02-14 2007-08-22 华为技术有限公司 一种通过h.248协议实现多媒体录制的方法及系统
WO2007096001A1 (en) * 2006-02-24 2007-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Ims-enabled control channel for iptv
CN101179702A (zh) * 2007-12-03 2008-05-14 中兴通讯股份有限公司 一种iptv直播电视的实时录制方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885187A (zh) * 2022-06-23 2022-08-09 深圳市必提教育科技有限公司 一种在线教育直播回放方法和系统
CN114885187B (zh) * 2022-06-23 2023-08-08 深圳市必提教育科技有限公司 一种在线教育直播回放方法和系统

Also Published As

Publication number Publication date
CN101674470A (zh) 2010-03-17
CN101674470B (zh) 2011-11-16

Similar Documents

Publication Publication Date Title
US8332527B2 (en) Streaming media network system, streaming media service realization method and streaming media service enabler
US8307049B2 (en) Method and device for obtaining media description information of IPTV services
EP2175591B1 (en) A method, a system, a device and a computer program readable medium for realizing the services of network televison
JP4932906B2 (ja) Ｉｍｓアーキテクチャ・ネットワークにおけるｉｐサービスに渡ってテレビジョンにアクセスするためのシステム
WO2008151550A1 (fr) Procédé d'enregistrement de réseau de programmes, serveur de traitement multimédia et système d'enregistrement de réseau
WO2009046654A1 (fr) Procédé de commande, système et entité d'enregistrement de réseau
WO2008101444A1 (fr) Système multimédia en flux, dispositif de transmission de signalisation et procédé d'envoi de multimédia en flux
US20100122281A1 (en) Method and system for controlling authorization of service resources
WO2010022570A1 (zh) 基于网际协议电视的信息推送方法、装置及系统
WO2009030133A1 (fr) Procédé, système et entité pour réaliser une vidéo image dans image
WO2008134955A1 (fr) Procédé, système et appareil pour appliquer des informations de capacité de terminal dans un service iptv
WO2009026813A1 (fr) Procédé, système et entité pour réaliser un enregistrement de réseau
KR20090123781A (ko) 멀티캐스트 세션을 통해 수신한 어플리케이션에 기초한 ｉｐｔｖ 서비스 이용 방법 및 장치
EP2448260B1 (en) Content upload method and content delivery function entity
WO2010028591A1 (zh) 实现客户端录制的方法、系统及录制控制实体
US20110167441A1 (en) An interactive iptv system and a content pushing method thereof
WO2010028601A1 (zh) 以文件方式传输媒体内容的方法、系统及设备
CN101741816A (zh) 基于网际协议电视的信息推送方法、装置及系统
WO2010025675A1 (zh) 一种业务内容的播放方法、系统和装置
JP2010010892A (ja) 通信制御装置と通信システムおよび通信制御方法
CN101668164B (zh) 基于网际协议电视的内容发布方法、装置及系统
KR20110000593A (ko) 멀티캐스트 스트림을 이용하여 주문형 스트리밍 콘텐츠의 제공을 촉진하기 위한 방법 및 장치
WO2010022603A1 (zh) 附着到对等网络及获取iptv内容的方法、系统和装置
WO2009012714A1 (fr) Procédé et dispositif pour commander les médias en flux
WO2009026810A1 (fr) Procédé, entité et système pour réaliser une commande de distribution de multimédia

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

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

Country of ref document: EP

Kind code of ref document: A1