WO2014131270A1

WO2014131270A1 - Method and system for sharing usage record of over-the-top (ott) tv

Info

Publication number: WO2014131270A1
Application number: PCT/CN2013/082008
Authority: WO
Inventors: 尤许; 陶长标
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-03-01
Filing date: 2013-08-21
Publication date: 2014-09-04
Also published as: CN104023252A; CN104023252B

Abstract

Disclosed are a method and a system for sharing a usage record of an over-the-top (OTT) TV. The method comprises: an EPG server receiving a usage record updating request sent by a first terminal, of a current user, and forwarding the usage record updating request to an SLP server; the SLP server updating usage record data of the current user according to the usage record updating request; the EPG server receiving a usage record visit request sent by a second terminal, of the current user, and forwarding the usage record visit request to the SLP server; and the SLP server querying, according to the usage data visit request, in the usage record data of the current user for usage record data whose sharing status is "shared by the current user" and usage record data whose sharing status is "private data of the second terminal", and sending the data to the EPG server, and the EPG server forwarding the data to the second terminal. By means of the present invention, personal privacy can be protected and sharing is more flexible, the impact on performance of a service processing server and a database is avoided, and the efficiency of data processing of a system is significantly improved.

Description

TECHNICAL FIELD The present invention relates to the field of network television technologies, and in particular, to a οττ Internet television usage record sharing method and system. Background technique

OTT (Over The Top) TV refers to an open Internet-based video service, which is a service that integrates IP video and Internet applications transmitted over a public Internet to networked devices (television, PC, mobile terminals). OTT TV distributes video and audio streams to TV terminals, PCs and mobile terminals via the Internet. However, unlike traditional IPTV Internet video and audio technologies, operators do not need to build a dedicated network for OTT TVs. The network or mobile network provides services to users. The existing technologies for supporting OTT services are very mature. The terminals of OTT services are no longer limited to access only in the home network, but also support access through the mobile Internet and the Internet, so that users can use them on different terminals. OTT business. In order to ensure the continuity of the service of the user on different terminals, the user data between the OTT terminals is required to be shared. At present, the traditional data sharing mode of the OTT is limited to the user data between the terminals of the home network, including the progress of the program, the collection information of the program channel, etc., usually according to the system level configuration, or according to the user level configuration setting sharing, this sharing mode Only system-level or user-level data sharing can be realized. Data sharing for each transaction level of the user cannot be achieved. The sharing granularity is too rough to meet the increasing user personalized requirements, and it is difficult to adapt to the dynamic adaptation of OTT technology. The need for flexible sharing. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a OTT Internet TV usage record sharing method and system that can share data for each business record level of a user. The present invention provides a OTT Internet TV usage record sharing method, comprising the steps of: Step A: An EPG (Electronic Programmer Guide) server receives a current user usage record update request sent by the first terminal, and forwards it to the SLP (Service) a Logic Point (Service Logic Control Point) server; the usage record update request carries a current status of the current usage record data of the current user and the current use record data; Step B, the SLP server is used according to the use Record update request, update the SLP The usage record data of the current user stored in the server; Step C, the EPG server receives the usage record access request of the current user sent by the second terminal, and forwards the request to the SLP server; Step D, the SLP server according to the Using the record access request, querying the usage record data shared by the current user and the usage record data shared by the current terminal in the current user's usage record data, and transmitting the usage record data to the EPG server, by the EPG server. Forwarding to the second terminal. Preferably, the step B specifically includes: Step B01, the SLP server acquires, according to the account of the current user carried in the usage record update request, an update time of the current user usage record data stored in the database to the database. Step B02, the SLP server determines whether the update timestamp of the usage record data of the current user stored in the SLP server is consistent with the update timestamp of the usage record data of the current user stored in the database; if not, Then, step B03 is performed; if yes, step B04 is performed; step B03, the SLP server acquires usage record data of the current user stored in the database, and updates usage record data of the current user stored in the SLP server, and Updating the update time stamp of the usage record data of the current user stored in the SLP server to be consistent with the update time stamp of the usage record data of the current user stored in the database, and performing step B04; Step B04, the SLP server According to the current record of the current user carried in the use record update request Updating the usage history data of the current user stored in the SLP server, and updating the time stamp of the usage history data of the current user stored in the SLP server, using the shared state of the record data and the current use record data Update to current time. Preferably, after the step B04, the method further includes: Step B05, the SLP server caches the updated current user usage record data as incremental data; Step B06, when the synchronization time arrives or the number of the incremental data When greater than or equal to the update threshold, the SLP server synchronizes the delta data to the database. Preferably, after the step B04, the method further includes: Step B07, the SLP server uses, according to the current user account carried in the usage record update request and the device identifier of the first terminal, the updated current user usage. The usage record data in the record data is the usage record data shared by the current user and the usage record data shared by the first terminal is fed back to the EPG server, and is forwarded by the EPG server to the first terminal. Preferably, the step D specifically includes: Step D01, the SLP server acquires, according to the account of the current user carried in the use record access request, an update time of the current user's usage record data stored in the database to the database. Step S102, the SLP server determines whether the update timestamp of the usage record data of the current user stored in the SLP server is consistent with the update timestamp of the usage record data of the current user stored in the database; if not, Then, step D03 is performed; if yes, step D04 is performed; step D03, the SLP server acquires usage record data of the current user stored in the database, and updates usage record data of the current user stored in the SLP server, and The current use stored in the SLP server The update timestamp of the usage record data of the user is updated to be consistent with the update timestamp of the usage record data of the current user stored in the database, and step D04 is performed; Step D04, the SLP server carries the access request according to the usage record. The account of the current user and the device identifier of the second terminal are used to query the usage history data shared by the current user and the usage history data shared by the second terminal in the usage record data of the current user. And sent to the EPG server, and forwarded by the EPG server to the second terminal. The present invention also provides an OTT Internet TV usage record sharing system, including an EPG server and an SLP server: the EPG server is configured to receive a current user usage record update request sent by the first terminal, and forward the request to the SLP server; Using the record update request to carry the current use record data of the current user and the share status of the current use record data; receiving a use record access request of the current user sent by the second terminal, and forwarding the request to the SLP server; The usage status of the SLP server is forwarded to the second terminal by using the usage record data shared by the current user and the usage record data shared by the second terminal; the SLP server is configured to update the request according to the usage record Updating the usage record data of the current user stored in the SLP server; querying the usage history data shared by the current user and the sharing status as the second terminal in the current user usage record data according to the usage record access request Private use of recorded data, and sent The EPG server. Preferably, the SLP server is specifically configured to: obtain an update timestamp of the usage record data of the current user stored in the database according to the account of the current user carried in the usage record update request; and determine the SLP Whether the update timestamp of the usage record data of the current user stored in the server is consistent with the update timestamp of the usage record data of the current user stored in the database; when the update timestamps are inconsistent, the current user stored in the database is acquired. Using the record data, updating the usage record data of the current user stored in the SLP server, and updating the update time stamp of the current user's usage record data stored in the SLP server to the current user stored in the database The update timestamp of the usage record data is consistent; when the update timestamps are consistent, the update status is updated according to the current use record data of the current user and the share state of the current use record data carried in the use record update request The current user's usage record stored in the SLP server Recording data, and updating the update time stamp of the current user's usage record data stored in the SLP server to the current time. Preferably, the SLP server is further configured to: cache the updated usage history data of the current user as incremental data; when the synchronization time arrives or the number of the incremental data is greater than or equal to the update threshold, The SLP server synchronizes the delta data to the database. Preferably, the SLP server is further configured to query the sharing status in the updated usage data of the current user according to the current user account and the device identifier of the first terminal carried in the usage record update request. The usage record data and the shared state shared by the current user are the use record data private to the first terminal, and are fed back to the EPG server. The EPG server is further configured to: the shared state fed back by the SLP server is the current user. The shared usage record data and the usage status are forwarded to the first terminal by the first terminal private usage record data. Preferably, the SLP server is further configured to: obtain an update timestamp of the usage record data of the current user stored in the database from the database according to the account of the current user carried in the use record access request; Whether the update timestamp of the usage record data of the current user stored in the SLP server is consistent with the update timestamp of the usage record data of the current user stored in the database; when the update timestamps are inconsistent, acquiring the current stored in the database Updating the usage record data of the current user stored in the SLP server by using the record data of the user, and updating the update time stamp of the usage record data of the current user stored in the SLP server to be current with the current stored in the database The update timestamp of the user's usage record data is consistent; when the update timestamps are consistent, according to the current user's account number carried in the use record access request and the device identifier of the second terminal, the updated current user's use Record the shared status of the query in the data as the current user Shared data and shared use of the recording state to the second terminal using a private record data, and sends it to the EPG server. The invention separately processes according to the sharing state set by each user using the record data, which protects the personal privacy of each user on the one hand, and makes the sharing more flexible on the other hand, and updates the data in real time only when the user initiates the request. And using the SLP server as a cache module for recording data, the use of recorded data is not directly stored in the database, as much as possible to reduce the SLP server and the database to synchronize the full amount of user data, to avoid impact on the business processing server and database performance, in mass In the case of user data, the efficiency of processing data by the system can be greatly improved. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a flowchart of a first embodiment of a method for recording and sharing OTT Internet TV according to the present invention; FIG. 2 is a flowchart of a second embodiment of a method for recording and sharing OTT Internet TV according to the present invention; FIG. 4 is a flowchart of a fourth embodiment of a OTT Internet TV usage record sharing method according to the present invention; FIG. 5 is a flowchart of a OTT Internet TV usage record sharing method according to the present invention; a flowchart of the fifth embodiment; FIG. 6 is a schematic structural diagram of a first embodiment of a OTT Internet TV usage record sharing system according to the present invention. The implementation, functional features, and advantages of the present invention will be further described with reference to the accompanying drawings. The specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. As shown in FIG. 1, FIG. 1 is a flowchart of a first embodiment of a method for recording and sharing OTT Internet TV according to the present invention. The OTT Internet TV usage record sharing method mentioned in this embodiment includes the following steps: Step A: The EPG server receives the current user usage record update request sent by the first terminal, and forwards the request to the SLP server. The first terminal is a set top box, a PC or a mobile terminal. The current user may input the current user's account at the first terminal to log in to the OTT TV service, and the first terminal initiates an update request. The usage update record carries the current usage history data of the current user and the sharing status of the current usage record data, and the sharing status can be distinguished by setting the sharing identifier. For example, when the sharing identifier is 0, it means not sharing, as the first Private data of a terminal, only the current user enters the current user account to log in on the first terminal, and can access the private data. If the current user logs in through other terminals, even if the same current user account or the current user account is input. The associated account cannot access the private data. When the share identifier is 1, it indicates sharing. As the shared data of the current user, the current user enters the current user account or the account associated with the current user account on any terminal. You can access these private data by logging in. Step B: The SLP server updates the usage record data of the current user stored in the SLP server according to the usage record update request. The current update record data of the current user is carried in the record update request, and the SLP server updates the original data by using the current use record data of the current user. In this embodiment, the data is updated in real time only when the user initiates the request, and the SLP server is used as the cache module for using the recorded data, and the used record data is not directly stored in the database, thereby minimizing the synchronization of the SLP server and the database with the full amount of user data. Avoid impact on the performance of the business processing server and database, in the case of massive user data, can greatly improve the efficiency of the system processing data. Step C: The EPG server receives the current user usage record access request sent by the second terminal, and forwards the request to the SLP server. The second terminal is a set top box, a PC or a mobile terminal. The usage record access request may include an account of the current user, a device identifier of the second terminal, and the like. Step D: The SLP server queries, according to the usage record access request, the usage record data in the current user's usage record data that is shared by the current user and the usage record data shared by the second terminal, and sent to the EPG server, and sent to the EPG server. The EPG server forwards to the second terminal.

