WO2017016276A1 - 基于ott的npvr实现方法及装置 - Google Patents

基于ott的npvr实现方法及装置 Download PDF

Info

Publication number
WO2017016276A1
WO2017016276A1 PCT/CN2016/081763 CN2016081763W WO2017016276A1 WO 2017016276 A1 WO2017016276 A1 WO 2017016276A1 CN 2016081763 W CN2016081763 W CN 2016081763W WO 2017016276 A1 WO2017016276 A1 WO 2017016276A1
Authority
WO
WIPO (PCT)
Prior art keywords
npvr
ott
record
module
request
Prior art date
Application number
PCT/CN2016/081763
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 WO2017016276A1 publication Critical patent/WO2017016276A1/zh

Links

Images

Classifications

    • 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/433—Content storage operation, e.g. storage operation in response to a pause request, caching 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/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25866—Management of end-user data
    • H04N21/25891—Management of end-user data being end-user preferences
    • 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/41—Structure of client; Structure of client peripherals
    • H04N21/4104—Peripherals receiving signals from specially adapted client devices
    • H04N21/4126—The peripheral being portable, e.g. PDAs or mobile phones
    • 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/4335—Housekeeping operations, e.g. prioritizing content for deletion because of storage space restrictions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64746—Control signals issued by the network directed to the server or the client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/858—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot
    • H04N21/8586—Linking data to content, e.g. by linking an URL to a video object, by creating a hotspot by using a URL

