WO2009026813A1

WO2009026813A1 - A method, a system and an entity for realizing network recording

Info

Publication number: WO2009026813A1
Application number: PCT/CN2008/071803
Authority: WO
Inventors: Jianfeng Zhong; Xiaosong Lei; Geng Wang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-27
Filing date: 2008-07-30
Publication date: 2009-03-05
Also published as: CN101378492A; CN101378492B

Abstract

A method for realizing network recording is disclosed, which includes the following steps: a network recording controlling entity receives a recording task, and controls a network recording media entity and a content resource to establish a transmission channel according to the recording task, and controls the network recording media entity to receive and record the media stream from the content resource through the transmission channel. In addition, a system for realizing network recording, a network recording controlling entity and a network recording media entity are also disclosed. Said method, system and entities can be used in the field of IP television technology and can realize network recording in the IMS-based IPTV architecture.

Description

Method, system and entity for realizing network recording

The present invention relates to an IP television (IPTV) technology, and more particularly to a method, system, and network recording control entity and network recording media entity for implementing network recording.

Background technique

IPTV is a brand-new technology that utilizes a broadband cable TV network and integrates various technologies such as Internet, multimedia, and communication to provide home users with a variety of interactive services including digital TV. IPTV uses Transmission Control Protocol/Internet Protocol (TCP/IP) as the bearer protocol for unicast, broadcast or multicast video services, effectively combining the three fields of TV network, telephone network and Internet. Representative business.

The IP Multimedia Subsystem (IMS) is an IP-based standard system independent of access technologies, IMS and existing voice and data networks (whether fixed network users such as PSTN, ISDN, Internet, etc.) Or mobile network users such as GSM and CDMA can communicate with each other. The IMS architecture enables peer-to-peer IP communications through all types of clients and the quality of service required. In addition to session management, the IMS architecture also involves the functions necessary to complete service provisioning (eg registration, security, billing, bearer control, roaming). That is, the IMS system forms the core of the IP core network.

In order to realize the unified control of IMS access to fixed network users, a network attachment subsystem (NASS, Network At tachment Sub-System) and a resource and admission control subsystem (RACS, Resource and Admi ss ion Control) are introduced in the network architecture. Subsys tem). NASS is used to complete the management of user attachment to the access network, including user authentication and network address allocation, location management. RACS is mainly used to complete policy control, resource reservation and admission control. The service/application level can use the RACS to request the access network to reserve related resources.

The IMS-based IPTV architecture that is currently launched will directly reuse the related functional entities of IMS, and support the IPTV service by appropriately adding new functional entities and expanding related functions of existing functional entities. FIG. 1 shows a networking diagram of an IMS-based IPTV architecture in the prior art. As shown in FIG. 1, each IPTV service is composed of a pair of IPTV Service Control Functions (SCF) and IPTV (Media Functions). The SCF is a SIP application server, and the tasks mainly include: (1) authorizing the session during initialization; (2) implementing a modification process, checking user data to determine whether to allow the user to access the service; (3) account control; (4) Select the appropriate MF. The MF is responsible for the control and delivery of media streams and can be divided into Media Control Function (MCF) and Media Delivery Function (MDF). Among them, MCF's tasks mainly include: (1) handling media stream control; ( ² ) monitoring MDF status (optional); ( ³ ) management and user equipment (UE) interaction; ( ⁴ ) controlling multiple in MCF In the MDF, select an MDF; (5) accurately perceive the distribution of the status and content of different MDFs; (5) generate billing information. The tasks of the MDF mainly include: (1) processing the delivery of the media stream; (2) reporting the status to the MCF (optional).

As can be seen from Figure 1, SCF and MF include: CoD (Content on Demand), Broadcast Service (BC) and Personal Video Recorder (PVR).

Among them, CoD is an IPTV service function, which is a service control part (CoD-SCF) in the SCF, and is divided into a media control part (CoD-MCF) and a media delivery function (CoD-MDF) in the MF. BC realized broadcasting IPTV service, the service control section (BC-SCF) in the SCF, the media is divided into the control portion (BC-MCF) filed in the MF and media functions (BC-MDF) ₀ PVR implements the PVR IPTV service, In the SCF, it is a service control part (PVR-SCF), which is divided into a media control part (PVR-MCF) and a media delivery function (PVR-MDF) in the MF. The PVR service provides recording functions for video media streams. According to the provided methods, it can be divided into network-based PVR and personal-based PVR. The network-based PVR refers to: Allocating a certain storage space for users in the network, and recording users by the network. The media features to be recorded, and play them according to the user's wishes.

The CoD-SCF, the BC-SCF, and the PVR-SCF exchange messages with the UE through the IMS, and the media control messages between the CoD-MCF, the BC-MCF, and the PVR-MCF and the UE interact through the Xc' reference point. The media data between the CoD-MDF, BC-MDF, and PVR-MDF and the UE interacts through the Xc" reference point.

Secondly, in the network architecture, the service discovery function (SDF) and the service selection function (SSF) are also added. It is used to provide the necessary information for the UE when selecting an IPTV service. Among them, the SSF provides a list of available services that the UE can browse and select.

J3⁄4, including the multicast control function in the Transmit t Proces s ing Funct ions (TPF); the user data is stored in the User Attribute Server Function (UPSF).

In the above IMS-based IPTV architecture, although the main tasks of each functional entity are given, there is no exact solution in the existing network architecture for how to perform information interaction between functional entities to complete network recording. Network recording is not yet possible in IPTV technology.

Summary of the invention

In view of this, in one embodiment of the present invention, a method for implementing network recording is provided, and another system and entity for implementing network recording are provided to implement network recording in the IPTV technology.

The method for implementing network recording provided by the embodiment of the present invention includes:

The network recording control entity receives the recording task, controls the network recording media entity and the content source to establish a transmission channel according to the recording task, and controls the network recording media entity to receive the media stream from the content source transmitted through the transmission channel and Recording.

The system for implementing network recording provided by the embodiment of the present invention includes:

a network recording control entity, configured to receive a recording task, and send, to the network recording media entity, control information that carries the content source information according to the recording task;

a network recording media entity, configured to establish a transmission channel with the content source according to the received control information carrying the content source information, and receive and record the media stream from the content source transmitted through the transmission channel;

A content source, used to stream media to a network recording media entity.

The network recording control entity provided by the embodiment of the present invention includes:

a receiving module, configured to receive a recording task;

And a control module, configured to send, to the network recording media entity, control information that carries the content source information according to the recording task.

The network recording media entity provided by the embodiment of the present invention includes: a receiving module, configured to receive control information that carries content source information;

a channel establishing module, configured to establish a transmission channel with the content source according to the content source information in the control information;

A receiving recording module is configured to receive and record a media stream from a content source transmitted through the established transmission channel.

As can be seen from the foregoing solution, in the embodiment of the present invention, the network recording control entity controls a network to establish a transmission channel between the network recording media entity and the content source according to the received recording task, and controls the network recording media entity to media stream from the content source. Receive and record, enabling network recording in an IMS-based IPTV architecture.

DRAWINGS

FIG. 1 is a schematic diagram of networking of an IMS-based IPTV architecture in the prior art;

2 is an exemplary flowchart of a method for implementing network recording in an embodiment of the present invention;

3 is an exemplary structural diagram of a system for implementing network recording in an embodiment of the present invention;

4 is a schematic structural diagram of a network recording control entity in the system shown in FIG. 3;

5 is a schematic structural diagram of a network recording media entity in the system shown in FIG. 3;

6 is a schematic flowchart of implementing network recording in Example 1 of the present invention;

7 is a schematic flowchart of implementing network recording in Example 2 of the present invention;

FIG. 8 is a schematic flowchart of implementing network recording in Example 3 of the present invention.

detailed description

In the embodiment of the present invention, the network recording control entity receives the recording task, controls the network recording media entity and the content source to establish a transmission channel according to the received recording task, and controls the network recording media entity to transmit through the built transmission channel. The media stream from the content source is received and recorded.

The method, system and entity for realizing network recording in the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 2 is an exemplary flowchart of a method for implementing network recording in an embodiment of the present invention. As shown in Figure 2, the process includes the following steps: Step 201: The recording task requesting entity submits a recording task to the network recording control entity. In this step, the recording task may be submitted by the UE, or may be configured by the network. Correspondingly, the recording task requesting entity may be a UE, or may be a network entity that stores data for the storage network.

The recording task includes information related to recording, such as channel information, recording time period, or recorded program.

In this embodiment, the network recording control entity may be a PVR-SCF, or a combined entity of the PVR-SCF and the BC-SCF, but is not limited thereto, and may be other entities.

When the recording task requesting entity is the UE and the network recording control entity is the PVR-SCF, the recording task may be transmitted through the Ut interface between the UE and the PVR-SCF based on the Hypertext Transfer Protocol (HTTP); or, the recording task may be based on the session. The Initialization Protocol (SIP) is transmitted through the session control interface between the UE and the PVR-SCF.

When the transmission is based on the SIP protocol, the recording task can be transmitted through an invitation (INVITE) message or a commit (REFER) message in the SIP protocol, and when transmitting through the session control interface, the specific transmission mode can be at least two Kind:

Transmission mode 1: The UE directly sends the recording task to the PVR-SCF.

Transmission mode 2: The UE forwards the recording task to the PVR-SCF through the BC-SCF.

In the above two transmission modes, the recording task can be forwarded between the entities involved in the above by the network entities in the IMS, such as the Proxy Call Session Control Function (P-CSCF) and the Serving Call Session Control Function (S-CSCF). .

Step 202: The network recording control entity controls, according to the received recording task, a transmission channel between the network recording media entity and the content source.

In this step, if the recording task is a scheduled recording task submitted in advance, and the recording task includes information such as channel information and recording time period, the network recording control entity controls the network recording media entity and needs to record before the start of the corresponding time period. A transmission channel is established between the content sources; if the recording task is a currently submitted real-time recording task, and the recording task includes channel information, the network recording control entity directly controls the network recording media entity and needs to record when receiving the recording task. Between content sources Vertical transmission channel.

In this embodiment, the network recording media entity may be a PVR-MF or a combined entity of the PVR-MF and the BC-MF, but is not limited thereto, and may be other entities. The content source is usually stored in the BC-MF, and the content source information in the BC-MF is usually pre-configured to the BC-SCF.

When the network recording control entity is PVR-SCF and the network recording media entity is PVR-MF, the specific process of the network recording control entity controlling the establishment of the transmission channel between the network recording media entity and the content source may include: PVR-SCF and BC-SCF After the information is exchanged, the content source information is obtained, and then the PVR-SCF interacts with the PVR-MF to notify the PVR-MF of the obtained content source information, and the PVR-MF is based on the obtained content source information and the content source. Establish a transmission channel.

When the PVR-SCF and the BC-SCF exchange information, if the media stream from the content source is transmitted in a multicast manner, the obtained content source information may be multicast source information, such as a multicast source address. If the media stream from the content source is transmitted in a unicast manner, the obtained content source information may be unicast channel information.

Correspondingly, if the PVR-SCF notifies the PVR-MF of the acquired multicast source information, the PVR-MF sends a request to join the multicast to the multicast control function entity. And the multicast control function entity distributes the media stream from the content source to the PVR-MF according to the request for joining the multicast, thereby implementing multicast channel establishment between the PVR-MF and the content source; if the PVR-SCF is to be The obtained unicast channel information is notified to the PVR-MF, and the PVR-MF establishes a unicast channel between the unicast channel information and the content source.

The multicast control function entity may be a basic forwarding function/basic control function (EFF/ECF) or other functional entities.

Step 203: The network recording media entity receives and records the media stream from the content source.

In this step, taking the case that the network recording media entity is a PVR-MF, if the media stream from the content source is transmitted in a multicast manner, the PVR-MF receives the media stream distributed by the multicast control function entity. If the media stream from the content source is transmitted in a unicast manner, the PVR-MF receives the media stream through a unicast channel established with the content source. The PVR-MF records the received media stream in real time. Step 204: After the recording is completed or after receiving the end recording request of the UE, the transmission channel established between the network recording media entity and the content source is removed.

In this step, the case where the network recording control entity is the PVR-SCF and the network recording media entity is the PVR-MF is taken as an example. The process of removing the transmission channel established between the PVR-MF and the content source may be performed by the PVR-MF or The PVR-SCF initiates a session end request, and the PVR-SCF sends a session end request to the BC-SCF, thereby ending the session between the PVR-SCF and the BC-SCF, and the PVR-MF actively disassembles or the PVR-SCF notifies the PVR-MF. The transmission channel established between the removal and the content source.

If the media stream from the content source is transmitted in a multicast manner, when the PVR-MF removes the transmission channel established between the content source and the content source, the PVR-MF may send the leaving group to the multicast control function entity. For the broadcast request, the multicast control function entity stops distributing the media stream from the content source to the PVR-MF according to the request to leave the multicast. If the media stream from the content source is transmitted in unicast mode, the PVR-MF directly tears down the unicast transmission channel established between the content source and the content source.

Step 205: The network recording media entity uploads the recording result information to the network recording control entity. The recording result information may include: any combination of recorded storage location, duration, file format, and the like.

Step 206: The network recording control entity notifies the recording task request entity of the received recording result information.

In a specific implementation, the recording task requesting entity may also subscribe the recording result information to the network recording control entity, and then the steps 205 and 206 are retained in the above process. If the recording task requesting entity does not subscribe to the recording result information to the network recording control entity, step 205 and step 206 may be retained or omitted, or step 205 may be retained and step 206 may be omitted.

In addition, the recording task requesting entity may also subscribe the recording event information to the network recording control entity, and the network recording control entity may notify the recording task requesting entity of the received recording event information from the network recording media entity. The recording event information may include current recording status, such as recording duration, recording abnormality, and the like.

The network recording media entity sends the recording result and/or the recorded event information to the network recording control. The entity may be reported by default according to the network configuration, or the network recording control entity may subscribe to the recording result and/or record event information of the network recording media entity, and the network recording media entity reports the recording result to the network recording control entity according to the subscription requirement and/or Or record event information.

Further, when the UE initiates a play request for the recorded content, the network recording media entity transmits the recorded media stream to the UE.

In this embodiment, the message interaction between the recording task requesting entity and the network recording control entity, between the network recording control entity and the network recording media entity, the network recording control entity, and the content source may all be through the network entity in the IMS. Routing, no longer here - repeat.

The method for implementing network recording in the embodiment of the present invention is described in detail above. The system for implementing network recording in the embodiment of the present invention is described in detail below.

FIG. 3 is an exemplary structural diagram of a system for implementing network recording in an embodiment of the present invention. As shown in FIG. 3, the system includes: a network recording control entity 31, a network recording media entity 32, and a content source 33.

The network recording control entity 31 is configured to receive a recording task, and send control information carrying the content source information to the network recording media entity 32 according to the recording task.

The network recording media entity 32 is configured to establish a transmission channel with the content source 33 according to the received control information carrying the content source information, and receive and record the media stream from the content source 33 transmitted through the transmission channel. The transmission channel may be a multicast channel or a unicast channel described in the process shown in FIG. 2, and the specific establishment process may also be consistent with the description in the process shown in FIG. 2.

The content source 33 is used to transmit the media stream to the network recording media entity through the established transmission channel.

32.

In a specific implementation, the specific operation process of each functional entity in the system shown in FIG. 3 may be consistent with the operation process described in the process shown in FIG. 2, and is not described here.

The recording task may be submitted by the UE, or may be configured by the network. If the UE submits, the system may further include: a UE, configured to submit a recording task to the network recording control entity. If the network recording control entity is a PVR-SCF, the manner in which the UE submits the recording task to the PVR-SCF may be multiple, which may be consistent with the description in step 201 in the process shown in FIG. 2 . In addition, if the network recording control entity 31 is a PVR-SCF and the network recording media entity 32 is a PVR-MF, the system may further include: a BC-SCF for performing information interaction with the PVR-SCF and providing the PVR-SCF with Content source information. The network recording control entity 31 may be a combined entity of the PVR-SCF and the BC-SCF, and the network recording media entity 32 may be a combined entity of the PVR-MF and the BC-MF.