After receiving the record access request, the SLP server searches the SLP server for the current user's usage record data according to the current user's account, and searches for the shared state as the data shared by the current user according to the shared identifier, and the shared data can be sent to one. The terminal device searches for the data shared by the second terminal according to the shared identifier and the device identifier, and the private data can only be sent to the terminal device corresponding to the private data. For example, the current user views a certain video file through the first terminal at 9:00 this morning, the video plays to 20%, the current user sends a usage record update request via the first terminal, and marks the usage record of 9:00 this morning as sharing, SLP The server saves the update record; the current user re-accesses the video file through the first terminal at 2 pm today, and the SLP server notifies the first terminal, the first terminal, that the video has been played to 20% of the usage record data according to the updated data. The video starts playing from 20%, the video plays to 60%, the current user sends a usage record update request via the first terminal, and marks the usage record at 2 pm today as private, and the SLP server saves the update record; the current user is today The video file is re-accessed by the second terminal at 8:00 pm, and the SLP server does not have the first terminal private because the data updated in the afternoon is updated according to the updated data. Therefore, the SLP server still plays the video to 20% according to the data updated in the morning. Using the recorded data to inform the second terminal that the second terminal starts playing the game from 20% Frequency. This embodiment performs separate processing according to the sharing state set by each user using the record data, which protects the personal privacy of each user, and on the other hand makes the sharing more flexible. As shown in FIG. 2, FIG. 2 is a flowchart of a second embodiment of a method for recording and sharing OTT Internet TV according to the present invention. This embodiment is based on the embodiment shown in FIG. 1 and is described in detail in step B. Step B specifically includes: Step B01: The SLP server obtains the current stored in the database from the database according to the account of the current user carried in the record update request. The update timestamp of the user's usage record data. In order to avoid updating to useless data when the data is updated, it should be ensured that the data stored on the SLP server is the latest data. When receiving the update request of the terminal device, the SLP server needs to compare with the data stored in the database to determine whether it is a database. The latest data stored in the method can be judged by comparing the timestamps, that is, whether the data stored on the SLP server is the same as the update time marked by the data stored in the database. Step B02, the SLP server determines whether the update timestamp of the usage record data of the current user stored in the SLP server is consistent with the update timestamp of the usage record data of the current user stored in the database; if not, executing step B03; if yes, Then step B04 is performed. Step B03, the SLP server acquires the usage record data of the current user stored in the database, updates the usage record data of the current user stored in the SLP server, and updates the update time stamp of the current user usage record data stored in the SLP server to The update timestamp of the usage record data of the current user stored in the database is consistent, and step B04 is performed. When the update timestamp of the data in the SLP server is inconsistent with the update timestamp of the data in the database, it indicates that the data stored in the SLP server is not the latest data, and the latest data should be downloaded from the database to update the data in the SLP server to avoid Update to useless data as the data is updated. Since the SLP server accesses the database only when the user initiates the request, and when the data is inconsistent, the SLP server downloads the data from the database, thereby reducing the number of data transmissions between the SLP server and the database as much as possible. Avoid impact on the performance of the business processing server and database, in the case of massive user data, can greatly improve the efficiency of the system processing data. Step B04, the SLP server updates the usage record data of the current user stored in the SLP server according to the current usage record data of the current user and the sharing status of the current usage record data carried in the usage record update request, and stores the usage record data of the current user in the SLP server. The update timestamp of the current user's usage record data is updated to the current time. In this embodiment, when the update timestamp of the data in the SLP server is consistent with the update timestamp of the data in the database, it means that the data stored in the SLP server is the same as the data stored in the database, and is the latest data. When the data is updated, the latest data can be updated to facilitate data updates. As shown in FIG. 3, FIG. 3 is a flowchart of a third embodiment of a method for recording and sharing OTT Internet TV according to the present invention. The embodiment is based on the embodiment shown in FIG. 2. After step B04, the method further includes: Step B05: The SLP server caches the updated current user usage record data as incremental data. In step B06, when the synchronization time arrives or the number of pieces of incremental data is greater than or equal to the update threshold, the SLP server synchronizes the incremental data to the database.