Definitions

  • This document relates to, but is not limited to, the field of computer technology, and relates to an OTT-based NPVR implementation method and apparatus.
  • OTT an abbreviation of “Over The Top”, refers to providing various application services to users through the Internet. This kind of application is different from the communication service provided by the current operator. OTT only uses the operator's network, and the service is provided by a third party other than the operator. Currently, typical OTT services include Internet TV services, Apple App Store, and others.
  • the OTT discussed in this application refers specifically to the Internet video playing service, the CDN (Content Distribution Network) and the set-top box are all provided by accessing the Internet (public network).
  • the bearer network is different. In order to guarantee the quality of service and support multicast, the traditional IPTV is operated by the private network and is isolated from the Internet.
  • OTT currently supports not only the most basic on-demand and live broadcast functions, but also supports Time-shifted Television (TSTV), TVOD (True Video On Demand), and NPVR (network personal video recorder).
  • TSTV Time-shifted Television
  • TVOD True Video On Demand
  • NPVR network personal video recorder
  • the functions such as personal network recording include OTT STB (Set Top Box), telephone (Phone) or PAD (portable android device).
  • NPVR refers to a characteristic personal service in IPTV network Internet TV. Users can record and save their favorite programs (or channel programs) and watch them repeatedly. The recorded content can be deleted by users. However, each user has a certain NPVR space limit, and you can increase your NPVR space by purchasing. NPVR has been widely used in IPTV services and has become one of the featured services carried out by operators, mainly for TV and set-top box users. At present, for the IPTV (the main application scenarios of the IPTV services of the mobile phone, the PAD, the PC, and the like, including playback, bookmarking, time shifting, and recording), the service has many limitations, and the NPVR service cannot be completed through the OTT.
  • the embodiment of the invention provides an OTT-based NPVR implementation method and device, so that the IPTV service of the mobile phone, the PAD, the PC, and the like can complete the NPVR service through the OTT.
  • the NPVR attribute is configured to support the OTT NPVR attribute, and a new interface is configured between the control point CP and the content distribution network CDN to complete the OTT NPVR message through the new interface. Hair extension.
  • the method further includes:
  • the NPVR code, the processing status, and the IP address are expanded in the first preset table.
  • the method further includes:
  • the NPVR record is a single episode NPVR record or a normal NPVR record, inserting a request NPVR recording notification task or canceling the NPVR recording notification task in the second preset table;
  • the NPVR record is directly deleted, and the delete NPVR recording notification task is inserted in the second preset table.
  • the method further includes:
  • the corresponding NPVR record is shifted according to the NPVR code. To delete the table.
  • the method further includes:
  • the NPVR update notification task is inserted to notify the CDN that the user has already sold the account.
  • the method further includes:
  • the embodiment of the invention further provides an OTT-based network recording service NPVR implementation device, including:
  • a receiving module configured to receive an OTT-based NPVR service request instruction
  • a determining module configured to determine whether there is a site for docking the OTT after receiving the OTT-based NPVR service requesting instruction
  • a configuration module configured to configure an NPVR attribute to support an OTT NPVR attribute when the site of the docking OTT exists, and configure a new interface between the control point CP vendor and the content distribution network CDN to pass the new interface
  • the interface completes the OTT NPVR message transmission and reception.
  • the device further includes: an update module, a save module, and an expansion module;
  • the receiving module is further configured to receive an NPVR recording request
  • the update module is configured to update the NPVR record after receiving the NPVR recording request
  • the saving module is configured to save the updated NPVR record and the network protocol IP address of the user to initiate the NPVR recording request;
  • the expansion module is configured to expand the NPVR code, the processing status, and the IP address in the first preset table.
  • the device further includes a deletion module
  • the expansion module is further configured to insert a request NPVR recording notification task or cancel the NPVR in the second preset table when the NPVR is recorded as a single episode NPVR record or a normal NPVR record. Recording a notification task; further configured to insert a delete NPVR recording notification task in the second preset table;
  • the deleting module is configured to directly delete the NPVR record when receiving the NPVR deletion task.
  • the device further includes an obtaining module and a processing module;
  • the acquiring module is configured to scan a second preset table, and send the obtained notification task to the CDN;
  • the processing module is configured to move the corresponding NPVR record to the deletion table according to the NPVR code if the CDN reception fails or the response times out.
  • the processing module is further configured to: after receiving the account cancellation request, clear the NPVR record of the corresponding user of the account cancellation request;
  • the expansion module is further configured to insert an NPVR update notification task to notify the CDN that the user has already sold the account.
  • the receiving module is further configured to receive a play URL parameter insertion request of the OTT;
  • the expansion module is further configured to insert a parameter corresponding to the play URL parameter insertion request in the play URL of the OTT, to calculate a play behavior of the user by using the inserted parameter.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements an OTT-based network recording service NPVR implementation method.
  • the foregoing technical solution supports the OTT NPVR attribute in the presence of the OTT NPVR, and configures a new interface between the CP and the CDN to provide a new interface for OTT NPVR messaging and OTT NPVR.
  • An NPVR function supporting OTT is proposed to implement OTT-based NPVR services, so that NPVR services are no longer limited, thereby improving the applicability of NPVR services.
  • FIG. 1 is a schematic flowchart of an OTT-based NPVR implementation method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an OTT-based NPVR implementation method according to Embodiment 2 of the present invention
  • FIG. 3 is a schematic diagram of a process of applying/cancelling an NPVR recording according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic flowchart of an OTT-based NPVR implementation method according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic flowchart diagram of an OTT-based NPVR implementation method according to Embodiment 4 of the present invention.
  • FIG. 6 is a schematic diagram of a flow of cleaning up an NPVR by a customer in the fourth embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of an OTT-based NPVR implementation method according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic diagram of functional modules of an OTT-based NPVR implementation apparatus according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic diagram of functional modules of an OTT-based NPVR implementation apparatus according to Embodiment 6 of the present invention.
  • FIG. 10 is a schematic diagram of functional modules of an OTT-based NPVR implementation apparatus according to Embodiment 6 of the present invention.
  • the OTT-based NPVR service requesting instruction is received to determine whether there is a site for the OTT connection; when there is a site for the OTT connection, the NPVR attribute is configured to support the OTT NPVR attribute at the control point (CP).
  • a new interface is configured between the Control Point and the content distribution network CDN to complete the OTT NPVR messaging through the new interface.
  • the OTT NPVR attribute is configured, the OTT NPVR attribute is configured, and a new interface is configured between the CP and the CDN to provide a new interface for OTT NPVR messaging and OTT NPVR.
  • OTT Effectively avoiding the current OTT (the main application scenarios are IPTV services for mobile phones, PADs, PCs, etc., including playback, bookmarking, time shifting, recording, etc.), which have many limitations and cannot complete NPVR services through OTT.
  • An NPVR function supporting OTT is proposed to implement OTT-based NPVR services, so that NPVR services are no longer limited, thereby improving the applicability of NPVR services.
  • an embodiment of the present invention provides an OTT-based NPVR implementation method.
  • FIG. 1 is a schematic flowchart diagram of an OTT-based NPVR implementation method according to Embodiment 1 of the present invention. As shown in FIG. 1, the OTT-based NPVR implementation method includes:
  • Step S10 Receive an OTT-based NPVR service request instruction, and determine whether there is a site for docking the OTT.
  • the manner of triggering the OTT NPVR service request instruction includes the following: 1) triggering through a physical button on the terminal, for example, after continuously pressing a physical button 2 times; 2) passing the service on the terminal
  • the application instruction virtual button triggers, for example, setting a service request instruction virtual button at the center of the terminal, and triggering by touching the virtual button; 3) automatically triggering when the OTT NPVR service is requested.
  • the triggering manners of the NPVR service requesting instructions of the OTT listed above are merely exemplary. Those skilled in the art can use the technical idea of the present application to trigger the OTT NPVR service requesting instructions of other OTTs according to their specific requirements. Within the scope of protection of the present application, it is not exhaustive here.
  • the OTT-based NPVR service request instruction is received to determine whether there is a site for docking the OTT.
  • step S20 when there is a site for docking the OTT, the NPVR attribute is configured to support the OTT NPVR attribute, and a new interface is configured between the control point CP and the content distribution network CDN to complete the OTT NPVR through the new interface. Messages are sent and received.
  • the NPVR attribute is configured to support the OTT NPVR attribute.
  • the configuration is 2, the configuration is 2 to support the OTT NPVR function, and the IPTV NPVR function is compatible.
  • a new interface is developed between the CP and the CDN to support the transmission and reception of OTT NPVR messages.
  • the OTT NPVR attribute is configured to configure a new interface between the CP and the CDN.
  • the IPTV user can log in to the RTSP (Real Time Streaming Protocol) node to enjoy the traditional IPTV basic service and NPVR function.
  • the OTT user can log in to the OTT node.
  • there are some other configuration items for the docking of CDN and CP. Refer to Table 1:
  • the configuration that needs to be completed for the OTT NPVR includes the configuration of simultaneously docking 2.0 CDN and 3.0 CDN.
  • the above configuration only involves the NPVR function. In fact, if the OTT content and channel are released, you need to configure the 370 interface related configuration.
  • the foregoing technical solution supports the OTT NPVR attribute in the presence of the OTT NPVR, and configures a new interface between the CP and the CDN to provide a new interface for OTT NPVR messaging and OTT NPVR.
  • the above technical solution proposes an NPVR function that supports OTT, and implements an OTT-based NPVR service, so that the NPVR service is no longer limited, thereby improving the applicability of the NPVR service.
  • FIG. 2 is another schematic flowchart of an OTT-based NPVR implementation method according to an embodiment of the present invention. As shown in FIG. 2, based on the foregoing OTT-based NPVR implementation method, after the step S20, the method further includes:
  • Step S30 after receiving the NPVR recording request, updating the NPVR record
  • Step S40 saving the updated NPVR record and the IP (Internet Protocol) address of the NPVR recording request;
  • Step S50 expanding the NPVR code, the processing status, and the IP address in the first preset table.
  • the NPVR record is updated, and the updated NPVR record and the IP of the user-initiated NPVR recording request are saved.
  • the address expands the NPVR code, the processing status, and the IP address in the first preset table.
  • the first table may be a s830_NPVR_record table.
  • the user can pass The EPG (Electronic Program Guide) initiates a recording (application) request or cancellation request for the NPVR recording, and notifies the CP to update the NPVR record through the relevant interface.
  • the CP calls the DB (Database, Database) stored procedure to apply for or cancel the NPVR recording.
  • the NPVR recorded service flow remains unchanged.
  • the IP address of the user initiated NPVR operation is saved.
  • sys_special_NPVR is configured to 2 (ie OTT NPVR)
  • the processing logic is as follows:
  • NPVRCode NPVR code
  • State processing state
  • Userip user IP address
  • NPVRCode 0100000000060000000187.
  • State indicates the processing state of NPVR and different values of State. Indicates different processing status: 999 means user reservation; 1 means reservation is successful; 2 means recording is successful; -1 means NPVR failure, the State field defaults to 2.
  • the userid is the userid in the s830_user table, not the usercode.
  • the userid is the account ID that initiates the NPVR operation; the recordid is the recordid in the s830_record table, not the recordcode.
  • the foregoing technical solution is to update the NPVR record by receiving the NPVR recording request, and save the NPVR code, the processing status, and the IP address of the processing in the first preset table, so that the first preset table can be queried or automatically completed in time.
  • the process improves the efficiency of NPVR business execution.
  • FIG. 4 is a schematic flowchart diagram of an OTT-based NPVR implementation method according to an embodiment of the present invention. As shown in FIG. 4, based on the foregoing OTT-based NPVR implementation method, after the step S30, the method further includes:
  • Step S60 when the NPVR record is a single episode NPVR record or a normal NPVR record, insert a request NPVR recording notification task or an NPVR cancel NPVR recording notification task in the second preset table;
  • Step S70 When receiving the NPVR deletion task, directly delete the NPVR record, and insert a delete NPVR recording notification task in the second preset table.
  • the second preset table may be a s830_task table.
  • a request NPVR recording notification task or insert a cancel NPVR recording notification task into the s830_task table where parameter 1: user IP; parameter 2: user ID; parameter 3: RecordCode; parameter 4: action (1 means add NPVR; 0 means delete NPVR); parameter 5: NPVRCode; parameter 6: end time of TVOD.
  • action (1 means add NPVR; 0 means delete NPVR); parameter 5: NPVRCode; parameter 6: end time of TVOD.
  • For the NPVR deletion task directly delete the NPVR record and insert the notification task, and do not need to wait for the CDN to report the processing result.
  • the method further includes:
  • the second preset table is scanned, and the obtained notification task is sent to the CDN; if the CDN receives the failure or the response times out, the corresponding NPVR record is moved to the deletion table according to the NPVR code.
  • the CP periodically scans the s830_task table to obtain a notification task, and sends the obtained notification task to the CDN. If the CDN receiving the NPVR recording operation fails or the CDN response times out, the corresponding NPVR record is moved to the deletion table according to the NPVRCode. Then, the NPVR record in the delete table is cleared by the timed task; if the CDN requesting the NPVR recording operation is successfully received, the corresponding NPVR record status is set to 1 according to the NPVRCode, indicating that the reservation is successful and waiting for the CDN processing result.
  • the CDN reports the processing result of the NPVR record, and calls back the DB storage process, and the processing logic is as follows:
  • the CP processes according to the NPVRCode callback DB storage process. If the CDN fails to report, the corresponding record state is moved to the delete table according to the NPVRCode, and the NPVR record in the table is deleted by the scheduled task. If the CDN report is successful, the corresponding record status is set to 2 according to NPVRCode.
  • timing task processing flow is as follows:
  • Timed tasks (for example, 5 minutes or 8 minutes, etc., can also be 1 day or a week, etc.)
  • the corresponding recording state is moved to the deletion table according to the NPVRCode, and the NPVR record in the table is deleted by the timing task.
  • a scheduled task (for example, a day task or a weekly task or a monthly task, etc.) cleans up the timed task in the delete table with a status of -1.
  • aging is not allowed for TVODs with NPVR records.
  • the foregoing technical solution can update the processing status of the NPVR in time by inserting the request NPVR recording notification task or the NPVR to cancel the NPVR recording notification task or the NPVR in the second preset table, and then query or report the NPVR through the second preset table in time.
  • Business process processing status improves NPVR business processing results.
  • FIG. 5 is a schematic flowchart diagram of a fourth embodiment of an OTT-based NPVR implementation method according to the present invention. As shown in FIG. 5, based on the foregoing OTT-based NPVR implementation method, the method further includes:
  • Step S80 After receiving the account cancellation request, clear the NPVR record corresponding to the user of the account cancellation request, and insert an NPVR update notification task to notify the CDN that the user has already sold the account.
  • the user when the user needs to clear the service user of the NPVR, the user issues a customer account request, and after receiving the account cancellation request, clears the NPVR record of the corresponding user request and inserts the NPVR update notification task. In order to notify the CDN that the user has already sold the account.
  • the corresponding NPVR record is cleared, and the NPVR notification task, the scheduled task, or the NPVR notification task is inserted to cancel the NPVR recording, cache the NPVR task, and report the processing result through the CDN, for example, whether the account is successfully sold, or the account fails. Wait.
  • the step S80 may be performed after the step S70, and may also be performed at any position in the step S10 to the step S70.
  • FIG. 7 is a schematic flowchart diagram of an OTT-based NPVR implementation method according to an embodiment of the present invention.
  • Figure 7 As shown, based on the above OTT-based NPVR implementation method, the method further includes:
  • Step S90 receiving a play URL (Uniform Resole Locator) parameter insertion request of the OTT, inserting a parameter corresponding to the play URL parameter insertion request in the play URL of the OTT, to count the user by using the inserted parameter. Play behavior.
  • a play URL Uniform Resole Locator
  • the parameters added in the play URL of the OTT include: columnnid, programid, boid, contentid, cpcode, stbid, terminalflag, and videoid.
  • the meanings of the OTT URL and the parameter values are as follows:
  • ContentID is the physical contentid of the physical channel
  • programid is the service channel code
  • boid is the operator code of the login account
  • contentid is the service channel code
  • stbid is the device ID of the login terminal
  • stbid for the STB and device UUID for the other terminal
  • Universally Unique Identifier Universal Unique Identifier
  • terminalflag is the terminal type of the login terminal
  • videoid is the recording plan code (code).
  • the step S90 may be performed after the step S80, and may also be performed at any position in the step S10 to the step S80.
  • the user's play behavior can be counted in time, so that the OTT-based NPVR service is better and more reasonable.
  • the execution bodies of the OTT-based NPVR implementation methods in the foregoing Embodiments 1 to 5 may all be terminals.
  • the OTT-based NPVR implementation method may be implemented by a client-based OTT-based NPVR implementation program on the installation terminal, where the terminal includes, but is not limited to, a mobile phone, a pad, a notebook computer, and the like.
  • the embodiment of the invention provides an OTT-based NPVR implementation device.
  • FIG. 8 is a schematic diagram of functional modules of an OTT-based NPVR implementation apparatus according to an embodiment of the present invention.
  • the OTT-based NPVR implementation apparatus includes: a receiving module 10, a determining module 20, and a configuration module 30.
  • the receiving module 10 is configured to receive an OTT-based NPVR service request instruction
  • the determining module 20 is configured to: after receiving the OTT-based NPVR service requesting instruction, determine whether there is a site for docking the OTT;
  • the manner of triggering the OTT NPVR service request instruction includes the following: 1) triggering through a physical button on the terminal, for example, after continuously pressing a physical button 2 times; 2) passing the service on the terminal
  • the application instruction virtual button triggers, for example, setting a service request instruction virtual button at the center of the terminal, and triggering by touching the virtual button; 3) automatically triggering when the OTT NPVR service is requested.
  • the triggering manners of the NPVR service requesting instructions of the OTT listed above are merely exemplary. Those skilled in the art can use the technical idea of the present application to trigger the OTT NPVR service requesting instructions of other OTTs according to their specific requirements. Within the scope of protection of the present application, it is not exhaustive here.
  • the OTT-based NPVR service request instruction is received to determine whether there is a site for docking the OTT.
  • the configuration module 30 is configured to configure the NPVR attribute to support the OTT NPVR attribute when there is a site of the docking OTT, and configure a new interface between the control point CP and the content distribution network CDN to complete through the new interface.
  • OTT NPVR messaging is configured to configure the NPVR attribute to support the OTT NPVR attribute when there is a site of the docking OTT, and configure a new interface between the control point CP and the content distribution network CDN to complete through the new interface.
  • the NPVR attribute is configured to support the OTT NPVR attribute.
  • the configuration is 2, the configuration is 2 to support the OTT NPVR function, and the IPTV NPVR function is compatible.
  • a new interface is developed between the CP and the CDN to support the transmission and reception of OTT NPVR messages.
  • the OTT NPVR attribute is configured to configure a new interface between the CP and the CDN.
  • the IPTV user can log in to the RTSP (Real Time Streaming Protocol) node to enjoy the traditional IPTV basic service and NPVR function.
  • the OTT user can log in to the OTT node.
  • OTT NPVR capabilities there are some other configuration items for the docking of CDN and CP.
  • the IPTV service is connected to the OTT, about OTT
  • the configuration required for NPVR including the simultaneous docking of 2.0CDN and 3.0CDN configurations.
  • the above configuration only involves the NPVR function. In fact, if the OTT content and channel are released, you need to configure the 370 interface related configuration.
  • the foregoing technical solution supports the OTT NPVR attribute in the presence of the OTT NPVR, and configures a new interface between the CP and the CDN to provide a new interface for OTT NPVR messaging and OTT NPVR.
  • An NPVR function supporting OTT is proposed to implement OTT-based NPVR services, so that NPVR services are no longer limited, thereby improving the applicability of NPVR services.
  • the OTT-based NPVR implementation apparatus further includes an update module 40, a save module 50, and an extension module 60.
  • the receiving module 10 is further configured to receive an NPVR recording request
  • the update module 40 is configured to update the NPVR record after receiving the NPVR recording request;
  • the saving module 50 is configured to save the updated NPVR record and the IP address of the user initiated NPVR recording request;
  • the expansion module 60 is configured to expand the NPVR code, the processing status, and the IP address in the first preset table.
  • the NPVR record is updated, and the updated NPVR record and the IP of the user-initiated NPVR recording request are saved.
  • the address expands the NPVR code, the processing status, and the IP address in the first preset table.
  • the first table may be a s830_NPVR_record table.
  • the user can initiate a recording (application) request or cancel request of the NPVR recording through the EPG (Electronic Program Guide), and notify the CP to update the NPVR record through the relevant interface.
  • the CP calls the DB (Database, Database) stored procedure to apply for or cancel the NPVR recording.
  • the NPVR recorded service flow remains unchanged.
  • the IP address of the user initiated NPVR operation is saved.
  • sys_special_NPVR is configured to 2 (ie OTT NPVR)
  • the processing logic is as follows:
  • NPVRCode NPVR code
  • State processing state
  • Userip user IP address
  • NPVRCode 0100000000060000000187.
  • State indicates the processing state of NPVR and different values of State. Indicates different processing status: 999 means user reservation; 1 means reservation is successful; 2 means recording is successful; -1 means NPVR failure, the State field defaults to 2.
  • the userid is the userid in the s830_user table, not the usercode.
  • the userid is the account ID that initiates the NPVR operation; the recordid is the recordid in the s830_record table, not the recordcode.
  • the foregoing technical solution is to update the NPVR record by receiving the NPVR recording request, and save the NPVR code, the processing status, and the IP address of the processing process in the first preset table, so that the first preset table can be queried or automatically completed in time.
  • Business processes improve the efficiency of NPVR business execution.
  • the OTT-based NPVR implementation apparatus further includes a deletion module 70.
  • the expansion module 60 is further configured to insert a request NPVR recording notification task or an NPVR cancel NPVR recording notification task in the second preset table when the NPVR is recorded as a single episode NPVR record or a normal NPVR record; Inserting and deleting an NPVR recording notification task in the second preset table;
  • the deleting module 70 is configured to directly delete the NPVR record when receiving the NPVR deletion task.
  • the second preset table may be a s830_task table.
  • a request NPVR recording notification task or insert a cancel NPVR recording notification task into the s830_task table where parameter 1: user IP; parameter 2: user ID; parameter 3: RecordCode; parameter 4: action (1: new; 0: delete); parameter 5: NPVRCode; parameter 6: end time of TVOD.
  • NPVR deletion task directly delete the NPVR record and insert the notification task, without waiting for the CDN report processing. result.
  • the device further includes:
  • the obtaining module 80 is configured to scan the second preset table, and send the obtained notification task to the CDN;
  • the processing module 90 is configured to move the corresponding NPVR record to the deletion table according to the NPVR code if the CDN reception fails or the response times out.
  • the CP periodically scans the s830_task table to obtain a notification task, and sends the obtained notification task to the CDN. If the CDN receiving the NPVR recording operation fails or the CDN response times out, the corresponding NPVR record is moved to the deletion table according to the NPVRCode. Then, the NPVR record in the delete table is deleted by the timed task. Otherwise, the corresponding NPVR record status is set to 1 according to the NPVRCode, indicating that the reservation is successful and waiting for the CDN processing result.
  • the CDN reports the processing result of the NPVR record, and calls back the DB storage process, and the processing logic is as follows:
  • the CP processes according to the NPVRCode callback DB storage process. If the CDN fails to report, the corresponding record state is moved to the delete table according to the NPVRCode, and the NPVR record in the table is deleted by the scheduled task. If the CDN report is successful, the corresponding record status is set to 2 according to NPVRCode.
  • timing task processing flow is as follows:
  • the CDN processing timeout is considered.
  • the corresponding record status is moved to the delete table, and then the NPVR record in the table is deleted by the timed task.
  • a scheduled task (a day task or a weekly task or a monthly task, etc.) cleans up the timed task in the delete table with a status of -1. In the DB timing task, aging is not allowed for TVODs with NPVR records.
  • the foregoing technical solution can update the processing status of the NPVR in time by inserting the request NPVR recording notification task or the NPVR to cancel the NPVR recording notification task or the NPVR in the second preset table, and then query or report the NPVR through the second preset table in time.
  • Business process processing status improves NPVR business processing results.
  • the processing module 90 is further configured to: after receiving the account cancellation request, clear the NPVR record corresponding to the user of the account request;
  • the expansion module 60 is further configured to insert an NPVR update notification task to notify the CDN that the user has already sold the account.
  • the user when the user needs to clear the service user of the NPVR, the user issues a customer account request, and after receiving the account cancellation request, clears the NPVR record of the corresponding user request and inserts the NPVR update notification task. In order to notify the CDN that the user has already sold the account.
  • the corresponding NPVR record is cleared, the NPVR notification task, the scheduled task or the NPVR notification task is inserted, the NPVR recording is cancelled, the NPVR task is cached, and the processing result is reported through the CDN, for example, whether the account is successfully sold, or the account is failed.
  • the receiving module 10 is further configured to receive a play URL parameter insertion request of the OTT;
  • the expansion module 60 is further configured to insert a parameter corresponding to the play URL insertion request in the play URL of the OTT, to calculate a play behavior of the user by using the inserted parameter.
  • the parameters added in the play URL of the OTT include: columnnid, programid, boid, contentid, cpcode, stbid, terminalflag, and videoid.
  • the meanings of the OTT URL and the parameter values are as follows:
  • ContentID is the physicalcontentid of the physical channel
  • programid is the service channel code
  • boid is the operator code of the login account
  • contentid is the service channel code
  • stbid is the The device ID of the terminal is stbid for the STB, and the UUID (Universally Unique Identifier) for the other terminal
  • the terminalflag is the terminal type of the login terminal
  • the videoid is the recording plan code (codecode).
  • the foregoing technical solution can timely count the user's play behavior, so that the OTT-based NPVR service is better and more reasonable.
  • the embodiment of the present invention further provides a terminal, where the terminal includes a processor, and the processor is configured to receive an OTT-based NPVR service request instruction to determine whether there is a site for docking the OTT;
  • the NPVR attribute is configured to support the OTT NPVR attribute, and a new interface is configured between the CP and the CDN to complete the OTT NPVR message transmission through the new interface.
  • the terminal includes, but is not limited to, a mobile phone, a pad, a notebook computer, and the like.
  • the OTT NPVR attribute when configured, the OTT NPVR attribute is configured, and a new interface is configured between the CP and the CDN to provide a new interface for OTT NPVR messaging and OTT NPVR.
  • An NPVR function supporting OTT is proposed to implement OTT-based NPVR services, so that NPVR services are no longer limited, thereby improving the applicability of NPVR services.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, implements an OTT-based network recording service NPVR implementation method.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any particular form of hardware and software. Combine.
  • the above technical solution proposes an NPVR function that supports OTT, and implements an OTT-based NPVR service, so that the NPVR service is no longer limited, thereby improving the applicability of the NPVR service.

