CN107948171B - User account management method and device - Google Patents
User account management method and device Download PDFInfo
- Publication number
- CN107948171B CN107948171B CN201711236159.3A CN201711236159A CN107948171B CN 107948171 B CN107948171 B CN 107948171B CN 201711236159 A CN201711236159 A CN 201711236159A CN 107948171 B CN107948171 B CN 107948171B
- Authority
- CN
- China
- Prior art keywords
- account
- abnormal
- normal
- removal
- sent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
Abstract
The embodiment of the invention discloses a method and a device for user account management, and belongs to the technical field of internet. The method comprises the following steps: determining abnormal accounts and normal accounts in the accounts according to the account information corresponding to the accounts; endowing each normal account with removal authority to each abnormal account, and setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account; and when a removal request of a first abnormal account in a live broadcast room where a first normal account is located from the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account. By adopting the invention, the removal error can be prevented.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a method and a device for managing a user account.
Background
With the development of electronic technology and internet technology, terminals such as mobile phones and computers are widely used, and the types of application programs on the corresponding terminals are more and more, and the functions are more and more abundant. A live application is a very common application.
The audience accounts can watch the performance of the main broadcasting account through the live broadcasting application program, and in the process of live broadcasting, some audience accounts in the live broadcasting room can publish an unvoiced statement in the live broadcasting room (wherein, the account which publishes the unvoiced statement can be called an abnormal account), so that the normal environment of the live broadcasting room is damaged. To ensure a normal environment for the live room, the server may grant certain account removal rights. Specifically, when an account with a removal authority wants to remove a certain account from the current live broadcast room, the account with the removal authority can trigger the terminal to send a removal request corresponding to the account to the server through operation. After the server receives a removal request corresponding to the account sent by the terminal, the server may delete the account from the live broadcast room, and freeze the account.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
based on the processing method, the account with the removal authority can remove any account in the live broadcast room, and if the account with the removal authority is a normal account, the server still removes the account, so that a removal error is caused.
Disclosure of Invention
In order to solve the problem of removal errors in the related art, embodiments of the present invention provide a method and an apparatus for user account management. The technical scheme is as follows:
in one aspect, a method for user account management is provided, where the method includes:
determining abnormal accounts and normal accounts in the accounts according to the account information corresponding to the accounts;
endowing each normal account with removal authority to each abnormal account, and setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account;
and when a removal request of a first abnormal account in a live broadcast room where a first normal account is located from the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account.
Optionally, after receiving a request sent by a login terminal of a first normal account for removing a first abnormal account in a live broadcast room where the first normal account is located, the removing process performed on the first abnormal account includes:
after a removal request of a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by a login terminal of the first normal account is received, and when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account is received, the comment data are sent to login terminals of other accounts except the first normal account in the live broadcast room.
Optionally, the method further includes:
updating the removed times corresponding to the first abnormal account;
and when the removed times reach a preset time threshold value, freezing the first abnormal account.
Optionally, the account information includes one or more of the following information:
abnormal account reporting information, account behavior data, Internet Protocol (IP) addresses and recharging information.
Optionally, the method further includes:
when receiving a permission menu acquisition request of a first account to a second account, which is sent by a login terminal of the first account, if the first account has a removal permission to the second account, sending a permission menu containing a removal option to the login terminal of the first account.
In one aspect, an apparatus for user account management is provided, where the apparatus includes:
the determining module is used for determining an abnormal account and a normal account in each account according to the account information corresponding to each account;
the giving module is used for giving each normal account with the removing authority to each abnormal account;
the setting module is used for setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account;
and the removing module is used for executing removing processing on the first abnormal account after receiving a removing request of the first normal account to the first abnormal account in the live broadcast room where the first normal account is located, which is sent by the login terminal of the first normal account.
Optionally, the removing module is configured to:
after a removal request of a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by a login terminal of the first normal account is received, and when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account is received, the comment data are sent to login terminals of other accounts except the first normal account in the live broadcast room.
Optionally, the apparatus further comprises:
the updating module is used for updating the removed times corresponding to the first abnormal account;
and the freezing module is used for freezing the first abnormal account when the removed times reach a preset time threshold.
Optionally, the account information includes one or more of the following information:
abnormal account reporting information, account behavior data, Internet Protocol (IP) addresses and recharging information.
Optionally, the apparatus further comprises:
the sending module is used for sending an authority menu containing a removal option to the login terminal of the first account if the first account has a removal authority to the second account when receiving an authority menu acquisition request of the first account to the second account, which is sent by the login terminal of the first account.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, according to the account information corresponding to each account, an abnormal account and a normal account are determined in each account; and when a removal request of the first abnormal account to the first abnormal account in the live broadcast room of the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account. In this way, only the normal account has the removal authority for the abnormal account, the abnormal account does not have any removal authority, the normal account does not have the removal authority for the normal account, and the normal account is not removed by the account having the removal authority, so that the removal error can be prevented.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a method for managing a user account according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an interface provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram of an interface provided by an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an apparatus for user account management according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an apparatus for user account management according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an apparatus for user account management according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a terminal according to an 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.
The embodiment of the invention provides a method for managing a user account, wherein an execution subject of the method is a server. The server may be a server with a removal function, and may be a background server of a live application. The server may include a processor, memory, transceiver, etc. The processor may be a CPU (Central Processing Unit) or the like, and may be used to perform Processing related to the removal Processing. The Memory may be a RAM (Random Access Memory), a Flash Memory, or the like, and may be configured to store received data, data required by the processing procedure, data generated in the processing procedure, or the like, for example, each normal account has a removal right for each abnormal account. The transceiver, which may include an antenna, matching circuitry, a modem, etc., may be used for data transmission with a terminal or other server, such as a location server, for example, to receive a removal request sent by the terminal and may send an authorization menu to the terminal.
The process flow shown in fig. 1 will be described in detail below with reference to specific embodiments, and the contents may be as follows:
The abnormal account may be an account suspected (possibly) to be black powder determined by the server according to the account information, and the normal account may be a civilized account determined by the server according to the account information. The account information may be information reflecting characteristics of the account.
In implementation, a trigger event for determining the abnormal account and the normal account may be set in the server, where the trigger event may be a preset determination period. Specifically, each time a preset determination period is reached, the server may obtain account information corresponding to each account, and further, may determine an abnormal account and a normal account in each account. In the processing mode, the server can uniformly determine the normal account and the abnormal account every time the preset determination period is reached. In addition, the server can also determine whether a certain account is an abnormal account or not. Specifically, when it is detected that a certain account (which may be referred to as a third account) is successfully registered, timing may be started, and when the registration duration reaches a preset duration, the server may obtain account information corresponding to the third account, and further, may determine whether the third account is an abnormal account or a normal account according to the account information corresponding to the third account.
Optionally, the account information may include one or more of the following information: abnormal account reporting information, account behavior data, IP address and recharging information.
In an implementation, when an account (which may be referred to as a fourth account) feels that the account (which may be referred to as a fifth account) is an abnormal account, the fourth account may send, to the server, reporting information for reporting that the fifth account is the abnormal account through the login terminal, after receiving the reporting information, the server may record abnormal account reporting information corresponding to the fifth account as being reported as an abnormal account, and if the server does not receive the reporting information for reporting that the fifth account is the abnormal account, the server may record the abnormal account reporting information corresponding to the fifth account as not being reported as the abnormal account. The server can record abnormal account reporting information corresponding to each account according to the processing mode. When the abnormal account and the normal account are determined, the server can acquire abnormal account reporting information corresponding to each account, and further, the corresponding abnormal account reporting information is determined to be the abnormal account which is reported as the abnormal account, and the corresponding abnormal account reporting information is determined to be the normal account which is not reported as the abnormal account.
The account behavior data may be the number of times of entering and exiting the live broadcast room within a preset duration corresponding to the account, and correspondingly, the server may count the number of times of entering and exiting the live broadcast room within the preset duration corresponding to each account. The abnormal accounts usually frequently enter and exit the live broadcast rooms, so that when the abnormal accounts and the normal accounts are determined, the server can acquire the times of entering and exiting the live broadcast rooms within the preset time length corresponding to each account, further, the accounts with the times of entering and exiting the live broadcast rooms within the preset time length reaching the preset time threshold value can be determined as the abnormal accounts, and the accounts with the times of entering and exiting the live broadcast rooms within the preset time length not reaching the preset time threshold value can be determined as the normal accounts. In addition, when the server detects that a batch of accounts frequently enters the live broadcast room at the same time and exits the live broadcast room at the same time, the batch of accounts can be determined as abnormal accounts, and other accounts can be determined as normal accounts.
The account information may be an IP (Internet Protocol) address, and when determining an abnormal account and a normal account, the server may obtain a current IP address of a login terminal of each account, and may further determine whether the IP address is located in a pre-stored abnormal IP segment, and the server may determine an account whose corresponding IP address is located in the pre-stored abnormal IP segment as the abnormal account, and may determine an account whose corresponding IP address is not located in the pre-stored abnormal IP segment as the normal account.
The account information may include recharge information, wherein the recharge information may be a recharge amount within a preset time duration. When determining the abnormal account and the normal account, the server may obtain the recharge quantity within the preset time length corresponding to each account, and further, may determine the account whose recharge quantity within the corresponding preset time length is smaller than the preset quantity threshold as the abnormal account, and may determine the account whose recharge quantity within the corresponding preset time length reaches the preset quantity threshold as the normal account. In this case, the server may determine the abnormal account determined according to each type of information as the final abnormal account, and the other accounts may be normal accounts. Alternatively, the server may determine the abnormal account determined by the various pieces of information as the final abnormal account, and the other accounts are normal accounts.
And 102, endowing each normal account with the removal authority of each abnormal account, and setting the head portrait of each abnormal account as the head portrait for indicating that each abnormal account is an abnormal account.
In implementation, after the server determines each normal account and each abnormal account, the server may give each normal account a removal authority, where the removal authority is only the removal authority of the normal account to the abnormal account. Specifically, the server may record an authority table, where the authority table may include a exercising authority party and a exercised authority party, and after determining each normal account and each abnormal account, the account identifier of each normal account may be added to the exercising authority party, and the account identifier of each abnormal account may be added to the exercised authority party.
In addition, after the abnormal account is determined, the server may set a head portrait corresponding to the abnormal account, and correspondingly, the server may further perform the following processing: and setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account.
In implementation, after the server determines each abnormal account, the avatar of each abnormal account may be set as a special avatar (where the server may add a special avatar to each abnormal account, or perform a special mark on a normal avatar set for each abnormal account), where the special avatar may be used to indicate that each abnormal account is an avatar of an abnormal account, for example, the avatar of each abnormal account may be set as an avatar with an "abnormal" word. In addition, the head portrait of each set abnormal account is only visible for other accounts and is invisible for the account. That is, when the server receives an avatar acquisition request of a login terminal of a certain account (which may be referred to as a sixth account) to another account (which may be referred to as a seventh account), the server may determine whether the seventh account is an abnormal account, if so, the server may send a special avatar corresponding to the seventh account to the login terminal of the sixth account, otherwise, the server may send a normal avatar pre-uploaded by the seventh account to the login terminal of the sixth account. When the server receives an avatar acquiring request of the login terminal of the sixth account to the sixth account, the server may determine whether the sixth account is an abnormal account, and if so, the server may send a normal avatar pre-uploaded by the sixth account to the login terminal of the sixth account.
For example, when the sixth account enters the live broadcast room where the seventh account is located, and the login terminal of the sixth account sends the avatar acquisition request corresponding to each account in the live broadcast room to the server, the server may determine whether the sixth account is an abnormal account after receiving the avatar acquisition request, and if so, the server may send the normal avatar pre-uploaded by the sixth account for the sixth account, and for other abnormal accounts, the server may send the special avatar set for the abnormal account, and for the normal account, the server may send the normal avatar pre-uploaded by the normal account. Therefore, each account in the live broadcast room can clearly see which accounts are abnormal accounts, and further, the abnormal accounts can be noticed more.
Optionally, the terminal may send an authority menu obtaining request to the server, and when the server receives the authority menu obtaining request, the server may determine a corresponding authority menu based on the authority table, and correspondingly, the server may further perform the following processing: when receiving a permission menu acquisition request of a first account to a second account, which is sent by a login terminal of the first account, if the first account has a removal permission to the second account, sending a permission menu containing a removal option to the login terminal of the first account.
In implementation, an account identifier list of each account in the live broadcast room may be displayed in the live broadcast interface, each account may send comment data to the server through the login terminal while watching a performance of the anchor account, and when the server receives comment data sent by the login terminal of a certain account (may be referred to as an eighth account), the server may send the comment data to the login terminal of each account in the live broadcast room. When an account (which may be referred to as a first account) does not like comment data issued by another account (which may be referred to as a second account), or the first account feels that the behavior of the second account belongs to the behavior of an abnormal account, the login terminal may be triggered to send a permission menu acquisition request of the first account for the second account to the server by an operation (for example, an account identifier of the second account displayed in a live interface may be clicked), after the server receives the permission menu acquisition request sent by the login terminal of the first account, it may be determined whether the first account has a removal permission for the second account in the permission list, and if the first account has the removal permission for the second account, the server may send a permission menu including a removal option to the login terminal of the first account (in this case, the first account is a normal account, and the second account is an abnormal account), the permission menu may further include other permissions of the first account to the second account, and the login terminal of the first account may display the permission menu after receiving the permission menu, as shown in fig. 2. If the first account does not have the removal authority for the second account, the server may send an authority menu not including the removal option to the login terminal of the first account, where the authority menu includes other authorities of the first account for the second account, as shown in fig. 3. If the permission menu received by the login terminal of the first account contains a removal option, the first account can trigger the server to execute removal processing on the second account by clicking the removal option, and the specific processing will be described in the following.
In implementation, when a normal account (which may be referred to as a first normal account) with a removal permission wants to remove a certain abnormal account (which may be referred to as a first abnormal account) in a live broadcast room where a first account is located, a login terminal may be triggered to send a request for removing the first abnormal account from the first normal account to a server through operation.
After the login terminal of the first normal account sends the request for removing the first abnormal account from the first normal account to the server, the server may receive the request for removing the first abnormal account from the first normal account sent by the login terminal of the first normal account, and then may perform removal processing on the first abnormal account.
Optionally, after receiving a request for removing the first abnormal account from the first normal account sent by the login terminal, the server may no longer forward the comment data issued by the first abnormal account to the login terminal, and accordingly, the processing procedure in step 103 may be as follows: after a request for removing a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by the login terminal of the first normal account is received, comment data are sent to the login terminals of other accounts except the first normal account in the live broadcast room when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account are received.
In implementation, after receiving a removal request of a first normal account sent by a login terminal of a first normal account for a first abnormal account in a live broadcast room where the first normal account is located, when receiving comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account, a server may not send comment data to the login terminal of the first normal account any more, and may send comment data to login terminals of other accounts (where the other accounts may be accounts for which the login terminal has not sent the removal request of the first abnormal account) in the live broadcast room besides the first normal account. In addition, after the login terminal of the first normal account sends the request for removing the first abnormal account from the first normal account to the server, the account identifier of the first abnormal account can be deleted from the account identifiers of the accounts displayed on the live interface, that is, the terminal can no longer display the account identifier of the first abnormal account on the live interface. That is to say, after receiving a removal request of a first normal account sent by a login terminal of a first normal account to a first abnormal account in a live broadcast room where the first normal account is located, for the first normal account, the first abnormal account is invisible in the live broadcast room, that is, information related to the first abnormal account is no longer displayed in a live broadcast interface displayed in the login terminal of the first normal account, and for other accounts in the live broadcast room except the first normal account, the first abnormal account is visible in the live broadcast room, that is, information related to the first abnormal account is still displayed in live broadcast interfaces displayed in login terminals of other accounts.
Optionally, when the number of times of removal corresponding to the first abnormal account reaches a preset number threshold, the server may freeze the first abnormal account, and after receiving a request sent by the login terminal of the first normal account to remove the first abnormal account in the live broadcast room where the first normal account is located, the server may further perform the following processing: updating the removed times corresponding to the first abnormal account; and when the removal times reach a preset time threshold value, freezing the first abnormal account.
In implementation, after receiving a removal request of the first normal account to the first abnormal account in the live broadcast room where the first normal account is located, sent by the login terminal of the first normal account, the server may further add one to the removed times corresponding to the first abnormal account, so that the removed times corresponding to the first abnormal account may be updated. After the removal times corresponding to the first abnormal account are updated, the server can judge the removal times corresponding to the first abnormal account and the size of the preset time threshold, and when the removal times are detected to reach the preset time threshold, the server can freeze the first abnormal account, namely the first abnormal account exits from login, and the subsequent first abnormal account cannot log in. In addition, the server may also preset a freezing duration, for example, one day, one month, and the like, in which case, after the server freezes the first abnormal account, the first abnormal account cannot log in within the freezing duration.
Optionally, when it is detected that the number of times of removal reaches the preset number threshold, the server may determine, as a blacklist, in addition to freezing the first abnormal account, and correspondingly, the server may further perform the following processing: and setting the head portrait corresponding to the first abnormal account as a head portrait used for indicating that the first abnormal account is a blacklist.
In implementation, when it is detected that the number of times of removal reaches a preset number threshold, the server may determine the first abnormal account as a blacklist, and may set an avatar corresponding to the first abnormal account as a blacklist avatar, where the blacklist avatar may be used to indicate that the first abnormal account is the blacklist. Therefore, for some reasons, if the server fails to freeze the first abnormal account this time, after the avatar of the first abnormal account is set as the blacklist avatar, it is convenient for other accounts to make sure that the first abnormal account is the blacklist account, and the login terminal can be triggered to send a removal request for the first abnormal account to the server through operation again, so that the server freezes the first abnormal account again.
In the embodiment of the invention, according to the account information corresponding to each account, an abnormal account and a normal account are determined in each account; and when a removal request of the first abnormal account to the first abnormal account in the live broadcast room of the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account. In this way, only the normal account has the removal authority for the abnormal account, the abnormal account does not have any removal authority, the normal account does not have the removal authority for the normal account, and the normal account is not removed by the account having the removal authority, so that the removal error can be prevented.
Based on the same technical concept, an embodiment of the present invention further provides a device for user account management, as shown in fig. 4, the device includes:
the determining module 410 is configured to determine an abnormal account and a normal account in each account according to account information corresponding to each account;
the giving module 420 is used for giving each normal account the removing authority of each abnormal account;
the setting module 430 is configured to set the avatar of each abnormal account as an avatar indicating that each abnormal account is an abnormal account;
the removing module 440 is configured to, after receiving a request sent by a login terminal of a first normal account for removing a first abnormal account in a live broadcast room where the first normal account is located, execute removal processing on the first abnormal account.
Optionally, the removing module 440 is configured to:
after a removal request of a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by a login terminal of the first normal account is received, and when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account is received, the comment data are sent to login terminals of other accounts except the first normal account in the live broadcast room.
Optionally, as shown in fig. 5, the apparatus further includes:
an updating module 450, configured to update the removed times corresponding to the first abnormal account;
a freezing module 460, configured to freeze the first abnormal account when the removed number of times reaches a preset number threshold.
Optionally, the account information includes one or more of the following information:
abnormal account reporting information, account behavior data, Internet Protocol (IP) addresses and recharging information.
Optionally, as shown in fig. 6, the apparatus further includes:
the sending module 470 is configured to, when receiving a request sent by a login terminal of a first account for obtaining an authority menu of the first account for a second account, send an authority menu including a removal option to the login terminal of the first account if the first account has a removal authority for the second account.
In the embodiment of the invention, according to the account information corresponding to each account, an abnormal account and a normal account are determined in each account; and when a removal request of the first abnormal account to the first abnormal account in the live broadcast room of the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account. In this way, only the normal account has the removal authority for the abnormal account, the abnormal account does not have any removal authority, the normal account does not have the removal authority for the normal account, and the normal account is not removed by the account having the removal authority, so that the removal error can be prevented.
It should be noted that: in the device for user account management provided in the foregoing embodiment, when the user account is managed, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the server is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus for user account management and the method embodiment for user account management provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.
Fig. 7 is a block diagram illustrating a terminal 700 according to an exemplary embodiment of the present invention. The terminal 700 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 700 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.
In general, terminal 700 includes: a processor 701 and a memory 702.
The processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 701 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 701 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 701 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
In some embodiments, the terminal 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, a positioning component 708, and a power source 709.
The peripheral interface 703 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 701 and the memory 702. In some embodiments, processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.
The Radio Frequency circuit 704 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 704 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 704 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 704 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 705 is a touch display screen, the display screen 705 also has the ability to capture touch signals on or over the surface of the display screen 705. The touch signal may be input to the processor 701 as a control signal for processing. At this point, the display 705 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 705 may be one, providing the front panel of the terminal 700; in other embodiments, the display 705 can be at least two, respectively disposed on different surfaces of the terminal 700 or in a folded design; in still other embodiments, the display 705 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The Display 705 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.
The camera assembly 706 is used to capture images or video. Optionally, camera assembly 706 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuitry 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing or inputting the electric signals to the radio frequency circuit 704 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 700. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 707 may also include a headphone jack.
The positioning component 708 is used to locate the current geographic Location of the terminal 700 for navigation or LBS (Location Based Service). The Positioning component 708 can be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.
In some embodiments, terminal 700 also includes one or more sensors 710. The one or more sensors 710 include, but are not limited to: acceleration sensor 711, gyro sensor 712, pressure sensor 713, fingerprint sensor 714, optical sensor 715, and proximity sensor 716.
The acceleration sensor 711 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the terminal 700. For example, the acceleration sensor 711 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 701 may control the display screen 705 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 711. The acceleration sensor 711 may also be used for acquisition of motion data of a game or a user.
The gyro sensor 712 may detect a body direction and a rotation angle of the terminal 700, and the gyro sensor 712 may cooperate with the acceleration sensor 711 to acquire a 3D motion of the terminal 700 by the user. From the data collected by the gyro sensor 712, the processor 701 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
Pressure sensors 713 may be disposed on a side frame of terminal 700 and/or underneath display 705. When the pressure sensor 713 is disposed on a side frame of the terminal 700, a user's grip signal on the terminal 700 may be detected, and the processor 701 performs right-left hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at a lower layer of the display screen 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 705. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 714 is used for collecting a fingerprint of a user, and the processor 701 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 714, or the fingerprint sensor 714 identifies the identity of the user according to the collected fingerprint. When the user identity is identified as a trusted identity, the processor 701 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 714 may be disposed on the front, back, or side of the terminal 700. When a physical button or a vendor Logo is provided on the terminal 700, the fingerprint sensor 714 may be integrated with the physical button or the vendor Logo.
The optical sensor 715 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the display screen 705 based on the ambient light intensity collected by the optical sensor 715. Specifically, when the ambient light intensity is high, the display brightness of the display screen 705 is increased; when the ambient light intensity is low, the display brightness of the display screen 705 is adjusted down. In another embodiment, processor 701 may also dynamically adjust the shooting parameters of camera assembly 706 based on the ambient light intensity collected by optical sensor 715.
A proximity sensor 716, also referred to as a distance sensor, is typically disposed on a front panel of the terminal 700. The proximity sensor 716 is used to collect the distance between the user and the front surface of the terminal 700. In one embodiment, when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually decreases, the processor 701 controls the display 705 to switch from the bright screen state to the dark screen state; when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 is gradually increased, the processor 701 controls the display 705 to switch from the breath-screen state to the bright-screen state.
Those skilled in the art will appreciate that the configuration shown in fig. 7 is not intended to be limiting of terminal 700 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
In the embodiment of the invention, according to the account information corresponding to each account, an abnormal account and a normal account are determined in each account; and when a removal request of the first abnormal account to the first abnormal account in the live broadcast room of the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account. In this way, only the normal account has the removal authority for the abnormal account, the abnormal account does not have any removal authority, the normal account does not have the removal authority for the normal account, and the normal account is not removed by the account having the removal authority, so that the removal error can be prevented.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A method for managing a user account is applied to a server, and comprises the following steps:
determining abnormal accounts and normal accounts in the accounts according to the account information corresponding to the accounts;
endowing each normal account with a removal authority for each abnormal account, and setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account, wherein each abnormal account does not have the removal authority for any account;
and when a removal request of a first abnormal account in a live broadcast room where a first normal account is located from the first normal account, which is sent by a login terminal of the first normal account, is received, removing the first abnormal account.
2. The method according to claim 1, wherein after receiving a request sent by a login terminal of a first normal account for removing a first abnormal account in a live broadcast room where the first normal account is located, the removing process performed on the first abnormal account includes:
after a removal request of a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by a login terminal of the first normal account is received, and when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account is received, the comment data are sent to login terminals of other accounts except the first normal account in the live broadcast room.
3. The method of claim 2, further comprising:
updating the removed times corresponding to the first abnormal account;
and when the removed times reach a preset time threshold value, freezing the first abnormal account.
4. The method of claim 1, wherein the account information comprises one or more of the following:
abnormal account reporting information, account behavior data, Internet Protocol (IP) addresses and recharging information.
5. The method of claim 1, further comprising:
when receiving a permission menu acquisition request of a first account to a second account, which is sent by a login terminal of the first account, if the first account has a removal permission to the second account, sending a permission menu containing a removal option to the login terminal of the first account.
6. An apparatus for user account management, the apparatus comprising:
the determining module is used for determining an abnormal account and a normal account in each account according to the account information corresponding to each account;
the system comprises a giving module, a removing module and a judging module, wherein the giving module is used for giving each normal account a removing authority for each abnormal account, and each abnormal account does not have the removing authority for any account;
the setting module is used for setting the head portrait of each abnormal account as a head portrait for indicating that each abnormal account is an abnormal account;
and the removing module is used for executing removing processing on the first abnormal account after receiving a removing request of the first normal account to the first abnormal account in the live broadcast room where the first normal account is located, which is sent by the login terminal of the first normal account.
7. The apparatus of claim 6, wherein the removal module is configured to:
after a removal request of a first abnormal account in a live broadcast room of the first normal account from the first normal account sent by a login terminal of the first normal account is received, and when comment data of the first abnormal account in the live broadcast room sent by the login terminal of the first abnormal account is received, the comment data are sent to login terminals of other accounts except the first normal account in the live broadcast room.
8. The apparatus of claim 7, further comprising:
the updating module is used for updating the removed times corresponding to the first abnormal account;
and the freezing module is used for freezing the first abnormal account when the removed times reach a preset time threshold.
9. The apparatus of claim 6, wherein the account information comprises one or more of the following:
abnormal account reporting information, account behavior data, Internet Protocol (IP) addresses and recharging information.
10. The apparatus of claim 6, further comprising:
the sending module is used for sending an authority menu containing a removal option to the login terminal of the first account if the first account has a removal authority to the second account when receiving an authority menu acquisition request of the first account to the second account, which is sent by the login terminal of the first account.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711236159.3A CN107948171B (en) | 2017-11-30 | 2017-11-30 | User account management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711236159.3A CN107948171B (en) | 2017-11-30 | 2017-11-30 | User account management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107948171A CN107948171A (en) | 2018-04-20 |
| CN107948171B true CN107948171B (en) | 2020-12-22 |
Family
ID=61946900
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711236159.3A Active CN107948171B (en) | 2017-11-30 | 2017-11-30 | User account management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107948171B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008377A (en) * | 2019-10-12 | 2020-04-14 | 中国平安财产保险股份有限公司 | Account monitoring method and device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753760A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Instant messaging group message control method and control device |
| CN105262672A (en) * | 2015-08-31 | 2016-01-20 | 小米科技有限责任公司 | Intra-group anti-harassment method and device |
| CN105657471A (en) * | 2016-01-29 | 2016-06-08 | 广州酷狗计算机科技有限公司 | Account management method and device |
| CN105704016A (en) * | 2016-04-29 | 2016-06-22 | 北京小米移动软件有限公司 | Group message shielding processing method, device and terminal |
| CN107040494A (en) * | 2015-07-29 | 2017-08-11 | 深圳市腾讯计算机系统有限公司 | User account exception prevention method and system |
-
2017
- 2017-11-30 CN CN201711236159.3A patent/CN107948171B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753760A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Instant messaging group message control method and control device |
| CN107040494A (en) * | 2015-07-29 | 2017-08-11 | 深圳市腾讯计算机系统有限公司 | User account exception prevention method and system |
| CN105262672A (en) * | 2015-08-31 | 2016-01-20 | 小米科技有限责任公司 | Intra-group anti-harassment method and device |
| CN105657471A (en) * | 2016-01-29 | 2016-06-08 | 广州酷狗计算机科技有限公司 | Account management method and device |
| CN105704016A (en) * | 2016-04-29 | 2016-06-22 | 北京小米移动软件有限公司 | Group message shielding processing method, device and terminal |
Non-Patent Citations (1)
| Title |
|---|
| 在QQ群中怎么设置屏蔽某个成员的发言，https://www.jb51.net/qq/433235.html;佚名;《www.jb51.net》;20160214;1-4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107948171A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110674022B (en) | Behavior data acquisition method and device and storage medium | |
| CN110278464B (en) | Method and device for displaying list | |
| CN110308956B (en) | Application interface display method and device and mobile terminal | |
| CN111107389B (en) | Method, device and system for determining live broadcast watching time length | |
| CN110839128B (en) | Photographing behavior detection method and device and storage medium | |
| CN111083516A (en) | Live broadcast processing method and device | |
| CN107896337B (en) | Information popularization method and device and storage medium | |
| CN110569220A (en) | Game resource file display method and device, terminal and storage medium | |
| CN109783176B (en) | Page switching method and device | |
| CN109660876B (en) | Method and device for displaying list | |
| CN108401194B (en) | Time stamp determination method, apparatus and computer-readable storage medium | |
| CN111131392A (en) | Method, device, electronic equipment and medium for processing message | |
| CN110769120A (en) | Method, device, equipment and storage medium for message reminding | |
| CN108683699B (en) | Method and device for forwarding service request | |
| CN110825465A (en) | Log data processing method and device, electronic equipment and storage medium | |
| CN107948171B (en) | User account management method and device | |
| CN110971692B (en) | Method and device for opening service and computer storage medium | |
| CN110380956B (en) | Method, device and system for transmitting instant communication message | |
| CN113836426A (en) | Information pushing method and device and electronic equipment | |
| CN108310767B (en) | Information display method, device, equipment and computer readable storage medium | |
| CN109189525B (en) | Method, device and equipment for loading sub-page and computer readable storage medium | |
| CN113099378A (en) | Positioning method, device, equipment and storage medium | |
| CN112000576A (en) | Code data detection method, device, equipment and storage medium | |
| CN111158780A (en) | Method, device, electronic equipment and medium for storing application data | |
| CN110941458A (en) | Method, device and equipment for starting application program and storage medium |
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 |