The SLP server does not update the data in the database immediately after the data update, but caches the data to be updated to reduce the number of accesses to the database, and minimizes the STP server and the database to synchronize the full amount of user data, alleviating the Traffic pressure, to avoid impact on business processing server and database performance, in the case of massive user data, can greatly improve the efficiency of the system processing data. As shown in FIG. 4, FIG. 4 is a flowchart of a fourth embodiment of a method for recording and sharing OTT Internet TV according to the present invention. This embodiment is based on the embodiment shown in FIG. 2, and further includes after step B04: Step B07: The SLP server queries, according to the account of the current user and the device identifier of the first terminal carried in the use record update request, the usage history data shared by the current user in the used usage record data of the current user. Recording data for the private use of the first terminal is fed back to the EPG server and forwarded by the EPG server to the first terminal. After the data update is completed, the SLP server feeds back the update result to the first terminal, and informs the first terminal of the current update status. If the first terminal needs to continue to access the current service immediately after the update is completed, the access request is not required to be reduced. The access process eases the flow pressure and helps improve system processing efficiency. As shown in FIG. 5, FIG. 5 is a flowchart of a fifth embodiment of a method for recording and sharing OTT Internet TV according to the present invention. This embodiment is based on the embodiment shown in FIG. 1 and is described in detail in step D. Step D specifically includes: Step D01: The SLP server acquires the current stored in the database from the database according to the current user account carried in the record access request. The update timestamp of the user's usage record data. The record access request carries the account of the current user and the device identifier of the second terminal. In order to avoid accessing useless data during data access, ensure that the data stored on the SLP server is the latest data. After receiving the access request from the terminal device, the SLP server needs to compare with the data stored in the database to determine whether it is a database. The latest data stored in the method can also be judged in the same way as the timestamp. Step D02, the SLP server determines whether the update timestamp of the usage record data of the current user stored in the SLP server is consistent with the update timestamp of the usage record data of the current user stored in the database; if not, executing step D03; if yes, Then step D04 is performed. Step D03: The SLP server acquires the usage record data of the current user stored in the database, updates the usage record data of the current user stored in the SLP server, and updates the update time stamp of the current user usage record data stored in the SLP server to The update timestamp of the usage record data of the current user stored in the database is consistent, and step D04 is performed. When the update timestamp of the data in the SLP server is inconsistent with the update timestamp of the data in the database, it indicates that the data stored in the SLP server is not the latest data, and the latest data should be downloaded from the database to update the data in the SLP server to avoid Access to useless data during data access, and minimize the number of data transfers between the SLP server and the database, avoiding impact on the business processing server and database performance, and greatly improving the system in the case of massive user data. The efficiency of processing data. Step D04: The SLP server queries the sharing status of the current user in the usage record data of the current user according to the account of the current user and the device identifier of the second terminal carried in the record access request. The usage record data and the share status are private use record data of the second terminal, and are sent to the EPG server, and are forwarded by the EPG server to the second terminal. In this embodiment, when the update timestamp of the data in the SLP server is consistent with the update timestamp of the data in the database, it means that the data stored in the SLP server is the same as the data stored in the database, and is the latest data. When accessing data, you can access the latest data, which is good for data download. As shown in FIG. 6, FIG. 6 is a schematic structural diagram of a first embodiment of a OTT Internet TV usage record sharing system according to the present invention. The OTT Internet TV usage record sharing system mentioned in this embodiment includes an EPG server 10 and an SLP server 20:

The EPG server 10 is configured to receive the current user's usage record update request sent by the first terminal 30, and forward it to the SLP server 20; the use record update request carries the current user's current use record data and the current use record data. The sharing status is received by the second terminal 40, and is forwarded to the SLP server 20; the sharing status sent by the SLP server 20 is the usage record data shared by the current user and the sharing status is private to the second terminal 40. The usage record data is forwarded to the second terminal 40.

The SLP server 20 is configured to update the usage record data of the current user stored in the SLP server 20 according to the usage record update request; and query the usage status shared by the current user in the usage record data of the current user according to the usage record access request. The data and sharing status are private usage record data of the second terminal 40, and are sent to the EPG server 10. In this embodiment, the first terminal 30 is a set top box, a PC, or a mobile terminal. The current user may enter the current user's account at the first terminal 30 to log in to the OTT TV service, and the first terminal 30 initiates an update request. The usage update record carries the current usage history data of the current user and the sharing status of the current usage record data, and the sharing status can be distinguished by setting the sharing identifier. For example, when the sharing identifier is 0, it means not sharing, as the first The private data of a terminal 30, only the current user enters the current user account to log in on the first terminal 30, and can access the private data. If the current user logs in through other terminals, even if the same current user account or the current input is entered The account associated with the user account cannot access the private data; when the share identifier is 1, it indicates sharing, as the shared data of the current user, the current user inputs the current user account on any terminal or is associated with the current user account. The account login can access these private data. The current usage record data of the current user is carried in the record update request, and the SLP server 20 updates the original data by using the current use record data of the current user. In this embodiment, the data is updated in real time only when the user initiates the request, and the SLP server 20 is used as the cache module for using the recorded data, and the used record data is not directly stored in the database 50, thereby minimizing the synchronization of the SLP server 20 and the database 50 as much as possible. User data, to avoid impact on the performance of the business processing server and database 50, in the case of massive user data, can greatly improve the system The efficiency of processing data. The second terminal 40 of this embodiment is a set top box, a PC or a mobile terminal. The usage record access request may include an account of the current user, a device identifier of the second terminal 40, and the like. After receiving the record access request, the SLP server searches the SLP server 20 for the current user's usage record data according to the current user's account, and searches for the shared state as the data shared by the current user according to the shared identifier, and the shared data can be sent to the user. A terminal device searches for the private data of the second terminal 40 according to the shared identifier and the device identifier, and the private data can only be sent to the terminal device corresponding to the private data. For example, the current user views a certain video file through the first terminal 30 at 9:00 this morning, the video is played to 20%, the current user sends a usage record update request via the first terminal 30, and marks the usage record of 9:00 this morning as sharing. The SLP server 20 saves the update record; the current user re-accesses the video file through the first terminal 30 at 2 pm today, and the SLP server 20 informs the first that the video has been played to 20% of the usage record data according to the updated data. The terminal 30, the first terminal 30 starts playing the video from 20%, and the video plays to 60%. The current user sends a usage record update request via the first terminal 30, and marks the use record of 2 pm today as private, and the SLP server 20 saves This update record; the current user re-accesses the video file through the second terminal 40 at 8:00 this evening, and the SLP server 20 does not have the first terminal 30 private because the data updated in the afternoon is not according to the updated data, therefore, the SLP server 20 still follows The data updated in the morning, the video has been played to 20% of the usage record data to inform the second terminal 40, the second End 40 starts to play video from 20%. This embodiment performs separate processing according to the sharing state set by each user using the record data, which protects the personal privacy of each user on the one hand, and makes the sharing more flexible on the other hand. In the embodiment of the present invention, the SLP server 20 is specifically configured to: obtain an update time stamp of the usage record data of the current user stored in the database 50 from the database 50 according to the account of the current user carried in the use record update request. It is judged whether or not the update time stamp of the current user's usage record data stored in the SLP server 20 coincides with the update time stamp of the current user's usage record data stored in the database 50. When the update time stamps are inconsistent, the usage record data of the current user stored in the database 50 is acquired, the usage record data of the current user stored in the SLP server 20 is updated, and the update of the usage record data of the current user stored in the SLP server 20 is obtained. The timestamp is updated to coincide with the update timestamp of the current user's usage record data stored in database 50. When the update time stamps are consistent, the usage history data of the current user stored in the SLP server 20 is updated according to the sharing status of the current usage record data of the current user and the current usage record data carried in the usage record update request, and the SLP is The update time stamp of the usage record data of the current user stored in the server 20 is updated to the current time. In this embodiment, in order to avoid updating to useless data when the data is updated, it is ensured that the data stored on the SLP server 20 is the latest data, and the SLP server 20 needs to perform data with the data stored in the database 50 when receiving the update request of the terminal device. For comparison, it is judged whether it is the latest data stored in the database 50, and the manner of judging can adopt the method of comparing time stamps, that is, whether the data stored on the SLP server 20 and the update time marked by the data stored in the database 50 are the same. When the update time stamp of the data in the SLP server 20 does not coincide with the update time stamp of the data in the database 50, it indicates that the data stored in the SLP server 20 is not the latest data, and the latest data should be downloaded from the database 50 to update the SLP server 20. The data in the data, to avoid updating to useless data when the data is updated. Since the SLP server 20 accesses the database 50 only when the user initiates the request, and when the data is determined to be inconsistent, the SLP server 20 downloads the data from the database 50, minimizing the SLP server 20 and the database 50. The number of times of data transmission avoids impact on the performance of the business processing server and database 50. In the case of massive user data, the efficiency of processing data by the system can be greatly improved. In this embodiment, when the update timestamp of the data in the SLP server 20 coincides with the update timestamp of the data in the database 50, that is, the data stored in the SLP server 20 is the same as the data stored in the database 50, and is the latest data. At this time, when the data is updated, the latest data can be updated to facilitate data update. In the embodiment of the present invention, the SLP server 20 is further configured to: cache the updated usage history data of the current user as incremental data. The SLP server 20 synchronizes the delta data to the database 50 when the synchronization time arrives or the number of increments of data is greater than or equal to the update threshold. The SLP server 20 of the present embodiment does not immediately update the data in the database 50 after performing the data update, but caches the data to be updated to reduce the number of accesses to the database 50, and minimizes the SLP server 20 and the database. 50 Synchronize the full amount of user data, alleviate the traffic pressure, avoid the impact on the performance of the business processing server and database 50, in the case of massive user data, can greatly improve the efficiency of the system processing data. In the embodiment of the present invention, the SLP server 20 is further configured to query the sharing status in the updated usage data of the current user according to the account of the current user and the device identifier of the first terminal 30 carried in the usage record update request. The usage record data and the sharing status shared by the current user are the usage history data private to the first terminal 30, and are fed back to the EPG server 10.