Landscapes

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

Abstract

一种基于OTT的NPVR实现方法，包括：接收基于到OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；在存在对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在CP与CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。上述技术方案提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。

Description

基于OTT的NPVR实现方法及装置 技术领域
本文涉及但不限于计算机技术领域，涉及基于OTT的NPVR实现方法及装置。
背景技术
OTT，是“Over The Top”的缩写，是指通过互联网向用户提供各种应用服务。这种应用和目前运营商所提供的通信业务不同，OTT仅利用运营商的网络，而服务由运营商之外的第三方提供。目前，典型的OTT业务有互联网电视业务，苹果应用商店等。本申请讨论的OTT，特指互联网视频播放业务，CDN(Content Distribution Network，内容分发网络)和机顶盒都是通过接入互联网(公网)来提供服务。与传统IPTV(Internet Protocol Television，交互式网络电视)相比，承载网络不同，传统IPTV为了保证服务质量、支持组播等，都是专网运营，与互联网是隔离的。OTT目前不仅支持最基本的点播、直播功能，也已经支持了时移TSTV(Time-shifted Television，时移电视)，TVOD(True Video On Demand，即点即播)，NPVR(network personal video recorder，个人网络录像)等功能，其使用的终端包括OTT STB(Set Top Box，机顶盒)，电话(Phone)或PAD(portable android device，平板电脑)等。
NPVR是指IPTV网络互联网电视中的一种特色个人业务。用户可以将自己喜爱的节目(或频道节目)录制并保存下来反复观看，录制的内容用户可以自定义删除，但是每个用户都有一定的NPVR空间限制，可以通过购买来增加自己的NPVR空间。NPVR已经被广泛应用于IPTV业务，成为运营商开展的特色业务之一，这主要针对于电视和机顶盒用户。而目前针对日益发展的OTT(其主要应用场景为手机、PAD、PC等客户端的IPTV业务，包括播放、书签、时移以及录制等)，业务局限较多，无法通过OTT完成NPVR业务。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种基于OTT的NPVR实现方法及装置，使手机、PAD、PC等客户端的IPTV业务可以通过OTT完成NPVR业务。
本发明实施例提供的一种基于OTT的网络录制服务NPVR实现方法，包括：
接收到基于OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；
在存在所述对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
可选地，所述在控制点CP与内容分发网络CDN之间配置新的接口的步骤之后，所述方法还包括：
接收到NPVR录制请求后，更新NPVR记录；
保存更新后的NPVR记录及发起所述NPVR录制请求的网络协议IP地址；
在第一预设表格中扩展NPVR码、处理状态和所述IP地址。
可选地，所述接收到NPVR录制请求后，更新NPVR记录的步骤之后，所述方法还包括：
在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或取消NPVR录制通知任务；
在接收到NPVR删除任务时，直接删除所述NPVR记录，并在所述第二预设表格中插入删除NPVR录制通知任务。
可选地，所述在所述第二预设表格中插入删除NPVR录制通知任务的步骤之后，所述方法还包括：
扫描所述第二预设表格，将获取的通知任务发送至CDN；
若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移 至删除表中。
可选地，所述方法还包括：
在接收到销户请求后，清除该销户请求对应用户的NPVR记录；
插入NPVR更新通知任务，以通知CDN所述用户已经销户。
可选地，所述方法还包括：
接收OTT的播放URL参数插入请求，在所述OTT的播放URL中插入与所述播放URL参数插入请求对应的参数，以通过插入的参数统计用户的播放行为。
本发明实施例还提供一种基于OTT的网络录制服务NPVR实现装置，包括：
接收模块，设置为接收基于OTT的NPVR服务申请指令；
确定模块，设置为接收到所述基于OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；
配置模块，设置为在存在所述对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP商与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
可选地，所述装置还包括：更新模块、保存模块和扩展模块；
所述接收模块，还设置为接收NPVR录制请求；
所述更新模块，设置为接收到NPVR录制请求后，更新NPVR记录；
所述保存模块，设置为保存更新后的NPVR记录及用户发起NPVR录制请求的网络协议IP地址；
所述扩展模块，设置为在第一预设表格中扩展NPVR码、，处理状态和所述IP地址。
可选地，所述装置还包括删除模块；
所述扩展模块，还设置为在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或取消NPVR 录制通知任务；还设置为在所述第二预设表格中插入删除NPVR录制通知任务；
所述删除模块，设置为在接收到NPVR删除任务时，直接删除所述NPVR记录。
可选地，所述装置还包括获取模块和处理模块；
所述获取模块，设置为扫描第二预设表格，将获取的通知任务发送至CDN；
所述处理模块，设置为若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移至删除表中。
可选地，
处理模块，还设置为在接收到销户请求后，清除该销户请求对应用户的NPVR记录；
所述扩展模块，还设置为插入NPVR更新通知任务，以通知CDN所述用户已经销户。
可选地，
所述接收模块，还设置为接收OTT的播放URL参数插入请求；
所述扩展模块，还设置为在所述OTT的播放URL中插入与所述播放URL参数插入请求对应的参数，以通过插入的参数统计用户的播放行为。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现基于OTT的网络录制服务NPVR实现方法。
上述技术方案通过在存在对接OTT的局点时，配置支持OTT NPVR属性，且在CP与CDN之间配置新的接口，提供新的接口供OTT的NPVR消息接发，支持OTT的NPVR功能。提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。
在阅读并理解了附图和详细描述后，可以明白其它方面。
附图说明
图1为本发明实施例一基于OTT的NPVR实现方法的流程示意图；
图2为本发明实施例二基于OTT的NPVR实现方法的流程示意图；
图3为本发明实施例二中申请/取消NPVR录制流程示意图；
图4为本发明实施例三基于OTT的NPVR实现方法流程示意图；
图5为本发明实施例四基于OTT的NPVR实现方法的流程示意图；
图6为本发明实施例四中销户清理NPVR流程示意图；
图7为本发明实施例五基于OTT的NPVR实现方法的流程示意图；
图8为本发明实施例六基于OTT的NPVR实现装置的功能模块示意图；
图9为本发明实施例六基于OTT的NPVR实现装置的功能模块示意图；
图10为本发明实施例六基于OTT的NPVR实现装置的功能模块示意图。
具体实施方式
下面结合附图和实施例对本申请的技术方案做详细的说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
在本发明实施例中，接收基于OTT的NPVR服务申请指令，确定是否存在对接OTT的局点；在存在对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点(CP，Control Point)与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。通过在存在对接OTT的局点时，配置支持OTT NPVR属性，且在CP与CDN之间配置新的接口，提供新的接口供OTT的NPVR消息接发，支持OTT的NPVR功能。有效避免目前针对日益发展的OTT(其主要应用场景为手机、PAD、PC等客户端的IPTV业务，包括播放，书签，时移，录制等)，业务局限较多，无法通过OTT完成NPVR业务的问题。提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。
实施例一
基于上述问题，本发明实施例提供一种基于OTT的NPVR实现方法。
图1为本发明实施例一的基于OTT的NPVR实现方法的流程示意图。如图1所示，所述基于OTT的NPVR实现方法包括：
步骤S10，接收基于OTT的NPVR服务申请指令，确定是否存在对接OTT的局点；
在本实施例中，触发OTT的NPVR服务申请指令的方式包括以下多种：1)通过终端上的物理按键触发，例如，连续按压某个物理按键2次之后触发；2)通过终端上的服务申请指令虚拟按键触发，例如，在终端的中心位置设置一个服务申请指令虚拟按键，通过触摸该虚拟按键来触发；3)在请求OTT的NPVR业务时，自动触发。以上所列举出的OTT的NPVR服务申请指令的触发方式仅仅为示例性的，本领域技术人员利用本申请的技术思想，根据其具体需求所提出的其它OTT的NPVR服务申请指令的触发方式均在本申请的保护区间内，在此不进行一一穷举。在基于OTT的NPVR服务申请指令触发后，接收基于OTT的NPVR服务申请指令，确定是否存在对接OTT的局点。
步骤S20，在存在对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
在本实施例中，在不存在对接OTT的局点时，例如，国内没有OTT的局点，使用默认值0，按照IPTV NPVR流程执行，不支持OTT NPVR；在存在OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，例如，配置为2，配置为2表示支持OTT NPVR功能，并兼容支持IPTV NPVR功能。在配置支持OTT NPVR属性后，在CP与CDN之间开发新的接口，支持OTT的NPVR消息的接发。通过配置支持OTT NPVR属性，在CP与CDN之间配置新的接口，IPTV用户可以登录RTSP(Real Time Streaming Protocol，实时传输协议)节点享用传统的IPTV基本业务和NPVR功能，OTT用户可以登录OTT节点享用新的OTT业务和OTT NPVR功能。除此之外，还有一些其他的配置项用于CDN和CP的对接，参考表1：
Figure PCTCN2016081763-appb-000001
Figure PCTCN2016081763-appb-000002
表1
参考表1，在IPTV业务对接OTT时，关于OTT NPVR需要完成的配置，包括同时对接2.0CDN和3.0CDN的配置。以上配置只涉及NPVR功能，实际上如果是OTT内容和频道的发布，还需要配置370接口相关配置。
上述技术方案通过在存在对接OTT的局点时，配置支持OTT NPVR属性，且在CP与CDN之间配置新的接口，提供新的接口供OTT的NPVR消息接发，支持OTT的NPVR功能。上述技术方案提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。
实施例二
图2为本发明实施例的基于OTT的NPVR实现方法的另一流程示意图。如图2所示，基于上述基于OTT的NPVR实现方法，所述步骤S20之后，所述方法还包括：
步骤S30，接收到NPVR录制请求后，更新NPVR记录；
步骤S40，保存更新后的NPVR记录及发起NPVR录制请求的IP(Internet Protocol，网络协议)地址；
步骤S50，在第一预设表格中扩展NPVR码、处理状态和所述IP地址。
在本实施例中，在用户需要NPVR服务时，即需要录制节目时，发出NPVR录制请求，在接收到NPVR录制请求后，更新NPVR记录，保存更新后的NPVR记录及用户发起NPVR录制请求的IP地址，在第一预设表格中扩展NPVR码、处理状态和所述IP地址。所述第一表格可以为s830_NPVR_record表格。
参考图3，以第一表格为s830_NPVR_record表格为例，用户可以通过 EPG(Electronic Program Guide，电子节目菜单)发起NPVR录制的录制(申请)请求或取消请求，通过相关接口通知CP更新NPVR记录。CP调用DB(Database，数据库)的存储过程，申请或取消NPVR录制。NPVR录制的业务流程保持不变，在保存NPVR记录时，保存用户发起NPVR操作(申请或取消)的IP地址，当sys_special_NPVR配置成2时(即OTT的NPVR)，处理逻辑如下：
在s830_NPVR_record表格中扩展NPVR码(NPVRCode)、处理状态(State)和用户IP地址(Userip)，其中，NPVRCode＝01(内容类型，当前固定为01)+userid(10位左补零)+recordid(10位左补零)。
举例来说：假设用户的userid为6，对应的recordid为187，则生成的NPVRCode为0100000000060000000187，该字段没有默认值，其他模式下也按照该规则生成；State表示NPVR的处理状态，State的不同值表示不同的处理状态：999表示用户预约；1表示预约成功；2表示录制成功；-1表示NPVR失败，该State字段默认为2。在用户发起NPVR申请时，将sys_special_NPVR配置成2时，该State字段为999，其他模式下直接置成2。需要说明的是，userid为s830_user表中的userid，而不是usercode，userid是发起NPVR操作的帐号ID；recordid为s830_record表中的recordid，而不是recordcode。
上述技术方案通过接收NPVR录制请求，更新NPVR记录，将处理过程的NPVR码、处理状态和IP地址保存在第一预设表格中，使得能及时通过所述第一预设表格查询或者自动完成业务流程，提高了NPVR业务执行的效率。
实施例三
图4为本发明实施例基于OTT的NPVR实现方法的流程示意图。如图4所示，基于上述基于OTT的NPVR实现方法，所述步骤S30之后，所述方法还包括：
步骤S60，在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或NPVR取消NPVR录制通知任务；
步骤S70，在接收到NPVR删除任务时，直接删除所述NPVR记录，并在所述第二预设表格中插入删除NPVR录制通知任务。
在本实施例中，所述第二预设表格可以为s830_task表。参考图3，对于更新的单集NPVR记录和普通NPVR记录，向s830_task表中插入请求NPVR录制通知任务或者插入取消NPVR录制通知任务，其中参数1：用户IP；参数2：用户ID；参数3：RecordCode；参数4：action(1表示新增NPVR；0表示删除NPVR)；参数5：NPVRCode；参数6：TVOD的结束时间(endtime)。对于NPVR删除任务，直接删除NPVR记录，并插入通知任务，不需要等CDN上报处理结果。
可选地，在本发明实施例中，所述第二预设表格中插入删除NPVR录制通知任务后，所述方法还包括：
扫描第二预设表格，将获取的通知任务发送至CDN；若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移至删除表中。
参考图3，CP定时扫描s830_task表，获取通知任务，将获取到的通知任务发送至CDN，如果申请NPVR录制操作的CDN接收失败或者CDN响应超时，则根据NPVRCode将对应NPVR记录移至删除表中，再通过定时任务清理删除表中的NPVR记录；如果申请NPVR录制操作的CDN接收成功，则根据NPVRCode将对应的NPVR记录状态置为1，表明预约成功，等待CDN处理结果。
本实施例中，CDN上报NPVR记录的处理结果，回调DB存储过程，处理逻辑如下：
如果action＝1(新增)，则CP根据NPVRCode回调DB存储过程进行处理，如果CDN上报失败，则根据NPVRCode将对应记录状态移到删除表中，再通过定时任务清理删除表中的NPVR记录；如果CDN上报成功，则根据NPVRCode将对应记录状态置成2。
在本实施例中，定时任务处理流程如下：
定时任务(例如，可以是5分钟或8分钟等，还可以是1天或一周等)检查state＝999or state＝1的NPVR记录，当对应TVOD已经超过保存有效期 时(s830_record表的validtime)，认为CDN处理超时，根据NPVRCode将对应记录状态移到删除表中，再通过定时任务清理删除表中的NPVR记录。定时任务(例如，可以是天任务或周任务或月任务等)清理删除表中状态为-1的定时任务。DB定时任务中，对于存在NPVR记录的TVOD，不允许老化。
上述技术方案通过在第二预设表格中插入请求NPVR录制通知任务或NPVR取消NPVR录制通知任务或删除通知任务，使得及时更新NPVR的处理状态，进而可以及时通过第二预设表格查询或者上报NPVR业务流程处理状态，提高NPVR业务处理效果。
实施例四
图5为本发明基于OTT的NPVR实现方法的第四实施例的流程示意图。如图5所示，基于上述基于OTT的NPVR实现方法，所述方法还包括：
步骤S80，在接收到销户请求后，清除该销户请求对应用户的NPVR记录，插入NPVR更新通知任务，以通知CDN所述用户已经销户。
在本实施例中，参考图6，用户在需要清除NPVR的业务用户时，发出销户请求，在接收到销户请求后，清除该销户请求对应用户的NPVR记录，插入NPVR更新通知任务，以通知CDN所述用户已经销户。
该用户销户后清理对应的NPVR记录，插入NPVR通知任务、定时任务或NPVR通知任务，以取消NPVR的录制，缓存NPVR任务，通过CDN上报处理结果，例如，是否成功销户，或销户失败等。
在本发明实施例中，所述步骤S80可以为执行在步骤S70之后，也还可以执行在步骤S10至步骤S70中的任意位置。
上述技术方案通过销户清除NPVR记录，使得销户用户的NPVR业务流程记录不再保存，保证用户安全及节省系统存储空间。
实施例五
图7为本发明实施例基于OTT的NPVR实现方法的流程示意图。如图7 所示，基于上述基于OTT的NPVR实现方法，所述方法还包括：
步骤S90，接收OTT的播放URL(Uniform Resoure Locator，统一资源定位器)参数插入请求，在所述OTT的播放URL中插入与所述播放URL参数插入请求对应的参数，以通过插入的参数统计用户的播放行为。
在本实施例中，在OTT的播放URL中增加的参数包括：columnid、programid、boid、contentid、cpcode、stbid、terminalflag、videoid，涉及OTT URL和参数取值含义如下：
http://RRAddress/CMSID/mediaservice/ContentID？AuthInfo＝xxx&version＝x xx&param1＝xxx&paramN＝xxx&virtualDomain＝CMSID.npvr_文件类型.zte.com&tvodcode＝xxx&programbegin＝xxx
&programend＝xxx&programid＝xxx&boid＝xxx&contentid＝xxx&stbid＝xxx&terminalflag＝xxx&videoid＝xxx
其中，ContentID是物理频道的physicalcontentid；programid是业务频道code，boid是登录帐号的运营商code，contentid是业务频道code，stbid是登录终端的设备ID，对于STB是stbid，对于其他终端是设备UUID(Universally Unique Identifier，通用唯一识别码)；terminalflag是登录终端的终端类型，videoid是录制计划代码(code)，即recordcode。
在本发明实施例中，所述步骤S90可以为执行在步骤S80之后，也还可以执行在步骤S10至步骤S80中的任意位置。
本实施例通过在OTT播放URL中增加一些参数，可以及时统计到用户的播放行为，使得基于OTT的NPVR业务更佳合理。
上述实施例一至实施例五的基于OTT的NPVR实现方法的执行主体均可以为终端。该基于OTT的NPVR实现方法可以由安装终端上的客户端基于OTT的NPVR实现程序实现，其中，该终端包括但不限于手机、pad、笔记本电脑等。
实施例六
本发明实施例提供一种基于OTT的NPVR实现装置。
参照图8，图8为本发明实施例基于OTT的NPVR实现装置的功能模块示意图。，所述基于OTT的NPVR实现装置包括：接收模块10、确定模块20及配置模块30。
接收模块10，设置为接收基于OTT的NPVR服务申请指令；
确定模块20，设置为接收到所述基于OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；
在本实施例中，触发OTT的NPVR服务申请指令的方式包括以下多种：1)通过终端上的物理按键触发，例如，连续按压某个物理按键2次之后触发；2)通过终端上的服务申请指令虚拟按键触发，例如，在终端的中心位置设置一个服务申请指令虚拟按键，通过触摸该虚拟按键来触发；3)在请求OTT的NPVR业务时，自动触发。以上所列举出的OTT的NPVR服务申请指令的触发方式仅仅为示例性的，本领域技术人员利用本申请的技术思想，根据其具体需求所提出的其它OTT的NPVR服务申请指令的触发方式均在本申请的保护区间内，在此不进行一一穷举。在基于OTT的NPVR服务申请指令触发后，接收基于OTT的NPVR服务申请指令，确定是否存在对接OTT的局点。
配置模块30，设置为在存在对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
参考表1，在本实施例中，在不存在对接OTT的局点时，例如，国内没有OTT的局点，使用默认值0，按照IPTV NPVR流程执行，不支持OTT NPVR；在存在OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，例如，配置为2，配置为2表示支持OTT NPVR功能，并兼容支持IPTV NPVR功能。在配置支持OTT NPVR属性后，在CP与CDN之间开发新的接口，支持OTT的NPVR消息的接发。通过配置支持OTT NPVR属性，在CP与CDN之间配置新的接口，IPTV用户可以登录RTSP(Real Time Streaming Protocol，实时传输协议)节点享用传统的IPTV基本业务和NPVR功能，OTT用户可以登录OTT节点享用新的OTT业务和OTT NPVR功能。除此之外，还有一些其他的配置项用于CDN和CP的对接。在IPTV业务对接OTT时，关于OTT  NPVR需要完成的配置，包括同时对接2.0CDN和3.0CDN的配置。以上配置只涉及NPVR功能，实际上如果是OTT内容和频道的发布，还需要配置370接口相关配置。
上述技术方案通过在存在对接OTT的局点时，配置支持OTT NPVR属性，且在CP与CDN之间配置新的接口，提供新的接口供OTT的NPVR消息接发，支持OTT的NPVR功能。提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。
可选地，如图9所示，所述基于OTT的NPVR实现装置还包括更新模块40、保存模块50和扩展模块60。
所述接收模块10，还设置为接收NPVR录制请求；
所述更新模块40，设置为接收到NPVR录制请求后，更新NPVR记录；
所述保存模块50，设置为保存更新后的NPVR记录及用户发起NPVR录制请求的IP地址；
所述扩展模块60，设置为在第一预设表格中扩展NPVR码，处理状态和所述IP地址。
在本实施例中，在用户需要NPVR服务时，即需要录制节目时，发出NPVR录制请求，在接收到NPVR录制请求后，更新NPVR记录，保存更新后的NPVR记录及用户发起NPVR录制请求的IP地址，在第一预设表格中扩展NPVR码、处理状态和所述IP地址。所述第一表格可以为s830_NPVR_record表格。
参考图3，以第一表格为s830_NPVR_record表格为例，用户可以通过EPG(Electronic Program Guide，电子节目菜单)发起NPVR录制的录制(申请)请求或取消请求，通过相关接口通知CP更新NPVR记录。CP调用DB(Database，数据库)的存储过程，申请或取消NPVR录制。NPVR录制的业务流程保持不变，在保存NPVR记录时，保存用户发起NPVR操作(申请或取消)的IP地址，当sys_special_NPVR配置成2时(即OTT的NPVR)，处理逻辑如下：
在s830_NPVR_record表格中扩展NPVR码(NPVRCode)、处理状态(State)和用户IP地址(Userip)，其中，NPVRCode＝01(内容类型，当前固定为01)+userid(10位左补零)+recordid(10位左补零)。
举例来说：假设用户的userid为6，对应的recordid为187，则生成的NPVRCode为0100000000060000000187，该字段没有默认值，其他模式下也按照该规则生成；State表示NPVR的处理状态，State的不同值表示不同的处理状态：999表示用户预约；1表示预约成功；2表示录制成功；-1表示NPVR失败，该State字段默认为2。在用户发起NPVR申请时，将sys_special_NPVR配置成2时，该State字段为999，其他模式下直接置成2。需要说明的是，userid为s830_user表中的userid，而不是usercode，userid是发起NPVR操作的帐号ID；recordid为s830_record表中的recordid，而不是recordcode。
上述技术方案通过接收NPVR录制请求，更新NPVR记录，将处理处理过程的NPVR码、处理状态和IP地址保存在第一预设表格中，使得能及时通过所述第一预设表格查询或者自动完成业务流程，提高了NPVR业务执行的效率。
可选地，如图10所示，所述基于OTT的NPVR实现装置还包括删除模块70。
所述扩展模块60，还设置为在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或NPVR取消NPVR录制通知任务；还设置为在所述第二预设表格中插入删除NPVR录制通知任务；
所述删除模块70，设置为在接收到NPVR删除任务时，直接删除所述NPVR记录。
在本实施例中，所述第二预设表格可以为s830_task表。参考图3，对于更新的单集NPVR记录和普通NPVR记录，向s830_task表中插入请求NPVR录制通知任务或者插入取消NPVR录制通知任务，其中参数1：用户IP；参数2：用户ID；参数3：RecordCode；参数4：action(1：新增；0：删除)；参数5：NPVRCode；参数6：TVOD的结束时间(endtime)。对于NPVR删除任务，直接删除NPVR记录，并插入通知任务，不需要等CDN上报处理 结果。
可选地，所述装置还包括：
获取模块80，设置为扫描第二预设表格，将获取的通知任务发送至CDN；
处理模块90，设置为若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移至删除表中。
参考图3，CP定时扫描s830_task表，获取通知任务，将获取到的通知任务发送至CDN，如果申请NPVR录制操作的CDN接收失败或者CDN响应超时，则根据NPVRCode将对应NPVR记录移至删除表中，再通过定时任务清理删除表中的NPVR记录，否则根据NPVRCode将对应的NPVR记录状态置为1，表明预约成功，等待CDN处理结果。
本实施例中，CDN上报NPVR记录的处理结果，回调DB存储过程，处理逻辑如下：
如果action＝1(新增)，则CP根据NPVRCode回调DB存储过程进行处理，如果CDN上报失败，则根据NPVRCode将对应记录状态移到删除表中，再通过定时任务清理删除表中的NPVR记录；如果CDN上报成功，则根据NPVRCode将对应记录状态置成2。
在本实施例中，定时任务处理流程如下：
定时任务(5分钟或8分钟等，还可以是1天或一周等)检查state＝999or state＝1的NPVR记录，当对应TVOD已经超过保存有效期时(s830_record表的validtime)，认为CDN处理超时，根据NPVRCode将对应记录状态移到删除表中，再通过定时任务清理删除表中的NPVR记录。定时任务(天任务或周任务或月任务等)清理删除表中状态为-1的定时任务。DB定时任务中，对于存在NPVR记录的TVOD，不允许老化。
上述技术方案通过在第二预设表格中插入请求NPVR录制通知任务或NPVR取消NPVR录制通知任务或删除通知任务，使得及时更新NPVR的处理状态，进而可以及时通过第二预设表格查询或者上报NPVR业务流程处理状态，提高NPVR业务处理效果。
可选地，所述处理模块90，还设置为在接收到销户请求后，清除该销户请求对应用户的NPVR记录；
所述扩展模块60，还设置为插入NPVR更新通知任务，以通知CDN所述用户已经销户。
在本实施例中，参考图6，用户在需要清除NPVR的业务用户时，发出销户请求，在接收到销户请求后，清除该销户请求对应用户的NPVR记录，插入NPVR更新通知任务，以通知CDN所述用户已经销户。
该用户销户后清理对应的NPVR记录，插入NPVR通知任务、定时任务或NPVR通知任务，取消NPVR的录制，缓存NPVR任务，通过CDN上报处理结果，例如，是否成功销户，或销户失败等。
上述技术方案通过销户清除NPVR记录，使得销户用户的NPVR业务流程记录不再保存，保证用户安全及节省系统存储空间。
可选地，所述接收模块10，还设置为接收OTT的播放URL参数插入请求；
所述扩展模块60，还设置为在所述OTT的播放URL中插入与所述播放URL插入请求对应的参数，以通过插入的参数统计用户的播放行为。
在本实施例中，在OTT的播放URL中增加的参数包括：columnid、programid、boid、contentid、cpcode、stbid、terminalflag、videoid，涉及OTT URL和参数取值含义如下：
http://RRAddress/CMSID/mediaservice/ContentID？AuthInfo＝xxx&version＝x xx&param1＝xxx&paramN＝xxx&virtualDomain＝CMSID.npvr_文件类型.zte.com&tvodcode＝xxx&programbegin＝xxx
&programend＝xxx&programid＝xxx&boid＝xxx&contentid＝xxx&stbid＝xxx&terminalflag＝xxx&videoid＝xxx
其中，ContentID是物理频道的physicalcontentid；programid是业务频道code，boid是登录帐号的运营商code，contentid是业务频道code，stbid是登 录终端的设备ID，对于STB是stbid，对于其他终端是设备UUID(Universally Unique Identifier，通用唯一识别码)；terminalflag是登录终端的终端类型，videoid是录制计划代码(code)，即recordcode。
上述技术方案通过在OTT播放URL中增加一些参数，可以及时统计到用户的播放行为，使得基于OTT的NPVR业务更佳合理。
基于上述基于OTT的NPVR实现装置，本发明实施例还提出一种终端，所述终端包括处理器，所述处理器设置为接收基于OTT的NPVR服务申请指令，确定是否存在对接OTT的局点；在存在对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在CP与CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。所述终端包括但不限于手机、pad、笔记本电脑等。本实施例通过在存在对接OTT的局点时，配置支持OTT NPVR属性，且在CP与CDN之间配置新的接口，提供新的接口供OTT的NPVR消息接发，支持OTT的NPVR功能。提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被执行时实现基于OTT的网络录制服务NPVR实现方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的 结合。本领域的普通技术人员应当理解，可以对本申请的技术方案进行修改或者等同替换，而不脱离本申请技术方案的精神和范围，均应涵盖在本申请的权利要求范围当中。
工业实用性
上述技术方案提出一种支持OTT的NPVR功能，实现基于OTT的NPVR业务，使得NPVR业务不再受到局限，进而提高NPVR业务的适用性。