If the media stream from the content source is transmitted in a multicast manner, the system further includes: a multicast control function entity, configured to distribute the media stream from the content source under the PVR-MF joining multicast request Give PVR-MF.

In a specific implementation, the network recording control entity and the network recording media entity may have multiple specific implementation forms. The following describes one of the specific implementations of the network recording control entity and the network recording media entity.

FIG. 4 shows an internal structure diagram of a network recording control entity. As shown in FIG. 4, the entity includes: a receiving module 41 and a control module 42.

The receiving module 41 is configured to receive a recording task. This recording task can come from the UE or from the network configuration. Control information.

The above network recording control entity may be a PVR-SCF or a combined entity of the PVR-SCF and the BC-SCF.

In addition, the entity may further include: a content source information obtaining module, configured to acquire content source information from the BC-SCF.

In addition, the entity may further include: an information acquisition module, configured to acquire recording event information and/or recording result information from the PVR-MF.

Further, the entity may further include: an information module, configured to upload the acquired recording event information and/or recording result information to the requesting entity of the recording task.

In addition, the entity may further include: a subscription acceptance module for accepting requests from the recording task The subscribing to the recording event information and/or the subscription request of the recording result information, and notifying the information reporting module to perform the above reporting operation according to the accepted subscription request.

In addition, the entity may further include: a recording end notification module, configured to send a session end request to the PVR-MF, and notify the PVR-MF to tear down the transmission channel established between the content source and the content source.

Figure 5 shows an internal structure diagram of a network recording media entity. As shown in FIG. 5, the entity includes: a receiving module 51, a channel establishing module 52, and a receiving recording module 53.

The receiving module 51 is configured to receive control information that carries content source information. Among them, the content source information can come from BC_SCF.

The channel establishing module 52 is configured to establish a transmission channel with the content source according to the content source information in the control information. The transmission channel may be a multicast channel or a unicast channel described in the process shown in FIG. 2, and the specific establishment process may also be consistent with the description in the process shown in FIG. 2.

The receiving recording module 5 3 is for receiving and recording a media stream from a content source transmitted through the established transmission channel.

The above network recording media entity may be a PVR-MF or a combined entity of PVR-MF and BC-MF.

In addition, the entity may further include: an information module, configured to obtain recording event information and/or recording result information of the recording, and report the obtained recording event information and/or recording result information to the network recording control entity.

Further, the entity may further include: a media playing module, configured to transmit the recorded media stream corresponding to the play request to the UE according to the play request of the UE.

Further, the entity may further include: a subscription receiving module, configured to receive a subscription request for subscription recording event information and/or recording result information from the network recording control entity, and notify the information reporting module to execute according to the accepted subscription request The reporting operation.

The following takes the case where the recording task requesting entity is the UE, the network recording control entity is the PVR-SCF, and the network recording media entity is the PVR-MF. The method, system, and entity for implementing the network recording are described in detail through several specific examples. . Example 1:

The example system includes: UE, SDF, SSF, PVR-SCF, PVR_MF, BC-SCF and BC_MF. In this example, it is assumed that the UE schedules a recording task in advance. Fig. 6 is a flow chart showing the implementation of network recording in the first example of the present invention. As shown in Figure 6, the process includes the following steps:

Step 601: The UE submits a predetermined recording task to the PVR-SCF.

In this embodiment, the UE may perform IPTV service discovery and service selection in advance through the information provided by the SDF and the SSF, and register the predetermined recording task by HTTP for the selected IPTV service, and submit it to the PVR-SCF. Alternatively, it can be submitted to the PVR-SCF by carrying the recording task in a SIP message.

The information included in the recording task may include: channel information, recording time period, user terminal information (optional), network recording preference information (optional), PVR-SCF policy (optional), to be recorded Program related information (optional), etc.

In addition, after submitting the recording task, the UE can also subscribe to the recording event and/or the recorded recording result during the recording, so that if the UE is online, the PVR-SCF can notify the recording status and/or the recording result, for example: the recording is successful. Or record anomalies and other information.

Step 602: The PVR-SCF performs information interaction with the BC-SCF to obtain information of the content source according to the received recording task, when the recording time period is reached.

There are many specific implementation steps in this step. Only one of them will be described in detail below:

The PVR-SCF may send an INVITE message to the BC-SCF through the IMS system to request content source information from the BC-SCF. The PVR-SCF may carry the negotiation proposal (Offer) or the 0ffer in the INVITE message. For example, if the UE reports the channel information and the program related information to be recorded in the recording task submitted to the PVR-SCF, the INVITE message may carry the relevant Offer information.

The BC-SCF receives the INVITE message from the PVR-SCF, and returns a response message (200 0K) to the PVR-SCF according to the received INVITE message. If the INVITE message received by the BC-SCF carries the Offer, the 200 0K message is sent. Carry an negotiation response (Answer), otherwise the 200 0K message carries the side Offer. The 200 OK message carries content source information.

The PVR-SCF receives the 200 0K message from the BC-SCF, obtains the content source information therefrom, and sends an acknowledgement (ACK) message to the sending BC-SCF according to the received 200 0K message, if the PVR-SCF receives the 200 0K message. If the Offer carries the Offer, the ACK message carries the Answer. If the 200 VK message received by the PVR-SCF carries the Answer, the Answer message does not carry the Answer.