The EPG server 10 is further configured to forward the sharing status fed back by the SLP server 20 to the first terminal 30 for the usage record data shared by the current user and the usage record data shared by the first terminal 30. After performing the update of the data in this embodiment, the SLP server 20 also feeds back the update result to the first terminal 30, and informs the first terminal 30 of the current update status. If the first terminal 30 needs to continue to access the current service immediately after the update is completed, There is no need to make an access request, which reduces the access process, relieves traffic pressure, and helps improve system processing efficiency. In the embodiment of the present invention, the SLP server 20 is further configured to: obtain an update time stamp of the usage record data of the current user stored in the database 50 from the database 50 according to the account of the current user carried in the record access request. It is judged whether or not the update time stamp of the current user's usage record data stored in the SLP server 20 coincides with the update time stamp of the current user's usage record data stored in the database 50. When the update time stamps are inconsistent, the usage record data of the current user stored in the database 50 is obtained, and the update is performed.

The usage record data of the current user stored in the SLP server 20, and the update time stamp of the usage record data of the current user stored in the SLP server 20 is updated to be consistent with the update time stamp of the usage record data of the current user stored in the database 50. . When the update timestamps are consistent, the usage history data shared by the current user is queried in the updated current user usage record data according to the current user's account number carried in the record access request and the device identifier of the second terminal 40. And the shared state is the usage record data private to the second terminal 40, and is sent to the EPG server 10. The usage record access request of this embodiment carries the account of the current user and the device identifier of the second terminal 40. In order to avoid accessing useless data during data access, it is ensured that the data stored on the SLP server 20 is the latest data. After receiving the access request of the terminal device, the SLP server 20 needs to compare with the data stored in the database 50 to determine Whether it is the latest data stored in the database 50, the manner of judging can also adopt the method of comparing time stamps. When the update time stamp of the data in the SLP server 20 does not coincide with the update time stamp of the data in the database 50, it indicates that the data stored in the SLP server 20 is not the latest data, and the latest data should be downloaded from the database 50 to update the SLP server 20. The data in the file avoids accessing useless data during data access, and minimizes the number of data transfers between the SLP server 20 and the database 50, avoiding impact on the performance of the service processing server and the database 50, in the case of massive user data. In this case, the efficiency of the system processing data can be greatly improved. In this embodiment, when the update timestamp of the data in the SLP server 20 coincides with the update timestamp of the data in the database 50, that is, the data stored in the SLP server 20 is the same as the data stored in the database 50, and is the latest data. At this time, when accessing the data, the latest data can be accessed, which is beneficial to data download. The above description is only the preferred embodiment of the present invention, and is not intended to limit the scope of the invention, and the equivalent structure or equivalent flow transformation made by the specification and the drawings of the present invention may be directly or indirectly applied to other related The technical field is equally included in the scope of patent protection of the present invention.