Claims (12)

  1. 一种基于OTT的网络录制服务NPVR实现方法，包括：
    接收到基于OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；
    在存在所述对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
  2. 如权利要求1所述的基于OTT的NPVR实现方法，所述在控制点CP与内容分发网络CDN之间配置新的接口的步骤之后，所述方法还包括：
    接收到NPVR录制请求后，更新NPVR记录；
    保存更新后的NPVR记录及发起所述NPVR录制请求的网络协议IP地址；
    在第一预设表格中扩展NPVR码、处理状态和所述IP地址。
  3. 如权利要求2所述的基于OTT的NPVR实现方法，所述接收到NPVR录制请求后，更新NPVR记录的步骤之后，所述方法还包括：
    在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或取消NPVR录制通知任务；
    在接收到NPVR删除任务时，直接删除所述NPVR记录，并在所述第二预设表格中插入删除NPVR录制通知任务。
  4. 如权利要求3所述的基于OTT的NPVR实现方法，所述在所述第二预设表格中插入删除NPVR录制通知任务的步骤之后，所述方法还包括：
    扫描所述第二预设表格，将获取的通知任务发送至CDN；
    若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移至删除表中。
  5. 如权利要求1至4任一项所述的基于OTT的NPVR实现方法，所述方法还包括：
    在接收到销户请求后，清除该销户请求对应用户的NPVR记录；
    插入NPVR更新通知任务，以通知CDN所述用户已经销户。
  6. 如权利要求1至4任一项所述的基于OTT的NPVR实现方法，所述方法还包括：
    接收OTT的播放URL参数插入请求，在所述OTT的播放URL中插入与所述播放URL参数插入请求对应的参数，以通过插入的参数统计用户的播放行为。
  7. 一种基于OTT的网络录制服务NPVR实现装置，包括：
    接收模块，设置为接收基于OTT的NPVR服务申请指令；
    确定模块，设置为：在所述接收模块接收到所述基于OTT的NPVR服务申请指令后，确定是否存在对接OTT的局点；
    配置模块，设置为在存在所述对接OTT的局点时，将NPVR的属性配置为支持OTT NPVR属性，在控制点CP与内容分发网络CDN之间配置新的接口，以通过所述新的接口完成OTT的NPVR消息接发。
  8. 如权利要求7所述的基于OTT的NPVR实现装置，所述装置还包括：更新模块、保存模块和扩展模块；
    所述接收模块，还设置为接收NPVR录制请求；
    所述更新模块，设置为：所述接收模块接收到NPVR录制请求后，更新NPVR记录；
    所述保存模块，设置为保存更新后的NPVR记录及用户发起NPVR录制请求的网络协议IP地址；
    所述扩展模块，设置为在第一预设表格中扩展NPVR码、处理状态和所述IP地址。
  9. 如权利要求8所述的基于OTT的NPVR实现装置，所述装置还包括删除模块；
    所述扩展模块，还设置为在所述NPVR记录为单集NPVR记录或普通NPVR记录时，在第二预设表格中插入请求NPVR录制通知任务或取消NPVR录制通知任务；还设置为在所述第二预设表格中插入删除NPVR录制通知任务；
    所述删除模块，设置为在接收到NPVR删除任务时，直接删除所述NPVR记录。
  10. 如权利要求9所述的基于OTT的NPVR实现装置，所述装置还包括获取模块和处理模块；
    所述获取模块，设置为扫描第二预设表格，将获取的通知任务发送至CDN；
    所述处理模块，设置为若CDN接收失败或响应超时，则根据NPVR码将对应的NPVR记录移至删除表中。
  11. 如权利要求10所述的基于OTT的NPVR实现装置，其中，
    所述处理模块，还设置为在接收到销户请求后，清除该销户请求对应用户的NPVR记录；
    所述扩展模块，还设置为插入NPVR更新通知任务，以通知CDN所述用户已经销户。
  12. 如权利要求8至11任一项所述的基于OTT的NPVR实现装置，其中，
    所述接收模块，还设置为接收OTT的播放URL参数插入请求；
    所述扩展模块，还设置为在所述OTT的播放URL中插入与所述播放URL参数插入请求对应的参数，以通过插入的参数统计用户的播放行为。