Thereby completing the corresponding Offer/Answer process.

The content source information may be multicast source information or unicast channel information.

Step 603: The PVR-SCF performs information interaction with the PVR-MF, and notifies the PVR-MF of the obtained content source information.

The specific implementation process of this step may be various, and one of them may be similar to the process in step 602, that is, the PVR-SCF interacts with the PVR-MF for the Offer/Answer process of the S IP protocol, and the content source information is informed to the PVR_MF. Specifically, the PVR-SCF sends an INVITE (Offer) message carrying the content source information to the PVR-MF, and the PVR-MF returns a 200 0K (answer) message to the PVR-SCF according to the received INVITE message, and the PVR-SCF receives the message. After the 200 0K message, an ACK message is returned to the PVR-MF, thereby completing the Offer/Answer process interaction.

Step 604: The PVR-MF establishes a transmission channel between itself and the content source according to the received content source information.

In this step, if the content source information is the multicast source information, the PVR-MF may send a request for joining the multicast to the multicast control function entity according to the multicast source information, and the multicast control function entity according to the multicast join function. Requesting, distributing the media stream from the content source to the PVR-MF, thereby implementing multicast channel establishment between the PVR-MF and the content source; if the content source information is unicast channel information, the PVR-MF may be based on the unicast A unicast channel is established between the channel information and the content source.

Step 605: The PVR-SCF subscribes to the recording result information to the PVR-MF.

In a specific implementation, the PVR-SCF may send a SUBSCRIBE message to the PVR-MF, and the subscription may be performed in the session initiated by the PVR-SCF to the PVR-MF through the INVITE in step 603. This subscription is mainly used for PVR-MF to immediately notify the recording status information during the recording process, including abnormal information. This step This is an optional step.

Step 606: The PVR-MF receives and records the media stream from the content source.

Step 607: When the recording ends, the PVR-MF sends a session end request to the PVR-SCF.

This step also includes removing the transmission channel established between the PVR-MF and the content source. If the content source is transmitted in a multicast manner, the PVR-MF may send a request to leave the multicast to the multicast control function entity, and the multicast control function entity stops the request from the content source according to the request to leave the multicast. The media stream is distributed to the PVR-MF; if the content source is transmitted in unicast mode, the PVR-MF directly removes the unicast transmission channel from the content source.

In this step, the session end request may be a BYE message in the SIP message, or other message. Step 608: The PVR-SCF returns a response message to the PVR-MF.

This step is an optional step, and the response message can be a 200 OK message.

Step 609: The PVR-SCF sends a session end request to the BC-SCF.

In this step, the session end request may be a BYE message in the SIP message.

Step 61 0: The BC-SCF ends the session with the PVR-SCF according to the received session end request, and further returns a response message to the PVR-SCF.

The response message can be a 200 0K message.

Step 61: If the PVR-SCF subscribes to the recording result information or the network configuration is PVR-MF default in step 605, the PVR-MF will record the result information to the PVR-SCF.

In this step, the recording result information depends on the information that the user needs to obtain, for example, the information includes: duration, media format, remaining space size, storage location, and the like.

Step 612, the PVR-SCF returns a response message to the PVR-MF.

Step 61 3: If the UE subscribes to the recording result information in step 601, the PVR-SCF will report the recording result information. The reporting method can be provided in combination with the subscription method used in step 601.

The reported content may include a recording duration, a media format, an abnormal event, and the like. In the user experience, a dialog box can be displayed on the screen to inform the user of the success of the recording or the recording failure and its cause. In the above process, if the PVR-SCF subscribes to the PVR-MF for recording event information or the network configuration is PVR-MF default reporting, if a recording abnormality occurs during recording, such as storage space overflow, the PVR-MF will go to the PVR- If the SCF reports an abnormal event, step 607-step 608 may be omitted, and the PVR-SCF directly sends a session end request to the BC-SCF, and the BC-SCF ends the PVR-SCF and the BC-SCF according to the received session end request. At the same time, the PVR-SCF also sends a session end request to the PVR-MF, and the PVR-MF tears down the transmission channel established between the content source and the content source according to the session end request. Similarly, the session end request can be a BYE message in a SIP message, or other message. Alternatively, after the PVR-MF reports an abnormal event to the PVR-SCF, and sends a session end request to the PVR-SCF, the PVR-SCF sends a session end request to the BC-SCF, and the PVR-MF is removed and the content source is The transmission channel established between.

In addition, in the above process, there is no strict sequence between some steps. For example, step 61 Γ 612 may be before step 607 or before step 609. In this embodiment, for the convenience of description, the steps are set for each step. The serial number may be implemented according to the actual situation. In addition, the specific implementation process in step 602 and step 603 in the foregoing process may also be an OF fer/Answer process of the SIP protocol between the BC-SCF and the PVR-MF. Interaction, PVR-SCF forwards between two entities.

Messages between the UE and the PVR-SCF, between the PVR-SCF and the PVR-MF, and between the PVR-SCF and the BC-SCF in the above process can be routed through entities in the IMS system. The entities in the IMS system mainly include P_SCSF, S-CSCF, and the like.

Example two:

The example system includes: UE, PVR-SCF, PVR-MF, BC-SCF and BC_MF. In this example, it is assumed that a live television (LTV) service (the process of establishing an LTV service can be performed with reference to the prior art) is being performed, and a real-time recording task is submitted during the UE viewing process. Fig. 7 is a flow chart showing the process of realizing network recording in the second example of the present invention. As shown in Figure 7, the process includes the following steps:

Step 701: The UE submits a recording task for recording the current program of the current channel to the PVR-SCF, that is, the network is expected to initiate instant recording from the current viewing position.

In the specific implementation, the INVI TE message in the SIP message may be initiated, or may be in the SIP message. The REFER message is initiated and so on.

Step 702: The PVR-SCF returns a response message to the UE.

Step 703: The UE initiates subscription recording event information to the PVR-SCF.

The subscription recording event information can be implemented by using a SUBSCRIBE message in the IP message.

If step 701 uses an INVITE message to send a recording task, this step can directly perform the subscription. If the step 701 is to use the REFER message to send the recording task, the session between the UE and the PVR-SCF is released after the REFER message is executed. Therefore, according to the implicit subscription rule of the REFER message, step 702 and this step are performed. The method further includes: the PVR-SCF sends a NOTIFY message to the UE, and is used to carry the session ID information of the PVR-SCF to initiate a call to the BC-SCF. After receiving the NOTIFY message, the UE returns a 200 0K message to the PVR-SCF. Then, the SUBSCRIBE message in this step also needs to carry the session ID information obtained from the NOTIFY message.

Step 704: The PVR-SCF returns a response message to the UE.

If the step 701 is to use the REFER message to send the recording task, the PVR-SCF queries the local session according to the session ID information in the subscription request of the UE, and locates the corresponding session, and further returns a response message to the UE. . The response message can be a 200 0K message.

Steps 705-709 are consistent with steps 602-606 shown in FIG. If the PVR-SCF sends an INVITE message to the BC-SCF and the Offer is carried in the INVITE message, the initial information of the Of fer can be passed through the step 701. The INVITE message or REFER message carries, for example, a Portable Session Description Protocol (SDP) message body, and the like.

Step 710: During the recording process, the PVR-SCF reports the event information to the UE.

During recording, events that occur will be reported, such as events caused by insufficient storage space on the PVR-MF or other abnormal information. In actual applications, the recording of event information can be reported by the NOTIFY message in the S IP message.

Step 711: The UE returns a response message to the PVR-SCF.

This step is an optional step, and the response message can be a 200 OK message. Step 712: If the recording event information reported in step 710 indicates that the recording is abnormal, the UE may actively request to end the recording in this step, and send a recording end request to the PVR-SCF.

If the INVITE message is used in the step 701 to send the recording task, the recording end request in this step may be a BYE message; if the REFER message is used in the step 701 to send the recording task, the The recording end request can be a REFER message.

Step 71 3: The PVR-SCF returns a response message to the UE.

Step 714: The PVR-SCF sends a session end request to the BC-SCF.

In this step, the session end request may be a BYE message in the SIP message. In addition, the PVR-SCF also sends a session end request to the PVR-MF, and the PVR-MF tears down the transmission channel established between the content source and the content source according to the session end request. The channel removal process is consistent with the description in step 607 shown in FIG.

Step 715: The BC-SCF ends the session with the PVR-SCF according to the received session end request, and further returns a response message to the PVR-SCF.

The response message can be a 200 0K message.

In the above process, steps 703, 704, 710, and 711 are optional steps.

In addition, if the user carries the recorded duration information in 701 and does not receive the recording end request from the UE before the recording duration expires, steps 712 and 71 can be omitted, and the PVR-SCF or PVR-MF The session end request is initiated to remove the session between the PVR-SCF and the BC-SCF and the transmission channel between the PVR-MF and the content source.

Further, after the recording is completed, the PVR-SCF can notify the UE of the recording result information through the NOTIFY message.

In addition, in the foregoing process, messages between the UE and the PVR-SCF, between the PVR-SCF and the PVR-MF, and between the PVR-SCF and the BC-SCF can be routed through entities in the IMS system. The entities in the IMS system mainly include P_SCSF, S-CSCF, and so on.

Similarly, in the above process, there is no strict sequence between some steps. For example, steps 703-704 may be after step 705. In this embodiment, for the convenience of description, the steps are set for each step. The serial number can be executed according to the actual situation when it is implemented.

Example three:

The example system includes: UE, PVR_SCF, PVR_MF, BC-SCF, and BC_MF. In this example, it is assumed that a live television (LTV) service (the process of establishing an LTV service can be performed with reference to the prior art) is being performed, and a real-time recording task is submitted during the UE viewing process. Fig. 8 is a flow chart showing the process of realizing network recording in the third example of the present invention. As shown in Figure 8, the process includes the following steps:

Step 801: The UE submits a recording task for recording the current program of the current channel to the BC-SCF, that is, the network is expected to initiate instant recording from the current viewing position.

In the specific implementation, the INVITE message in the S IP message may be initiated, or may be initiated through a REFER message in the S IP message.

Step 802: The BC-SCF returns a response message to the UE.

Step 803: The UE initiates subscription recording event information to the PVR-SCF.

If step 801 uses an INVITE message to send a recording task, this step can directly perform the subscription. If the REFER message is used to send the recording task in step 801, the session between the UE and the BC-SCF is released after the REFER message is executed. Therefore, according to the implicit subscription rule of the REFER message, step 802 and this step are performed. The method further includes: the BC-SCF sends a notification ( NOTIFY) message to the UE, and is used to carry the session ID information that the BC-SCF wants to initiate a call to the PVR-SCF. After receiving the NOTIFY message, the UE returns a 200 OK message to the BC-SCF. Then, the SUBSCRIBE message in this step also needs to carry the session ID information obtained from the NOTIFY message.