Claims

A claim for rights, a method for sharing records using OTT Internet TV, including:

Step A: The EPG server receives the usage record update request of the current user sent by the first terminal, and forwards the request to the SLP server; the usage record update request carries the current usage record data of the current user and the current usage record data. Shared state

Step B: The SLP server updates the usage record data of the current user stored in the SLP server according to the usage record update request.

Step C: The EPG server receives a usage record access request of a current user sent by the second terminal, and forwards the request to the SLP server;

Step D: The SLP server queries, according to the usage record access request, the usage record data shared by the current user and the usage record data shared by the current user in the usage record data of the current user, and is sent to the usage data of the second terminal privately. The EPG server is forwarded by the EPG server to the second terminal. The OTT Internet TV usage record sharing method according to claim 1, wherein the step B specifically includes:

Step B01, the SLP server acquires, according to the account of the current user carried in the use record update request, an update time stamp of the current user's usage record data stored in the database to the database;

Step B02, the SLP server determines whether an update timestamp of the usage record data of the current user stored in the SLP server is consistent with an update timestamp of the usage record data of the current user stored in the database; if not, executing Step B03; If yes, proceed to step B04;

Step B03, the SLP server acquires usage record data of the current user stored in the database, updates usage record data of the current user stored in the SLP server, and records usage records of the current user stored in the SLP server. The update timestamp of the data is updated to be consistent with the update timestamp of the usage record data of the current user stored in the database, and step B04 is performed;

Step B04, the SLP server updates the usage record of the current user stored in the SLP server according to the current usage record data of the current user and the sharing status of the current usage record data carried in the usage record update request. Data, and update the update time stamp of the current user's usage record data stored in the SLP server to the current time. The OTT Internet TV usage record sharing method according to claim 2, wherein the step B04 further comprises:

Step B05, the SLP server caches the updated usage record data of the current user as the incremental data.

