CN103731682A - Method, device and system for keeping synchronous watching record among multiple film watching devices - Google Patents
Method, device and system for keeping synchronous watching record among multiple film watching devices Download PDFInfo
- Publication number
- CN103731682A CN103731682A CN201410037487.0A CN201410037487A CN103731682A CN 103731682 A CN103731682 A CN 103731682A CN 201410037487 A CN201410037487 A CN 201410037487A CN 103731682 A CN103731682 A CN 103731682A
- Authority
- CN
- China
- Prior art keywords
- record
- video
- request
- broadcasting
- user
- 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.)
- Granted
Links
Images
Abstract
The invention provides a method, device and system for keeping synchronous watching record among multiple film watching devices. The method comprises the following steps: receiving a request of a reporting playing record sent by a client, wherein the request of the reporting playing record carries a video ID (Identification), a user ID, current playing time, ID of an album to which the video belongs, a video type and a client type; according to the difference of the user ID, sending the request of the reporting playing record to pre-divided different message queuing middlewares, wherein the quantity of the message queuing middlewares is at least two; only preserving a replaying record for one video, deleting repeated reporting playing records of the video ID and the album ID; generating a unique ID for the replaying records, and storing the playing records carrying the unique ID into a cache and a database. According to the method, the request of responding the client can be accelerated, and the occupation space of the cache or database is reduced.
Description
Technical field
The present invention relates to video playback technical field, particularly between one kind of multiple viewing equipment, keep synchronously watching method, the equipment and system of record.
Background technology
Several major names of paper this area:
Cloud record: a kind of service end account form, client does not retain any data, directly user record is reported to server end fast, by the calculating of server end complexity, by the preservation of withing a hook at the end property of result.
User-generated content (UGC, User Generated Content): user shows own original content or offers other users by internet platform.
Memcacheq: a kind of message-oriented middleware product, effect is the data relay platform as the message producer and consumer.
LVS: the scheduler of realizing load balancing between Web cluster.
NGINX (Engine x): high performance HTTP and Reverse Proxy.
REDIS: a high performance key-value (Key-value) storage system.
MYSQL: a high performance Relational DBMS.
JSON(JavaScript Object Notation): the data interchange format that is a kind of lightweight.It is based on JavaScript(Standard ECMA-2623rd Edition-December1999) a subset.JSON adopts the text formatting that is totally independent of language, but has also used the custom (comprising C, C++, C#, Java, JavaScript, Perl, Python etc.) that is similar to C family of language.These characteristics make JSON become desirable exchanges data language.
Because cloud computing is in high development period, therefore, increasing businessman and the Internet giant start in the research and development of the technology of putting into and the popularization of application, and the technology of cloud computing also progressively moves to maturity and be perfect.Cloud service end can be regarded a small-sized cloud system as.Client only need to simply report and obtain broadcasting record, and complicated calculating and storage problem are given the processing of cloud service end.
Cloud service end is used Web cluster to process request, realizes the load balancing between server with LVS.Use Distributed Services to guarantee the stability of service, when there being service because network or machine reason while hanging, can be switched to other services.Use Message Queuing Middleware to preserve the request that reports, use JAVA Thread Pool Technology asynchronous process to report request.Storage aspect, is used REDIS as buffer memory, uses MYSQL as database.
For video website, when user watches video, viewing equipment can record service end and report to cloud this user's the record of watching, and the video of wherein watching record to comprise that user watches is the playing progress rate of what and this video.When user uses the client of PC end to watch video, viewing equipment can regularly report and watch record, for example, every two minutes, report once.When user uses client on mobile phone to watch video, when logging off, viewing equipment can record service end to cloud and report broadcasting record.
For cloud, record service end, receive viewing equipment and report while playing the request of recording, deposit buffer memory and database in; Receive viewing equipment and obtain while playing the request of recording, preferentially from buffer memory, search, in buffer memory, do not go again to search in database, return to JSON data format.
At present, along with the customer volume rising of website and the diversity of viewing equipment increase, the visit capacity of video increases sharply, and client upload is play the concurrency recording will be very large, directly the service of calling may can not get responding timely, even can cause the collapse of the overtime or service of calling.Therefore, prior art exists uploads that to play record reaction slow or upload the problem of failure, and client plays while recording obtaining, and response also has certain delay.
Summary of the invention
The technical problem to be solved in the present invention is to provide the method, the equipment and system that between one kind of multiple viewing equipment, keep synchronously watching record, can respond in time and play reporting and obtaining of record.
The embodiment of the present invention provides the method that between one kind of multiple viewing equipment, record is synchronously watched in maintenance, comprising:
Receive the request of playing record that reports that client sends, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
According to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, the number of described Message Queuing Middleware is at least two;
In described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record;
For described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
Preferably, described according to the difference of user ID, before the described request that reports broadcasting to record is sent in the different Message Queuing Middleware of dividing in advance, also comprise:
The broadcasting record request that reports that is pc client by described client type is first kept in thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
Preferably, described is that described broadcasting record generates unique ID, is specially:
Use REDIS as distributed I D maker, for described broadcasting record generates the unique ID of the overall situation.
Preferably, also comprise:
Receive client send obtain play record request, described in obtain play record request in carry user ID, video ID and video type;
According to described user ID, from buffer memory, search the list of the video ID that user corresponding to this user ID watch; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again;
By the list of the described video ID that finds, from buffer memory, obtain the broadcasting record of video; If do not have described broadcasting record to obtain from database again in buffer memory;
Described broadcasting record is returned to client.
The embodiment of the present invention also provides between one kind of multiple viewing equipment the equipment that keeps synchronously watching record, comprising: report and play record request receiver module, report and play record request and divide module, play and record duplicate removal module, play Record ID generation module and memory module is recorded in broadcasting;
Described reporting play record request receiver module, for receiving the request of playing record that reports that client sends, described in report to play and carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type in record request;
Described reporting play record request division module, for according to the difference of user ID, by described, reports the request of playing record to send in the different Message Queuing Middleware of dividing in advance, and the number of described Message Queuing Middleware is at least two;
Duplicate removal module is recorded in described broadcasting, at described Message Queuing Middleware, is that a video only retains a record of playing, and that deletes that video ID and special edition ID repeat reports broadcasting record;
Described broadcasting Record ID generation module, is used to described broadcasting record to generate unique ID;
Memory module is recorded in described broadcasting, and the broadcasting record that carries described unique ID is stored in buffer memory and database.
Preferably, also comprise and report broadcasting record request duplicate removal module;
Described reporting play record request duplicate removal module, for the broadcasting record request that reports that is pc client by described client type, is first kept at thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
Preferably, described broadcasting Record ID generation module comprises that playing Record ID generates submodule, for using REDIS as distributed I D maker, for described broadcasting record generates the unique ID of the overall situation.
Preferably, also comprise: obtain and play record request receiver module, video ID list is searched module, play and record acquisition module and play record and return to module;
Described obtaining play record request receiver module, for receiving the request of playing record of obtaining that client sends, described in obtain in the request of playing record and carry user ID, video ID and video type;
Module is searched in described video ID list, for search the list of the video ID that user corresponding to this user ID watch from buffer memory according to described user ID; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again;
Acquisition module is recorded in described broadcasting, for the list of the described video ID by finding, obtains the broadcasting record of video from buffer memory; If do not have described broadcasting record to obtain from database again in buffer memory;
Described broadcasting record returns to module, for described broadcasting record is returned to client.
The embodiment of the present invention also provides the system that between one kind of multiple viewing equipment, record is synchronously watched in maintenance, comprising: client, server end;
Described client, for send the request of playing record that reports to described server end, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
Described server end, for according to the difference of user ID, reports the request of playing record to send in the different Message Queuing Middleware of dividing in advance by described, and the number of described Message Queuing Middleware is at least two; In described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record; For described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
10, the system that between multiple viewing equipment according to claim 9, record is synchronously watched in maintenance, it is characterized in that, described server end, according to the difference of user ID, before the described request that reports broadcasting to record is sent in the different Message Queuing Middleware of dividing in advance, also comprises:
The broadcasting record request that reports that is pc client by described client type is first kept in thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
11, according to the system that keeps between the multiple viewing equipment described in claim 9 or 10 synchronously watching record, it is characterized in that, described client, also for send the request of playing record of obtaining to described server end, described in obtain in the request of playing record and carry user ID, video ID and video type;
Described server end, also for searching the list of the video ID that user corresponding to this user ID watch from buffer memory according to described user ID; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again; By the list of the described video ID that finds, from buffer memory, obtain the broadcasting record of video; If do not have described broadcasting record to obtain from database again in buffer memory; Described broadcasting record is returned to client.
Compared with prior art, the present invention has the following advantages:
Between the multiple viewing equipment that the embodiment of the present invention provides, keep the method for synchronously watching record, according to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, can avoid like this reporting the queue of broadcasting record oversize, thereby the request of customer in response end is accelerated, in addition, for a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record, can reduce like this taking up room of buffer memory or database, and obtain the broadcasting record that can find quickly request when broadcasting is recorded in client, thereby accelerate the response of request.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skills, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is embodiment of the method one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 2 is embodiment of the method two schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 3 is embodiment of the method three schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 4 is apparatus embodiments one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 5 is apparatus embodiments two schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 6 is apparatus embodiments three schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention;
Fig. 7 is system embodiment one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention.
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 clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, rather than whole embodiment.Based on the embodiment in the present invention, those of ordinary skills, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
For above-mentioned purpose of the present invention, feature and advantage can be become apparent more, below in conjunction with accompanying drawing, the specific embodiment of the present invention is described in detail.
Embodiment of the method one:
Referring to Fig. 1, this figure is embodiment of the method one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention.
Between the multiple viewing equipment that the present embodiment provides, keep the method for synchronously watching record, comprise the following steps:
S101: receive the request of playing record that reports that client sends, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
It should be noted that, when user uses client to watch video, need to report broadcasting record, play record and comprise video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
Wherein, current reproduction time refers to, and video that user watches is current has watched which second of which point etc.
Wherein, client type can be divided into pc client, and mobile client etc.Mobile client is for example cell-phone customer terminal, PAD client etc.
When user uses the client of PC end to watch video, viewing equipment can regularly report and watch record, for example, every two minutes, report once.When user uses client on mobile phone to watch video, when logging off, viewing equipment can record service end to cloud and report broadcasting record.
Wherein, described in video, special edition refers to the video set that has denominator, and for example certain TV play can be called a special edition, and the video of a TV play belongs in same special edition, but a video may belong to one or more special edition, also may not belong to any special edition.
First client will report broadcasting record request to send to LVS;
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX, as reverse proxy, will report broadcasting record request to be forwarded to corresponding WEB end server.
S102: according to the difference of user ID, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance by described, the number of described Message Queuing Middleware is at least two;
It should be noted that, described Message Queuing Middleware can be realized by Memcacheq, also can be realized by other Message Queuing Middleware.
Specifically how according to the difference of user ID, to divide to report to play and be recorded in different Memcacheq queues, can set from origin, for example, when two different Memcacheq queues are set, what can be even number by user ID be placed in a Memcacheq queue, and what by user ID, be odd number is placed in another Memcacheq queue.
When three different Memcacheq queues are set, can utilize the algorithm (%3) of the remainder of asking 3, user ID is remmed to 3, is 0,1 and 2 to put into respectively first Memcacheq queue, second Memcacheq queue and the 3rd Memcacheq queue according to remainder.
Be understandable that, when having two Memcacheq queues, also can utilize user ID to rem to 2, remainder is 0 and 1 to put into two different Memcacheq queues, for example, remainder is 0 to put into first Memcacheq queue, and remainder is 1 to put into second Memcacheq queue.
For example user ID is 3438434, can utilize this numerical value to rem to 2.
Be understandable that, first server end can resolve the various information of playing in record request that report of client transmission, and this information comprises video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
It should be noted that, first will report the request of playing record to send in different Message Queuing Middlewares in the embodiment of the present invention, main is like this oversize in order to prevent reporting the request queue of broadcasting record, and server response is too slow.
Be understandable that, the concrete number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but two of minimum needs, and Message Queuing Middleware and prior art are as broad as long, do not have the effect that prevents that queue is oversize.
S103: in described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record;
Because the broadcasting record of reporting of user has a lot, for example, the video that user watches is a TV play, has seen now the 16th collection, and the broadcasting that the 1st collection-15 can be collected record is all deleted, and only retains the broadcasting record of the 16th collection.Because client does not wish to chase after while seeing a TV play, see and oneself play the multiple broadcasting records that have same portion TV play in record.
S104: for described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
Between the multiple viewing equipment that the embodiment of the present invention provides, keep the method for synchronously watching record, according to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, can avoid like this reporting the queue of broadcasting record oversize, thereby the request of customer in response end is accelerated, in addition, for a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record, can reduce like this taking up room of buffer memory or database, and obtain the broadcasting record that can find quickly request when broadcasting is recorded in client, thereby accelerate the response of request.
Embodiment of the method two:
Referring to Fig. 2, this figure is embodiment of the method two schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention.
Due to when client is pc client, because pc client transmission rule is more random, easily there is a lot of repetitions, the very short request that reports broadcasting record interval time, for example, pc client sent and once reports the request of playing record every two minutes, just had so within an hour a large amount of broadcasting records that report.In the present embodiment in order to alleviate the pressure of server end, just send in different Message Queuing Middlewares after reporting the request duplicate removal of playing record at WEB end.
As an example of embodiment of the method two example, describe below.
S201 in the present embodiment is identical with the S101 in embodiment of the method one, does not repeat them here.
S202: judge that according to client type whether client is pc client, if not pc client, carries out S204; If pc client is carried out S203;
S203: the broadcasting record request that reports that is pc client by described client type is first kept in thread pool, is used hash to play record request to reporting in described thread pool every the scheduled time and carries out duplicate removal.
Specifically the mode of duplicate removal is, moves a thread pool that size can be expanded, and in thread pool, each thread has the obstruction queue of oneself, and each obstruction queue is used for preserving the request of playing record that reports of client.Each scheduled time of each thread reports the request of playing record described in going to take out in oneself obstruction queue, uses hash duplicate removal, then reporting after duplicate removal is play to record and carries out the processing of S204.
Particularly, first WEB end selects one not at the thread of operation in thread pool, by playing record from reporting of pc client, sends in the obstruction queue of this thread.
S204 is identical with the S102 in embodiment of the method one, does not repeat them here.
S205: first judge in Message Queuing Middleware whether effectively reporting user ID in the request of playing record and special edition ID whether effective; If effectively,, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record;
S206: use REDIS as distributed ID maker, generate the unique ID of the overall situation for playing record, the broadcasting record that carries described unique ID is stored in buffer memory and database.
Owing to there being multiple servers reporting in processing messages queue middleware, play the request of recording, if generate the method for ID from increasing with ID in traditional database, can impact database, because when request amount is large, peak time the request increment having more than 1,000 per second, very large on the impact of database like this, database faces very large pressure.Therefore, in the present embodiment, adopt REDIS to come to generate unique ID for playing record.
Request in multiple servers while processing messages queue middlewares, can accelerate response speed, the request stacking while avoiding a server process like this.
The advantage of the method that the present embodiment provides is, reporting of pc client play before record request puts into Message Queuing Middleware, first reporting of pc client play to record request and carry out duplicate removal processing, because there is a lot of repetitions, very short request of the time interval in the broadcasting record request that reports that pc client sends, after deleting the request repeating, can alleviate the pressure of server end, thereby accelerate the response time.
It should be noted that, after broadcasting record client being reported at server end is preserved successfully, can return to whether successfully feedback message of preservation with JSON data.
Embodiment of the method three:
Embodiment of the method one and embodiment of the method two report to play with client and are recorded as example and are described, and introduce client obtain to play and be recorded as example and be described below in conjunction with accompanying drawing.
Referring to Fig. 3, this figure is embodiment of the method three schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention.
S301: receive client send obtain play record request, described in obtain play record request in carry user ID, video ID and video type;
It should be noted that, when user initiatively clicks video, explanation is to obtain broadcasting record, and now the client of viewing equipment sends from trend server end the request of playing record of obtaining.
S302: the list of searching the video ID that user corresponding to this user ID watch according to described user ID from buffer memory; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again;
S303: by the list of the described video ID that finds, obtain the broadcasting record of video from buffer memory; If do not have described broadcasting record to obtain from database again in buffer memory;
S304: described broadcasting record is returned to client.
It should be noted that, the embodiment of the present invention provides, and to obtain the method for playing record be on the basis based on embodiment of the method or embodiment of the method two, and server end receives and obtains the broadcasting record that finds this request correspondence after the request of playing record and return to client.
The method of synchronously watching record is provided between the multiple viewing equipment providing based on above embodiment, and the embodiment of the present invention also provides the equipment that keeps synchronously watching record between one kind of multiple viewing equipment, below in conjunction with accompanying drawing, describes in detail.
Referring to Fig. 4, this figure is apparatus embodiments one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention.
Apparatus embodiments one:
Between the multiple viewing equipment that the embodiment of the present invention provides, the equipment of record is synchronously watched in maintenance, comprising: report and play record request receiver module 400, report broadcasting record request division module 500, broadcasting to record duplicate removal module 600, broadcasting Record ID generation module 700 and broadcasting and record memory module 800;
Report and play record request receiver module 400, for receiving the request of playing record that reports that client sends, described in report to play and carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type in record request;
It should be noted that, when user uses client to watch video, need to report broadcasting record, play record and comprise video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
Wherein, current reproduction time refers to, and video that user watches is current has watched which second of which point etc.
Wherein, client type can be divided into pc client, and mobile client etc.Mobile client is for example cell-phone customer terminal, PAD client etc.
When user uses the client of PC end to watch video, viewing equipment can regularly report and watch record, for example, every two minutes, report once.When user uses client on mobile phone to watch video, when logging off, viewing equipment can record service end to cloud and report broadcasting record.
Wherein, described in video, special edition refers to the video set that has denominator, and for example certain TV play can be called a special edition, and the video of a TV play belongs in same special edition, but a video may belong to one or more special edition, also may not belong to any special edition.
First client will report broadcasting record request to send to LVS;
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX, as reverse proxy, will report broadcasting record request to be forwarded to corresponding WEB end server.
Report and play record request division module 500, for according to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, the number of described Message Queuing Middleware is at least two;
Be understandable that, first server end can resolve the various information of playing in record request that report of client transmission, and this information comprises video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
It should be noted that, described Message Queuing Middleware can be realized by Memcacheq, also can be realized by other Message Queuing Middleware.
Specifically how according to the difference of user ID, to divide to report to play and be recorded in different Memcacheq queues, can set from origin, for example, when two different Memcacheq queues are set, what can be even number by user ID be placed in a Memcacheq queue, and what by user ID, be odd number is placed in another Memcacheq queue.
When three different Memcacheq queues are set, can utilize the algorithm (%3) of the remainder of asking 3, user ID is remmed to 3, is 0,1 and 2 to put into respectively first Memcacheq queue, second Memcacheq queue and the 3rd Memcacheq queue according to remainder.
Be understandable that, when having two Memcacheq queues, also can utilize user ID to rem to 2, remainder is 0 and 1 to put into two different Memcacheq queues, for example, remainder is 0 to put into first Memcacheq queue, and remainder is 1 to put into second Memcacheq queue.
For example user ID is 3438434, can utilize this numerical value to rem to 2.
It should be noted that, first will report the request of playing record to send in different Message Queuing Middlewares in the embodiment of the present invention, main is like this oversize in order to prevent reporting the request queue of broadcasting record, and server response is too slow.
Be understandable that, the concrete number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but two of minimum needs, and Message Queuing Middleware and prior art are as broad as long, do not have the effect that prevents that queue is oversize.
Because the broadcasting record of reporting of user has a lot, for example, the video that user watches is a TV play, has seen now the 16th collection, and the broadcasting that the 1st collection-15 can be collected record is all deleted, and only retains the broadcasting record of the 16th collection.Because client does not wish to chase after while seeing a TV play, see and oneself play the multiple broadcasting records that have same portion TV play in record.
Play Record ID generation module 700, be used to described broadcasting record to generate unique ID;
Between the multiple viewing equipment that the embodiment of the present invention provides, keep synchronously watching the equipment of record, according to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, can avoid like this reporting the queue of broadcasting record oversize, thereby the request of customer in response end is accelerated, in addition, for a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record, can reduce like this taking up room of buffer memory or database, and obtain the broadcasting record that can find quickly request when broadcasting is recorded in client, thereby accelerate the response of request.
Apparatus embodiments two:
Referring to Fig. 5, this figure is apparatus embodiments two schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention.
Due to when client is pc client, because pc client transmission rule is more random, easily there is a lot of repetitions, the very short request that reports broadcasting record interval time, for example, pc client sent and once reports the request of playing record every two minutes, just had so within an hour a large amount of broadcasting records that report.In the present embodiment in order to alleviate the pressure of server end, just send in different Message Queuing Middlewares after reporting the request duplicate removal of playing record at WEB end.
As an example of apparatus embodiments two example, describe below.
The equipment that the present embodiment provides, also comprises reporting and plays record request duplicate removal module 900;
Described reporting play record request duplicate removal module 900, for the broadcasting record request that reports that is pc client by described client type, is first kept at thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
Specifically the mode of duplicate removal is, moves a thread pool that size can be expanded, and in thread pool, each thread has the obstruction queue of oneself, and each obstruction queue is used for preserving the request of playing record that reports of client.Each scheduled time of each thread reports the request of playing record described in going to take out in oneself obstruction queue, uses hash duplicate removal, then reporting after duplicate removal is play to record and carries out the processing of S204.
Particularly, first WEB end selects one not at the thread of operation in thread pool, by playing record from reporting of pc client, sends in the obstruction queue of this thread.
In the present embodiment, described broadcasting Record ID generation module 700 comprises that playing Record ID generates submodule 700a, for using REDIS as distributed I D maker, for described broadcasting record generates the unique ID of the overall situation.
Owing to there being multiple servers reporting in processing messages queue middleware, play the request of recording, if generate the method for ID from increasing with ID in traditional database, can impact database, therefore, in the present embodiment, adopt REDIS to come to generate unique ID for playing record.
The advantage of the equipment that the present embodiment provides is, reporting of pc client play before record request puts into Message Queuing Middleware, first reporting of pc client play to record request and carry out duplicate removal processing, because there is a lot of repetitions, very short request of the time interval in the broadcasting record request that reports that pc client sends, after deleting the request repeating, can alleviate the pressure of server end, thereby accelerate the response time.
It should be noted that, after broadcasting record client being reported at server end is preserved successfully, can return to whether successfully feedback message of preservation with JSON data.
Apparatus embodiments three:
Referring to Fig. 6, this figure is apparatus embodiments three schematic diagrames that keep synchronously watching record between multiple viewing equipment provided by the invention.
Embodiment of the method one and embodiment of the method two report to play with client and are recorded as example and are described, and introduce client obtain to play and be recorded as example and be described below in conjunction with accompanying drawing.
Between the multiple viewing equipment that the present embodiment provides, keep synchronously watching the equipment of record, also comprise: obtain and play record request receiver module 100, video ID list is searched module 200, play and record acquisition module 300 and play record and return to module 400;
Described obtaining play record request receiver module 100, for receiving the request of playing record of obtaining that client sends, described in obtain in the request of playing record and carry user ID, video ID and video type;
It should be noted that, when user initiatively clicks video, explanation is to obtain broadcasting record, and now the client of viewing equipment sends from trend server end the request of playing record of obtaining.
Described broadcasting record returns to module 400, for described broadcasting record is returned to client.
It should be noted that, the embodiment of the present invention provides, and to obtain the method for playing record be on the basis based on embodiment of the method or embodiment of the method two, and server end receives and obtains the broadcasting record that finds this request correspondence after the request of playing record and return to client.
Between one kind of multiple viewing equipment that provide based on above embodiment, keep synchronously watching the method and apparatus of record, the embodiment of the present invention also provides the system that between one kind of multiple viewing equipment, record is synchronously watched in maintenance, below in conjunction with accompanying drawing, is described in detail.
System embodiment one:
Referring to Fig. 7, this figure is system embodiment one schematic diagram that keeps synchronously watching record between multiple viewing equipment provided by the invention.
This enforcement provides the system that between one kind of multiple viewing equipment, record is synchronously watched in maintenance, comprising: client 1000, server end 2000;
Described client 1000, for sending to described server end 2000 request of playing record that reports, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
It should be noted that, when user uses client sight 1000 to see video, need to report broadcasting record, play record and comprise video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
Wherein, current reproduction time refers to, and video that user watches is current has watched which second of which point etc.
Wherein, client type can be divided into pc client, and mobile client etc.Mobile client is for example cell-phone customer terminal, PAD client etc.
When user uses pc client to watch video, viewing equipment can regularly report and watch record, for example, every two minutes, report once.When user uses client on mobile phone to watch video, when logging off, viewing equipment can record service end to cloud and report broadcasting record.
Wherein, described in video, special edition refers to the video set that has denominator, and for example certain TV play can be called a special edition, and the video of a TV play belongs in same special edition, but a video may belong to one or more special edition, also may not belong to any special edition.
LVS will report broadcasting record request to be forwarded on a certain NGINX server according to load balancing.
NGINX, as reverse proxy, will report broadcasting record request to be forwarded to corresponding WEB end server.
Described server end 2000, for according to the difference of user ID, reports the request of playing record to send in the different Message Queuing Middleware of dividing in advance by described, and the number of described Message Queuing Middleware is at least two; In described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record; For described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
It should be noted that, described Message Queuing Middleware can be realized by Memcacheq, also can be realized by other Message Queuing Middleware.
Specifically how according to the difference of user ID, to divide to report to play and be recorded in different Memcacheq queues, can set from origin, for example, when two different Memcacheq queues are set, what can be even number by user ID be placed in a Memcacheq queue, and what by user ID, be odd number is placed in another Memcacheq queue.
When three different Memcacheq queues are set, can utilize the algorithm (%3) of the remainder of asking 3, user ID is remmed to 3, is 0,1 and 2 to put into respectively first Memcacheq queue, second Memcacheq queue and the 3rd Memcacheq queue according to remainder.
Be understandable that, when having two Memcacheq queues, also can utilize user ID to rem to 2, remainder is 0 and 1 to put into two different Memcacheq queues, for example, remainder is 0 to put into first Memcacheq queue, and remainder is 1 to put into second Memcacheq queue.
For example user ID is 3438434, can utilize this numerical value to rem to 2.
Be understandable that, first server end can resolve the various information of playing in record request that report of client transmission, and this information comprises video ID, user ID, current reproduction time.Special edition ID, video type and client type described in video;
It should be noted that, first will report the request of playing record to send in different Message Queuing Middlewares in the embodiment of the present invention, main is like this oversize in order to prevent reporting the request queue of broadcasting record, and server response is too slow.
Be understandable that, the concrete number of Message Queuing Middleware is not specifically limited in embodiments of the present invention, but two of minimum needs, and Message Queuing Middleware and prior art are as broad as long, do not have the effect that prevents that queue is oversize.
Because the broadcasting record of reporting of user has a lot, for example, the video that user watches is a TV play, has seen now the 16th collection, and the broadcasting that the 1st collection-15 can be collected record is all deleted, and only retains the broadcasting record of the 16th collection.Because client does not wish to chase after while seeing a TV play, see and oneself play the multiple broadcasting records that have same portion TV play in record.
Between the multiple viewing equipment that the embodiment of the present invention provides, keep the system of synchronously watching record, according to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, can avoid like this reporting the queue of broadcasting record oversize, thereby the request of customer in response end is accelerated, in addition, for a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record, can reduce like this taking up room of buffer memory or database, and obtain the broadcasting record that can find quickly request when broadcasting is recorded in client, thereby accelerate the response of request.
System embodiment two:
The system that the present embodiment provides, described server end 2000, according to the difference of user ID, before the described request that reports broadcasting to record is sent in the different Message Queuing Middleware of dividing in advance, also comprises:
The broadcasting record request that reports that is pc client by described client type is first kept in thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
Due to when client is pc client, because pc client transmission rule is more random, easily there is a lot of repetitions, the very short request that reports broadcasting record interval time, for example, pc client sent and once reports the request of playing record every two minutes, just had so within an hour a large amount of broadcasting records that report.In the present embodiment in order to alleviate the pressure of server end, just send in different Message Queuing Middlewares after reporting the request duplicate removal of playing record at WEB end.
Specifically the mode of duplicate removal is, moves a thread pool that size can be expanded, and in thread pool, each thread has the obstruction queue of oneself, and each obstruction queue is used for preserving the request of playing record that reports of client.Each scheduled time of each thread reports the request of playing record described in going to take out in oneself obstruction queue, uses hash duplicate removal.
Owing to there being multiple servers reporting in processing messages queue middleware, play the request of recording, if generate the method for ID from increasing with ID in traditional database, can impact database, therefore, in the present embodiment, adopt REDIS to come to generate unique ID for playing record.
The advantage of the system that the present embodiment provides is, reporting of pc client play before record request puts into Message Queuing Middleware, first reporting of pc client play to record request and carry out duplicate removal processing, because there is a lot of repetitions, very short request of the time interval in the broadcasting record request that reports that pc client sends, after deleting the request repeating, can alleviate the pressure of server end, thereby accelerate the response time.
It should be noted that, after broadcasting record client being reported at server end is preserved successfully, can return to whether successfully feedback message of preservation with JSON data.
Above embodiment reports to play with client and is recorded as example and is described, and introduces client below and obtains to play and be recorded as example and be described.
Described client 1000, also for sending to described server end 2000 request of playing record of obtaining, described in obtain in the request of playing record and carry user ID, video ID and video type;
Described server end 2000, also for searching the list of the video ID that user corresponding to this user ID watch from buffer memory according to described user ID; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again; By the list of the described video ID that finds, from buffer memory, obtain the broadcasting record of video; If do not have described broadcasting record to obtain from database again in buffer memory; Described broadcasting record is returned to client.
The method, apparatus and system that the above embodiment of the present invention provides, the comparatively fast request of customer in response end can realize user and play the synchronous of record between multiple terminals.
The above, be only preferred embodiment of the present invention, not the present invention done to any pro forma restriction.Although the present invention discloses as above with preferred embodiment, but not in order to limit the present invention.Any those of ordinary skill in the art, do not departing from technical solution of the present invention scope situation, all can utilize method and the technology contents of above-mentioned announcement to make many possible variations and modification to technical solution of the present invention, or be revised as the equivalent embodiment of equivalent variations.Therefore, every content that does not depart from technical solution of the present invention,, all still belongs in the scope of technical solution of the present invention protection any simple modification made for any of the above embodiments, equivalent variations and modification according to technical spirit of the present invention.
Claims (11)
1. between one kind of multiple viewing equipment, keep the method for synchronously watching record, it is characterized in that, comprising:
Receive the request of playing record that reports that client sends, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
According to the difference of user ID, by described, report the request of playing record to send in the different Message Queuing Middleware of dividing in advance, the number of described Message Queuing Middleware is at least two;
In described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record;
For described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
2. between multiple viewing equipment according to claim 1, keep the method for synchronously watching record, it is characterized in that, described according to the difference of user ID, before the described request that reports broadcasting to record is sent in the different Message Queuing Middleware of dividing in advance, also comprise:
The broadcasting record request that reports that is pc client by described client type is first kept in thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
3. between multiple viewing equipment according to claim 1, keep the method for synchronously watching record, it is characterized in that, described is that described broadcasting record generates unique ID, is specially:
Use REDIS as distributed I D maker, for described broadcasting record generates the unique ID of the overall situation.
4. according to the method that keeps between the multiple viewing equipment described in claim 1-3 any one synchronously watching record, it is characterized in that, also comprise:
Receive client send obtain play record request, described in obtain play record request in carry user ID, video ID and video type;
According to described user ID, from buffer memory, search the list of the video ID that user corresponding to this user ID watch; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again;
By the list of the described video ID that finds, from buffer memory, obtain the broadcasting record of video; If do not have described broadcasting record to obtain from database again in buffer memory;
Described broadcasting record is returned to client.
5. between one kind of multiple viewing equipment, keep synchronously watching the equipment of record, it is characterized in that, comprising: report and play record request receiver module, report broadcasting record request division module, broadcasting to record duplicate removal module, broadcasting Record ID generation module and broadcasting and record memory module;
Described reporting play record request receiver module, for receiving the request of playing record that reports that client sends, described in report to play and carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type in record request;
Described reporting play record request division module, for according to the difference of user ID, by described, reports the request of playing record to send in the different Message Queuing Middleware of dividing in advance, and the number of described Message Queuing Middleware is at least two;
Duplicate removal module is recorded in described broadcasting, at described Message Queuing Middleware, is that a video only retains a record of playing, and that deletes that video ID and special edition ID repeat reports broadcasting record;
Described broadcasting Record ID generation module, is used to described broadcasting record to generate unique ID;
Memory module is recorded in described broadcasting, and the broadcasting record that carries described unique ID is stored in buffer memory and database.
6. the equipment that keeps synchronously watching record between multiple viewing equipment according to claim 5, is characterized in that, also comprises reporting playing record request duplicate removal module;
Described reporting play record request duplicate removal module, for the broadcasting record request that reports that is pc client by described client type, is first kept at thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
7. between multiple viewing equipment according to claim 5, keep synchronously watching the equipment of record, it is characterized in that, described broadcasting Record ID generation module comprises that playing Record ID generates submodule, be used for using REDIS as distributed I D maker, for described broadcasting record generates the unique ID of the overall situation.
8. according to the equipment that keeps synchronously watching record between the multiple viewing equipment described in claim 5-7 any one, it is characterized in that, also comprise: obtain and play record request receiver module, video ID list is searched module, play and record acquisition module and play record and return to module;
Described obtaining play record request receiver module, for receiving the request of playing record of obtaining that client sends, described in obtain in the request of playing record and carry user ID, video ID and video type;
Module is searched in described video ID list, for search the list of the video ID that user corresponding to this user ID watch from buffer memory according to described user ID; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again;
Acquisition module is recorded in described broadcasting, for the list of the described video ID by finding, obtains the broadcasting record of video from buffer memory; If do not have described broadcasting record to obtain from database again in buffer memory;
Described broadcasting record returns to module, for described broadcasting record is returned to client.
9. between one kind of multiple viewing equipment, keep the system of synchronously watching record, it is characterized in that, comprising: client, server end;
Described client, for send the request of playing record that reports to described server end, described in report and in the request of playing record, carry special edition ID under video ID, user ID, current reproduction time, video, video type and client type;
Described server end, for according to the difference of user ID, reports the request of playing record to send in the different Message Queuing Middleware of dividing in advance by described, and the number of described Message Queuing Middleware is at least two; In described Message Queuing Middleware, be that a video only retains a record of playing, that deletes that video ID and special edition ID repeat reports broadcasting record; For described broadcasting record generates unique ID, the broadcasting record that carries described unique ID is stored in buffer memory and database.
10. between multiple viewing equipment according to claim 9, keep the system of synchronously watching record, it is characterized in that, described server end, according to the difference of user ID, before the described request that reports broadcasting to record is sent in the different Message Queuing Middleware of dividing in advance, also comprises:
The broadcasting record request that reports that is pc client by described client type is first kept in thread pool, uses hash to play record request to reporting in described thread pool carry out duplicate removal every the scheduled time.
11. according to the system that keeps between the multiple viewing equipment described in claim 9 or 10 synchronously watching record, it is characterized in that, described client, also for send the request of playing record of obtaining to described server end, described in obtain in the request of playing record and carry user ID, video ID and video type;
Described server end, also for searching the list of the video ID that user corresponding to this user ID watch from buffer memory according to described user ID; If search the list of the video ID watching less than user corresponding to this user ID in buffer memory searches from database again; By the list of the described video ID that finds, from buffer memory, obtain the broadcasting record of video; If do not have described broadcasting record to obtain from database again in buffer memory; Described broadcasting record is returned to 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 true CN103731682A (en) | 2014-04-16 |
| CN103731682B 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) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104822090A (en) * | 2014-04-25 | 2015-08-05 | 腾讯科技（北京）有限公司 | Video playing method, device and system |
| CN105007504A (en) * | 2015-07-13 | 2015-10-28 | 无锡天脉聚源传媒科技有限公司 | Browsing history processing method and device |
| CN105681428A (en) * | 2016-01-25 | 2016-06-15 | 浪潮软件股份有限公司 | User information synchronizing system, method and device |
| CN105872720A (en) * | 2015-11-25 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Method and device for screening playing records in video application |
| WO2017088382A1 (en) * | 2015-11-25 | 2017-06-01 | 乐视控股（北京）有限公司 | Data processing method and device |
| CN107172492A (en) * | 2017-06-06 | 2017-09-15 | 环球智达科技（北京）有限公司 | A kind of reporting system for playing record |
| CN107396181A (en) * | 2017-08-24 | 2017-11-24 | 广州创维平面显示科技有限公司 | A kind of shared method, storage medium and intelligent television for playing record |
| WO2018018457A1 (en) * | 2016-07-27 | 2018-02-01 | 黄新勇 | Method and system for distinguishing watching types in television broadcasting |
| CN112508380A (en) * | 2020-12-03 | 2021-03-16 | 浪潮云信息技术股份公司 | System and method applied to asynchronous processing of high-concurrency evaluation data |
| CN114051162A (en) * | 2022-01-12 | 2022-02-15 | 飞狐信息技术（天津）有限公司 | Caching method and device based on play records |
| CN114302186A (en) * | 2021-12-29 | 2022-04-08 | 湖南快乐阳光互动娱乐传媒有限公司 | Play record processing method and related device |
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 |
|---|
| 魏之春: "《互联网广告经营管理系统的设计与实现》", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104822090A (en) * | 2014-04-25 | 2015-08-05 | 腾讯科技（北京）有限公司 | Video playing method, device and system |
| CN104822090B (en) * | 2014-04-25 | 2017-12-01 | 腾讯科技（北京）有限公司 | The methods, devices and systems of video playback |
| CN105007504A (en) * | 2015-07-13 | 2015-10-28 | 无锡天脉聚源传媒科技有限公司 | Browsing history processing method and device |
| CN105872720A (en) * | 2015-11-25 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Method and device for screening playing records in video application |
| WO2017088382A1 (en) * | 2015-11-25 | 2017-06-01 | 乐视控股（北京）有限公司 | 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 |
| CN107396181A (en) * | 2017-08-24 | 2017-11-24 | 广州创维平面显示科技有限公司 | A kind of shared method, storage medium and intelligent television 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 |
| CN114051162A (en) * | 2022-01-12 | 2022-02-15 | 飞狐信息技术（天津）有限公司 | Caching method and device based on play records |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103731682B (en) | 2017-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103731682A (en) | Method, device and system for keeping synchronous watching record among multiple film watching devices | |
| US11196829B2 (en) | Method and apparatus for pushing target information | |
| KR101778424B1 (en) | Network coded storage with multi-resolution codes | |
| US9712835B2 (en) | Video encoding system and method | |
| WO2013159703A1 (en) | Offline download method, multimedia file download method and system thereof | |
| CN105338124A (en) | Resource propagating tracking method and apparatus, and resource propagating system | |
| CN105099894B (en) | Information push method, apparatus and system | |
| CN104572966A (en) | Zip file unzipping method and device | |
| CN108184170B (en) | Data processing method and device | |
| CN111159219B (en) | Data management method, device, server and storage medium | |
| WO2015010593A1 (en) | Method and apparatus for displaying contact list | |
| CN105577772A (en) | Material receiving method, material uploading method and device | |
| US11775480B2 (en) | Method and system for deleting obsolete files from a file system | |
| US20190005534A1 (en) | Providing media assets to subscribers of a messaging system | |
| CN108829809A (en) | A kind of information displaying method and its terminal device, the network equipment | |
| CN107203532A (en) | Construction method, the implementation method of search and the device of directory system | |
| CN106331089A (en) | Video play control method and system | |
| CN104811458A (en) | Method and device for displaying information | |
| TWI602431B (en) | Method and device for transmitting information | |
| CN112307058B (en) | Short link processing method and device, storage medium and computer equipment | |
| US8510426B2 (en) | Communication and coordination between web services in a cloud-based computing environment | |
| CN104753811A (en) | Streaming medium service optimizing method, device and system | |
| CN104917754A (en) | Video data sending and receiving methods, servers and clients | |
| CN103905661A (en) | Message forwarding method and cloud server | |
| CN104834728B (en) | A kind of method for pushing and device for subscribing to video |
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 |