Step 804: The PVR-SCF returns a response message to the UE.

If the step 801 uses the REFER message to send the recording task, the PVR-SCF queries the local session according to the session ID information in the subscription request of the UE, and locates the corresponding session, and further returns a response message to the UE. . The response message can be a 200 0K message.

Step 805 - Step 811 is identical to steps 705 - 711 shown in FIG. Step 812: If the recording event information reported in step 81 0 indicates that the recording is abnormal, the UE may actively request to end the recording in this step, and send a recording end request to the BC-SCF.

If the INVITE message is used in the step 801 to send the recording task, the recording end request in this step may be a BYE message; if the REFER message is used in the step 801 to send the recording task, the The recording end request can be a REFER message.

Step 81 3: The BC-SCF returns a response message to the UE.

Step 814: The BC-SCF sends a session end request to the PVR-SCF.

In this step, the session end request may be a BYE message in the SIP message.

Step 815: The PVR-SCF ends the session with the BC-SCF according to the received session end request, and further returns a response message to the BC-SCF. The response message can be a 200 0K message.

In addition, the PVR-SCF sends a session end request to the PVR-MF, and the PVR-MF tears down the transmission channel established between the content source and the content source according to the session end request. The channel removal process is consistent with the description in step 607 of Figure 6.

In the above embodiments, the LTV service is taken as an example to describe a method, a system, and an entity for implementing network recording. In addition, a network recording may be performed on a CoD service or a time-shifted transmission television (TsTV) service. The general process of implementation is the same. The only difference is that the content source information contains only the unicast address, and the bearer channel between the network recording media entity and the content source can only be a unicast channel. When acquiring the content source information, the SCF controlling the CoD service and the TsTV service needs to directly perform content address acquisition and media negotiation with the MF that processes the CoD service and the TsTV service, similar to media negotiation between the PVR-SCF and the PVR-MF. process. Those skilled in the art can implement the work without labor according to the scheme in this document, and will not be repeated here.

The network recording media entity and the content source in the above embodiments may be combined, and the transmission channel at this time may be an internal communication channel.

In addition, the method for the network recording media entity in the foregoing embodiments to report the event information and/or the recording result information to the network recording control entity may exist independently, that is, for other network recording parties. The same applies. In addition, the method in which the network recording control entity reports the recording event information and/or the recording result information to the recording task requesting entity may also exist independently, that is, the same applies to other network recording methods.

The above described specific embodiments of the present invention are further described in detail, and it is to be understood that the foregoing description is only the preferred embodiments of the present invention The scope of the present invention is intended to be included within the scope of the present invention. Any modifications, equivalents, improvements, etc., are included in the scope of the present invention.

Claims

Claim

A method for implementing network recording, the method comprising:

The method for implementing network recording according to claim 1, wherein the recording task is a recording task submitted by the user equipment UE; or a recording task configured for the network.

The method for implementing network recording according to claim 2, wherein the network recording control entity is: a personal video recorder function-service control function PVR-SCF;

The manner in which the UE submits the recording task is: a recording task submitted by the UE to the PVR-SCF based on the Hypertext Transfer Protocol HTTP, or a recording task submitted by the UE to the PVR-SCF based on the Session Initiation Protocol SIP.

The method for implementing network recording according to claim 3, wherein the manner in which the UE submits a task to the PVR-SCF based on the SIP is: the UE sends an INVITE message in the SIP or submits a REFER message to the PVR. SCF recording task;

Or: The UE forwards the recording task to the PVR-SCF by the broadcast service function-service control function BC-SCF through the invitation INVITE message in the SIP or the submission of the REFER message.

The method for implementing network recording according to claim 1, wherein the network recording control entity is a PVR-SCF, and the network recording media entity is a personal video recorder function-media function PVR-MF;

The network recording control entity controls the network recording media entity and the content source to establish a transmission channel, including: PVR-SCF interacts with the BC-SCF to obtain content source information, and the PVR-SCF notifies the obtained content source information to the PVR-MF. The PVR-MF establishes a transmission channel with the content source according to the received content source information.

6. The method for implementing network recording according to claim 1, wherein said network recording The control entity is a joint entity of the PVR-SCF and the BC-SCF, and the network recording media entity is a combined entity of the PVR-MF and the broadcast service function-media function BC-MF.

The network recording control entity controls the network recording media entity and the content source to establish a transmission channel, including: the PVR-SCF in the network recording control entity interacts with the BC-SCF to obtain content source information, and the PVR-SCF obtains the information. Content source information is notified to the network recording media entity

PVR-MF;

The PVR-MF in the network recording media entity establishes an internal transmission channel with the content source BC-MF according to the received content source information.

The method for implementing network recording according to claim 5, wherein the media stream from the content source is transmitted in a multicast manner;

The content source information is multicast source information;

The PVR-MF establishes a transmission channel according to the received content source information and the content source: The PVR-MF sends a request for joining the multicast to the multicast control function entity according to the received multicast source information, and the multicast control function entity According to the request for joining the multicast, the media stream from the content source is distributed to the PVR-MF, and the transmission channel establishment between the PVR-MF and the content source is completed.

The method for implementing network recording according to claim 5, wherein the media stream from the content source is transmitted in a unicast manner;

The content source information is unicast channel information;