Step B06, when the synchronization time arrives or the number of the incremental data is greater than or equal to the update threshold, the SLP server synchronizes the incremental data to the database. The OTT Internet TV usage record sharing method according to claim 2 or 3, wherein the step B04 further comprises:

In step B07, the SLP server queries the shared user's usage record data in the updated current user usage record data according to the current user's account number and the device identifier of the first terminal that are carried in the usage record update request. Using the recorded data and the shared state as the usage data of the first terminal private, and feeding back to the EPG server, and forwarding by the EPG server to the first terminal

The OTT Internet TV usage record sharing method according to claim 1 or 2, wherein the step D specifically includes:

Step D01, the SLP server acquires, according to the account of the current user carried in the record access request, an update time stamp of the current user's usage record data stored in the database to the database;

Step D02, the SLP server determines whether an update timestamp of the usage record data of the current user stored in the SLP server is consistent with an update timestamp of the usage record data of the current user stored in the database; if not, executing Step D03; If yes, step D04 is performed;

Step D03, the SLP server acquires usage record data of the current user stored in the database, updates usage record data of the current user stored in the SLP server, and records usage records of the current user stored in the SLP server. The update timestamp of the data is updated to be consistent with the update timestamp of the usage record data of the current user stored in the database, and step D04 is performed;

In step D04, the SLP server queries the shared user's usage record data in the updated current user usage record data according to the current user account and the device identifier of the second terminal that are carried in the use record access request. Using the recorded data and the shared state as the usage data of the second terminal private, and sent to the EPG server, and forwarded by the EPG server to the second terminal An OTT Internet TV usage record sharing system, comprising an EPG server and an SLP server, wherein the EPG server is configured to receive a current user usage record update request sent by the first terminal, and forward the request to the SLP server; The record update request carries the current use record data of the current user and the share status of the current use record data; receiving a use record access request of the current user sent by the second terminal, and forwarding the request to the SLP server; The usage record sent by the SLP server is the usage record data shared by the current user and the usage record data shared by the second terminal is forwarded to the second terminal by the second terminal;

The SLP server is configured to update the usage record data of the current user stored in the SLP server according to the usage record update request; and query the sharing status in the current user usage record data according to the usage record access request The usage record data and the sharing status shared by the current user are the usage record data private to the second terminal, and are sent to the EPG server. The ΟΤΤInternet TV usage record sharing system according to claim 6, wherein the SLP server is specifically configured to:

And obtaining, according to the account of the current user carried in the record update request, an update time stamp of the current user's usage record data stored in the database to the database;

Determining whether an update timestamp of the usage record data of the current user stored in the SLP server is consistent with an update timestamp of the usage record data of the current user stored in the database;

When the update time stamps are inconsistent, acquiring usage record data of the current user stored in the database, updating usage record data of the current user stored in the SLP server, and using the current user usage record stored in the SLP server The update timestamp of the data is updated to be consistent with the update timestamp of the usage record data of the current user stored in the database;

Updating the usage record of the current user stored in the SLP server according to the sharing status of the current usage record data of the current user and the current usage record data carried in the usage record update request when the update time stamps are consistent. Data, and update the update time stamp of the current user's usage record data stored in the SLP server to the current time. The ΟΤΤInternet TV usage record sharing system according to claim 7, wherein the SLP server is further configured to:

Caching the updated current user usage record data into incremental data;

The SLP server synchronizes the delta data to the database when the synchronization time arrives or the number of increments of data is greater than or equal to an update threshold. The OTT Internet TV usage record sharing system according to claim 7 or 8, wherein the SLP server is further configured to: according to the account of the current user and the first terminal carried in the usage record update request The device identifier is used to query, in the updated usage record data of the current user, the usage record data shared by the current user and the usage record data shared by the first terminal, and fed back to the EPG server;

The EPG server is further configured to: forward the shared status fed back by the SLP server to the first terminal by using the usage record data shared by the current user and the usage record data shared by the first terminal. The OTT Internet TV usage record sharing system according to claim 6 or 7, wherein the SLP server is further configured to:

Obtaining, according to the account of the current user carried in the record access request, an update time stamp of the current user's usage record data stored in the database to the database;

When the update timestamps are consistent, according to the account of the current user and the device identifier of the second terminal carried in the use record access request, the shared status of the current user is used to query the shared status as shared by the current user. The usage record data and the share status are private use record data of the second terminal, and are sent to the EPG server.