CN111491172B - Live broadcast authority management system and live broadcast authority management method - Google Patents

Live broadcast authority management system and live broadcast authority management method Download PDF

Info

Publication number
CN111491172B
CN111491172B CN202010276192.4A CN202010276192A CN111491172B CN 111491172 B CN111491172 B CN 111491172B CN 202010276192 A CN202010276192 A CN 202010276192A CN 111491172 B CN111491172 B CN 111491172B
Authority
CN
China
Prior art keywords
user
service
level
permission
layer
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
Application number
CN202010276192.4A
Other languages
Chinese (zh)
Other versions
CN111491172A (en
Inventor
陈明铝
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bigo Technology Pte Ltd
Original Assignee
Guangzhou Baiguoyuan Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Baiguoyuan Information Technology Co Ltd filed Critical Guangzhou Baiguoyuan Information Technology Co Ltd
Priority to CN202010276192.4A priority Critical patent/CN111491172B/en
Publication of CN111491172A publication Critical patent/CN111491172A/en
Application granted granted Critical
Publication of CN111491172B publication Critical patent/CN111491172B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21—Server components or server architectures
    • H04N21/218—Source of audio or video content, e.g. local disk arrays
    • H04N21/2187—Live feed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
    • H04N21/23106—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion involving caching operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H04N21/2541—Rights Management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
    • H04N21/26258—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists for generating a list of items to be played back in a given order, e.g. playlist, or scheduling item distribution according to such list
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44213—Monitoring of end-user related data
    • H04N21/44222—Analytics of user selections, e.g. selection of programs or purchase activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Social Psychology (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

The invention discloses a live broadcast authority management system and a live broadcast authority management method, wherein the system comprises: the method comprises the following steps: the user content service layer is used for determining the historical live broadcast participation information of the user corresponding to the trigger event according to the permission after monitoring the new permission determination trigger event, determining the user permission level of the corresponding user and caching the user permission level; and the service authority management layer is used for acquiring the user authority level of the user associated with the service access request by the access user content service layer when receiving the service access request sent by the client side, and determining the response authority of the service access request according to the user authority level. By utilizing the system, the user content service layer and the service authority management layer are arranged at the service end of the live broadcast application to trigger the updating and the determination of the user authority level of the live broadcast user, and the determined user authority level is adopted to realize the real-time monitoring and the management of the user service authority at the live broadcast client side, thereby realizing the automatic management control of the user live broadcast authority.

Description

Live broadcast authority management system and live broadcast authority management method
Technical Field
The invention relates to the technical field of live broadcast services, in particular to a live broadcast authority management system and a live broadcast authority management method.
Background
In the field of live webcasting, live webcasting is generally performed through a live webcasting service platform, and the live webcasting service platform generally needs to strictly supervise live webcasting content based on the requirement of content security so as to manage and control the live webcasting permission of a user through a monitoring result of the live webcasting content.
In a traditional live broadcast service platform, user behaviors of live broadcast users are mainly tracked by operators, the live broadcast behaviors of the live broadcast users are judged by regular analysis, and white lists or other business authorities are set for the live broadcast users to control the live broadcast users.
The above-mentioned mode has reached the purpose of supervising the broadcast high-risk content to a certain extent, but has the following defects: the control authority set for the live broadcast user mainly depends on subjective analysis of an operator, the decision authority set for the authority is held in the hands of the operator, the control authority of the live broadcast user is usually updated regularly, and the operator cannot adjust the control authority of the live broadcast user in real time according to abnormal behaviors generated by the user in the live broadcast.
Disclosure of Invention
The embodiment of the invention provides a live broadcast authority management system and a live broadcast authority management method, which realize real-time and effective determination of user live broadcast authority.
In a first aspect, an embodiment of the present invention provides a live broadcast right management system, including: a user content service layer and a service authority management layer;
the user content service layer is used for determining the historical live broadcast participation information of the user corresponding to the permission determination trigger event according to the permission determination trigger event after monitoring a new permission determination trigger event, determining the user permission level of the corresponding user and caching the user permission level;
and the service authority management layer is used for accessing the user content service layer to obtain the user authority level of the user associated with the service access request when receiving the service access request sent by the client side, and determining the response authority of the service access request according to the user authority level.
In a second aspect, an embodiment of the present invention provides a live rights management method, which is executed by the live rights management system provided in the first aspect of the present embodiment, and includes:
after receiving a front-end process allocation request sent by a back-end service process, a service management process in a live broadcast service layer determines front-end process deployment information corresponding to the front-end allocation request and feeds the front-end process deployment information back to a container management cluster on a container management layer;
and the container management cluster determines a corresponding target process image file and a target server according to the front-end process deployment information, creates a target container in the target server based on the target process image file and deploys a target front-end service process in the target container.
In the above-described live rights management system and live rights management method, the live rights management system includes: the system comprises a user content service layer and a business authority management layer, wherein the user content service layer can monitor a new authority determination trigger event, determine historical live broadcast participation information of a user corresponding to the trigger event according to the authority, determine a user authority level of the corresponding user and cache the user authority level; when the service authority management layer can receive a service access request sent by a client side, the access user content service layer obtains the user authority level of a user associated with the service access request, and determines the response authority of the service access request according to the user authority level. According to the technical scheme, the user content service layer and the service authority management layer are arranged at the service end of the live broadcast application to trigger the updating and determining of the user authority level of the live broadcast user, meanwhile, the determined user authority level is adopted to realize the real-time monitoring and management of the user service authority of the live broadcast client side, compared with the existing live broadcast authority management, the automatic management control of the user live broadcast authority is realized through the real-time monitoring and analysis of the live broadcast user behavior data, and the management efficiency of the user live broadcast authority is effectively improved.
Drawings
Fig. 1 is an architecture diagram of a live broadcast right management system according to an embodiment of the present invention;
fig. 2 is an architecture diagram of a live broadcast rights management system according to a second embodiment of the present invention;
fig. 3 is a flowchart illustrating an exemplary implementation of a live rights management method executed by a live rights management system in a third embodiment of the present invention;
FIG. 4 is a flowchart illustrating three exemplary user permission level determinations performed by the live rights management system in accordance with embodiments of the present invention;
fig. 5 is a flowchart illustrating three exemplary operations of service right management performed by the live right management system according to the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. In addition, the embodiments and features of the embodiments of the present invention may be combined with each other without conflict, and the respective embodiments may be mutually referred to and cited.
Example one
Fig. 1 is an architecture diagram of a live rights management system according to an embodiment of the present invention, and as shown in fig. 1, the live rights management system includes: a user content service layer 11 and a service authority management layer 12;
the user content service layer 11 is configured to, after monitoring a new permission determination trigger event, determine, according to historical live broadcast participation information possessed by a user corresponding to the permission determination trigger event, a user permission level of the corresponding user and cache the user permission level;
the service authority management layer 12 is configured to, when receiving a service access request sent by a client, obtain, by the access user content service layer 11, a user authority level of a user associated with the service access request, and determine, according to the user authority level, a response authority of the service access request.
It should be noted that the live rights management system provided in this embodiment is mainly configured on a live service platform for performing live service, and specific operations of layers in the live rights management system are executed by a server constituting the live service platform.
In this embodiment, the user content service layer 11 may be specifically considered as an execution layer for determining a user permission level, a server supporting the user content service layer 11 in the live broadcast service platform may be considered as an execution subject for determining the user permission level, and all live broadcast users (which may include an anchor user and an audience user) on the live broadcast application client side that need to perform user permission determination may implement the determination of the user permission level through the operation of the user content service layer 11, where the user permission level may be specifically understood as a limit level of the live broadcast user in the live broadcast application, and in this embodiment, the user permission level may be divided into 4 level layers, and live broadcast users under different level layers have different service access permissions.
Specifically, the user content service layer 11 is always in a monitoring state, and may monitor whether a new permission determination trigger event is received, and trigger a user permission level determination operation after receiving the new permission determination trigger event, where the permission determination trigger event that triggers the user permission level determination may be understood as a trigger event that includes live broadcast user information and user behavior information (which may be participation duration of a user participating in live broadcast or an illegal event in a process of the user participating in live broadcast, etc.) to be subjected to the user permission level determination; the user content service layer 11 can know the corresponding user of the permission determination trigger event through the live user information in the permission determination trigger event.
Then, the user content service layer 11 may obtain the historical live broadcast participation information of the user corresponding to the permission determination trigger event, and may determine the user permission level of the corresponding user through analysis of the obtained historical live broadcast participation information and cache the user permission level in the set cache space. The historical live broadcast participation information can be live broadcast participation information generated by a live broadcast user in a previous period relative to the current time, and the live broadcast participation information can comprise watching duration, live broadcast duration, interaction information or violation information in live broadcast and the like.
It should be noted that a database for data storage is also associated on a live broadcast service platform providing a live broadcast application service, and in this embodiment, live broadcast participation information generated by a live broadcast user in a live broadcast may be stored in a set database, and in addition, a key-value storage system Redis may be used in this embodiment to implement the relevant cache of the user permission level.
In this embodiment, the service right management layer 12 may be regarded as an execution layer of service right management, and a server supporting the service right management in the live broadcast service platform may be regarded as an execution subject of the service right management, for example, when a live broadcast user has a live broadcast service requirement (for example, watching a live broadcast, connecting to a live broadcast user, creating a live broadcast room for live broadcast, and the like), a service access request may be sent to the live broadcast service end side through the live broadcast client, and the service right management layer 12 on the live broadcast service end side may receive the service access request, and may determine a specific live broadcast user through analysis of the service access request, which is denoted as an associated user corresponding to the service access request in this embodiment.
It should be noted that, after receiving the service access request, the service right management layer 12 cannot directly provide a relevant response to the service access request, but needs to further determine whether the associated user has the access right of the service corresponding to the service access request, that is, needs to further determine the response right corresponding to the service access request, and when the response right of the service access request is a normal response, it may be considered that the associated user has the access right of the service.
Specifically, after determining the associated user corresponding to the service access request, the service right management layer 12 may search the user content service layer 11 for the user right level of the associated user and determine the response right to the service access request based on the obtained user right level. For example, after the service authority management layer 12 obtains the user authority level of the associated user, assuming that the user authority level has the access authority to the service corresponding to the service access request, the service authority management layer 12 may consider that the response authority that the service access request has is a normal response, and thus the service authority management layer 12 may allow the associated user to normally access the service corresponding to the service access request.
In the live broadcast authority management system provided by the embodiment of the invention, the user content service layer and the service authority management layer are arranged at the service end of the live broadcast application to trigger the updating and the determination of the user authority level of the live broadcast user, and the determined user authority level is adopted to realize the real-time monitoring and management of the user service authority of the live broadcast client side.
As an optional embodiment of the present invention, the optional embodiment is optimized based on the above embodiment, and after the foregoing fig. 1, the live broadcast right management system shown in fig. 1 further includes: a data management layer 13 and a message publishing and subscribing layer 14;
the data management layer 13 is connected to the message publishing and subscribing layer 14, and is configured to acquire behavior data generated by a client-side user in real time, determine participation duration data or violation data of a corresponding user according to the behavior data, form corresponding participation duration information or violation events, and feed back the corresponding participation duration information or violation events to the message publishing and subscribing layer 14 in real time;
and the message publishing and subscribing layer 14 is connected with the user content service layer 11 and is used for caching participation duration information or violation events fed back by the data management layer 13 in real time, selecting the participation duration information or the violation events as the permission determination trigger events according to the message sending rule, and sending the participation duration information or the violation events to the user content service layer 11.
In this embodiment, the live broadcast right management system further includes a data management layer 13 and a message publish-subscribe layer 14, and it can be understood that, in this embodiment, the user content service layer 11 may start to determine the user right level after monitoring a new right determination trigger event, and the right determination trigger event is formed in real time based on the behavior data of the live broadcast user, so that it can be seen that the determination of the user right level is actually a real-time update process.
The embodiment may obtain, through the data management layer 13, behavior data of a live user on the live client side in real time, and form a trigger event for permission level determination through analysis and processing of the obtained behavior data. It is understood that the data management layer 13 can also be regarded as an execution layer, which is specifically used for receiving and processing the behavior data of the live broadcast user in real time, and specifically takes the server supporting the data management layer 13 on the live broadcast service platform as an execution subject.
It should be noted that the data volume of the live users participating in live broadcasting at the same time is large, so that the data management layer 13 may receive behavior data of a large number of live users at the same time, analyze and process the behavior data respectively, and may generate a plurality of permission determination triggering events, and the user content service layer 11 may not have the capability of receiving and determining permission levels of a plurality of users at the same time, thereby possibly causing a problem that data congestion may not effectively process data. To solve the problem, the present embodiment further adds a message publish-subscribe layer 14 to buffer data congestion from the data management layer 13 directly to the user content service layer 11 through the caching of each data message generated by the data management layer 13 by the message publish-subscribe layer 14.
Specifically, the data management layer 13 is specifically connected to the message publishing and subscribing layer 14, and may capture, in real time, behavior data generated when a live client-side user performs a live broadcast operation, where the behavior data may include: the time when the user enters the live broadcast room, the time when the user exits the live broadcast room, text information or image information pushed by the user, and the like, and then the data management layer 13 can process the received behavior data, so as to obtain information required by permission determination triggering, wherein the information can be participation duration of live broadcast by the user (the participation duration of live broadcast watching can be used as the participation duration of anchor broadcast, and also can be illegal data detected and the like; finally, the user management layer may further package the participation duration or the violation data to form data information that can be fed back to the message publishing subscription layer 14, for example, combine the participation duration with the user information of the corresponding user to form the participation duration information of the corresponding user, or combine the violation data with the user information of the corresponding user to form the violation event of the corresponding user, and feed back the participation duration information or the violation event to the message publishing subscription layer 14 in real time.
In this embodiment, the message publishing and subscribing layer 14 may be preferably regarded as a kafka message cluster, which is mainly connected to the user content service layer 11 and can be used to cache large-scale message data. Based on this, the message publishing and subscribing layer 14 may receive one or more participation duration information or violation events fed back by the data management layer 13, and cache the received information, and then may select participation duration information or violation events serving as the current permission determination trigger event according to a message sending rule possessed by the message publishing and subscribing layer 14 itself, or according to a message sending rule set manually in advance, and send the selected participation duration information or violation events to the user content service layer 11.
For example, the formed participation duration information or violation event may be regarded as user information of the corresponding user as a key, and the participation duration or violation data as key-value pair information of a value.
On the basis of the above-described alternative embodiment, the data management layer 13 includes:
the anchor management sublayer is used for acquiring anchor behavior data generated by an anchor user at an anchor client side in real time, determining playing duration data of a corresponding anchor user according to the anchor behavior data, combining anchor associated information of the corresponding anchor user with the playing duration data to form participation duration information and feeding the participation duration information back to the message publishing subscription layer 14 in real time;
and the audience management sublayer is used for acquiring audience behavior data generated by audience users at the audience client side in real time, determining watching duration data of corresponding audience users according to the audience behavior data, combining audience correlation information of the corresponding audience users with the watching duration data to form participation duration information, and feeding the participation duration information back to the message publishing subscription layer 14 in real time.
The embodiment may perform sub-layer division on the behavior data processed by the data management layer 13 from different sources, specifically, the system can comprise a main broadcasting management sublayer and an audience management sublayer, wherein the main broadcasting management sublayer mainly analyzes and processes behavior data generated by a main broadcasting client, users at the main broadcasting client side are marked as main broadcasting users, the main broadcasting users can establish live broadcasting rooms through the main broadcasting client to perform live broadcasting interaction with audience users, the behavior data thus generated corresponds to anchor behavior data, the anchor management sublayer determines the on-air duration data of the corresponding anchor user by the live room creation time and the live room closing time in the anchor behavior data, and may combine the play duration data with the anchor associated information of the corresponding anchor user to form participation duration information fed back to the message publish-subscribe layer 14.
Similarly, the audience management sublayer mainly analyzes and processes the behavior data generated from the audience client, the user at the audience client side is marked as the audience user, the audience user can enter the live broadcast room to watch live broadcast through the audience client or interact with the main broadcast user who carries out the live broadcast, the generated behavior data is equivalent to the audience behavior data, the audience management sublayer determines the watching duration data of the corresponding audience user through the time of entering the live broadcast room and the time of leaving the live broadcast room in the audience behavior data, and the watching duration data and the audience correlation information of the corresponding audience user can be combined to form participation duration information which is fed back to the message publishing subscription layer 14.
It should be noted that the anchor associated information includes an anchor user identifier, an anchor room identifier, and a room start creation time; the audience relevant information comprises audience user identification, watching room identification and watching starting time. In this embodiment, the anchor associated information or the audience associated information may be used as a unique identifier of a participation duration corresponding to a corresponding user to perform associated recording with corresponding duration data.
Meanwhile, on the basis of the above-mentioned alternative embodiment, the data management layer 13 further includes:
and the violation detection sublayer is used for analyzing the acquired behavior data of the client-side user, and forming a violation event to be stored and fed back to the message publishing and subscribing layer 14 in real time when determining that the corresponding user has a live broadcast violation, a picture violation or a character violation.
When the client side user is an anchor client side anchor user, the behavior data is anchor behavior data; when the client side user is a spectator client side spectator user, the behavior data is spectator behavior data.
In this embodiment, the data management layer 13 further includes a violation detection sublayer according to different administrative performances, where the violation detection sublayer is mainly configured to detect whether a violation behavior of the user exists in the live broadcast by analyzing user behavior data, and the violation behavior may include violation setting of a user avatar cover, violation editing of pushing a public screen character by the user, and violation statements or violation behavior in the live broadcast by the user. When the violation detection sublayer detects that the user behavior data contains the violation behaviors, the violation data corresponding to the violation behaviors can be extracted, and a violation event is formed and fed back to the message publishing and subscribing layer 14. It is to be understood that the behavior data obtained by the violation detection sublayer may be anchor behavior data of an anchor client side corresponding to an anchor user, or may be viewer behavior data of a viewer client side viewer user,
in this embodiment, the key to the violation detection sublayer determining the violation event is how to determine violation information from the behavior data of the user, and this optional embodiment further provides a specific operation of the violation detection sublayer to implement violation behavior detection, that is, the violation detection sublayer may specifically be configured to:
extracting user head portrait picture information, user public screen character information and a current live video frame in the acquired behavior data of the user at the client side; carrying out violation detection on the user head portrait picture information, the user public screen character information and the current live video frame by adopting corresponding detection strategies; when detecting that the head portrait picture information of the user, the public screen text information of the user or the illegal object exists in the current live video frame, combining the illegal type of the illegal object and the user identification of the corresponding user with the illegal object to form an illegal event; and storing the violation event in a preset violation data table, and feeding back the violation event to the message publishing and subscribing layer 14 in real time.
In this embodiment, the behavior data of the user at the client side may include user avatar picture information, user public screen text information (that is, headline or bulletin text pushed by the user in the live broadcast application), and a live broadcast video frame when the user participates in live broadcast. In addition, the violation item to be detected with the violation behavior is determined as the violation object, the violation type to which each violation object belongs can be determined, and the violation event is formed by combining the violation type, the user identifier of the corresponding user of the analyzed behavior data, and the violation object. In the embodiment, after the violation event is formed by the violation detection sublayer, the violation event is stored in the violation data table, wherein the data space where the violation data table is located is associated with the data management layer 13.
The optional embodiment of the invention further adds a data management layer and a message publishing and subscribing layer, realizes the real-time acquisition and analysis of user behavior data through the data management layer, provides the live broadcast participation information used as the right item determination triggering condition for the execution of the user right level on the user content service layer, and better realizes the real-time report and reliable transmission of the live broadcast participation information through the added message publishing and subscribing layer, thereby avoiding the data congestion problem caused by the concurrent generation of data. Meanwhile, the optional embodiment further performs specific description on the data management layer, so that the working mechanism of the data management layer is more definite, and precondition information is provided for effectively determining the user permission level in the user content service layer.
Example two
Fig. 2 is an architecture diagram of a live rights management system according to a second embodiment of the present invention, where the embodiment is optimized based on the first embodiment, in the embodiment, the optimizing user content service layer 11 further includes: an information monitoring sublayer 111 and a level determination sublayer 112;
the information monitoring sublayer 111 is configured to monitor whether the message publishing subscription layer 14 has a new permission determination trigger event to send, and receive the permission determination trigger event sent by the message publishing subscription layer 14, where the permission determination trigger event is participation duration information or an illegal event;
a level determining sublayer 112, configured to parse the permission determination trigger event to determine a corresponding target user, obtain historical live broadcast participation information possessed by the target user, determine a user permission level of the target user according to the historical live broadcast participation information, and cache the user permission level, where the user permission level includes: the service authority which can be executed in different authority levels is different from the high authority level, the medium-low authority level and the low authority level.
In the embodiment, corresponding service authority ranges are set for different authority levels, for example, table 1 gives the associated information between the user authority level and the service authority range,
TABLE 1 user class-Business Authority Association Table
User permission level Scope of service authority
High privilege level S Live list display, connecting wheat, fighting and permission of open live broadcast
Medium and high privilege level A Continuous-microphone, opposite-block, small group allowed live broadcast
Medium and low permission level B Continuous-microphone, opposite-block, small group allowed live broadcast
Low privilege level C Live broadcast of small group
As shown in table 1, it can be seen that the service right range corresponding to the high right level is: displaying a live broadcast list, connecting the wheat, checking and allowing open live broadcast; the corresponding service authority ranges under the medium-high authority level and the medium-low authority level can be as follows: connecting wheat, checking and allowing a small group to carry out live broadcast; the corresponding service right range under the low right level can only be: and (5) carrying out live broadcast on a small group.
In this embodiment, on the basis that the first embodiment includes the data management layer 13 and the message publishing subscription layer 14, the user content service layer 11 is further expanded and optimized, the information monitoring sublayer 111 included in the user content service layer 11 is specifically configured to monitor the transmission content of the message publishing subscription layer 14, which is equivalent to taking the participation duration information or the violation event sent by the message publishing subscription layer 14 as a monitoring object, if it is monitored that there is new participation duration information or a violation event, it is considered that the message publishing subscription layer 14 has a new right to determine that a trigger event is sent, and the information monitoring sublayer 111 may receive the right to determine that the trigger event is sent.
The level determination sublayer 112 in this embodiment may further analyze the permission determination trigger event, so as to determine a target user to be subjected to user permission level determination, may then respectively obtain historical participation duration and historical violation events serving as historical live broadcast participation information from a corresponding database, and determine a user permission level of the target user through analysis of the historical live broadcast participation information, where the target user and the corresponding user permission level thereof may be cached in Redis in an associated manner.
In the second technical scheme of this embodiment, the user content service layer 11 is further optimized on the basis of the above embodiment, the live broadcast permission management system provided in this embodiment can trigger updating and determining of the permission level of the user where the live broadcast user is located, and meanwhile, real-time monitoring and management of the user service permission at the live broadcast client side are realized by using the determined user permission level.
As an optional embodiment of the present invention, further optimizing the level determination sublayer 112 may specifically include:
the user determination module is used for extracting a user identifier in the participation duration information to determine a target user when the received permission determination triggering event is the participation duration information; or when the received permission determination trigger event is an illegal event, extracting a user identifier included in the illegal event to determine a target user;
the participation information determining module is used for searching the historical accumulated participation duration of the target user in a set time period from a preset duration record table and searching the historical violation event of the target user in the set time period from a preset violation data table;
and the permission level determining module is used for determining and caching the user permission level of the target user according to the historical accumulated participation duration and the historical violation event.
The optional embodiment further specifically describes the operation when the permission determination trigger event is participation duration information or an illegal event, where the participation duration information or the illegal event is sent by the message publishing and subscribing layer 14, and the specific data management layer 13 determines the permission determination trigger event by analyzing and processing the user behavior data. The participation duration information or the violation event formed by the data management layer 13 includes related information for uniquely identifying the live broadcast user, and the user determination module may extract the unique identifier included therein, thereby obtaining the target user to be subjected to authority level determination.
After the target user is determined, historical live broadcast participation information of the target user needs to be acquired, the historical live broadcast participation information includes historical accumulated participation duration and historical violation events of the target user in a time period set from the current time to the previous time, in the embodiment, it is preferable that the selected set time period is 30 days from the current time, correspondingly, the historical accumulated participation duration is viewing accumulated duration and/or broadcasting accumulated duration within 30 days, and the historical violation events are all violation events within 30 days.
The user permission level of the target user can be determined according to the determined historical accumulated participation duration and the historical violation event in combination with the preset level division determination rule.
On the basis of the above optimization, the permission level determination module may be specifically configured to perform the following steps:
a) analyzing all historical violation events of the target user.
Illustratively, each historical violation event is displayed in the form of violation record information, and the violation record information includes a user identifier of a target user, a violation type of the violation record, and a violation object itself. The permission level determination module through this step may analyze the specific information included in the historical violation events.
b) Judging whether the historical violation events exist in a serious violation category, and if not, executing the step c); if yes, executing step e).
It can be known that the severe violation category includes a violation type belonging to a severe violation, and the permission level determination module may determine whether the violation type belongs to the severe violation category according to the violation type in each historical violation event, and may perform different branch operations according to the determination result.
c) Judging whether the broadcasting accumulated time length in the historical accumulated participation time length is greater than or equal to a first set time length, if so, executing the step d); if not, executing step e).
It can be known that, for a target user, the target user may be used as a viewer user to perform live viewing on a viewer client, or may be used as a anchor user to perform broadcast interaction on the anchor client.
For example, the permission level determination module may determine whether the cumulative time duration of broadcasting of the target user is greater than or equal to a first set time duration again when no serious violation event exists in the historical violation events of the target user, and may also perform different branch operations according to the determination result, where the first set time duration may preferably be 5 hours.
d) And determining that the target user is in an anchor white list, and determining that the corresponding user permission level is a high permission level.
Correspondingly, when the permission level determining module executes the step c) to determine that the cumulative duration of the broadcast is greater than or equal to the first set duration, the target user can be considered to be in the anchor white list when being taken as an anchor user, and at this time, the user permission level corresponding to the target user can be determined to be a high permission level. And the service access authority possessed by the user under the high authority level is the widest.
e) Determining whether the violation times of violation events included in the historical violation events are greater than or equal to a set violation threshold; if not, executing step f); if yes, execute partial step g).
Correspondingly, when the permission level determining module performs step b) to determine that an illegal event in a serious violation category exists in the historical illegal events of the target user, or when it is determined that the cumulative broadcast duration is smaller than a first set duration when step c is performed, the permission level determining module needs to further perform step e) to determine whether the violation frequency of the illegal event included in the historical illegal events of the target user is greater than or equal to a set violation threshold, and different branch operations can be performed according to the determination result, wherein the set violation threshold is preferably 3 times.
f) Judging whether the watching accumulated time length in the historical accumulated participation time length is less than or equal to a second set time length, if so, executing the step g); if not, executing step h) or step i).
Correspondingly, when the permission level determining module determines that the number of violations is less than the set violation threshold when performing step e), it is further necessary to perform step f) to determine whether the cumulative viewing duration of the target user is less than or equal to a second set duration, and different branch operations may be performed according to the determination result, where the second set duration is preferably 1 hour.
g) And determining the user authority level of the target user as a low authority level.
Correspondingly, when the permission level determining module executes the step e) to determine that the violation times are greater than or equal to the set violation threshold, the step g) may be further executed to determine that the user permission level of the target user is a low permission level.
Or, when the permission level determining module executes the step f) to determine that the watching accumulated time length of the target user is less than or equal to the second set time length, the step g) can also be executed to determine that the user permission level of the target user is the low permission level.
Wherein the number of services executable by a user with a low privilege level is minimal.
h) And when the watching accumulated time length is longer than the second set time length and shorter than a third set time length, determining that the user permission level of the target user is a middle-low permission level.
Correspondingly, when the permission level determining module executes the step f) to determine that the watching accumulated time length of the target user is longer than the second set time length, the user permission level of the target user can be determined to be the middle-low permission level through the step h) when the watching accumulated time length is longer than the second set time length and shorter than the third set time length;
the number of services executable by the user with the middle and low permission levels is only higher than the number of services corresponding to the low permission level.
i) And when the watching accumulated duration is greater than or equal to the third set duration, determining that the user permission level of the target user is a medium-high permission level.
Correspondingly, when the permission level determination module executes the step f) to determine that the cumulative viewing duration of the target user is longer than the second set duration, the user permission level of the target user can be determined to be the medium-high permission level through the step h) when the cumulative viewing duration is longer than or equal to the third set duration.
The number of executable services of the user with the middle and high permission levels is superior to that of the services with the middle and low permission levels, and is only inferior to the data with the service access permission of the high permission level.
The user content service layer of the optional embodiment of the invention performs the specific operation of determining the user permission level, and better embodies the automatic analysis and determination of the user permission level by the live broadcast permission management system provided by the embodiment of the invention.
Meanwhile, as another optional embodiment of the present invention, the user content service layer 11 in the optional embodiment further optimizes and includes:
the information recording sublayer 113 is configured to record the participation duration information into a preset duration recording table when the received permission determination trigger event is the participation duration information;
and the manual configuration access sub-layer 114 is used for receiving manual level configuration information input by an operator through a manual configuration interface and storing the manual level configuration information in association with a corresponding user.
In this embodiment, after receiving the participation duration information serving as the permission determination trigger event, the user content service layer 11 may further need to store the parameter duration information in a duration record table constructed under the database through the information record sublayer 113, so as to facilitate obtaining of the required historical live broadcast participation information when determining the permission level of the user.
It should be noted that, a manual configuration interface suitable for operation of an operator is further provided on the user content service layer 11 on the live broadcast service platform, and the operator can manually configure the permission level of the selected live broadcast user through the manual configuration interface, the user content service layer 11 in this embodiment further includes a manual configuration access sublayer 114, manual level configuration information input by the operator through the manual configuration interface can be received through the manual configuration access sublayer 114, the manual level configuration information includes user identification information of the live broadcast user selected by the operator, the manual level configuration information and the corresponding live broadcast user can be stored in an associated manner based on the user identification information, and the stored manual level configuration information can also be used for subsequent service permission management.
On the basis of the above optimization, the service authority management layer 12 includes:
the level obtaining sublayer 121 is configured to, after receiving a service access request sent by a client, determine an associated user of the service access request, and send a level query request of the associated user to the user content service layer 11, so as to obtain a user permission level of the associated user;
and the permission response sublayer 122 is configured to determine a response permission with respect to the service access request according to the service type in the service access request and the received user permission level of the associated user.
In this embodiment, the service right management layer 12 starts service right management of a live broadcast user by receiving a service access request from a client side, and in this embodiment, the service right management layer 12 is specifically optimized to be the level acquisition sublayer 121 and the right response sublayer 122. The level obtaining sublayer 121 may establish information interaction with the user content service layer 11, and specifically may send a level query request of an associated user corresponding to the service access request to the user content service layer 11, and thereby obtain the user permission level of the associated user. Through the permission response sublayer 122, whether the service corresponding to the service access request can normally respond can be determined according to the user permission level of the associated user.
Further, on the basis of the above optimization for the service right management layer 12, the user content service layer 11 may further be configured to:
receiving a grade query request sent by a service authority management layer 12, and acquiring a user identifier contained in the grade query request to determine an associated user to be searched; if the manual level configuration information of the associated user is determined to exist, feeding back level information contained in the corresponding manual level configuration information as a user permission level to the service permission management layer 12; otherwise, searching a level information cache table; when a target user permission level matched with the associated user is determined from the level information cache table, feeding the target user permission level back to the service permission management layer 12; when the level information cache table does not have a matched user permission level, determining a corresponding user permission level according to the historical accumulated participation duration of the associated user and the historical violation event, and storing and feeding back the corresponding user permission level to the service permission management layer 12.
The present embodiment specifically provides a response operation of the user content service layer 11 to the level query request sent by the service right management layer 12, and through the above operation, the user right level of the associated user may be determined based on manual level configuration information, or the user right level of the associated user may be determined based on a level information cache table cached in Redis, or the user right level of the associated user may not be included in the level information cache table, and the user right level may be determined in real time directly according to historical live broadcast participation information of the associated user. It can be seen that the manual level configuration information is set to have the highest search priority in the present embodiment.
Meanwhile, on the basis of the optimization of the service authority management layer 12, when the service access request is a service request for broadcasting, the corresponding associated user is a first target anchor user; when the service access request is a connecting or block service request, the corresponding associated users are a source user and a target user for connecting or block; and when the service access request is a live list display request, the corresponding associated user is a second target anchor user.
In this embodiment, a relevant limitation that the service right management layer 12 determines the associated user is specifically given, for example, the service right management layer 12 may specifically analyze the service access request, when the service access request is a request for broadcasting, that is, a request formed when a live broadcast room needs to be created for broadcasting, at this time, the corresponding associated user may be marked as a first target anchor user. When the service access request is a connected-to-microphone service request or a pending service request, it can be found that the two service requests at least relate to the interaction of two live broadcast users. When the service access request is a live list display request, that is, a request formed when the user needs to display the played information to the audience user in a list form, the corresponding associated user may be marked as a second target anchor user at this time.
It can be understood that, in this embodiment, the permission response sublayer 122 under the service permission management layer 12 specifically analyzes the service types in the service access request, and when the service types are different, the corresponding associated users are different, and the service permissions to be considered are also different. Specifically, the present embodiment provides different limitations for the execution operation of the permission response sublayer 122 according to different service types corresponding to the service access requests.
For example, the permission response sublayer 122 may specifically determine, when the service type in the service access request is an open service, an open entry identifier of the open service; if the broadcast entry identifier is the small group live broadcast, directly determining that the response authority corresponding to the service request is a normal response; if the broadcast entry identifier is open live broadcast, determining that the response authority corresponding to the service request is normal response when the user authority level of the first target anchor user is a high authority level; when the user permission level of the first target anchor user is a non-high permission level, determining that the response permission corresponding to the service request is a limited response; wherein the non-high privilege level comprises: medium and low permission levels, medium and low permission levels.
For example, the permission response sublayer 122 may specifically determine that the response permission corresponding to the service request is a limited response if the user permission level of the source user or the target user is a low permission level when the service type in the service access request is a continuous service or a block service; otherwise, determining the response authority corresponding to the service request as a normal response.
In addition, the permission response sublayer 122 may specifically determine that the response permission corresponding to the service request is a normal response if the user permission level of the second target anchor user is a high permission level when the service type in the service access request is a live list presentation service; otherwise, determining the response authority corresponding to the service request as a limited response.
It can be known that, when the response right corresponding to the service access request is a normal response, the service right management layer 12 may normally provide a corresponding service response operation for the service access request, and when the response right corresponding to the service access request is a restriction response, the service right management layer 12 considers that the associated user of the service access request does not have the response right of the related service, and ignores the corresponding service response, or provides a related prompt without the service execution right.
It should be noted that, when the service type of the service access request is a live broadcast list display service and the corresponding response permission does not normally respond, the service permission management layer 12 may display live broadcast information corresponding to the associated user in the live broadcast list, but the display position of the live broadcast information in the live broadcast list needs to be further determined according to the user permission levels of the audience users existing in the live broadcast room, if the user permission levels of the audience users are all relatively higher than a level range, the live broadcast information may be displayed at a position before the live broadcast list, and if the user permission levels of the audience users are relatively lower than a level range, the live broadcast information is displayed at a position after the live broadcast list, so as to implement dynamic adjustment of the exposure effect of the main broadcast user.
In this embodiment, an implementation process of determining a response right corresponding to a service access request by a user content service layer and a service right management layer in cooperation with each other is specifically provided, in this embodiment, a user content service layer and a service right management layer are set at a server of a live broadcast application to trigger updating and determining of a user right level of a live broadcast user, and meanwhile, real-time monitoring and management of a user service right at a live broadcast client side are realized by using the determined user right level, so that automatic management control of the user live broadcast right is realized.
EXAMPLE III
Fig. 3 is a flowchart illustrating an example implementation of a live permission management method executed by a live permission management system in a third embodiment of the present invention, where the method is applicable to permission level confirmation and service permission management for a live user with a service access request, and the method may be executed by the live permission management system provided in the first embodiment or the second embodiment of the present invention.
According to the description of the live right management system in the above embodiment, it can be known that the live right management system specifically includes: the system comprises a container management layer containing a container management cluster and a container mirror warehouse, and a live broadcast service layer containing a back-end service process and a service management process, wherein the service management process can perform information interaction with the back-end service process and the container management cluster.
The live broadcast permission management method provided by the third embodiment may be specifically regarded as being implemented by cooperation of layers in a live broadcast permission management system, so as to ensure that a front-end service process is deployed on a container created by a container management cluster when the back-end service process needs to be allocated with the front-end service process.
As shown in fig. 3, a live broadcast authority management method provided in the third embodiment of the present invention specifically includes the following operations:
s301, after monitoring a new permission determination trigger event, the user content service layer determines the user permission level of the corresponding user according to the historical live broadcast participation information of the user corresponding to the permission determination trigger event and caches the user permission level.
For example, a server serving as an execution subject of a user content service layer may monitor a receiving state of an event, and after it is monitored that a new permission determination trigger event is received, a user to be subjected to permission level determination may be analyzed from the permission determination trigger event, and thus, historical live broadcast participation information of a corresponding user is obtained, so as to determine and cache a user permission level of the user.
The permission determination trigger event can be participation duration information or an illegal event fed back by a message publishing subscription layer; the historical live participation information of the user can be historical accumulated participation duration and historical violation events of the user in a set time period before the current time. And determining that the user permission level of the user may be a high permission level, a medium permission level, a low permission level and a low permission level based on the historical live broadcast participation information.
S302, when receiving a service access request sent by a client side, a service authority management layer accesses the user content service layer to obtain the user authority level of a user associated with the service access request, and determines the response authority of the service access request according to the user authority level.
In this embodiment, the service authority management layer may determine, when receiving the service access request, the associated user of the service access request, thereby generating a level query request including user information related to the associated user and sending the level query request to the user content service layer, so as to obtain the user authority level of the associated user through a query operation of the user content service layer, and determine, according to a service authority range corresponding to the user authority level, whether the associated user has an access authority with respect to a service corresponding to the service access request, so as to determine the response authority of the service access request.
In the third technical scheme of this embodiment, after monitoring a new permission determination trigger event, the user content service layer can determine historical live broadcast participation information of a user corresponding to the trigger event according to the permission determination trigger event, determine and cache a user permission level of the corresponding user; when the service authority management layer can receive a service access request sent by a client side, the access user content service layer obtains the user authority level of a user associated with the service access request, and determines the response authority of the service access request according to the user authority level. According to the technical scheme, the user content service layer and the service authority management layer are arranged at the service end of the live broadcast application to trigger the updating and determining of the user authority level of the live broadcast user, meanwhile, the determined user authority level is adopted to realize the real-time monitoring and management of the user service authority of the live broadcast client side, compared with the existing live broadcast authority management, the automatic management control of the user live broadcast authority is realized through the real-time monitoring and analysis of the live broadcast user behavior data, and the management efficiency of the user live broadcast authority is effectively improved.
In an optional embodiment of this embodiment, the live rights management method may further include: the data management layer acquires behavior data generated by a client-side user in real time, determines participation duration data or violation data of a corresponding user according to the behavior data, forms corresponding participation duration information or violation events and feeds back the corresponding participation duration information or violation events to the message publishing and subscribing layer in real time; and the message publishing and subscribing layer caches participation duration information or violation events fed back by the data management layer in real time, selects the participation duration information or the violation events as permission determination trigger events according to a message sending rule, and sends the participation duration information or the violation events to the user content service layer.
The optional embodiment can acquire the behavior data of the live user at the live client side in real time through the data management layer, and forms the trigger event for determining the permission level through the analysis and processing of the acquired behavior data. Meanwhile, considering that the data management layer may receive behavior data of a large number of live users at the same time, analyze and process the behavior data respectively, and may generate a plurality of permission determination trigger events, and the user content service layer may not have the capability of receiving and determining a plurality of user permission levels at the same time, this optional embodiment may buffer data congestion of the data management layer directly to the user content service layer by caching each data information generated by the data management layer through the message publishing subscription layer.
The above technical solution of this optional embodiment realizes effective analysis and processing of behavior data generated in real time by a live broadcast user in the live broadcast authority management system, thereby obtaining prerequisite data with a determined user authority level, and uses the message publishing subscription layer to buffer the influence of massive parallel prerequisite data on processing and calculation of the user content service layer, thereby better embodying the real-time performance and automatic execution performance of the live broadcast authority management.
In addition, in order to facilitate understanding of the determination and management of the service right of the live broadcast user by the live broadcast right management system provided in the embodiment of the present invention, an exemplary embodiment of the execution of the live broadcast right management is also provided in this embodiment. Specifically, fig. 4 shows three exemplary flowcharts of user permission level determination executed by the live broadcast permission management system according to the embodiment of the present invention, and as shown in fig. 4, the process of determining the given user permission level includes the following steps:
and S1, the anchor client sends the anchor behavior data of the anchor user to the data management layer in real time.
The step is a data interaction process of the anchor client and the data management layer, and the data management layer can collect anchor behavior data of an anchor user.
And S2, the data management layer determines the broadcasting duration data of the corresponding anchor user according to the anchor behavior data, combines the anchor associated information of the corresponding anchor user with the broadcasting duration data to form participation duration information, and feeds the participation duration information back to the message publishing subscription layer in real time.
The step is a process of analyzing and processing the anchor behavior data to obtain the play duration data and form participation duration information.
And S3, the audience client sends the audience behavior data of the audience user to the data management layer in real time.
The data interaction process of the audience client and the data management layer is adopted in the step, and the data management layer can collect audience behavior data of audience users.
S4, the data management layer determines the watching duration data of the corresponding audience users according to the audience behavior data, combines the audience correlation information of the corresponding audience users with the watching duration data to form participation duration information, and feeds the participation duration information back to the message publishing subscription layer in real time.
The step is a process of analyzing and processing the audience behavior data to obtain the watching duration data and form the participation duration information.
And S5, the data management layer analyzes the acquired behavior data of the client-side user, and forms a violation event to be stored and fed back to the message publishing and subscribing layer in real time when determining that the corresponding user has a live broadcast violation, a picture violation or a text violation.
The step is a process of carrying out violation detection on behavior data of a client-side user to obtain violation data and forming a violation event.
It is to be understood that the analysis and determination operations of the anchor duration data, the viewing duration data, and the violation data are not limited to be performed sequentially, and the three operations are performed independently.
S6, the message publishing and subscribing layer caches participation duration information or violation events fed back by the data management layer in real time, selects the participation duration information or the violation events as permission determination trigger events according to the message sending rules, and sends the participation duration information or the violation events to the user content service layer.
S7, the user content service layer monitors whether the message publishing subscription layer has new authority to determine the trigger event to send, and receives the authority determination trigger event sent by the message publishing subscription layer.
S8, the user content service layer analyzes the permission determination trigger event to determine a corresponding target user, obtains the historical live broadcast participation information of the target user, determines the user permission level of the target user according to the historical live broadcast participation information and caches the user permission level.
And S9, when the received permission determination trigger event is participation duration information, the user content service layer records the participation duration information into a preset duration record table.
And S10, the user content service layer receives manual grade configuration information input by an operator through a manual configuration interface and stores the manual grade configuration information in association with a corresponding user.
Secondly, the present embodiment mainly uses the interaction between the user content service layer and the service right management layer to describe the process of managing the live broadcast right of the live broadcast user in the actual service in real time by the mutual cooperation between the user content service layer and the service right management layer. Specifically, fig. 5 shows three exemplary flowcharts of the service right management executed by the live broadcast right management system in the embodiment of the present invention, and as shown in fig. 5, the management process of the given service right includes the following interactive operations:
s11, after receiving the service access request sent by the client side, the service authority management layer determines the associated user of the service access request.
S12, the service authority management layer generates the grade inquiry request of the associated user and sends the grade inquiry request to the user content service layer.
S13, the user content service layer obtains the user identification contained in the grade inquiry request to determine the associated user to be searched.
And S14, when the user content service layer determines that the manual level configuration information of the associated user exists, feeding back the level information contained in the corresponding manual level configuration information as the user authority level to the service authority management layer.
S15, when the user content service layer determines that the manual level configuration information of the associated user does not exist, the level information cache table is searched.
S16, when determining the user authority level matched with the associated user from the level information cache table, the user content service layer feeds back the user authority level to the service authority management layer, otherwise, determines the corresponding user authority level according to the historical accumulated participation duration and the historical violation event of the associated user, stores and feeds back the corresponding user authority level to the service authority management layer.
S17, the service authority management layer determines the response authority relative to the service access request according to the service type in the service access request and the received user authority level of the associated user.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (19)

1. A live rights management system, comprising: a user content service layer and a service authority management layer;
the user content service layer is used for determining the historical live broadcast participation information of the user corresponding to the permission determination trigger event according to the permission determination trigger event after monitoring a new permission determination trigger event, determining the user permission level of the corresponding user and caching the user permission level;
and the service authority management layer is used for accessing the user content service layer to obtain the user authority level of the user associated with the service access request when receiving the service access request sent by the client side, and determining the response authority of the service access request according to the user authority level.
2. The system of claim 1, further comprising: a data management layer and a message publishing and subscribing layer;
the data management layer is connected with the message publishing subscription layer and is used for acquiring behavior data generated by a client-side user in real time, determining participation duration data or violation data of a corresponding user according to the behavior data, forming corresponding participation duration information or violation events and feeding back the corresponding participation duration information or violation events to the message publishing subscription layer in real time;
and the message publishing and subscribing layer is connected with the user content service layer and is used for caching participation duration information or violation events fed back by the data management layer in real time, selecting the participation duration information or the violation events as the permission determination trigger events according to a message sending rule and sending the participation duration information or the violation events to the user content service layer.
3. The system of claim 2, wherein the data management layer comprises:
the anchor management sublayer is used for acquiring anchor behavior data generated by an anchor user at an anchor client side in real time, determining broadcasting duration data of a corresponding anchor user according to the anchor behavior data, combining anchor associated information of the corresponding anchor user with the broadcasting duration data to form participation duration information and feeding the participation duration information back to the message publishing subscription layer in real time;
and the audience management sublayer is used for acquiring audience behavior data generated by audience users at the audience client side in real time, determining watching duration data of corresponding audience users according to the audience behavior data, combining audience correlation information of the corresponding audience users with the watching duration data to form participation duration information and feeding the participation duration information back to the message publishing subscription layer in real time.
4. The system of claim 3,
the anchor associated information comprises an anchor user identifier, an anchor room identifier and a room starting creation time;
the audience relevant information comprises audience user identification, watching room identification and watching starting time.
5. The system of claim 2, wherein the data management layer further comprises:
and the violation detection sublayer is used for analyzing the behavior data of the obtained client-side user, and forming violation events to be stored and fed back to the message publishing and subscribing layer in real time when determining that the corresponding user has live broadcast violation, picture violation or character violation.
6. The system of claim 5,
when the client side user is an anchor client side anchor user, the behavior data is anchor behavior data;
when the client side user is a spectator client side spectator user, the behavior data is spectator behavior data.
7. The system according to claim 5, wherein the violation detection sublayer is specifically configured to:
extracting user head portrait picture information, user public screen character information and a current live video frame in the acquired behavior data of the user at the client side;
carrying out violation detection on the user head portrait picture information, the user public screen character information and the current live video frame by adopting corresponding detection strategies;
when detecting that the head portrait picture information of the user, the public screen text information of the user or the illegal object exists in the current live video frame, combining the illegal type of the illegal object and the user identification of the corresponding user with the illegal object to form an illegal event;
and storing the violation event in a preset violation data table, and feeding back the violation event to the message publishing and subscribing layer in real time.
8. The system according to any of claims 2-7, wherein said user content service layer comprises:
the information monitoring sublayer is used for monitoring whether the message publishing and subscribing layer has new authority to determine the sending of a trigger event and receiving the authority to determine the trigger event sent by the message publishing and subscribing layer, wherein the authority to determine the trigger event is participation duration information or an illegal event;
a level determining sublayer for analyzing the permission determining trigger event to determine a corresponding target user, acquiring historical live broadcast participation information possessed by the target user, determining a user permission level of the target user according to the historical live broadcast participation information and caching the user permission level,
wherein the user permission levels include: the service authority which can be executed in different authority levels is different from the high authority level, the medium-low authority level and the low authority level.
9. The system of claim 8, wherein the level determination sub-layer specifically comprises:
the user determination module is used for extracting a user identifier in the participation duration information to determine a target user when the received permission determination triggering event is the participation duration information; or when the received permission determination trigger event is an illegal event, extracting a user identifier included in the illegal event to determine a target user;
the participation information determining module is used for searching the historical accumulated participation duration of the target user in a set time period from a preset duration record table and searching the historical violation event of the target user in the set time period from a preset violation data table;
and the permission level determining module is used for determining and caching the user permission level of the target user according to the historical accumulated participation duration and the historical violation event.
10. The system of claim 9, wherein the permission level determination module is specifically configured to:
a) analyzing all historical violation events of the target user;
b) judging whether the historical violation events exist in a serious violation category, and if not, executing the step c); if yes, executing step e);
c) judging whether the broadcasting accumulated time length in the historical accumulated participation time length is greater than or equal to a first set time length, if so, executing the step d); if not, executing step e);
d) determining that the target user is in an anchor white list, and determining that the corresponding user permission level is a high permission level;
e) determining whether the violation times of violation events included in the historical violation events are greater than or equal to a set violation threshold; if not, executing step f); if yes, executing partial step g);
f) judging whether the watching accumulated time length in the historical accumulated participation time length is less than or equal to a second set time length, if so, executing the step g); if not, executing step h) or step i);
g) determining the user permission level of the target user as a low permission level;
h) when the watching accumulated time length is longer than the second set time length and shorter than a third set time length, determining that the user permission level of the target user is a middle-low permission level;
i) and when the watching accumulated duration is greater than or equal to the third set duration, determining that the user permission level of the target user is a medium-high permission level.
11. The system of claim 8, wherein the user content service layer further comprises:
the information recording sublayer is used for recording the participation duration information into a preset duration recording table when the received permission determination triggering event is the participation duration information;
and the manual configuration access sublayer is used for receiving manual grade configuration information input by an operator through a manual configuration interface and storing the manual grade configuration information in association with a corresponding user.
12. The system of claim 11, wherein the service rights management layer comprises:
the level obtaining sublayer is used for determining a related user of the service access request after receiving the service access request sent by the client side, and sending a level query request of the related user to the user content service layer so as to obtain the user permission level of the related user;
and the permission response sublayer is used for determining the response permission relative to the service access request according to the service type in the service access request and the received user permission level of the associated user.
13. The system of claim 12, wherein the user content service layer is further configured to:
receiving a grade query request sent by a service authority management layer, and acquiring a user identifier contained in the grade query request to determine an associated user to be searched;
if the manual level configuration information of the associated user is determined to exist, feeding back level information contained in the corresponding manual level configuration information as a user authority level to the service authority management layer; if not, then,
searching a grade information cache table;
when a target user permission level matched with the associated user is determined from the level information cache table, feeding the target user permission level back to the service permission management layer;
and when the matched user permission level does not exist in the level information cache table, determining the corresponding user permission level according to the historical accumulated participation duration of the associated user and the historical violation event, and storing and feeding back the corresponding user permission level to the service permission management layer.
14. The system of claim 12,
when the service access request is a service request for broadcasting, the corresponding associated user is a first target anchor user;
when the service access request is a connecting or block service request, the corresponding associated users are a source user and a target user for connecting or block;
and when the service access request is a live list display request, the corresponding associated user is a second target anchor user.
15. The system according to claim 14, wherein the permission response sublayer is specifically configured to:
when the service type in the service access request is a broadcast service, determining a broadcast entry identifier of the broadcast service;
if the broadcast entry identifier is the small group live broadcast, directly determining that the response authority corresponding to the service request is a normal response;
if the broadcast entry identifier is open live broadcast, determining that the response authority corresponding to the service request is normal response when the user authority level of the first target anchor user is a high authority level; when the user permission level of the first target anchor user is a non-high permission level, determining that the response permission corresponding to the service request is a limited response;
wherein the non-high privilege level comprises: medium and low permission levels, medium and low permission levels.
16. The system according to claim 14, wherein the permission response sublayer is specifically configured to:
when the service type in the service access request is a continuous service or a session service, if the user permission level of the source user or the target user is a low permission level, determining that the response permission corresponding to the service request is a limited response; otherwise, determining the response authority corresponding to the service request as a normal response.
17. The system according to claim 14, wherein the permission response sublayer is specifically configured to:
when the service type in the service access request is a live list display service, if the user permission level of the second target anchor user is a high permission level, determining that the response permission corresponding to the service request is a normal response; otherwise, determining the response authority corresponding to the service request as a limited response.
18. A live rights management method, performed by the live rights management system of any one of claims 1-17, the method comprising:
after monitoring a new permission determination trigger event, a user content service layer determines historical live broadcast participation information of a user corresponding to the trigger event according to the permission determination trigger event, determines a user permission level of the corresponding user and caches the user permission level;
when receiving a service access request sent by a client side, a service authority management layer accesses the user content service layer to obtain the user authority level of a user associated with the service access request, and determines the response authority of the service access request according to the user authority level.
19. The method of claim 18, further comprising:
the data management layer acquires behavior data generated by a client-side user in real time, determines participation duration data or violation data of a corresponding user according to the behavior data, forms corresponding participation duration information or violation events and feeds back the corresponding participation duration information or violation events to the message publishing and subscribing layer in real time;
and the message publishing and subscribing layer caches participation duration information or violation events fed back by the data management layer in real time, selects the participation duration information or the violation events as permission determination trigger events according to a message sending rule, and sends the participation duration information or the violation events to the user content service layer.
CN202010276192.4A 2020-04-09 2020-04-09 Live broadcast authority management system and live broadcast authority management method Active CN111491172B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010276192.4A CN111491172B (en) 2020-04-09 2020-04-09 Live broadcast authority management system and live broadcast authority management method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010276192.4A CN111491172B (en) 2020-04-09 2020-04-09 Live broadcast authority management system and live broadcast authority management method