The PVR-MF establishes a transmission channel according to the received content source information and the content source: The PVR-MF establishes a unicast channel between the received unicast channel information and the content source.

The method for implementing network recording according to any one of claims 1 to 8, wherein after the recording is completed or after receiving the end recording request or the session end request, the network recording media entity and the content source are removed. The established transmission channel.

The method for implementing network recording according to any one of claims 1 to 8, wherein the method further comprises: the network recording media entity reporting the recorded event information and/or the recording result information to the network recording control entity .

The method for implementing network recording according to claim 10, wherein before the network recording media entity reports the recording event information and/or the recording result information to the network recording control entity, the method further includes: the network recording control entity to the network The recording media entity subscribes to recording event information and/or recording result information.

The method for implementing network recording according to claim 10, wherein the method further comprises: the network recording control entity reporting the recorded event information and/or the recording result information to the requesting entity of the recording task.

The method for implementing network recording according to claim 12, wherein the network recording control entity reports the recorded event information and/or the recording result information to the requesting entity of the recording task, and further includes: a requesting entity that records the task Subscribe to the Network Recording Control Entity for recording event information and/or recording result information.

The method for implementing network recording according to any one of claims 1 to 8, wherein the method further comprises: the network recording media entity receiving a play request from the UE, according to the received play request, The recorded media stream corresponding to the play request is transmitted to the UE.

The method for implementing network recording according to any one of claims 1 to 8, wherein the recording task is a predetermined recording task, or a current real-time recording task.

The method for implementing network recording according to any one of claims 1 to 8, wherein a message between the network recording control entity and a network recording media entity, a network recording control entity, and a content source The interaction is routed through entities in the IP Multimedia Subsystem IMS.

17. A system for implementing network recording, the system comprising:

a network recording control entity (31), configured to receive a recording task, and send, to the network recording media entity, control information that carries the content source information according to the recording task;

The network recording media entity (32) is configured to establish a transmission channel with the content source according to the received control information carrying the content source information, and receive and record the media stream from the content source transmitted through the transmission channel;

A content source (33) for transmitting the media stream to the network recording media entity.

The system for implementing network recording according to claim 17, wherein the system further comprises: a user equipment UE, configured to submit a recording task to the network recording control entity (31).

The system for realizing network recording according to claim 17 or 18, wherein the network recording control entity (31) is a personal video recorder function-service control function PVR-SCF, and the network recording media entity (32) ) for personal video recorder function - media function PVR-MF.

The system for implementing network recording according to claim 17 or 18, wherein the network recording control entity (31) is a joint entity of a PVR-SCF and a BC-SCF, and the network recording media entity ( 32) is a combined entity of PVR-MF and BC-MF.

The system for implementing network recording according to claim 19, wherein the system further comprises: a broadcast service function-service control function BC-SCF, configured to provide content source information to the PVR-SCF.

The system for implementing network recording according to claim 21, wherein the media stream from the content source is transmitted in a multicast manner, the system further comprising: a multicast control function entity, configured to be in the PVR - The MF joins the multicast request to distribute the media stream from the content source to the PVR-MF.

23. A network recording control entity, wherein the entity comprises:

a receiving module (41), configured to receive a recording task;

The control module (42) is configured to send, to the network recording media entity, control information that carries the content source information according to the recording task.

24. The network recording control entity according to claim 23, wherein the entity is: a personal video recorder function-service control function PVR-SCF or a combined entity of a PVR-SCF and a BC-SCF.

The network recording control entity according to claim 24, wherein the entity further comprises: a content source information obtaining module, configured to acquire content source information from the broadcast service function-service control function BC-SCF.

The network recording control entity according to claim 25, wherein the entity further comprises: an information acquisition module, configured to acquire recording event information and/or recording result information from the personal video recorder function-media function PVR-MF.

The network recording control entity according to claim 26, wherein the entity further comprises: an information module, configured to send the acquired recording event information and/or recording result information to the recording task request entity.

The network recording control entity according to claim 27, wherein the entity further comprises: a subscription receiving module, configured to receive a subscription request for subscription recording event information and/or recording result information from the requesting entity of the recording task And notifying the information reporting module to perform the reporting operation according to the received subscription request.

The network recording control entity according to any one of claims 23 to 28, wherein the entity further comprises: a recording end notification module, configured to send a session end request to the PVR-MF, to notify the PVR-MF to dismantle The transmission channel established with the content source.

30. A network recording media entity, wherein the entity comprises:

a receiving module (51), configured to receive control information that carries content source information;

a channel establishing module (52), configured to establish a transmission channel with the content source according to the content source information in the control information;

A receiving recording module (53) is configured for receiving and recording a media stream from a content source transmitted through the established transmission channel.

31. The network recording media entity according to claim 30, wherein the entity is: a personal video recorder function-media function PVR-MF or a combined entity of PVR-MF and BC-MF.

The network recording media entity of claim 31, wherein the entity further comprises: an information reporting module, configured to acquire recording event information and/or recording result information of the recording, and obtain the recorded event information. And/or the recording result information is reported to the network recording control entity.

The network recording media entity of claim 31, wherein the entity further comprises: a media playing module, configured to transmit the recorded media stream corresponding to the play request to the play request of the UE UE.

The network recording media entity according to any one of claims 30 to 33, wherein the entity further comprises: a subscription receiving module, configured to receive a subscription recording from the network recording control entity The subscription request of the event information and/or the recording result information, according to the accepted subscription request, notifies the information reporting module to perform the reporting operation.