PCT/CN2016/081763 2015-07-29 2016-05-11 基于ott的npvr实现方法及装置 WO2017016276A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510456738.3A CN106658152B (zh) 2015-07-29 2015-07-29 基于ott的npvr实现方法及装置
CN201510456738.3 2015-07-29

Publications (1)

Publication Number Publication Date
WO2017016276A1 true WO2017016276A1 (zh) 2017-02-02

Family

ID=57884088

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081763 WO2017016276A1 (zh) 2015-07-29 2016-05-11 基于ott的npvr实现方法及装置

Country Status (2)

Country Link
CN (1) CN106658152B (zh)
WO (1) WO2017016276A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101849415A (zh) * 2007-09-06 2010-09-29 诺基亚西门子通信公司 电视分发系统的负载控制
US20140230003A1 (en) * 2013-02-12 2014-08-14 Azuki Systems, Inc. Content processing for personal over-the-top network video recorder
US20140337909A1 (en) * 2013-05-07 2014-11-13 Ericsson Television Inc. Network personal video recorder system, method and associated subscriber device
US20140337901A1 (en) * 2013-05-07 2014-11-13 Ericsson Television Inc. Network personal video recorder system, method and associated subscriber device
CN104363507A (zh) * 2014-10-23 2015-02-18 百视通网络电视技术发展有限责任公司 一种基于ott机顶盒的视音频录制及分享方法及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7610606B2 (en) * 2002-05-03 2009-10-27 Time Warner Cable, Inc. Technique for effectively providing various entertainment services through a communications network
CN101741498A (zh) * 2008-11-04 2010-06-16 中兴通讯股份有限公司 一种iptv系统中管理npvr的方法
CN103079095A (zh) * 2011-10-25 2013-05-01 深圳市龙视传媒有限公司 nPVR的智能录制方法及系统
CN102833579B (zh) * 2012-08-09 2016-08-31 山东智慧生活数据系统有限公司 一种网络个人录像业务实现的方法及装置
US9699485B2 (en) * 2012-08-31 2017-07-04 Facebook, Inc. Sharing television and video programming through social networking
US20140074961A1 (en) * 2012-09-12 2014-03-13 Futurewei Technologies, Inc. Efficiently Delivering Time-Shifted Media Content via Content Delivery Networks (CDNs)
CN104506923B (zh) * 2014-12-31 2017-11-28 华为技术有限公司 一种多媒体处理装置、多媒体处理服务器及其方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101849415A (zh) * 2007-09-06 2010-09-29 诺基亚西门子通信公司 电视分发系统的负载控制
US20140230003A1 (en) * 2013-02-12 2014-08-14 Azuki Systems, Inc. Content processing for personal over-the-top network video recorder
US20140337909A1 (en) * 2013-05-07 2014-11-13 Ericsson Television Inc. Network personal video recorder system, method and associated subscriber device
US20140337901A1 (en) * 2013-05-07 2014-11-13 Ericsson Television Inc. Network personal video recorder system, method and associated subscriber device
CN104363507A (zh) * 2014-10-23 2015-02-18 百视通网络电视技术发展有限责任公司 一种基于ott机顶盒的视音频录制及分享方法及系统