Publications (2)

Publication Number Publication Date
CN111491172A CN111491172A (en) 2020-08-04
CN111491172B true CN111491172B (en) 2021-09-14

Family

ID=71811788

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010276192.4A Active CN111491172B (en) 2020-04-09 2020-04-09 Live broadcast authority management system and live broadcast authority management method

Country Status (1)

Country Link
CN (1) CN111491172B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111954013B (en) * 2020-08-12 2022-11-18 深圳市富途网络科技有限公司 Live broadcast interaction method and device, terminal equipment, server and storage medium
CN113051704A (en) * 2020-10-29 2021-06-29 视伴科技(北京)有限公司 Event activity operation simulation system
CN112637628A (en) * 2020-12-21 2021-04-09 百果园技术(新加坡)有限公司 Live broadcast lottery method, device, equipment and storage medium
CN112822528B (en) * 2020-12-29 2023-04-18 百果园技术(新加坡)有限公司 Live list service system, live list management method, server and medium
CN114173141B (en) * 2021-11-11 2023-10-03 北京量子之歌科技有限公司 Live course authority management method, device, equipment and storage medium
CN114637952A (en) * 2022-04-01 2022-06-17 江苏红网技术股份有限公司 High-security portal website data service management system and method thereof
CN115150672A (en) * 2022-06-23 2022-10-04 广州方硅信息技术有限公司 Live broadcast interaction method and device for simulated workplace and electronic equipment
CN115242746A (en) * 2022-06-29 2022-10-25 赤子城网络技术（北京）有限公司 Safety processing method and system for social application users
CN115936735B (en) * 2023-02-15 2023-06-16 深圳市思为软件技术有限公司 Event processing method and device based on event validity verification
CN117333140B (en) * 2023-11-24 2024-02-20 贵州航天云网科技有限公司 Enterprise information service management system and method

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202893A (en) * 2007-06-27 2008-06-18 深圳市同洲电子股份有限公司 Method, system for preventing non-authorization user from obtaining service and video server
CN104796737A (en) * 2015-04-28 2015-07-22 天脉聚源(北京)传媒科技有限公司 Group-based channel play implementing method, system and equipment
CN105187296A (en) * 2015-08-11 2015-12-23 广州华多网络科技有限公司 Studio authority acquisition method and system
CN105303087A (en) * 2015-11-26 2016-02-03 中国农业银行股份有限公司 User permission information updating method and user permission information updating device
CN106101782A (en) * 2016-05-19 2016-11-09 天脉聚源(北京)传媒科技有限公司 A kind of Open control method and device of channel authority
CN106612250A (en) * 2015-10-21 2017-05-03 腾讯科技（深圳）有限公司 Resource utilization authority judgment system and method
CN110971580A (en) * 2018-09-30 2020-04-07 北京国双科技有限公司 Authority control method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10142596B2 (en) * 2015-02-27 2018-11-27 The United States Of America, As Represented By The Secretary Of The Navy Method and apparatus of secured interactive remote maintenance assist

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202893A (en) * 2007-06-27 2008-06-18 深圳市同洲电子股份有限公司 Method, system for preventing non-authorization user from obtaining service and video server
CN104796737A (en) * 2015-04-28 2015-07-22 天脉聚源(北京)传媒科技有限公司 Group-based channel play implementing method, system and equipment
CN105187296A (en) * 2015-08-11 2015-12-23 广州华多网络科技有限公司 Studio authority acquisition method and system
CN106612250A (en) * 2015-10-21 2017-05-03 腾讯科技（深圳）有限公司 Resource utilization authority judgment system and method
CN105303087A (en) * 2015-11-26 2016-02-03 中国农业银行股份有限公司 User permission information updating method and user permission information updating device
CN106101782A (en) * 2016-05-19 2016-11-09 天脉聚源(北京)传媒科技有限公司 A kind of Open control method and device of channel authority
CN110971580A (en) * 2018-09-30 2020-04-07 北京国双科技有限公司 Authority control method and device

Also Published As

Publication number Publication date
CN111491172A (en) 2020-08-04

Similar Documents

Publication Publication Date Title
CN111491172B (en) Live broadcast authority management system and live broadcast authority management method
EP1971075B1 (en) An information issuing system, a public media information issuing system and an issuing method
CN105210048A (en) Content-identification engine based on social media
CN106415546B (en) For the system and method in local detection institute consumer video content
CN111641866B (en) Method, system, and medium for inserting auxiliary media items into a primary media stream
US20230370656A1 (en) Dynamic Content Insertion On A User-By-User Basis
US20040194130A1 (en) Method and system for advertisement detection and subsitution
EP1769630A2 (en) System and method of anonymous settop event collection and processing in a multimedia network
CN107734362B (en) Video source determination method and device and computer readable storage medium
CN104602045A (en) Automatic sound configuration method, system and device
US20090094230A1 (en) Related information providing apparatus and providing method
CN110784751B (en) Information display method and device
CA2945801A1 (en) Systems and methods for generating network intelligence through real-time analytics
US20180332329A1 (en) Channel change server allocation
CN111797752A (en) Illegal video detection method, device, equipment and storage medium
JP2010283849A (en) Server, user device, program, and index processing method
CN106797327A (en) Performed using the message being associated with adaptive bitrate streaming and the media of mobile platform are monitored
CN107508914A (en) A kind of accurate method for pushing of message and system based on cloud computing analysis
US20080294717A1 (en) Information exchange method, information processor, information gathering system, communication method, communication system, intermediary device, and communication device
CN109086813B (en) Determination method, device and equipment for similarity of anchor and storage medium
US11278818B2 (en) Method for apply gamification techniques to a security system
US20180270543A1 (en) System and method for providing a platform for optimizing overlay location over programming content
US10257557B2 (en) Customized media streams
CN112565828A (en) Live video pushing method
CN112148920A (en) Data management method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20220602

Address after: 31a, 15 / F, building 30, maple mall, bangrang Road, Brazil, Singapore

Patentee after: Baiguoyuan Technology (Singapore) Co.,Ltd.

Address before: 5-13 / F, West Tower, building C, 274 Xingtai Road, Shiqiao street, Panyu District, Guangzhou, Guangdong 510000

Patentee before: GUANGZHOU BAIGUOYUAN INFORMATION TECHNOLOGY Co.,Ltd.

TR01 Transfer of patent right