CN114579204A - Risk control method, device, terminal and storage medium - Google Patents
Risk control method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN114579204A CN114579204A CN202210216741.8A CN202210216741A CN114579204A CN 114579204 A CN114579204 A CN 114579204A CN 202210216741 A CN202210216741 A CN 202210216741A CN 114579204 A CN114579204 A CN 114579204A
- Authority
- CN
- China
- Prior art keywords
- target
- function
- target application
- application
- page
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses a risk control method, a device, a terminal and a storage medium, wherein the risk control method comprises the following steps: starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding to realize the target application function. The scheme can reduce the development workload of adding the shielding.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a risk control method, apparatus, terminal, and storage medium.
Background
At present, in order to deal with risks, shielding of certain product functions is required, and a common scheme in the industry is to shield each page or function to be shielded by adding a related shielding code in a product code according to a shielding scheme proposed by a product manager, but this method brings great workload, and since the entrances of the page and the function may not be unique, omission is easy to occur.
For example, for multiple entries of a page or a function, if there is a multiplexed code, the code is masked at the multiplexed location, otherwise, the code of all the entries of the same page or function needs to be masked, and so on. However, for a large APP, various services are complicated in a cross manner, in an actual development process, for one page, multiple scenes of multiple pages may jump to the page entry, if each page entry is shielded, a lot of workload is inevitably increased, and omission is easy.
Accordingly, there is a need for improvement in the art.
Disclosure of Invention
The embodiment of the application provides a risk control method, a risk control device, a risk control terminal and a risk control storage medium, and can reduce development workload of adding shielding.
An embodiment of the present application provides a risk control method, including:
starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function.
In an alternative embodiment, the application function triggering event comprises a jump new page event;
when the application function triggering event aiming at the target application is responded, the target page information identification corresponding to the target page information providing the target application function is determined, and the method comprises the following steps:
when a new page jumping event aiming at a target application is responded, acquiring a page identifier of a new page corresponding to a new page function as the target page information identifier;
the prohibiting implementing the target application function includes:
and prohibiting the target application from jumping to the new page.
In an optional embodiment, after the starting the target application, the method further includes:
determining a first function used for executing the new page jump event in the target application, and adding a first hook function to the first function to intercept the new page jump event;
and monitoring a new page jump event of the target application through the first hook function.
In an alternative embodiment, the application functionality triggering event comprises a control functionality triggering event;
when the application function triggering event aiming at the target application is responded, the target page information identification corresponding to the target page information providing the target application function is determined, and the method comprises the following steps:
when a control function triggering event aiming at a target control in the target application is responded, determining a target control identification corresponding to the target control as the target page information identification;
the prohibiting implementing the target application function includes:
and forbidding the target control in the target application to trigger the corresponding control function.
In an optional embodiment, the determining a target control identifier corresponding to the target control includes:
acquiring link information of a target control in the target application, and determining each link node corresponding to the target control based on the link information;
and determining node identifications corresponding to the link nodes, and splicing the node identifications based on a preset rule to obtain target control identifications corresponding to the target controls.
In an optional embodiment, after the starting the target application, the method further includes:
determining a second function in the target application for executing the control function triggering event, and adding a second hook function to the second function to intercept the control function triggering event;
and monitoring a control function triggering event of the target application through the second hook function.
In an optional embodiment, after the starting the target application, the method further includes:
reading shielding configuration information corresponding to the target application from the local, and storing the shielding configuration information into a memory;
the obtaining of the shielding configuration information corresponding to the target application includes:
and reading the shielding configuration information from the memory.
In an optional embodiment, after the prohibiting the implementation of the target application function, the method further includes:
and displaying a prompt interface, and displaying shielding prompt information on the prompt interface, wherein the shielding prompt information is used for prompting a user that the target application function is in a forbidden use state.
An embodiment of the present application further provides a risk control device, including:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for starting a target application and acquiring shielding configuration information corresponding to the target application, and the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application;
the detection unit is used for determining a target page information identifier corresponding to target page information providing a target application function when responding to an application function trigger event aiming at a target application, wherein the target application function is an application function triggered by the application function trigger event;
a determining unit, configured to determine whether a page information identifier in the shielding configuration information includes the target page information identifier;
and the forbidding unit is used for forbidding the target application function if the target application function is realized.
The embodiment of the present application further provides a terminal, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein the processor implements the steps of the risk control method when executing the computer program.
Embodiments of the present application further provide a storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps of the risk control method.
The embodiment of the application provides a risk control method, which comprises the following steps: starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function.
According to the scheme, the corresponding application function can be shielded by comparing the page information identifier set in the shielding configuration information with the page information identifier determined by the application function triggering event, and the development workload of adding shielding can be reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are 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 system diagram of a risk control device according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a risk control method according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a risk control device according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the 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 application.
The embodiment of the application provides a risk control method, a risk control device, a terminal and a storage medium. In particular, the present embodiments provide methods applicable to a risk control device, which may be integrated in a computer device.
The Computer device may be a terminal device, such as a smart phone, a tablet Computer, a notebook Computer, a touch screen, a game machine, a Personal Computer (PC), a Personal Digital Assistant (PDA), and the like, and the terminal may further include a client, which may be a game application client, a browser client carrying a game program, or an instant messaging client. The computer device may also be a device such as a server, and the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and a big data and artificial intelligence platform, but is not limited thereto.
Referring to fig. 1, fig. 1 is a system schematic diagram of a risk control device according to an embodiment of the present disclosure. The system may include at least one terminal 1000, at least one server 2000, at least one database 3000, and a network 4000. The terminal 1000 held by the user can be connected to servers of different applications through the network 4000. Terminal 1000 can be any device having computing hardware capable of supporting and executing software products corresponding to application programs. In addition, terminal 1000 can have one or more multi-touch sensitive screens for sensing and obtaining user input through touch or slide operations performed at multiple points on one or more touch sensitive display screens. In addition, when the system includes a plurality of terminals 1000, a plurality of servers 2000, and a plurality of networks 4000, different terminals 1000 may be connected to each other through different networks 4000 and through different servers 2000. The network 4000 may be a wireless network or a wired network, such as a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a cellular network, a 2G network, a 3G network, a 4G network, a 5G network, and so on. In addition, different terminals 1000 may be connected to other terminals or a server using their own bluetooth network or hotspot network. For example, multiple users may be online through different terminals 1000 and thus connected through an appropriate network and synchronized with each other to support multiple users using an application. In addition, the system may include a plurality of databases 3000, the plurality of databases 3000 being coupled to different servers 2000, and information about the environment of the application may be continuously stored in the database 3000 when different users use the application online.
The application discloses a risk control method, which comprises the following steps: starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function.
The application does not limit the type of the target application, and it can be understood that the target application has various application functions and is triggered by corresponding trigger events.
The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
Referring to fig. 2, fig. 2 is a schematic flow chart of a risk control method according to an embodiment of the present disclosure, and as shown in fig. 2, a specific flow of the risk control method according to the embodiment of the present disclosure mainly includes steps 201 to 204, which are described in detail as follows:
201. starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application.
In the embodiment of the application, the terminal generates a starting instruction for the target application according to the operation of the user, and after the terminal detects the starting instruction, the corresponding target application is started. The terminal in the application can locally read the shielding configuration information corresponding to the target application and store the shielding configuration information into the memory; because the configuration information is synchronously stored in the memory, the configuration information can be more efficiently read by the terminal, and the problem that the user is blocked when judging after clicking an entrance is avoided. After the target application is started, the terminal acquires the shielding configuration information corresponding to the target application, that is, the shielding configuration information corresponding to the target application is directly read from the memory.
In the embodiment of the application, each time the application program is started in a hot state or a cold state, the interface is requested to acquire the shielding configuration information issued by the server, and the terminal updates the shielding configuration information in the memory according to the new shielding configuration information.
In the embodiment of the application, the shielding configuration information includes a page information identifier corresponding to page information providing an application function to be shielded in the target application. The application function may include a function of jumping to a new page, for example, jumping to a new page through a sliding operation on a certain page; the application functionality may also include functionality triggered by controls set in the application. The above functions may be prohibited to be used in the current target application, that is, the application function to be shielded may include, in the shielding configuration information, a page information identifier corresponding to the page information providing the application function to be shielded. For example, if the application function to be shielded is a function of sliding left to jump to a new page, the shielding configuration information includes a page information flag corresponding to the new page; and if the application function to be shielded is that a certain control in the application is forbidden to be used, shielding the control identification corresponding to the shielded control in the configuration information.
In the embodiment of the application, for controlling the new page jump event, after the target application is started, a related function used for executing the new page jump event in the target application is determined, the function is set as a first function, the first function is subjected to method replacement, namely, a first hook function is added to the first function to intercept the new page jump event, and the new page jump event of the target application is monitored through the first hook function. For control of the control function trigger event, after the target application is started, a related function used for executing the control function trigger event in the target application is determined, the function is set as a second function, the second function is subjected to method replacement, namely a second hook function is added to the second function to intercept the control function trigger event, and the control function trigger event of the target application is monitored through the second hook function. According to the method and the device, decoupling of the interception codes and the function codes is achieved through hook replacement operation, relevant codes of the shielding function are separated from the function business logic, and the problem that program errors or shielding failure possibly caused by mutual crossing of the business codes and the shielding codes is avoided.
202. When an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, and the target application function is an application function triggered by the application function triggering event.
In the embodiment of the application, when the terminal detects an application function trigger event for a target application, the application function trigger event may include a new page jump event and a control function trigger event. When the terminal responds to an application function triggering event aiming at the target application, a target page information identifier corresponding to target page information providing the target application function is determined, and the target application function is an application function triggered by the application function triggering event. For example, if the target application function is a new page function, the terminal determines a target page information identifier corresponding to target page information providing the new page function, where the target page information providing the new page function is a skipped new page, and the target page information identifier is a page information identifier corresponding to the new page. For example, if the target application function is a control function, the terminal determines a target page information identifier corresponding to target page information providing the control function, where the target page information providing the control function is the target control, and the target page information identifier is a control identifier corresponding to the target control.
In the embodiment of the application, if the application function triggering event is a new page jump event; the step "determining a target page information identifier corresponding to target page information providing a target application function when responding to an application function trigger event for the target application", specifically includes: and when responding to a new page jump event aiming at the target application, acquiring a page identifier of a new page corresponding to the new page function as a target page information identifier. For example, when the terminal detects a new page jump event for the target application and the terminal responds to the new page jump event for the target application, the application function corresponding to the new page jump event is a new page display function, that is, the new page function, and a page identifier corresponding to the new page is obtained, wherein the class name of the page can be used as the page identifier corresponding to the page; for example, the page identifier corresponding to page a is PageA.
In the embodiment of the application, if the application function triggering event is a control function triggering event; the step "determining a target page information identifier corresponding to target page information providing a target application function when responding to an application function trigger event for the target application", specifically includes: and when a control function triggering event aiming at a target control in the target application is responded, determining a target control identification corresponding to the target control as a target page information identification. For example, when the terminal detects a control function triggering event for the target application and the terminal responds to a new page jump event for the target application, and an application function corresponding to the control function triggering event is a control function, a control identifier corresponding to a target control triggering the control function is acquired.
Wherein, the steps are as follows: "determining the target control identifier corresponding to the target control", specifically includes: acquiring link information of a target control in a target application, and determining each link node corresponding to the target control based on the link information; and determining node identifications corresponding to the link nodes, and splicing the node identifications based on a preset rule to obtain target control identifications corresponding to the target controls. For example, taking a target control C as an example, determining link information corresponding to the target control C through configuration item information of a server, that is, determining which button or view in a target application the currently triggered target control C is, for example, determining that the target control C is a control in a page B displayed on a page a, then determining that each link node corresponding to the target control C is the page a, the page B, and the control C, then determining that node identifiers corresponding to the link node, the page a, the page B, and the control C are PageA, PageB, and butterc, and finally splicing the node identifiers through a preset rule to obtain a target control identifier corresponding to the target control. The preset rule may be set according to an actual situation of the application, for example, the target control identifier corresponding to the target control C may be PageA-PageB-button C or button C-PageB-PageA.
It can be understood that the flag in the shielding configuration information needs to be the same as the setting rule of the determined target page information flag. For example, the control identifier in the shielding configuration information includes node identifiers of a plurality of link nodes in the link information of the control, and if the splicing sequence of the control identifier of a control triggering the function of the control to be shielded in the shielding configuration information is started from the identifier of the current page, the determined splicing sequence of the target control identifier is also started from the identifier of the current page.
203. And determining whether the page information identifier in the shielding configuration information contains the target page information identifier.
In the embodiment of the application, after the terminal determines the target page information identifier corresponding to the target page information providing the target application function, the target page information identifier is compared with the obtained shielding configuration information, and whether the page information identifier in the shielding configuration information contains the target page information identifier is determined. If so, the application function corresponding to the target page information identifier is forbidden to be realized, and if not, the application function corresponding to the target page information identifier is normally realized. For example, if the obtained shielding configuration information includes a page information identifier PageB-button D, it indicates that the button D in the page B is shielded, and if the user clicks the button D in the page B at this time, it may be determined that the page information identifier corresponding to the button D is also PageB-button D, and the page information identifier is the same as the page information identifier in the shielding configuration information, the control function corresponding to the button D cannot be implemented.
204. And if so, forbidding the target application function.
In the embodiment of the present application, if the page information identifier in the shielding configuration information includes the target page information identifier, the target application is prohibited from implementing the corresponding target application function.
And if the target application function is the new page function, forbidding the target application function from being realized, and skipping to a new page for forbidding the target application. And if the target application function is the control function, forbidding the target application function from being realized, and triggering the corresponding control function for forbidding the target control in the target application. For example, if the shielding configuration information includes the page identifier of the page D, that is, the class name character string of the page D, for the event of the left-sliding jump to the page D, it indicates that the application may not jump to the page D in the left-sliding manner. For example, if the history information is viewed for the event of clicking the control F, and if the shielding configuration information includes the control identifier of the control F, it indicates that the control F in the application is prohibited from being used.
In the application, the terminal can also display a prompt interface, and if the target application is determined to be prohibited from being realized, shielding prompt information is displayed on the prompt interface of the terminal, wherein the shielding prompt information is used for prompting the current user that the target application function is in a prohibition use state. The display form and content of the shielding prompt message can be set by a user, which is not limited in the present application.
The risk control method of the embodiment of the application is based on the fact that the iOS system is limited about the page display interface and the user clicks the event link to know, and based on the thought that the full link is free of intrusion control, implantation work of risk switch control can be simplified.
In an embodiment of the application, after the terminal device starts an application program, the switch configuration of the local persistent cache is read, assigned to the memory, and the interface is requested to acquire the switch configuration issued by the server for updating each time when the terminal device is started in a hot state and a cold state; wherein, the switch configuration includes the shielding configuration information.
After the application program is started, carrying out method replacement on 'jump new page correlation function' to realize the monitoring of all triggering jump to a new page in the application program, judging the current page when the page is displayed each time, and if the page is a configured page type needing to be forbidden, popping and prompting to prevent the page from entering. Therefore, shielding of specific functional modules can be realized only by configuring related class name character strings at the server, and cost for implementing wind control switch control is reduced to the maximum extent. The method comprises the steps of monitoring all the time of jumping pages, judging interception when jumping is triggered, isolating the time from service codes, and enabling a product manager to realize appointed jumping interception only by configuring class names of corresponding pages in a server background and to customize prompt documents.
For the function provided without jumping to a new page, switching control is performed, and the iOS control object UIControl in the page needs to be monitored, and the function is replaced by clicking when starting, so as to achieve the purpose of monitoring. In the configuration item of the server, the current link stack splicing character string of the control is used as an id identifier (for example, a C button of a page B displayed on a page a can be identified as PageA-PageB-button C), which indicates which button or view is currently clicked. And when clicking, acquiring the class of the current page, analyzing a link stack of the control, splicing a character string as an identifier according to a set rule, comparing the character string with the identifier issued by the background configuration of the server, and popping up a prompt if the character string is consistent with the identifier issued by the background configuration of the server, so as to forbid the button from triggering the related service function. When the switch is newly added, only the character string identification corresponding to the button needs to be newly added at the server side, and the purpose of reducing the development cost is achieved. The function which does not need to jump is shielded, and in the iOS system, the click function can be monitored through hook replacement operation, and the purpose of interception can be achieved by comparing the corresponding button id at the moment.
In the embodiment of the application, because the shielding code is a blocking code, if triggered, the subsequent code cannot be executed. If the shielding code is additionally inserted into the functional service code, the problem that the functional code or the shielding code is invalid is easily caused. The risk control method realizes the decoupling of the interception code and the function code and avoids the problems. In addition, when the regression test is performed in the test stage, a tester can definitely and independently test the shielding module and the functional module, so that the error risk and the troubleshooting cost are reduced.
An embodiment of the present application provides a risk control method, including: starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function. According to the scheme, the corresponding application function can be shielded by comparing the page information identifier set in the shielding configuration information with the page information identifier determined by the application function triggering event, and the development workload of adding shielding can be reduced.
All the above technical solutions can be combined arbitrarily to form the optional embodiments of the present application, and are not described herein again.
In order to better implement the above risk control method, correspondingly, the embodiment of the present application further provides a risk control device, which may be specifically integrated in a computer device, for example, in the form of a terminal.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a risk control device according to an embodiment of the present disclosure. The risk control device comprises an acquisition unit 301, a first determination unit 302, a second determination unit 303 and a prohibition unit 304, as follows:
an obtaining unit 301, configured to start a target application and obtain shielding configuration information corresponding to the target application, where the shielding configuration information includes a page information identifier corresponding to page information providing an application function to be shielded in the target application;
a first determining unit 302, configured to determine, when an application function triggering event for a target application is responded, a target page information identifier corresponding to target page information providing a target application function, where the target application function is an application function triggered by the application function triggering event;
a second determining unit 303, configured to determine whether a page information identifier in the shielding configuration information includes the target page information identifier;
a prohibiting unit 304, configured to prohibit implementing the target application function if yes.
In an alternative embodiment, the application function triggering event comprises a jump new page event;
the first determining unit 302 further includes:
when a new page jumping event aiming at a target application is responded, acquiring a page identifier of a new page corresponding to a new page function as the target page information identifier;
the prohibiting unit 304 further includes:
and prohibiting the target application from jumping to the new page.
In an optional embodiment, the obtaining unit 301 further includes:
determining a first function used for executing the new page jump event in the target application, and adding a first hook function to the first function to intercept the new page jump event;
and monitoring a new page jump event of the target application through the first hook function.
In an alternative embodiment, the application functionality triggering event comprises a control functionality triggering event;
the first determining unit 302 further includes:
when a control function triggering event aiming at a target control in the target application is responded, determining a target control identification corresponding to the target control as the target page information identification;
the prohibiting unit 304 further includes:
and forbidding the target control in the target application to trigger the corresponding control function.
In an optional embodiment, the first determining unit 302 further includes:
acquiring link information of a target control in the target application, and determining each link node corresponding to the target control based on the link information;
and determining node identifications corresponding to the link nodes, and splicing the node identifications based on a preset rule to obtain target control identifications corresponding to the target controls.
In an optional embodiment, the obtaining unit 301 further includes:
determining a second function in the target application for executing the control function triggering event, and adding a second hook function to the second function to intercept the control function triggering event;
and monitoring a control function triggering event of the target application through the second hook function.
In an optional embodiment, the obtaining unit 301 further includes:
reading shielding configuration information corresponding to the target application from the local, and storing the shielding configuration information into a memory;
the acquiring unit 301 further includes:
and reading the shielding configuration information from the memory.
In an optional embodiment, the prohibiting unit 304 further includes:
and displaying a prompt interface, and displaying shielding prompt information on the prompt interface, wherein the shielding prompt information is used for prompting a user that the target application function is in a forbidden use state.
All the above technical solutions can be combined arbitrarily to form the optional embodiments of the present application, and are not described herein again.
In the risk control device provided in this embodiment of the present application, when the obtaining unit 301 starts a target application, shielding configuration information corresponding to the target application is obtained, where the shielding configuration information includes a page information identifier corresponding to page information that provides an application function to be shielded in the target application; then, when the first determining unit 302 responds to an application function triggering event for a target application, it determines a target page information identifier corresponding to target page information providing the target application function, where the target application function is an application function triggered by the application function triggering event; next, when the second determining unit 303 determines whether the page information identifier in the shielding configuration information includes the target page information identifier; finally, the prohibiting unit 304 prohibits the target application function from being implemented if yes.
Correspondingly, the embodiment of the present application further provides a terminal, where the terminal may be a Computer device such as a smart phone, a tablet Computer, a notebook Computer, a touch screen, a game console, a Personal Computer (PC), a Personal Digital Assistant (PDA), and the like. As shown in fig. 4, fig. 4 is a schematic structural diagram of a terminal 400 according to an embodiment of the present invention. The terminal 400 includes a processor 401 having one or more processing cores, a memory 402 having one or more computer-readable storage media, and a computer program stored on the memory 402 and executable on the processor. The processor 401 is electrically connected to the memory 402. Those skilled in the art will appreciate that the terminal 400 illustrated in the figures is not meant to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The processor 401 is a control center of the terminal 400, connects various parts of the entire terminal 400 using various interfaces and lines, performs various functions of the terminal 400 and processes data by running or loading software programs and/or modules stored in the memory 402 and calling data stored in the memory 402, thereby monitoring the entire terminal 400.
In this embodiment, the processor 401 in the terminal 400 loads instructions corresponding to processes of one or more application programs into the memory 402 according to the following steps, and the processor 401 runs the application programs stored in the memory 402, thereby implementing various functions:
starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Optionally, as shown in fig. 4, the terminal 400 further includes: touch-sensitive display screen 403, radio frequency circuit 404, audio circuit 405, input unit 406 and power 407. The processor 401 is electrically connected to the touch display screen 403, the radio frequency circuit 404, the audio circuit 405, the input unit 406, and the power source 407. Those skilled in the art will appreciate that the terminal configuration shown in fig. 4 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The touch display screen 403 may be used for displaying a graphical user interface and receiving operation instructions generated by a user acting on the graphical user interface. The touch display screen 403 may include a display panel and a touch panel. Among other things, the display panel may be used to display information input by or provided to the user and various graphical user interfaces of the terminal, which may be made up of graphics, text, icons, video, and any combination thereof. Alternatively, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations of a user on or near the touch panel (for example, operations of the user on or near the touch panel using any suitable object or accessory such as a finger, a stylus pen, and the like), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Alternatively, the touch panel may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 401, and can receive and execute commands sent by the processor 401. The touch panel may overlay the display panel, and when the touch panel detects a touch operation thereon or nearby, the touch panel may transmit the touch operation to the processor 401 to determine the type of the touch event, and then the processor 401 may provide a corresponding visual output on the display panel according to the type of the touch event. In the embodiment of the present invention, the touch panel and the display panel may be integrated into the touch display screen 403 to realize input and output functions. However, in some embodiments, the touch panel and the touch panel can be implemented as two separate components to perform the input and output functions. That is, the touch display screen 403 may also be used as a part of the input unit 406 to implement an input function.
The rf circuit 404 may be configured to transmit and receive rf signals to establish wireless communication with a network device or other terminals through wireless communication, and to transmit and receive signals with the network device or other terminals.
The audio circuit 405 may be used to provide an audio interface between the user and the terminal through a speaker, microphone. The audio circuit 405 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 405 and converted into audio data, which is then processed by the audio data output processor 401 and then transmitted to, for example, another terminal via the radio frequency circuit 404, or the audio data is output to the memory 402 for further processing. The audio circuit 405 may also include an earbud jack to provide communication of peripheral headphones with the terminal.
The input unit 406 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
The power supply 407 is used to power the various components of the terminal 400. Optionally, the power source 407 may be logically connected to the processor 401 through a power management system, so as to implement functions of managing charging, discharging, power consumption management, and the like through the power management system. The power supply 407 may also include one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, or any other component.
Although not shown in fig. 4, the terminal 400 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described in detail herein.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
As can be seen from the above, the terminal provided in this embodiment may start a target application, and obtain shielding configuration information corresponding to the target application, where the shielding configuration information includes a page information identifier corresponding to page information providing a function of an application to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function. According to the scheme, the corresponding application function can be shielded by comparing the page information identifier set in the shielding configuration information with the page information identifier determined by the application function triggering event, and the development workload of adding shielding can be reduced.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, embodiments of the present application provide a computer-readable storage medium, in which a plurality of computer programs are stored, and the computer programs can be loaded by a processor to execute the steps in any one of the risk control methods provided by the embodiments of the present application. For example, the computer program may perform the steps of:
starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application; when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event; determining whether a page information identifier in the shielding configuration information contains the target page information identifier; and if so, forbidding the target application function.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The method, the apparatus, the terminal and the storage medium for risk control provided in the embodiments of the present application are described in detail above, and specific examples are applied herein to explain the principles and embodiments of the present application, and the description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (11)
1. A risk control method, comprising:
starting a target application, and acquiring shielding configuration information corresponding to the target application, wherein the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application;
when an application function triggering event aiming at a target application is responded, a target page information identifier corresponding to target page information providing the target application function is determined, wherein the target application function is an application function triggered by the application function triggering event;
determining whether a page information identifier in the shielding configuration information contains the target page information identifier;
and if so, forbidding to realize the target application function.
2. The risk control method of claim 1, wherein the application function triggering event comprises a jump new page event;
when the application function trigger event aiming at the target application is responded, the target page information identification corresponding to the target page information providing the target application function is determined, and the method comprises the following steps:
when a new page jumping event aiming at a target application is responded, acquiring a page identifier of a new page corresponding to a new page function as the target page information identifier;
the prohibiting implementing the target application function includes:
and prohibiting the target application from jumping to the new page.
3. The risk control method of claim 2, further comprising, after the launching the target application:
determining a first function used for executing the new page jump event in the target application, and adding a first hook function to the first function to intercept the new page jump event;
and monitoring a new page jump event of the target application through the first hook function.
4. The risk control method of claim 1, wherein the application functionality triggering event comprises a control functionality triggering event;
when the application function trigger event aiming at the target application is responded, the target page information identification corresponding to the target page information providing the target application function is determined, and the method comprises the following steps:
when a control function triggering event aiming at a target control in the target application is responded, determining a target control identification corresponding to the target control as the target page information identification;
the prohibiting implementing the target application function includes:
and forbidding the target control in the target application to trigger the corresponding control function.
5. The risk control method according to claim 4, wherein the determining the target control identifier corresponding to the target control comprises:
acquiring link information of a target control in the target application, and determining each link node corresponding to the target control based on the link information;
and determining node identifications corresponding to the link nodes, and splicing the node identifications based on a preset rule to obtain target control identifications corresponding to the target controls.
6. The risk control method of claim 4, further comprising, after the launching the target application:
determining a second function in the target application for executing the control function triggering event, and adding a second hook function to the second function to intercept the control function triggering event;
and monitoring a control function triggering event of the target application through the second hook function.
7. The risk control method of claim 1, further comprising, after the launching of the target application:
reading shielding configuration information corresponding to the target application from the local, and storing the shielding configuration information into a memory;
the obtaining of the shielding configuration information corresponding to the target application includes:
and reading the shielding configuration information from the memory.
8. The risk control method of claim 1, further comprising, after the inhibiting implementation of the target application function:
and displaying a prompt interface, and displaying shielding prompt information on the prompt interface, wherein the shielding prompt information is used for prompting a user that the target application function is in a forbidden use state.
9. A risk control device, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for starting a target application and acquiring shielding configuration information corresponding to the target application, and the shielding configuration information comprises a page information identifier corresponding to page information providing an application function to be shielded in the target application;
the detection unit is used for determining a target page information identifier corresponding to target page information providing a target application function when responding to an application function trigger event aiming at a target application, wherein the target application function is an application function triggered by the application function trigger event;
a determining unit, configured to determine whether a page information identifier in the shielding configuration information includes the target page information identifier;
and the forbidding unit is used for forbidding the target application function if the target application function is realized.
10. A terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program performs the steps of the risk control method according to any of claims 1-8.
11. A computer-readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, performs the steps of risk control according to any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210216741.8A CN114579204A (en) | 2022-03-07 | 2022-03-07 | Risk control method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210216741.8A CN114579204A (en) | 2022-03-07 | 2022-03-07 | Risk control method, device, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114579204A true CN114579204A (en) | 2022-06-03 |
Family
ID=81778065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210216741.8A Pending CN114579204A (en) | 2022-03-07 | 2022-03-07 | Risk control method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579204A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106936793A (en) * | 2015-12-30 | 2017-07-07 | 腾讯科技（深圳）有限公司 | A kind of information intercepting processing method and terminal |
| CN110647373A (en) * | 2019-09-20 | 2020-01-03 | 北京小米移动软件有限公司 | Application page intercepting method and device |
| CN112380480A (en) * | 2020-12-02 | 2021-02-19 | 北京皮尔布莱尼软件有限公司 | Page jump method, computing device and storage medium |
| CN114035870A (en) * | 2021-10-13 | 2022-02-11 | 青岛海信移动通信技术股份有限公司 | Terminal device, application resource control method and storage medium |
-
2022
- 2022-03-07 CN CN202210216741.8A patent/CN114579204A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106936793A (en) * | 2015-12-30 | 2017-07-07 | 腾讯科技（深圳）有限公司 | A kind of information intercepting processing method and terminal |
| CN110647373A (en) * | 2019-09-20 | 2020-01-03 | 北京小米移动软件有限公司 | Application page intercepting method and device |
| CN112380480A (en) * | 2020-12-02 | 2021-02-19 | 北京皮尔布莱尼软件有限公司 | Page jump method, computing device and storage medium |
| CN114035870A (en) * | 2021-10-13 | 2022-02-11 | 青岛海信移动通信技术股份有限公司 | Terminal device, application resource control method and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20130097416A1 (en) | Dynamic profile switching | |
| WO2016003084A1 (en) | Method and apparatus of notifying of smishing | |
| JP2019506669A (en) | Graphic code display method, apparatus, and storage medium | |
| CN108804153B (en) | Application program preloading method and device, storage medium and terminal | |
| CN114327688B (en) | Data processing method, frame, storage medium and terminal equipment based on micro front end | |
| CN112399006B (en) | File sending method and device and electronic equipment | |
| CN108595965B (en) | Method and device for preventing attribute information of interface control from being stolen | |
| CN113867585A (en) | Interface display method and device, electronic equipment and storage medium | |
| CN111930565B (en) | Process fault self-healing method, device and equipment for components in distributed management system | |
| CN110213597B (en) | Method and device for entering live broadcast room through browser | |
| CN115589432A (en) | Message push management method, device, medium and equipment | |
| CN114579204A (en) | Risk control method, device, terminal and storage medium | |
| CN112558833B (en) | Application running method and device and electronic equipment | |
| CN113138786B (en) | Application updating method and device | |
| CN110753909B (en) | Service scheduling method and device, computer equipment and computer readable storage medium | |
| CN114489858B (en) | Application software information setting method and device, terminal equipment and storage medium | |
| CN115225966B (en) | Application starting method, device, terminal equipment and storage medium | |
| CN112783860B (en) | Method, device, storage medium and computer equipment for constructing mirror image database | |
| CN107920010B (en) | Method and system for realizing temporary session | |
| CN116186333A (en) | User event indexing method, device, electronic equipment and storage medium | |
| CN115779411A (en) | Game acceleration method, game acceleration device, computer equipment and computer readable storage medium | |
| CN115695062A (en) | Object interaction method and device, electronic equipment and storage medium | |
| CN115480819A (en) | Development environment configuration method and device, electronic equipment and readable storage medium | |
| CN116301578A (en) | Parameter configuration method, device, medium and equipment for cache function | |
| CN115103068A (en) | Outbound list generation method and device, storage medium and electronic equipment |
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 |