Also Published As

Publication number Publication date
CN106658152A (zh) 2017-05-10
CN106658152B (zh) 2020-06-02

Similar Documents

Publication Publication Date Title
WO2015096648A1 (zh) 智能电视中的视频分享方法及系统
US8490126B2 (en) System and method of restricting access to video content
US8045700B2 (en) System and method of providing voice communication
US8494520B2 (en) Systems and methods for providing centralized subscriber session state information
US9602656B2 (en) Method, apparatus and system for providing caller identification
CN108566561B (zh) 视频播放方法、装置及存储介质
US10034057B2 (en) Message processing method, device, gateway, STB and IPTV
US20120210356A1 (en) Image Sampling from Multicast Streams
US11108727B2 (en) System, method, and server for playing multimedia resource
CN103248939A (zh) 一种实现多屏同步显示的方法及系统
KR101774983B1 (ko) Ott 비디오의 품질을 모니터링하는 방법, 장치, 및 시스템
KR20120026006A (ko) 계승 통신 관리 장치 및 계승 통신 관리 방법
WO2007047102A2 (en) System and method of delivering video data
CN106998485B (zh) 视频直播方法及装置
WO2016127799A1 (zh) 一种视频广告过滤的方法、装置和系统
JP2006246434A (ja) コンテンツ配信方法及び中継装置
WO2020048386A1 (zh) 交互信息传输方法及装置
WO2011097991A1 (zh) 三屏融合中基于交互式网络电视的实现方法及系统
US20130151638A1 (en) Method, apparatus, and system for transferring file to user of instant message system
CN113630574A (zh) 视频通话方法及终端设备
CN104754384A (zh) 基于智能路由器播放视频的方法及装置
US20160294903A1 (en) Method and device for pushing resources to mobile communication terminal by smart television
WO2018014683A1 (zh) 一种可视通信管理方法及装置
CN104363507A (zh) 一种基于ott机顶盒的视音频录制及分享方法及系统
KR101290977B1 (ko) 푸쉬 서버를 이용한 메시지 전송 방법 및 그 시스템

Legal Events

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

Ref document number: 16829643

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

Country of ref document: EP

Kind code of ref document: A1