CN103731682B - Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment - Google Patents
Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment Download PDFInfo
- Publication number
- CN103731682B CN103731682B CN201410037487.0A CN201410037487A CN103731682B CN 103731682 B CN103731682 B CN 103731682B CN 201410037487 A CN201410037487 A CN 201410037487A CN 103731682 B CN103731682 B CN 103731682B
- Authority
- CN
- China
- Prior art keywords
- record
- video
- client
- request
- broadcasting
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Landscapes
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
The present invention keeps synchronous method, equipment and the system for watching record between providing one kind of multiple viewing equipment, and method includes：The request for reporting broadcasting to record that client is sent is received, reports and video ID, ID, current play time, the affiliated special edition ID of video, video type and client type is carried in the request played and recorded；According to the difference of ID, the request for playing record will be reported to be sent in the different Message Queuing Middlewares divided in advance, the number at least two of Message Queuing Middleware；It is that a video only retains a broadcasting record, that deletes video ID and special edition ID repetitions reports broadcasting record in Message Queuing Middleware；To play the record unique ID of generation, the broadcasting record storage of unique ID will be carried into caching and database.The present invention can accelerate the request at customer in response end, and reduce the space-consuming of caching or database.
Description
Technical field
The present invention relates to video display arts field, synchronous viewing note is kept between more particularly to one kind of multiple viewing equipment
Method, equipment and the system of record.
Background technology
Several major names of this area are introduced first：
Cloud is recorded：A kind of service end calculation, client does not retain any data, directly quickly reports user record
To server end, by the calculating that server end is complicated, by the preservation of withing a hook at the end property of result.
User-generated content（UGC, User Generated Content）：Oneself original content is passed through interconnection by user
Net platform is shown or is supplied to other users.
Memcacheq：A kind of message-oriented middleware product, the data relay for functioning as the message producer and consumer is put down
Platform.
LVS：Realize the scheduler of load balancing between Web clusters.
NGINX(Engine x)：One high performance HTTP and Reverse Proxy.
REDIS：One high performance key-value（Key-value）Storage system.
MYSQL：One high performance Relational DBMS.
JSON（JavaScript Object Notation）：It is a kind of data interchange format of lightweight.It is to be based on
JavaScript（Standard ECMA-2623rd Edition-December1999）A subset.JSON is using complete
Independently of the text formatting of language, but it also using the custom similar to C language family（Including C, C++, C#, Java,
JavaScript, Perl, Python etc.）.These characteristics make JSON turn into preferable data interchange language.
Because cloud computing is in high development period, therefore, increasing businessman and internet giant start input
Onto the popularization of research and development and the application of technology, the technology of cloud computing also progressively moves to maturity and perfect.Cloud server terminal can be regarded as
One small-sized cloud system.Client is only needed to simply report and obtain broadcasting record, and complicated calculating and storage problem are handed over
Give cloud server terminal processing.
Cloud server terminal handles request using Web clusters, and the load balancing between server is realized using LVS.Using point
The stability of cloth service guarantees service, when there is service to hang because of network or machine reason, can be switched to other services.
Preserved using Message Queuing Middleware and report request, request is reported using JAVA Thread Pool Technology asynchronous process.In terms of storage, make
With REDIS as caching, database is used as using MYSQL.
For video website, during user's viewing video, viewing equipment can record the viewing that service end reports the user to cloud
Record, wherein the video that viewing record includes user's viewing is the playing progress rate of what and the video.When user uses PC ends
Client viewing video when, viewing equipment can regularly report viewing record, for example reported once every two minutes.When user makes
When watching video with the client on mobile phone, when logging off, viewing equipment can report broadcasting to record to cloud record service end.
For cloud record service end, receive viewing equipment report play record request when, deposit caching and database；
When receiving the request of viewing equipment acquisition broadcasting record, preferentially searched from caching, do not go to look into database again in caching
Look for, return to JSON data formats.
At present, as the customer volume of website rises and the diversity increase of viewing equipment, the visit capacity of video increases rapidly
Plus, the concurrency that client uploads broadcasting record will be very big, and the service of directly invoking cannot may be responded timely, even
The collapse of the time-out called or service can be caused.Therefore, prior art exists to upload to play to record to react slow or upload and lost
The problem of losing, and client, when obtaining broadcasting record, response also has certain delay.
The content of the invention
The technical problem to be solved in the present invention is to provide the side that synchronous viewing record is kept between one kind of multiple viewing equipment
Method, equipment and system, can timely respond to play reporting and obtaining for record.
The embodiment of the present invention provides the method for keeping synchronous viewing to record between one kind of multiple viewing equipment, including：
The request for reporting broadcasting to record that client is sent is received, described report in the request played and recorded carries video
The affiliated special edition ID of ID, ID, current play time, video, video type and client type；
According to the difference of ID, the request for playing record is reported to be sent to the different message teams divided in advance by described
In row middleware, the number at least two of the Message Queuing Middleware；
In the Message Queuing Middleware, it is that a video only retains a broadcasting record, deletes video ID and special edition
What ID was repeated reports broadcasting to record；
The record unique ID of generation is played to be described, by carrying unique ID broadcasting record storage to caching and data
In storehouse.
Preferably, the difference according to ID, reports the request for playing record to be sent to what is divided in advance by described
Before in different Message Queuing Middlewares, in addition to：
Broadcasting record request is reported first to be stored in thread pool for pc client the client type, every predetermined
Time is using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
Preferably, it is described to play the record unique ID of generation to be described, be specially：
It is that the record of playing generates globally unique ID using REDIS as distributed ID makers.
Preferably, in addition to：
The request for the acquisition broadcasting record that client is sent is received, the acquisition is played in the request of record and carries user
ID, video ID and video type；
The list for the video ID that the corresponding user of the ID watches is searched from caching according to the ID；If slow
The list for depositing the video ID for searching user's viewing corresponding less than the ID is searched from database again；
By the video ID found list, the broadcasting record of video is obtained from caching；If do not had in caching
There is the record of playing to be obtained again from database；
The broadcasting record is returned into client.
The embodiment of the present invention also provides the equipment for keeping synchronous viewing to record between one kind of multiple viewing equipment, including：On
Report plays record request receiving module, reports broadcasting record request division module, play record deduplication module, play Record ID life
Into module and broadcasting record storage module；
It is described to report broadcasting record request receiving module, the request recorded is played for receiving reporting for client transmission,
Described report in broadcasting record request carries video ID, ID, current play time, the affiliated special edition ID of video, video type
And client type；
It is described to report broadcasting record request division module, for the difference according to ID, report broadcasting to record by described
Request be sent in the different Message Queuing Middlewares divided in advance, the number of the Message Queuing Middleware is at least two
It is individual；
It is described to play record deduplication module, in the Message Queuing Middleware, being that a video only retains portion
Record is played, that deletes video ID and special edition ID repetitions reports broadcasting to record；
The broadcasting Record ID generation module, for playing the unique ID of record generation to be described；
The broadcasting record storage module, will carry the broadcasting record storage of unique ID into caching and database.
Preferably, in addition to report broadcasting record request deduplication module；
It is described to report broadcasting record request deduplication module, for the client type to be reported into broadcasting for pc client
Record request is first stored in thread pool, at predetermined time intervals using hash to reporting broadcasting record request in the thread pool
Carry out duplicate removal.
Preferably, the broadcasting Record ID generation module includes playing Record ID generation submodule, for being made using REDIS
It is that the record of playing generates globally unique ID for distributed ID makers.
Preferably, in addition to：Broadcasting record request receiving module, video ID list lookups module, broadcasting record is obtained to obtain
Modulus block and broadcasting record return to module；
Described obtain plays record request receiving module, and the request of record is played in the acquisition for receiving client transmission,
Described obtain carries ID, video ID and video type in the request for playing record；
The video ID list lookup modules, for searching the corresponding use of the ID from caching according to the ID
The video ID of family viewing list；If searching the video ID of user's viewing corresponding less than ID list in caching again
Searched from database；
It is described to play record acquisition module, for the list of the video ID by finding, obtain and regard from caching
The broadcasting record of frequency；If there is no the record of playing to be obtained again from database in caching；
The record of playing returns to module, for the broadcasting record to be returned into client.
The embodiment of the present invention also provides the system for keeping synchronous viewing to record between one kind of multiple viewing equipment, including：Visitor
Family end, server end；
The client, the request recorded is played for sending to report to the server end, described to report broadcasting to record
Request in carry video ID, ID, current play time, the affiliated special edition ID of video, video type and client type；
The server end, for the difference according to ID, reports the request for playing record to be sent in advance by described
In the different Message Queuing Middlewares divided, the number at least two of the Message Queuing Middleware；In the message team
It is that a video only retains a broadcasting record, that deletes video ID and special edition ID repetitions reports broadcasting record in row middleware；
The record unique ID of generation is played to be described, the broadcasting record storage of unique ID will be carried into caching and database.
10th, the system that synchronous viewing record is kept between a variety of viewing equipment according to claim 9, its feature exists
In the server end reports the request for playing record to be sent to the difference divided in advance according to the difference of ID by described
Message Queuing Middleware in before, in addition to：
Broadcasting record request is reported first to be stored in thread pool for pc client the client type, every predetermined
Time is using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
11st, the system that synchronous viewing record is kept between a variety of viewing equipment according to claim 9 or 10, it is special
Levy and be, the client is additionally operable to send the request for obtaining and playing and recording to the server end, record is played in the acquisition
Request in carry ID, video ID and video type；
The server end, is additionally operable to search what the corresponding user of the ID watched from caching according to the ID
Video ID list；If searching the video ID of user's viewing corresponding less than ID list in caching again from database
It is middle to search；By the video ID found list, the broadcasting record of video is obtained from caching；If do not had in caching
The record of playing is obtained from database again；The broadcasting record is returned into client.
Compared with prior art, the present invention has advantages below：
The method that synchronous viewing record is kept between a variety of viewing equipment provided in an embodiment of the present invention, according to ID
Difference, described report is played the request that records and is sent in the different Message Queuing Middlewares divided in advance, so can be with
Avoid reporting the queue for playing record oversize, so that the request at customer in response end is accelerated, in addition, in order to which a video only retains
Portion plays record, and that deletes that video ID and special edition ID repeat reports broadcasting to record, and can so reduce caching or database
Space-consuming, and the broadcasting record of request can be quickly found when client obtains and plays record, so as to accelerate to ask
The response asked.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is the accompanying drawing used required in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
Some embodiments of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can be with
Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 is the signal of embodiment of the method one of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 2 is the signal of embodiment of the method two of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 3 is the signal of embodiment of the method three of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 4 is the signal of apparatus embodiments one of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 5 is the signal of apparatus embodiments two of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 6 is the signal of apparatus embodiments three of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure；
Fig. 7 is the signal of system embodiment one of the synchronous viewing record of holding between a variety of viewing equipment that the present invention is provided
Figure.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation is described, it is clear that described embodiment is only a part of embodiment of the invention, rather than whole embodiments.It is based on
Embodiment in the present invention, it is every other that those of ordinary skill in the art are obtained under the premise of creative work is not made
Embodiment, belongs to the scope of protection of the invention.
In order to facilitate the understanding of the purposes, features and advantages of the present invention, below in conjunction with the accompanying drawings to the present invention
Embodiment be described in detail.
Embodiment of the method one：
The method of synchronous viewing record is kept to implement referring to Fig. 1, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example one.
The method that synchronous viewing record is kept between a variety of viewing equipment that the present embodiment is provided, comprises the following steps：
S101：The request for reporting broadcasting to record that client is sent is received, described report in the request played and recorded carries
The affiliated special edition ID of video ID, ID, current play time, video, video type and client type；
It should be noted that when user watches video using client, it is necessary to report broadcasting to record, playing record includes
Video ID, ID, current play time.Special edition ID, video type and client type described in video；
Wherein, current play time refers to that the video of user's viewing is currently viewing and which point which etc. has been arrived second.
Wherein, client type can be divided into pc client, and mobile client etc..Mobile client is, for example, mobile phone
Client, PAD clients etc..
When user using PC ends client watch video when, viewing equipment can regularly report viewing record, for example every
Report once within two minutes.When user watches video using the client on mobile phone, when logging off, viewing equipment can be to cloud
Record service end reports broadcasting to record.
Wherein, special edition described in video refers to possessing the video collection of denominator, and such as certain TV play is properly termed as
One special edition, the video of a TV play belongs in same special edition, but may to belong to one or more special for a video
Volume, it is also possible to it is not belonging to any special edition.
Client will report broadcasting record request to be sent to LVS first；
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX will report broadcasting record request to be forwarded to corresponding WEB terminal server as reverse proxy.
S102：According to the difference of ID, described report is played the request that records and be sent to divide in advance different
In Message Queuing Middleware, the number at least two of the Message Queuing Middleware；
It should be noted that the Message Queuing Middleware can be realized by Memcacheq, it can also be disappeared by others
Queue middleware is ceased to realize.
Specific how to be divided according to the difference of ID reports broadcasting to recorded in different Memcacheq queues, can
To be set from origin, for example, when setting two different Memcacheq queues, ID for even number can be placed on one
In individual Memcacheq queues, by ID being placed in another Memcacheq queue for odd number.
When setting three different Memcacheq queues, it is possible to use seek the algorithm of 3 remainder（%3）, by ID
Remmed to 3, be 0,1 and 2 to be respectively put into first Memcacheq queue, in second Memcacheq queue according to remainder
And in the 3rd Memcacheq queue.
It is understood that when there is two Memcacheq queues, can also be remmed using ID to 2, remainder is
0 is put into two different Memcacheq queues with 1, for example, remainder is put into first Memcacheq queue for 0, remainder
It is put into for 1 in second Memcacheq queue.
Such as ID is 3438434, it is possible to use the numerical value rems to 2.
It is understood that server end can parse the various letters reported in broadcasting record request of client transmission first
Breath, the information includes video ID, ID, current play time.Special edition ID, video type and client type described in video；
It should be noted that first the request for playing record will be reported to be sent to different message teams in the embodiment of the present invention
In row middleware, so primarily to preventing that the request queue for reporting broadcasting to record is oversize, server response is too slow.
It is understood that the specific number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but
It is minimum needs two, a Message Queuing Middleware is not different with prior art, and not having prevents the too long of effect of queue.
S103：In the Message Queuing Middleware, be a video only retain it is a play record, delete video ID and
What special edition ID was repeated reports broadcasting to record；
Because the broadcasting record of reporting of user has a lot, for example, the video of user's viewing is a TV play, now
The 16th collection is seen, the broadcasting record of the 1st the-the 15 collection of collection can all be deleted, only retain the broadcasting record of the 16th collection.Because objective
Family is not intended to chase after when seeing a TV play, it is seen that oneself playing has same portion's TV play multiple broadcastings in record are recorded.
S104：The record unique ID of generation is played to be described, by carrying unique ID broadcasting record storage to caching
In database.
The method that synchronous viewing record is kept between a variety of viewing equipment provided in an embodiment of the present invention, according to ID
Difference, described report is played the request that records and is sent in the different Message Queuing Middlewares divided in advance, so can be with
Avoid reporting the queue for playing record oversize, so that the request at customer in response end is accelerated, in addition, in order to which a video only retains
Portion plays record, and that deletes that video ID and special edition ID repeat reports broadcasting to record, and can so reduce caching or database
Space-consuming, and the broadcasting record of request can be quickly found when client obtains and plays record, so as to accelerate to ask
The response asked.
Embodiment of the method two：
The method of synchronous viewing record is kept to implement referring to Fig. 2, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example two.
Due to when client is pc client, due to pc client, to send rule more random, easily exist it is many repeat,
Interval time is very short to report the request played and recorded, and once reports broadcasting to record for example, pc client was sent every two minutes
Request, so just have within an hour it is substantial amounts of report broadcasting record.In order to mitigate server end in the present embodiment
Pressure, is just sent in different Message Queuing Middlewares after WEB terminal plays the request duplicate removal of record to reporting.
Illustrated below by taking embodiment of the method two as an example.
S201 in the present embodiment is identical with the S101 in embodiment of the method one, will not be repeated here.
S202：Judge whether client is pc client according to client type, if not pc client, then perform
S204；If pc client, then S203 is performed；
S203：Broadcasting record request is reported first to be stored in thread pool for pc client the client type, often
Every the scheduled time using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
The mode of specific duplicate removal is to run each thread in the thread pool that a size can extend, thread pool to have certainly
Oneself obstruction queue, each obstruction queue is used for preserving the request for reporting broadcasting to record of client.Each thread each makes a reservation for
Time goes to report the request played and recorded in the obstruction queue of oneself described in taking-up, using hash duplicate removals, then by after duplicate removal
Report and play the processing that record carries out S204.
Specifically, WEB terminal selects one not in the thread of operation first in thread pool, by reporting from pc client
Record is played to be sent in the obstruction queue of the thread.
S204 is identical with the S102 in embodiment of the method one, will not be repeated here.
S205：First determine whether in Message Queuing Middleware report play record request in ID whether effectively with
And whether special edition ID is effective；If effectively, it is that a video only retains a broadcasting record, deletes video ID and special edition ID weights
Multiple reports broadcasting to record；
S206：Using REDIS as distributed ID makers, to play the ID that record generation is globally unique, it will carry
The broadcasting record storage of unique ID is into caching and database.
Due to there is multiple servers reporting in processing Message Queuing Middleware to play the request recorded, if using biography
The method that ID generates ID from increasing in the database of system, can be impacted to database, because when request amount is big, peak time is every
Second has more than 1,000 request increment, and so influence to database is very big, and database faces very big pressure.Therefore, originally
REDIS is used in embodiment to generate unique ID to play record.
Multiple servers handle the request in Message Queuing Middleware simultaneously, can so accelerate response speed, it is to avoid one
Request stacking during individual server process.
The advantage for the method that the present embodiment is provided is to report broadcasting record request to be put into message queue pc client
Before in middleware, first broadcasting record request is reported to carry out duplicate removal processing pc client, because pc client transmission is upper
Report play record request exist it is many repeat, time interval very short request, service can be mitigated after the request repeated by deleting
The pressure at device end, so as to accelerate the response time.
It should be noted that after the broadcasting record that server end reports client is preserved successfully, can be with JSON numbers
According to return preserve whether successful feedback message.
Embodiment of the method three：
Embodiment of the method one and embodiment of the method two are described so that client reports broadcasting to record as an example, tie below
Close exemplified by accompanying drawing introduces client acquisition broadcasting record and be described.
The method of synchronous viewing record is kept to implement referring to Fig. 3, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example three.
S301：The request for the acquisition broadcasting record that client is sent is received, the acquisition is played to be carried in the request of record
ID, video ID and video type；
It should be noted that when user actively clicks on video, explanation is to need to obtain to play record, now viewing equipment
Client is sent from trend server end obtains the request for playing record.
S302：The list for the video ID that the corresponding user of the ID watches is searched from caching according to the ID；
If the list that the video ID of user's viewing corresponding less than the ID is searched in caching is searched from database again；
S303：By the video ID found list, the broadcasting record of video is obtained from caching；If caching
In do not have it is described play record again from database obtain；
S304：The broadcasting record is returned into client.
It should be noted that the method provided in an embodiment of the present invention for obtaining broadcasting record is to be based on embodiment of the method or side
On the basis of method embodiment two, received server-side finds that the request is corresponding to be broadcast to after obtaining the request playing and record
Put record and return to client.
The method that synchronous viewing record is kept between a variety of viewing equipment provided based on above example, the present invention is implemented
Example additionally provides the equipment for keeping synchronous viewing to record between one kind of multiple viewing equipment, is situated between in detail below in conjunction with the accompanying drawings
Continue.
The equipment of synchronous viewing record is kept to implement referring to Fig. 4, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example one.
Apparatus embodiments one：
The equipment that synchronous viewing record is kept between a variety of viewing equipment provided in an embodiment of the present invention, including：Report and broadcast
Record request receiving module 400 is put, broadcasting record request division module 500 is reported, plays record deduplication module 600, plays note
Record ID generation modules 700 and play record storage module 800；
Broadcasting record request receiving module 400 is reported, the request recorded, institute are played for receiving reporting for client transmission
State report carried in broadcasting record request video ID, ID, current play time, the affiliated special edition ID of video, video type and
Client type；
It should be noted that when user watches video using client, it is necessary to report broadcasting to record, playing record includes
Video ID, ID, current play time.Special edition ID, video type and client type described in video；
Wherein, current play time refers to that the video of user's viewing is currently viewing and which point which etc. has been arrived second.
Wherein, client type can be divided into pc client, and mobile client etc..Mobile client is, for example, mobile phone
Client, PAD clients etc..
When user using PC ends client watch video when, viewing equipment can regularly report viewing record, for example every
Report once within two minutes.When user watches video using the client on mobile phone, when logging off, viewing equipment can be to cloud
Record service end reports broadcasting to record.
Wherein, special edition described in video refers to possessing the video collection of denominator, and such as certain TV play is properly termed as
One special edition, the video of a TV play belongs in same special edition, but may to belong to one or more special for a video
Volume, it is also possible to it is not belonging to any special edition.
Client will report broadcasting record request to be sent to LVS first；
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX will report broadcasting record request to be forwarded to corresponding WEB terminal server as reverse proxy.
Broadcasting record request division module 500 is reported, for the difference according to ID, described report is played what is recorded
Request is sent in the different Message Queuing Middlewares divided in advance, and the number of the Message Queuing Middleware is at least two
It is individual；
It is understood that server end can parse the various letters reported in broadcasting record request of client transmission first
Breath, the information includes video ID, ID, current play time.Special edition ID, video type and client type described in video；
It should be noted that the Message Queuing Middleware can be realized by Memcacheq, it can also be disappeared by others
Queue middleware is ceased to realize.
Specific how to be divided according to the difference of ID reports broadcasting to recorded in different Memcacheq queues, can
To be set from origin, for example, when setting two different Memcacheq queues, ID for even number can be placed on one
In individual Memcacheq queues, by ID being placed in another Memcacheq queue for odd number.
When setting three different Memcacheq queues, it is possible to use seek the algorithm of 3 remainder（%3）, by ID
Remmed to 3, be 0,1 and 2 to be respectively put into first Memcacheq queue, in second Memcacheq queue according to remainder
And in the 3rd Memcacheq queue.
It is understood that when there is two Memcacheq queues, can also be remmed using ID to 2, remainder is
0 is put into two different Memcacheq queues with 1, for example, remainder is put into first Memcacheq queue for 0, remainder
It is put into for 1 in second Memcacheq queue.
Such as ID is 3438434, it is possible to use the numerical value rems to 2.
It should be noted that first the request for playing record will be reported to be sent to different message teams in the embodiment of the present invention
In row middleware, so primarily to preventing that the request queue for reporting broadcasting to record is oversize, server response is too slow.
It is understood that the specific number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but
It is minimum needs two, a Message Queuing Middleware is not different with prior art, and not having prevents the too long of effect of queue.
Record deduplication module 600 is played, in the Message Queuing Middleware, being that a video only retains portion and broadcast
Record is put, that deletes video ID and special edition ID repetitions reports broadcasting to record；
Because the broadcasting record of reporting of user has a lot, for example, the video of user's viewing is a TV play, now
The 16th collection is seen, the broadcasting record of the 1st the-the 15 collection of collection can all be deleted, only retain the broadcasting record of the 16th collection.Because objective
Family is not intended to chase after when seeing a TV play, it is seen that oneself playing has same portion's TV play multiple broadcastings in record are recorded.
Record ID generation module 700 is played, for playing the unique ID of record generation to be described；
Record storage module 800 is played, the broadcasting record storage of unique ID will be carried into caching and database.
The equipment that synchronous viewing record is kept between a variety of viewing equipment provided in an embodiment of the present invention, according to ID
Difference, described report is played the request that records and is sent in the different Message Queuing Middlewares divided in advance, so can be with
Avoid reporting the queue for playing record oversize, so that the request at customer in response end is accelerated, in addition, in order to which a video only retains
Portion plays record, and that deletes that video ID and special edition ID repeat reports broadcasting to record, and can so reduce caching or database
Space-consuming, and the broadcasting record of request can be quickly found when client obtains and plays record, so as to accelerate to ask
The response asked.
Apparatus embodiments two：
The equipment of synchronous viewing record is kept to implement referring to Fig. 5, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example two.
Due to when client is pc client, due to pc client, to send rule more random, easily exist it is many repeat,
Interval time is very short to report the request played and recorded, and once reports broadcasting to record for example, pc client was sent every two minutes
Request, so just have within an hour it is substantial amounts of report broadcasting record.In order to mitigate server end in the present embodiment
Pressure, is just sent in different Message Queuing Middlewares after WEB terminal plays the request duplicate removal of record to reporting.
Illustrated below by taking apparatus embodiments two as an example.
The equipment that the present embodiment is provided, in addition to report broadcasting record request deduplication module 900；
It is described to report broadcasting record request deduplication module 900, for the reporting for pc client by the client type
Play record request to be first stored in thread pool, at predetermined time intervals using hash to reporting broadcasting to record in the thread pool
Request carries out duplicate removal.
The mode of specific duplicate removal is to run each thread in the thread pool that a size can extend, thread pool to have certainly
Oneself obstruction queue, each obstruction queue is used for preserving the request for reporting broadcasting to record of client.Each thread each makes a reservation for
Time goes to report the request played and recorded in the obstruction queue of oneself described in taking-up, using hash duplicate removals, then by after duplicate removal
Report and play the processing that record carries out S204.
Specifically, WEB terminal selects one not in the thread of operation first in thread pool, by reporting from pc client
Record is played to be sent in the obstruction queue of the thread.
In the present embodiment, the broadcasting Record ID generation module 700 includes playing Record ID generation submodule 700a, is used for
It is that the record of playing generates globally unique ID using REDIS as distributed ID makers.
Due to there is multiple servers reporting in processing Message Queuing Middleware to play the request recorded, if using biography
The method that ID generates ID from increasing in the database of system, can be impacted to database, therefore, and REDIS is used in the present embodiment
To play the unique ID of record generation.
The advantage for the equipment that the present embodiment is provided is to report broadcasting record request to be put into message queue pc client
Before in middleware, first broadcasting record request is reported to carry out duplicate removal processing pc client, because pc client transmission is upper
Report play record request exist it is many repeat, time interval very short request, service can be mitigated after the request repeated by deleting
The pressure at device end, so as to accelerate the response time.
It should be noted that after the broadcasting record that server end reports client is preserved successfully, can be with JSON numbers
According to return preserve whether successful feedback message.
Apparatus embodiments three：
The equipment of synchronous viewing record is kept to implement referring to Fig. 6, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example three.
Embodiment of the method one and embodiment of the method two are described so that client reports broadcasting to record as an example, tie below
Close exemplified by accompanying drawing introduces client acquisition broadcasting record and be described.
The equipment that synchronous viewing record is kept between a variety of viewing equipment that the present embodiment is provided, in addition to：Obtain and play
Request receiving module 100, video ID list lookups module 200 are recorded, record acquisition module 300 is played and plays record and returns to mould
Block 400；
The acquisition, which is played, records request receiving module 100, for receiving asking for the acquisition broadcasting record that client is sent
Ask, described obtain carries ID, video ID and video type in the request for playing record；
It should be noted that when user actively clicks on video, explanation is to need to obtain to play record, now viewing equipment
Client is sent from trend server end obtains the request for playing record.
The video ID list lookups module 200, for searching ID correspondence from caching according to the ID
User viewing video ID list；If searching the video ID of user's viewing corresponding less than ID row in caching
Table is searched from database again；
It is described to play record acquisition module 300, for the list of the video ID by finding, obtained from caching
The broadcasting record of video；If there is no the record of playing to be obtained again from database in caching；
The record of playing returns to module 400, for the broadcasting record to be returned into client.
It should be noted that the method provided in an embodiment of the present invention for obtaining broadcasting record is to be based on embodiment of the method or side
On the basis of method embodiment two, received server-side finds that the request is corresponding to be broadcast to after obtaining the request playing and record
Put record and return to client.
The method and apparatus that synchronous viewing record is provided between the one kind of multiple viewing equipment provided based on above example,
The embodiment of the present invention additionally provides the system for keeping synchronous viewing to record between one kind of multiple viewing equipment, enters below in conjunction with the accompanying drawings
The detailed introduction of row.
System embodiment one：
The system of synchronous viewing record is kept to implement referring to Fig. 7, between a variety of viewing equipment that the figure provides for the present invention
The schematic diagram of example one.
This implementation provides the system for keeping synchronous viewing to record between one kind of multiple viewing equipment, including：Client 1000,
Server end 2000；
The client 1000, the request recorded is played for sending to report to the server end 2000, described to report
Play and video ID, ID, current play time, the affiliated special edition ID of video, video type and client are carried in the request of record
Hold type；
It should be noted that when user sees video using client sight 1000, it is necessary to report broadcasting to record, broadcasting is recorded
Including video ID, ID, current play time.Special edition ID, video type and client type described in video；
Wherein, current play time refers to that the video of user's viewing is currently viewing and which point which etc. has been arrived second.
Wherein, client type can be divided into pc client, and mobile client etc..Mobile client is, for example, mobile phone
Client, PAD clients etc..
When user watches video using pc client, viewing equipment can regularly report viewing to record, such as every two points
Clock is reported once.When user watches video using the client on mobile phone, when logging off, viewing equipment can be recorded to cloud
Service end reports broadcasting to record.
Wherein, special edition described in video refers to possessing the video collection of denominator, and such as certain TV play is properly termed as
One special edition, the video of a TV play belongs in same special edition, but may to belong to one or more special for a video
Volume, it is also possible to it is not belonging to any special edition.
Client 1000 will report broadcasting record request to be sent to LVS first；
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX will report broadcasting record request to be forwarded to corresponding WEB terminal server as reverse proxy.
The server end 2000, for the difference according to ID, reports the request for playing record to be sent to by described
In the different Message Queuing Middlewares divided in advance, the number at least two of the Message Queuing Middleware；Disappear described
Cease in queue middleware, be that a video only retains a broadcasting record, what deletion video ID and special edition ID were repeated reports broadcasting
Record；The record unique ID of generation is played to be described, by carrying unique ID broadcasting record storage to caching and database
In.
It should be noted that the Message Queuing Middleware can be realized by Memcacheq, it can also be disappeared by others
Queue middleware is ceased to realize.
Specific how to be divided according to the difference of ID reports broadcasting to recorded in different Memcacheq queues, can
To be set from origin, for example, when setting two different Memcacheq queues, ID for even number can be placed on one
In individual Memcacheq queues, by ID being placed in another Memcacheq queue for odd number.
When setting three different Memcacheq queues, it is possible to use seek the algorithm of 3 remainder（%3）, by ID
Remmed to 3, be 0,1 and 2 to be respectively put into first Memcacheq queue, in second Memcacheq queue according to remainder
And in the 3rd Memcacheq queue.
It is understood that when there is two Memcacheq queues, can also be remmed using ID to 2, remainder is
0 is put into two different Memcacheq queues with 1, for example, remainder is put into first Memcacheq queue for 0, remainder
It is put into for 1 in second Memcacheq queue.
Such as ID is 3438434, it is possible to use the numerical value rems to 2.
It is understood that server end can parse the various letters reported in broadcasting record request of client transmission first
Breath, the information includes video ID, ID, current play time.Special edition ID, video type and client type described in video；
It should be noted that first the request for playing record will be reported to be sent to different message teams in the embodiment of the present invention
In row middleware, so primarily to preventing that the request queue for reporting broadcasting to record is oversize, server response is too slow.
It is understood that the specific number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but
It is minimum needs two, a Message Queuing Middleware is not different with prior art, and not having prevents the too long of effect of queue.
Because the broadcasting record of reporting of user has a lot, for example, the video of user's viewing is a TV play, now
The 16th collection is seen, the broadcasting record of the 1st the-the 15 collection of collection can all be deleted, only retain the broadcasting record of the 16th collection.Because objective
Family is not intended to chase after when seeing a TV play, it is seen that oneself playing has same portion's TV play multiple broadcastings in record are recorded.
The system that synchronous viewing record is kept between a variety of viewing equipment provided in an embodiment of the present invention, according to ID
Difference, described report is played the request that records and is sent in the different Message Queuing Middlewares divided in advance, so can be with
Avoid reporting the queue for playing record oversize, so that the request at customer in response end is accelerated, in addition, in order to which a video only retains
Portion plays record, and that deletes that video ID and special edition ID repeat reports broadcasting to record, and can so reduce caching or database
Space-consuming, and the broadcasting record of request can be quickly found when client obtains and plays record, so as to accelerate to ask
The response asked.
System embodiment two：
The system that the present embodiment is provided, the server end 2000 reports broadcasting to remember according to the difference of ID by described
Before the request of record is sent in the different Message Queuing Middlewares divided in advance, in addition to：
Broadcasting record request is reported first to be stored in thread pool for pc client the client type, every predetermined
Time is using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
Due to when client is pc client, due to pc client, to send rule more random, easily exist it is many repeat,
Interval time is very short to report the request played and recorded, and once reports broadcasting to record for example, pc client was sent every two minutes
Request, so just have within an hour it is substantial amounts of report broadcasting record.In order to mitigate server end in the present embodiment
Pressure, is just sent in different Message Queuing Middlewares after WEB terminal plays the request duplicate removal of record to reporting.
The mode of specific duplicate removal is to run each thread in the thread pool that a size can extend, thread pool to have certainly
Oneself obstruction queue, each obstruction queue is used for preserving the request for reporting broadcasting to record of client.Each thread each makes a reservation for
Time goes to report the request played and recorded in the obstruction queue of oneself described in taking-up, uses hash duplicate removals.
Due to there is multiple servers reporting in processing Message Queuing Middleware to play the request recorded, if using biography
The method that ID generates ID from increasing in the database of system, can be impacted to database, therefore, and REDIS is used in the present embodiment
To play the unique ID of record generation.
The advantage for the system that the present embodiment is provided is to report broadcasting record request to be put into message queue pc client
Before in middleware, first broadcasting record request is reported to carry out duplicate removal processing pc client, because pc client transmission is upper
Report play record request exist it is many repeat, time interval very short request, service can be mitigated after the request repeated by deleting
The pressure at device end, so as to accelerate the response time.
It should be noted that after the broadcasting record that server end reports client is preserved successfully, can be with JSON numbers
According to return preserve whether successful feedback message.
Above example is described so that client reports broadcasting to record as an example, and client is described below and obtains broadcasting
It is described exemplified by record.
The client 1000, is additionally operable to send the request for obtaining and playing and recording to the server end 2000, described to obtain
Take and ID, video ID and video type are carried in the request played and recorded；
The server end 2000, is additionally operable to search the corresponding user's sight of the ID from caching according to the ID
The video ID seen list；If searching the video ID of user's viewing corresponding less than ID list in caching again from number
Searched according in storehouse；By the video ID found list, the broadcasting record of video is obtained from caching；If in caching
There is no the record of playing to be obtained again from database；The broadcasting record is returned into client.
The method, apparatus and system that above example of the present invention is provided, are capable of the request at very fast customer in response end, Ke Yi
Realize that user plays the synchronization of record between multiple terminals.
The above described is only a preferred embodiment of the present invention, not making any formal limitation to the present invention.Though
So the present invention is disclosed above with preferred embodiment, but is not limited to the present invention.It is any to be familiar with those skilled in the art
Member, without departing from the scope of the technical proposal of the invention, all using the methods and techniques content of the disclosure above to the present invention
Technical scheme makes many possible variations and modification, or is revised as the equivalent embodiment of equivalent variations.Therefore, it is every without departing from
The content of technical solution of the present invention, the technical spirit according to the present invention is to any simple modification made for any of the above embodiments, equivalent
Change and modify, still fall within technical solution of the present invention protection in the range of.
Claims (11)
1. the method for synchronous viewing record is kept between one kind of multiple viewing equipment, it is characterised in that including：
The request for reporting broadcasting to record that client is sent is received, described report carries video ID, use in the request played and recorded
The affiliated special edition ID of family ID, current play time, video, video type and client type；The client type includes：PC visitors
Family end and mobile client；When the client type is pc client, the pc client can regularly report broadcasting to record
Request；When the client type is mobile client, the mobile client reports broadcasting to record when logging off
Request；
According to the difference of ID, the request for playing record is reported to be sent in the different message queues divided in advance by described
Between in part, the number at least two of the Message Queuing Middleware；
In the Message Queuing Middleware, it is that a video only retains a broadcasting record, deletes video ID and special edition ID weights
Multiple reports broadcasting to record；
The record unique ID of generation is played to be described, by carrying unique ID broadcasting record storage to caching and database
In.
2. the method for synchronous viewing record is kept between a variety of viewing equipment according to claim 1, it is characterised in that institute
The difference according to ID is stated, reports the request for playing record to be sent in the middle of the different message queues divided in advance by described
Before in part, in addition to：
Broadcasting record request is reported first to be stored in thread pool for pc client the client type, at predetermined time intervals
Using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
3. the method for synchronous viewing record is kept between a variety of viewing equipment according to claim 1, it is characterised in that institute
State and play the record unique ID of generation to be described, be specially：
It is that the record of playing generates globally unique ID using REDIS as distributed ID makers.
4. keeping the method for synchronous viewing record between a variety of viewing equipment according to claim any one of 1-3, it is special
Levy and be, in addition to：
The request for the acquisition broadcasting record that client is sent is received, the acquisition, which is played, to be carried ID, regards in the request of record
Frequency ID and video type；
The list for the video ID that the corresponding user of the ID watches is searched from caching according to the ID；If in caching
The list for searching the video ID of user's viewing corresponding less than the ID is searched from database again；
By the video ID found list, the broadcasting record of video is obtained from caching；If there is no institute in caching
Broadcasting record is stated to obtain from database again；
The broadcasting record is returned into client.
5. the equipment of synchronous viewing record is kept between one kind of multiple viewing equipment, it is characterised in that including：Broadcasting is reported to record
Request receiving module, broadcasting record request division module is reported, record deduplication module is played, plays and Record ID generation module and broadcast
Put record storage module；
It is described to report broadcasting record request receiving module, the request recorded is played for receiving reporting for client transmission, it is described
Report in broadcasting record request and carry video ID, ID, current play time, the affiliated special edition ID of video, video type and visitor
Family end type；The client type includes：Pc client and mobile client；When the client type is pc client
When, the pc client can regularly report the request played and recorded；When the client type is mobile client, the shifting
Dynamic client reports the request played and recorded when logging off；
Described report plays record request division module, and for the difference according to ID, described report is played into asking for record
Ask in the different Message Queuing Middlewares for being sent to and dividing in advance, the number at least two of the Message Queuing Middleware；
It is described to play record deduplication module, in the Message Queuing Middleware, being that a video only retains a broadcasting
Record, delete video ID and special edition ID repetitions reports broadcasting to record；
The broadcasting Record ID generation module, for playing the unique ID of record generation to be described；
The broadcasting record storage module, will carry the broadcasting record storage of unique ID into caching and database.
6. the equipment of synchronous viewing record is kept between a variety of viewing equipment according to claim 5, it is characterised in that also
Record request deduplication module is played including reporting；
It is described to report broadcasting record request deduplication module, for reporting broadcasting to record for pc client the client type
Request is first stored in thread pool, at predetermined time intervals using hash to reporting broadcasting record request to carry out in the thread pool
Duplicate removal.
7. the equipment of synchronous viewing record is kept between a variety of viewing equipment according to claim 5, it is characterised in that institute
Stating broadcasting Record ID generation module includes playing Record ID generation submodule, for using REDIS as distributed ID makers,
The globally unique ID of record generation is played to be described.
8. keeping the equipment of synchronous viewing record between a variety of viewing equipment according to claim any one of 5-7, it is special
Levy and be, in addition to：Obtain play record request receiving module, video ID list lookups module, play record acquisition module and
Play record and return to module；
Described obtain plays record request receiving module, and the request of record is played in the acquisition for receiving client transmission, described
Obtain and ID, video ID and video type are carried in the request for playing record；
The video ID list lookup modules, see for searching the corresponding user of the ID from caching according to the ID
The video ID seen list；If searching the video ID of user's viewing corresponding less than ID list in caching again from number
Searched according in storehouse；
It is described to play record acquisition module, for the list of the video ID by finding, video is obtained from caching
Play record；If there is no the record of playing to be obtained again from database in caching；
The record of playing returns to module, for the broadcasting record to be returned into client.
9. the system of synchronous viewing record is kept between one kind of multiple viewing equipment, it is characterised in that including：Client, service
Device end；
The client, the request recorded is played for being reported to server end transmission, and described report plays asking for record
Ask middle carrying video ID, ID, current play time, the affiliated special edition ID of video, video type and client type；The visitor
Family end type includes：Pc client and mobile client；When the client type is pc client, the pc client meeting
Timing reports the request played and recorded；When the client type is mobile client, the mobile client is stepped on exiting
The request played and recorded is reported during record；
The server end, for the difference according to ID, reports the request for playing record to be sent to advance division by described
Different Message Queuing Middlewares in, the number at least two of the Message Queuing Middleware；In the message queue
Between in part, be a video only retain it is a play record, that deletes that video ID and special edition ID repeats reports broadcasting to record；For institute
The broadcasting record unique ID of generation is stated, the broadcasting record storage of unique ID will be carried into caching and database.
10. the system of synchronous viewing record is kept between a variety of viewing equipment according to claim 9, it is characterised in that
The server end according to the difference of ID, by it is described report to play the request that records and be sent to divide in advance different disappear
Before ceasing in queue middleware, in addition to：
Broadcasting record request is reported first to be stored in thread pool for pc client the client type, at predetermined time intervals
Using hash to reporting broadcasting record request to carry out duplicate removal in the thread pool.
11. keeping the system of synchronous viewing record between a variety of viewing equipment according to claim 9 or 10, its feature exists
In the client is additionally operable to send the request that record is played in acquisition to the server end, asking for record is played in the acquisition
Ask middle carrying ID, video ID and video type；
The server end, is additionally operable to search the video that the corresponding user of the ID watches from caching according to the ID
ID list；If the list that the video ID of user's viewing corresponding less than the ID is searched in caching is looked into from database again
Look for；By the video ID found list, the broadcasting record of video is obtained from caching；If without described in caching
Record is played to obtain from database again；The broadcasting record is returned into client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410037487.0A CN103731682B (en) | 2014-01-26 | 2014-01-26 | Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410037487.0A CN103731682B (en) | 2014-01-26 | 2014-01-26 | Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103731682A CN103731682A (en) | 2014-04-16 |
| CN103731682B true CN103731682B (en) | 2017-09-22 |
Family
ID=50455583
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410037487.0A Active CN103731682B (en) | 2014-01-26 | 2014-01-26 | Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103731682B (en) |
Families Citing this family (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104822090B (en) * | 2014-04-25 | 2017-12-01 | 腾讯科技（北京）有限公司 | The methods, devices and systems of video playback |
| CN105007504B (en) * | 2015-07-13 | 2018-10-26 | 无锡天脉聚源传媒科技有限公司 | A kind of browsing record processing method and processing device |
| CN105872720A (en) * | 2015-11-25 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Method and device for screening playing records in video application |
| CN105657473A (en) * | 2015-11-25 | 2016-06-08 | 乐视云计算有限公司 | Data processing method and device |
| CN105681428A (en) * | 2016-01-25 | 2016-06-15 | 浪潮软件股份有限公司 | User information synchronizing system, method and device |
| WO2018018457A1 (en) * | 2016-07-27 | 2018-02-01 | 黄新勇 | Method and system for distinguishing watching types in television broadcasting |
| CN107172492A (en) * | 2017-06-06 | 2017-09-15 | 环球智达科技（北京）有限公司 | A kind of reporting system for playing record |
| CN107396181B (en) * | 2017-08-24 | 2019-10-11 | 广州创维平面显示科技有限公司 | A kind of shared method, storage medium and smart television for playing record |
| CN112508380A (en) * | 2020-12-03 | 2021-03-16 | 浪潮云信息技术股份公司 | System and method applied to asynchronous processing of high-concurrency evaluation data |
| CN114302186A (en) * | 2021-12-29 | 2022-04-08 | 湖南快乐阳光互动娱乐传媒有限公司 | Play record processing method and related device |
| CN114051162B (en) * | 2022-01-12 | 2022-04-26 | 飞狐信息技术（天津）有限公司 | Caching method and device based on play records |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101027906A (en) * | 2004-07-27 | 2007-08-29 | 夏普株式会社 | Pseudo video-on-demand system, pseudo video-on-demand system control method, and program and recording medium used for the same |
| CN103152653A (en) * | 2013-02-05 | 2013-06-12 | 东莞宇龙通信科技有限公司 | Method and system for playing stream media files |
| CN103475939A (en) * | 2013-09-02 | 2013-12-25 | 小米科技有限责任公司 | Method, device and server for processing play record |
-
2014
- 2014-01-26 CN CN201410037487.0A patent/CN103731682B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101027906A (en) * | 2004-07-27 | 2007-08-29 | 夏普株式会社 | Pseudo video-on-demand system, pseudo video-on-demand system control method, and program and recording medium used for the same |
| CN103152653A (en) * | 2013-02-05 | 2013-06-12 | 东莞宇龙通信科技有限公司 | Method and system for playing stream media files |
| CN103475939A (en) * | 2013-09-02 | 2013-12-25 | 小米科技有限责任公司 | Method, device and server for processing play record |
Non-Patent Citations (1)
| Title |
|---|
| 《互联网广告经营管理***的设计与实现》;魏之春;《中国优秀硕士学位论文全文数据库》;20101015;第5至第6章及图5-1、图5-3、图6-1 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103731682A (en) | 2014-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103731682B (en) | Method, equipment and the system of synchronous viewing record are kept between a variety of viewing equipment | |
| US20140165119A1 (en) | Offline download method, multimedia file download method and system thereof | |
| CN100505630C (en) | A method and system for broadcasting buffered advertisement in polling mode under the network living broadcast environment | |
| CN104581374B (en) | A kind of method, node and server for obtaining section file and generating sub- m3u8 files | |
| US20160227258A1 (en) | Method for playing back live video and device | |
| CN108366292B (en) | Cross-network video live broadcast method and system based on streaming media | |
| CN109002484B (en) | Method and system for sequentially consuming data | |
| CN107801051B (en) | Virtual sliced sheet information transferring method and device, video server | |
| CN103634616B (en) | A kind of stream media ordering method and device based on cloud storage | |
| CN105187950B (en) | A kind of method, apparatus and system that video file plays | |
| CN104348859B (en) | File synchronisation method, device, server, terminal and system | |
| CN110457305B (en) | Data deduplication method, device, equipment and medium | |
| CN108235051B (en) | Live broadcast system and method for storing and acquiring live broadcast data | |
| CN107203532A (en) | Construction method, the implementation method of search and the device of directory system | |
| CN106790454A (en) | Deferred information method for pushing and device | |
| CN103997662A (en) | Program pushing method and system | |
| CN104333813A (en) | Video playing method, device and system | |
| CN109842804A (en) | Processing method and server, the computer storage medium of audio, video data | |
| CN106331089A (en) | Video play control method and system | |
| CN107888941B (en) | Video segment transmission method, device and system | |
| CN108491499B (en) | Data acquisition method, data acquisition platform, client and business server | |
| CN105979297B (en) | One kind watching duration statistical method and system | |
| CN104168174A (en) | Method and apparatus for information transmission | |
| CN111346377A (en) | Recording and playback method and device for online game, server and terminal | |
| CN104753811A (en) | Streaming medium service optimizing method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |