WO2019223667A1 - 一种用于终端的信息查询方法及终端 - Google Patents

一种用于终端的信息查询方法及终端 Download PDF

Info

Publication number
WO2019223667A1
WO2019223667A1 PCT/CN2019/087703 CN2019087703W WO2019223667A1 WO 2019223667 A1 WO2019223667 A1 WO 2019223667A1 CN 2019087703 W CN2019087703 W CN 2019087703W WO 2019223667 A1 WO2019223667 A1 WO 2019223667A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
request
query
time
service information
Prior art date
Application number
PCT/CN2019/087703
Other languages
English (en)
French (fr)
Inventor
闫伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to US17/053,796 priority Critical patent/US11650993B2/en
Publication of WO2019223667A1 publication Critical patent/WO2019223667A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24564—Applying rules; Deductive queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/217—Database tuning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2477—Temporal data queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/248—Presentation of query results

Definitions

  • the present application relates to the field of communication technologies, and in particular, to an information query method and a terminal for a terminal.
  • the business system provides query of basic business information for the application (APP) of the terminal.
  • the terminal's APP includes: video app, application market app, game market app, music app, reading app, etc.
  • the basic business information includes: virtual currency, User points, user avatars, etc.
  • the basic service information of these APPs is the same.
  • a plurality of client APPs such as the video app, application market app, game market app, music app, and reading app, initiate a request to its back-end application server.
  • the received request initiates a business request to the business system.
  • the business system is provided with a flow control module and a business processing subsystem.
  • the flow control module performs flow control on the requests of multiple applications. When the business requests of multiple applications exceed the processing capacity of the business processing subsystem, the flow control module will Requests that exceed their processing capacity are discarded and a system busy response is returned to the application server side. Each application server returns a system busy and other failure information to its corresponding APP.
  • the service system will receive the request.
  • Multiple applications on the same terminal may send the same service request to their application server at the same time (or at short intervals), such as Obtain user virtual currency information, but since the basic user information of each APP in the operating system of the terminal is the same, the basic information corresponding to the same service request is also the same.
  • the wireless access method such as 4generation mobile communication technology (4G)
  • unnecessary bandwidth traffic of users is increased, and the processing pressure of the service system is increased.
  • the embodiments of the present application provide an information query method and terminal for a terminal, which are used to reduce unnecessary bandwidth traffic of a user and reduce processing pressure of a service system when querying service information in a terminal APP.
  • a first aspect of the embodiments of the present application provides an information query method for a terminal, which specifically includes: the terminal receives a first request, where the first request is used to instruct querying a target service of a first application APP on the terminal Information; and then the terminal determines whether to process the first request at the terminal or to request a service system associated with the terminal to process the first request according to a query policy preset in the terminal.
  • a query policy is preset in the terminal according to the embodiment of the present application.
  • the terminal can filter out a part of query requests according to the query policy.
  • the filtered query request can be processed internally in the terminal without sending to the service system side, thereby reducing the user's
  • the necessary bandwidth traffic reduces the processing pressure of business systems.
  • the method before receiving the first request, further includes: receiving, by the terminal, the target service information according to the second request, where the The second request instructs to query the target service information of the second APP on the terminal; and then stores the target service information and records the storage time of the target service information.
  • the target service information obtained from the service system is already stored in the terminal, which improves the implementability and integrity of the solution.
  • the terminal processes the first request or sends a service associated with the terminal according to a query policy preset in the terminal.
  • the system request to process the first request includes: when the first request meets a first condition, the terminal requests the service system to process the first request, wherein the first condition includes: the target service is not stored in the terminal
  • the service type of the information and / or the target service information is a first service type; when the first request does not satisfy the first condition, it is determined that the first service is processed at the terminal according to a storage duration of the target service information in the terminal.
  • the request is still a request from the business system to process the first request.
  • the terminal determines whether to process the first request within the terminal or send the first request to the service system according to the storage duration of the target service information, which can be filtered. Some query requests are dropped, which can reduce unnecessary bandwidth traffic for users and reduce the processing pressure of business systems.
  • processing the first request includes: the terminal determining whether the storage duration is greater than a first preset duration and less than a second preset duration, wherein the first preset duration and the second preset duration are respectively different from the first APP
  • the target service information corresponds; if the storage duration of the target service information is greater than the first preset duration and less than the second preset duration, the target service information is queried from the terminal.
  • a part of the query request can be processed inside the terminal, which can reduce unnecessary bandwidth traffic of the user and reduce the processing pressure of the business system.
  • determining whether the storage duration is greater than a first preset duration and less than a second preset duration includes: the terminal determines that the storage time and Whether the time interval between query times is greater than the first preset time length and smaller than the second preset time length, and the query time is the time when the first request is received.
  • This implementation manner provides a specific acquisition form of the storage duration, which increases the operability of the solution.
  • processing the first request includes: the terminal determining whether the storage duration is greater than a second preset duration, wherein the second preset duration corresponds to the target service information of the first APP; if the storage duration is greater than the second preset duration If the duration is set, then the first request is sent to the service system; and then the target service information sent by the service system is received.
  • This implementation manner provides another way for the terminal to process the first request, and sends the first request to the service system, and sends query requests that cannot be processed internally by the terminal to the service system for processing, thereby improving the realizability and integrity of the solution.
  • determining whether the storage duration is greater than a second preset duration includes: the terminal determining a time interval between the storage time and the query time Whether it is longer than the second preset time length, wherein the query time is the time when the first request is received.
  • the method further includes: storing the target service information and recording the target Storage time of business information.
  • the terminal after receiving the target service information from the service system, the terminal also stores the target service information, which increases the realizability and integrity of the solution.
  • processing the first request includes: the terminal determines whether the storage duration is shorter than a first preset duration, wherein the first preset duration corresponds to the target service information of the first APP; if it is shorter than the first preset duration, Then the terminal returns the request failure information to the first APP.
  • the request failure information is returned to the corresponding APP to avoid the terminal from frequently sending the same type of query information to the service system, and it can Avoid APP malicious programs from sending a large number of query requests to business systems.
  • determining whether the storage duration is shorter than the first preset duration includes: determining a time interval between the storage time and the query time Whether it is shorter than the first preset duration, the query time is the time when the first request is received.
  • the query strategy further includes: a range of APPs to which the query strategy is applicable in the terminal.
  • the query strategy in this implementation manner also includes the applicable scope of the query strategy, which improves the completeness of the solution.
  • a second aspect of the embodiments of the present application provides a terminal, including: a first receiving unit configured to receive a first request, where the first request is used to indicate a target of querying a first application APP on the terminal; Service information; a determining unit, configured to determine, according to a query policy preset in the terminal, to process the first request at the terminal or to request a service system associated with the terminal to process the first request.
  • a query policy is preset in the terminal according to the embodiment of the present application.
  • the terminal can filter out a part of query requests according to the query policy.
  • the filtered query request can be processed internally in the terminal without sending to the service system side, thereby reducing the user's
  • the necessary bandwidth traffic reduces the processing pressure of business systems.
  • the terminal further includes: a second receiving unit, configured to receive the target service information according to a second request, the second request Instructs to query the target service information of the second APP on the terminal; a storage unit, configured to store the target service information and record a storage time of the target service information.
  • a second receiving unit configured to receive the target service information according to a second request, the second request Instructs to query the target service information of the second APP on the terminal
  • a storage unit configured to store the target service information and record a storage time of the target service information.
  • the determination unit includes: a first processing subunit, configured to: when the first request meets a first condition, The service system requests to process the first request, and the first condition includes: the service type in which the target service information is not stored in the terminal and / or the target service information is a first service type; and a second processing subunit is used when When the first request does not satisfy the first condition, it is determined that the first request is processed at the terminal or the service system is requested to process the first request according to a storage duration of the target service information in the terminal.
  • the terminal determines whether to process the first request within the terminal or send the first request to the service system according to the storage duration of the target service information, which can be filtered. Some query requests are dropped, which can reduce unnecessary bandwidth traffic for users and reduce the processing pressure of business systems.
  • the second processing subunit includes: a first determining module, configured to determine whether the storage duration is greater than a first preset duration And is shorter than the second preset duration, the first preset duration and the second preset duration respectively correspond to the target service information of the first APP; the query module is configured to: when the storage duration is greater than the first preset duration When the duration is less than the second preset duration, the target service information is queried from the terminal.
  • a part of the query request can be processed inside the terminal, which can reduce unnecessary bandwidth traffic of the user and reduce the processing pressure of the business system.
  • the first determining module is specifically configured to determine whether a time interval between the storage time and the query time is greater than a first preset time.
  • the duration is set to be shorter than the second preset duration, and the query time is the time when the first request is received.
  • the second processing subunit includes: a second determining module, configured to determine whether the storage duration is greater than a second preset duration The second preset duration corresponds to the target service information of the first APP; a sending module is configured to send the first request to the service system when the storage duration is greater than the second preset duration; receive A module for receiving the target service information sent by the service system.
  • This implementation manner provides another way for the terminal to process the first request, and sends the first request to the service system, and sends query requests that cannot be processed internally by the terminal to the service system for processing, thereby improving the realizability and integrity of the solution.
  • the second determining module is specifically configured to determine whether a time interval between the storage time and the query time is greater than the second time.
  • the preset time length is the time when the first request is received.
  • the second processing subunit further includes: a storage module, configured to store the target service information and record the target service information. Store moments.
  • the terminal after receiving the target service information from the service system, the terminal also stores the target service information, which increases the realizability and integrity of the solution.
  • the second processing subunit includes: a third determining module, configured to determine whether the storage duration is less than a first preset duration , The first preset duration corresponds to the target service information of the first APP; a return module is configured to return request failure information to the first APP when the first preset duration is less than the first preset duration.
  • the request failure information is returned to the corresponding APP to avoid the terminal from frequently sending the same type of query information to the service system, and it can be sent from the terminal. Avoid APP malicious programs from sending a large number of query requests to business systems.
  • the third determining module is specifically configured to determine whether a time interval between the storage time and the query time is less than the first time
  • the preset time length is the time when the first request is received.
  • the query strategy further includes a range of APPs to which the query strategy is applicable in the terminal.
  • the query strategy in this implementation manner also includes the applicable scope of the query strategy, which improves the completeness of the solution.
  • a third aspect of the embodiments of the present application provides a terminal, which is characterized in that the terminal includes a processor, a memory, and a transceiver.
  • the processor, the memory, and the transceiver are connected through a bus.
  • the memory stores computer instructions.
  • the processor executes the computer instructions in the memory, the processor is configured to implement any implementation manner as in the first aspect.
  • Another aspect of the present application provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when executed on a computer, causes the computer to perform the methods described in the above aspects.
  • Yet another aspect of the present application provides a computer program product containing instructions that, when run on a computer, causes the computer to perform the methods described in the above aspects.
  • FIG. 1a is a schematic diagram of an application scenario in an embodiment of the present application.
  • FIG. 1b is a schematic diagram of an interface model definition of a query strategy in an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an embodiment of an information query method for a terminal according to an embodiment of the present application
  • 3a is a schematic diagram of a scenario for a method for querying information of a terminal according to an embodiment of the present application
  • 3b is a schematic diagram of another scenario of a method for querying information of a terminal according to an embodiment of the present application.
  • 3c is a schematic diagram of another scenario of an information query method for a terminal according to an embodiment of the present application.
  • 4a is a schematic diagram of another scenario of an information query method for a terminal according to an embodiment of the present application.
  • 4b is a schematic diagram of another scenario of an information query method for a terminal according to an embodiment of the present application.
  • 4c is a schematic diagram of another scenario of an information query method for a terminal according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 6 is another schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 7 is another schematic structural diagram of a terminal according to an embodiment of the present application.
  • the embodiments of the present application provide an information query method and terminal for a terminal, which are used to reduce unnecessary bandwidth traffic of a user and reduce processing pressure of a service system when querying service information in a terminal APP.
  • the terminal in the embodiment of the present application is provided with a query policy, wherein the query policy may be configured by an administrator through a policy configuration module in a business system, or may be configured by another server.
  • the device configured with the query policy is not limited here. After the device has configured the query policy, the configured query policy will be sent to the terminal.
  • an administrator uses a policy configuration module in a business system to configure a query policy as an example to describe the solution in this application.
  • FIG. 1a is a schematic diagram of an application scenario in an embodiment of the present application.
  • the application scenario diagram includes a terminal 200 and a service system 300.
  • the terminal 200 includes a client module 211 and a service agent module 212.
  • a service system 300 includes a policy configuration module 311, a policy library 312, a flow control module 313, and a service processing module 314.
  • the administrator sets the query policy in the policy configuration module 311 in the business system 300, then stores the set query policy in the policy database 312, and sends the query policy to the business proxy module 212 on the terminal 200 side.
  • the flow control module 313 is used to perform unified flow control on the query requests issued by the service agent module 212 on the terminal 200 side, and provides a terminal as a unit to perform a flow of query requests for service information of multiple APPs on a terminal. control.
  • the service processing module 314 is configured to process the received query request and return corresponding service information to the service proxy module 212 according to the query request.
  • the query request sent by the user through the APP in the client module 211 will be sent to the business agent module 212 first, and then the business agent module 212 determines whether to use the app according to a preset query policy.
  • the query request is sent to the cloud-side business system 300.
  • the query strategy includes: determining whether the query request received by the terminal 200 satisfies the first condition, and if the first condition is met, Request the business system 300 to process the query request. If the first condition is not met, determine whether to process the query request at the terminal 200 or request the business system to process the query request according to the storage duration of the target service information in the terminal 200.
  • the first condition is Including: the service type in which the target service information and / or the target service information is not stored in the terminal 200 is the first service type, the target service information is the service information corresponding to the query request, and the first service type is the one that needs to be requested from the service system. business type.
  • FIG. 1b An interface model definition of the query strategy in this application is shown in Figure 1b.
  • the policy model set corresponds to the service type (each service type corresponds to a policy model set.
  • the policy model set contains multiple query models).
  • Each policy model in the policy model set corresponds to a type of APP.
  • 1 and n in Figure 1b mean one or more meanings.
  • the policy model includes:
  • the request failure information is returned to the first APP, where the first APP is an APP corresponding to the query request.
  • the policy model set in the embodiment of the present application is stored in a storage area corresponding to a service type corresponding to the policy model set.
  • the query strategy in the embodiment of the present application further includes: a range of APPs applicable to the terminal where the query strategy is located.
  • the updated query strategy is synchronously updated to the business agent module 212 in the terminal 200.
  • the business The agent module 212 returns the information that the query policy is successfully updated to the business system 300.
  • an embodiment of an information query method for a terminal in an embodiment of the present application includes:
  • the terminal receives a first request.
  • the user when the user wants to query the target service information of the first APP installed on the terminal, the user will open the first APP in the terminal and query the target service information of the first APP through the first APP, where the target The service information belongs to basic service information.
  • the basic service information includes: virtual currency, user points, user avatar, etc .; as shown in FIG. 1a, the first APP in the terminal client module receives the first request from the user, and then The request is sent to the service proxy module in the terminal, and the service proxy module is allowed to process the first request.
  • FIG. 3a is a schematic diagram of a user opening the music app.
  • the terminal responds to the user's operation of opening the music app, and displays a page as shown in FIG. 3b.
  • Figure 3b is a schematic diagram of the terminal displaying the content of the Music APP and opening the "Account” operation. After the terminal opens the "Account” operation accordingly, the page shown in Figure 3c is displayed, and then click "User Points Information" in Figure 3c At this time, the terminal receives the first request triggered by the user.
  • the terminal determines whether the first request meets a first condition; if the first condition is satisfied, steps 203 to 205 are performed; if the first condition is not satisfied, step 206 is performed.
  • the service proxy module in the terminal after receiving the first request in the terminal, the service proxy module in the terminal first determines whether the first request meets the first condition, that is, determines whether a target corresponding to the first request already exists in the terminal.
  • the service proxy module determines whether the target service information corresponding to the first request is stored in the terminal, and determines whether the target service type is the first service type. There is no sequence.
  • the service agent module can determine that the first request meets the first condition as long as it determines that the first request meets one of the conditions.
  • the terminal sends a first request to the service system.
  • the terminal when the terminal determines that the first request meets the first condition, that is, that the target service information is not stored in the terminal and / or the target service type is the first service type, the terminal sends the first request to the service system to allow the service system To process the first request.
  • the terminal receives feedback information sent by the service system.
  • the service system sends feedback information according to the first request, where the feedback information includes: target service information or the system is busy information.
  • the business system will determine the processing capacity of the system at this time through the flow control module shown in Figure 1a. If the first request exceeds the processing capacity of the business system, the flow control module will The first request is discarded and the system busy response is returned to the service proxy module in the terminal. The service proxy module returns the system's busy interface to the first app that initiated the request. At this time, the terminal interface can be shown in Figure 4a. The interface displays "The system is busy, please try again later." If the business system still has processing capabilities, the flow control module sends a first request to the business processing module, and the business processing module sends the first request to the business processing module. The service proxy module in the terminal returns the target service information.
  • the specific processing procedure after the service system receives the first request is the prior art, and details are not described herein.
  • the terminal stores the received target service information and stores the storage time of the target service information.
  • the service agent module when the feedback information received by the service agent module in the terminal is the target service information, the service agent module will store the target service information and record the storage time of the target service information, and then the service agent module will transfer the target service The information is returned to the first APP that initiated the request.
  • the terminal interface may be as shown in FIG. 4b, and the specific user point information "user points: 3325 points" is displayed on the interface.
  • the feedback information received by the service agent module in the terminal is system busy information, it is not listed as a separate step in FIG. 2, but it can be understood by those skilled in the art.
  • the terminal determines the storage duration of the target service information in the terminal. If the storage duration is greater than the first preset duration and less than the second preset duration, step 207 is performed; if the storage duration is shorter than the first preset duration, execute Step 208: If the storage duration is greater than the second preset duration, execute steps 209 to 211.
  • the terminal when it is determined that the target service information is stored in the terminal and the service type corresponding to the first request is not the first service type, the terminal needs to determine the storage duration of the target service information stored in the terminal.
  • the storage duration of the target service information determined by the terminal in the terminal includes: a time interval between the storage time and the query time of the target service information determined by the terminal, where the storage time is the time when the terminal receives the first request.
  • the service agent module in the terminal determines whether the first request meets the first condition after receiving the first request. If it is determined that the first request is not satisfied, In the first condition, the service proxy module finds a policy model set corresponding to the service type according to the service type corresponding to the first request, and then finds the first policy model set in the policy model set according to the APP type (music APP) of the first APP.
  • APP corresponding policy model where the policy model is:
  • the cache time of the user's credit information locally cached at the terminal is 12:12:30, and the query time of the first request is 12:12:40, the cache time and query time of the user's credit information The difference is 10 seconds, 10 seconds is greater than 2 seconds and less than 30 seconds.
  • the terminal has user point information longer than 2 seconds and less than 30 seconds. Query target business information.
  • the cache time of the user's credit information locally cached at the terminal is 12:12:39, and the query time of the first request is 12:12:40. The difference between them is 1 second, and 1 second is less than 2 seconds.
  • the terminal has user point information stored for less than 2 seconds, and then the request failure information is returned to the music APP at this time.
  • the cache time of the user's credit information locally cached at the terminal is 12:11:40, and the query time of the first request is 12:12:30.
  • the time difference is 50 seconds, and 50 seconds is greater than 30 seconds.
  • the user point information stored in the terminal for more than 30 seconds at this time, then requests the business system to process the first request.
  • the time duration of the first preset duration and the second preset duration corresponds to the service type corresponding to the first request (the service type of the target service information) and the APP corresponding to the first request, that is, APPs with different service types.
  • the duration of the first preset duration and the second preset duration may be different, and the duration of the first preset duration and the second preset duration may be different for different service types in the same APP.
  • the administrator will set a corresponding first preset duration and a second preset duration for each service type in each APP.
  • the values of the first preset duration and the second preset duration are not specifically limited here.
  • the terminal Before the terminal receives the first request, the terminal also receives a second request.
  • the second request instructs to query the target service information of the second APP on the terminal, and the terminal obtains the target from the service system according to the second request.
  • Service information, and the target service information and the storage time of the target service information are recorded in the terminal.
  • the target service information will be automatically deleted after a certain length of time (for example, 40 seconds), and the storage time at which the target service information is stored is also cleared.
  • the second APP may be the same APP as the first APP. , Or an APP different from the first APP.
  • the terminal after the terminal receives the first request triggered by the user, the terminal will not directly send the first request to the cloud-side business system, but will be first processed by the service proxy module in the terminal in FIG. 1a.
  • a query strategy is preset in the service proxy module.
  • the service proxy module receives the first request, it determines whether the first request meets the first condition, and if the first condition is satisfied, sends the first request to the business system. If the first condition is not satisfied, the corresponding policy model is called according to the service type corresponding to the first request and the APP corresponding to the first request, and then the target business information is queried according to the policy model.
  • the terminal queries the target service information from its own cache.
  • the terminal when the terminal stores the target service information whose storage duration is longer than the first preset duration and shorter than the second preset duration, the terminal extracts the target service information from its own cache to the first APP, and the terminal interface At this time, as shown in FIG. 4b, the terminal responds to the first request, and displays specific user point information "user points: 3325 points" on the interface.
  • the terminal extracts the target service information from its own cache.
  • the terminal does not record the storage time of the target service information again. Only when the terminal obtains service information from the service system side, the terminal stores the service information and records and stores the service information. Storage moment.
  • the terminal When the terminal receives the first request, it does not forward the query request directly to the service system, but determines whether to forward the received query request to the service system according to the query policy in the service proxy module. As in this embodiment, When it is learned according to the query strategy that the target service information is stored in the terminal for a storage period longer than the first preset duration and shorter than the second preset duration, the target service information is directly extracted from the terminal's own cache at this time.
  • the terminal returns request failure information to the first APP.
  • the terminal when the terminal learns according to step 206 that target service information with a storage duration shorter than the first preset duration is stored in the terminal (that is, other APPs or the first APP in the terminal are within the first preset duration at this time) Have requested the same business information as the first request), then the terminal returns the request failure information to the first APP at this time, and the interface of the terminal at this time may display the specific information indicating the request failure as shown in FIG. 4c. Too frequent, please try again later. "
  • the terminal sends a first request to the service system.
  • the service proxy module when the terminal learns according to step 206 that the storage duration of the target service information in the terminal is longer than the second preset duration (that is, the APP in the terminal has not sent the requested target service within the second preset duration).
  • Information query request the service proxy module will send a first request to the service system.
  • the business system After the business system receives the first request, the business system will determine the processing capacity of the system at this time through the flow control module shown in Figure 1a. If the first request exceeds the processing capacity of the business system, the flow control module will A request is discarded and the system busy response is returned to the service proxy module in the terminal. The service proxy module returns the system's busy interface to the first APP that initiated the request. At this time, the terminal interface can be shown in Figure 4a. The message "The system is busy, please try again later" is displayed; if the business system still has processing capabilities, the flow control module sends a first request to the business processing module, and the business processing module sends the first request to the terminal according to the received first request. The service proxy module in the server returns the target service information.
  • the specific processing procedure after the service system receives the first request is the prior art, and details are not described herein.
  • the terminal receives feedback information sent by a service system.
  • the terminal stores the received target service information and records a storage time of the target service information.
  • steps 210 to 211 are similar to steps 204 to 205, and details are not described herein again.
  • the query strategy in the embodiment of the present application can be updated and is not static, so the specific query strategy is not limited here.
  • the target service information will be automatically deleted after being stored for a certain length of time, and the storage time of the target service information of the terminal is also deleted at this time.
  • the service agent module receives the first request for querying the target service information, it cannot query the terminal.
  • the target service information is stored.
  • the terminal forwards the request to the service system.
  • the terminal receives a first request, where the first request is used for instructing to query target service information of a first APP on the terminal; and then determining the location of the service according to a query policy preset in the terminal.
  • the terminal processes the first request or requests a service system associated with the terminal to process the first request.
  • the embodiment of the present application queries the target service information according to a preset query strategy, and can filter part of the query requests.
  • the filtered query requests do not need to be sent to the service system. Therefore, when querying the service information in the terminal APP, the user can effectively reduce The necessary bandwidth traffic reduces the processing pressure of business systems.
  • the embodiment of the present application can also prevent the APP malicious program from sending a large number of query requests to the business system from the end, which greatly reduces the processing pressure of the business system.
  • multiple APPs of the same type The business information is the same.
  • the business system implements the control and query capability of the user terminal as a unit for querying the business information, instead of using the APP as a unit.
  • the service to the user is more balanced, and multiple APPs on a user terminal are avoided in a short time.
  • Business systems request the same business information, reducing unnecessary bandwidth traffic for users. And through the local cache to quickly return the query results of the APP in the terminal, the user experience can be effectively improved.
  • An embodiment of the terminal in the embodiment of the present application includes:
  • a first receiving unit 501 configured to receive a first request for instructing to query target service information of a first application APP on the terminal;
  • a determining unit 502 is configured to determine, according to a query policy preset in the terminal, to process the first request at the terminal or to request a service system associated with the terminal to process the first request.
  • FIG. 6 another embodiment of the terminal in the embodiment of the present application includes:
  • a second receiving unit 601 configured to receive target service information according to a second request, where the second request instructs to query the target service information of the second APP on the terminal;
  • the storage unit 602 is configured to store the target service information and record a storage time of the target service information.
  • a first receiving unit 603, configured to receive a first request for instructing to query target service information of a first application APP on the terminal;
  • a determining unit 604 is configured to determine, according to a query policy preset in the terminal, to process the first request at the terminal or to request a service system associated with the terminal to process the first request.
  • the determining unit 604 includes:
  • a first processing subunit 6041 configured to request the service system to process the first request when the first request meets a first condition, the first condition includes: the target service information is not stored in the terminal and / or The service type of the target service information is a first service type;
  • a second processing subunit 6042 configured to determine, when the first request does not satisfy the first condition, to process the first request at the terminal or request the service system to process the first request according to a storage duration of the target service information in the terminal; First request.
  • the second processing sub-unit 6042 includes:
  • a first determining module 60421 is configured to determine whether the storage duration is greater than a first preset duration and less than a second preset duration, and the first preset duration and the second preset duration are respectively related to the target service of the first APP.
  • the query module 60422 is configured to query the target service information from the terminal when the storage duration is greater than the first preset duration and less than the second preset duration.
  • the first determining module 60421 is specifically configured to:
  • the second processing sub-unit 6042 includes:
  • a second determining module 60423, configured to determine whether the storage duration is greater than a second preset duration, where the second preset duration corresponds to the target service information of the first APP;
  • the storage module 60426 is configured to store the target service information and record a storage time of the target service information.
  • the second determining module 60423 is specifically configured to:
  • the second processing sub-unit 6042 includes:
  • the third determining module 60427 is configured to determine whether the storage duration is less than a first preset duration, where the first preset duration corresponds to the target service information of the first APP;
  • a return module 60428 is configured to return the request failure information to the first APP when the time is less than the first preset duration.
  • the third determining module 60427 is specifically configured to:
  • an embodiment of the present application further provides a terminal 700 including: one or more processors 702, a receiver 703, a transmitter 704, a memory 701, and a bus 705.
  • processors 702, a receiver 703, a transmitter 704, and a memory 701 are connected to each other through a bus 705.
  • the one or more processors 702 are configured to run at least one application program in the background and clean up at least one target application program according to user data.
  • the user data is statistical data obtained based on a history of a user using the application; and the target application is an application that meets a preset rule determined according to the user data.
  • the memory 701 stores one or more programs.
  • the memory 701 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, at least one application (Application, APP) required for a function, and the like.
  • the storage data area may store data and the like created according to the use of the terminal 700.
  • the memory 701 may include a high-speed random access memory, and may further include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the one or more processors 702 may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit). ASIC), Field Programmable Gate Array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • the processor may also be a combination that realizes computing functions, for example, a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the receiver 703 and the transmitter 704 are used for the terminal 700 and other devices to communicate with each other.
  • the bus 705 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, or the like.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • wired such as coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk (SSD)), and the like.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium , Including a number of instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks or optical disks, and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Software Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例公开了一种用于终端的信息查询方法及终端，用于在查询终端APP中的业务信息时，减少用户不必要的带宽流量，降低业务系统的处理压力。本申请实施例方法包括：接收第一请求，所述第一请求用于指示查询所述终端上的第一应用APP的目标业务信息；根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求。

Description

一种用于终端的信息查询方法及终端
本申请要求于2018年5月24日递交中国专利局、申请号为201810511527.9、发明名称为“一种用于终端的信息查询方法及终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种用于终端的信息查询方法及终端。
背景技术
业务系统为终端的应用(application，APP)提供基本业务信息的查询，终端的APP包括：视频APP、应用市场APP、游戏市场APP、音乐APP、阅读APP等，其中基本业务信息包括：虚拟货币、用户积分、用户头像等，在同一个终端中，这些APP的基本业务信息相同。
现有技术中，为了实现上述查询，由上述视频APP、应用市场APP、游戏市场APP、音乐APP、阅读APP等多个客户端APP，向其后端的应用服务器发起请求，各应用服务器再根据接收到的请求向业务系统发起业务请求。
业务系统内设有流量控制模块和业务处理子系统，流量控制模块对多个应用的请求进行流量控制，当多个应用的业务请求超过了业务处理子系统的处理能力时，由流量控制模块将超过其处理能力的请求丢弃，并返回系统忙响应到应用服务器侧，各应用服务器返回系统忙等失败信息到其对应的APP。
现有技术中的只要终端的APP发起请求，业务系统就会收到该请求，在同一个终端上的多个应用可能同时(或者间隔时间很短)向其应用服务器发出相同的业务请求，如获取用户虚拟货币信息等，但由于终端的操作系统内的各个APP的用户基本信息都相同，故相同的业务请求对应的基本信息也相同，多个应用发出相同的业务请求时，会造成了用户多条业务请求到业务系统，在第四代移动通信技术(4generation mobile communication technology，4G)等无线接入的方式下，增加了用户不必要的带宽流量，且增大了业务系统的处理压力。
发明内容
本申请实施例提供了一种用于终端的信息查询方法及终端，用于在查询终端APP中的业务信息时，减少用户不必要的带宽流量，降低业务系统的处理压力。
本申请实施例的第一方面提供了一种用于终端的信息查询方法，具体包括：终端接收第一请求，其中，该第一请求用于指示查询该终端上的第一应用APP的目标业务信息；然后该终端再根据该终端内预置的查询策略确定在该终端处理该第一请求还是向与该终端关联的业务系统请求处理该第一请求。本申请实施例的终端中预置有查询策略，终端可以根据该查询策略过滤掉一部分查询请求，过滤掉的查询请求可以在终端内部处理，而不需要发送至业务系统侧，从而可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第一方面的第一种实现方式中，在接收第一请求之前，该方法还包括：终端根据第二请求接收该目标业务信息，其中，该第二请求指示查询终端上的第二APP的该目标业务信息；然后存储该目标业务信息以及记录该目标业务信息的存储时刻。本实现方式中，在终端接收第一请求之前，终端中已经存储有从业务系统中获取的目标业务信息了，提升了方案的可实现性和完整性。
在一种可能的设计中，在本申请实施例第一方面的第二种实现方式中，根据该终端内预置的查询策略确定在该终端处理该第一请求或者向与该终端关联的业务系统请求处理该第一请求包括：当该第一请求满足第一条件的时候，终端向该业务系统请求处理该第一请求，其中，该第一条件包括：该终端内不存有该目标业务信息和/或该目标业务信息的业务类型为第一业务类型；当该第一请求不满足该第一条件的时候，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求还是向该业务系统请求处理该第一请求。本实现方式中，当第一请求不满足第一条件的时候，终端会根据目标业务信息的存储时长确定要在该终端内部处理该第一请求还是将该第一请求发送至业务系统，可以过滤掉部分查询请求，从而可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第一方面的第三种实现方式中，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求或者向该业务系统请求处理该第一请求包括：终端确定该存储时长是否大于第一预设时长且小于第二预设时长，其中，该第一预设时长与该第二预设时长分别与该第一APP的该目标业务信息相对应；如果目标业务信息的存储时长大于该第一预设时长且小于该第二预设时长，则从该终端中查询该目标业务信息。本实现方式中，可以在终端内部处理一部分查询请求，可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第一方面的第四种实现方式中，确定该存储时长是否大于第一预设时长且小于第二预设时长包括：终端确定该存储时刻与查询时刻之间的时间间隔是否大于第一预设时长且小于第二预设时长，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第一方面的第五种实现方式中，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求或者向该业务系统请求处理该第一请求包括：终端确定该存储时长是否大于第二预设时长，其中，该第二预设时长与该第一APP的该目标业务信息相对应；如果该存储时长大于该第二预设时长，那么则将该第一请求发送至该业务系统；然后接收该业务系统发送的该目标业务信息。本实现方式提供了终端处理第一请求的另一种方式，向业务系统发送该第一请求，将终端内部不能处理的查询请求发送至业务系统处理，提升了方案的可实现性和完整性。
在一种可能的设计中，在本申请实施例第一方面的第六种实现方式中，确定该存储时长是否大于第二预设时长包括：终端确定该存储时刻与查询时刻之间的时间间隔是否大于该第二预设时长，其中，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第一方面的第七种实现方式中，接收该业务系统发送的该目标业务信息之后，该方法还包括：存储该目标业务信息以及记录该目标业务 信息的存储时刻。本实现方式中，从业务系统中接收到目标业务信息之后，终端还要存储该目标业务信息，增加了方案的可实现性可完整性。
在一种可能的设计中，在本申请实施例第一方面的第八种实现方式中，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求或者向该业务系统请求处理该第一请求包括：终端确定该存储时长是否小于第一预设时长，其中，该第一预设时长与该第一APP的该目标业务信息相对应；如果小于该第一预设时长，那么终端则向该第一APP返回请求失败信息。本实现方式中，当终端中的目标业务信息存储时间小于第一预设时长时，则向相应的APP返回请求失败信息，避免终端频繁向业务系统发送同一类型的查询信息，并且可以从端上避免APP恶意程序向业务系统发送大量的查询请求。
在一种可能的设计中，在本申请实施例第一方面的第九种实现方式中，该确定该存储时长是否小于第一预设时长包括：确定该存储时刻与查询时刻之间的时间间隔是否小于该第一预设时长，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第一方面的第十种实现方式中，该查询策略还包括：该查询策略在该终端中适用的APP的范围。本实现方式中的查询策略还包括该查询策略的适用范围，提升了方案的完善度。
本申请实施例的第二方面提供了一种终端，其特征在于，包括：第一接收单元，用于接收第一请求，该第一请求用于指示查询该终端上的第一应用APP的目标业务信息；确定单元，用于根据该终端内预置的查询策略确定在该终端处理该第一请求或者向与该终端关联的业务系统请求处理该第一请求。本申请实施例的终端中预置有查询策略，终端可以根据该查询策略过滤掉一部分查询请求，过滤掉的查询请求可以在终端内部处理，而不需要发送至业务系统侧，从而可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第二方面的第一种实现方式中，该终端还包括：第二接收单元，用于根据第二请求接收该目标业务信息，该第二请求指示查询终端上的第二APP的该目标业务信息；存储单元，用于存储该目标业务信息以及记录该目标业务信息的存储时刻。本实现方式中，在终端接收第一请求之前，终端中已经存储有从业务系统中获取的目标业务信息了，提升了方案的可实现性和完整性。
在一种可能的设计中，在本申请实施例第二方面的第二种实现方式中，该确定单元包括：第一处理子单元，用于当该第一请求满足第一条件时，向该业务系统请求处理该第一请求，该第一条件包括：该终端内不存有该目标业务信息和/或该目标业务信息的业务类型为第一业务类型；第二处理子单元，用于当该第一请求不满足该第一条件时，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求或者向该业务系统请求处理该第一请求。本实现方式中，当第一请求不满足第一条件的时候，终端会根据目标业务信息的存储时长确定要在该终端内部处理该第一请求还是将该第一请求发送至业务系统，可以过滤掉部分查询请求，从而可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第二方面的第三种实现方式中，该第二处理子单元包括：第一确定模块，用于确定该存储时长是否大于第一预设时长且小于第二预设时长，该第一预设时长与该第二预设时长分别与该第一APP的该目标业务信息相对应；查询 模块，用于当该存储时长大于该第一预设时长且小于该第二预设时长时，从该终端中查询该目标业务信息。本实现方式中，可以在终端内部处理一部分查询请求，可以减少用户不必要的带宽流量，降低业务系统的处理压力。
在一种可能的设计中，在本申请实施例第二方面的第四种实现方式中，该第一确定模块具体用于：确定该存储时刻与查询时刻之间的时间间隔是否大于第一预设时长且小于第二预设时长，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第二方面的第五种实现方式中，该第二处理子单元包括：第二确定模块，用于确定该存储时长是否大于第二预设时长，该第二预设时长与该第一APP的该目标业务信息相对应；发送模块，用于当该存储时长大于该第二预设时长时，将该第一请求发送至该业务系统；接收模块，用于接收该业务系统发送的该目标业务信息。本实现方式提供了终端处理第一请求的另一种方式，向业务系统发送该第一请求，将终端内部不能处理的查询请求发送至业务系统处理，提升了方案的可实现性和完整性。
在一种可能的设计中，在本申请实施例第二方面的第六种实现方式中，该第二确定模块具体用于：确定该存储时刻与查询时刻之间的时间间隔是否大于该第二预设时长，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第二方面的第七种实现方式中，该第二处理子单元还包括：存储模块，用于存储该目标业务信息以及记录该目标业务信息的存储时刻。本实现方式中，从业务系统中接收到目标业务信息之后，终端还要存储该目标业务信息，增加了方案的可实现性可完整性。
在一种可能的设计中，在本申请实施例第二方面的第八种实现方式中，该第二处理子单元包括：第三确定模块，用于确定该存储时长是否小于第一预设时长，该第一预设时长与该第一APP的该目标业务信息相对应；返回模块，用于当小于该第一预设时长时，向该第一APP返回请求失败信息。本实现方式中，当终端中的目标业务信息存储时间小于第一预设时长时，则向相应的APP返回请求失败信息，避免终端频繁向业务系统发送同一类型的查询信息，并且可以从端上避免APP恶意程序向业务系统发送大量的查询请求。
在一种可能的设计中，在本申请实施例第二方面的第九种实现方式中，该第三确定模块具体用于：确定该存储时刻与查询时刻之间的时间间隔是否小于该第一预设时长，该查询时刻为接收该第一请求的时刻。本实现方式提供了存储时长的具体获取形式，增加了方案的可操作性。
在一种可能的设计中，在本申请实施例第二方面的第十种实现方式中，该查询策略还包括：该查询策略在该终端中适用的APP的范围。本实现方式中的查询策略还包括该查询策略的适用范围，提升了方案的完善度。
本申请实施例的第三方面提供了一种终端，其特征在于，该终端包括：处理器、存储器、收发器，该处理器、存储器以及收发器通过总线连接，该存储器存储有计算机指令，该处理器在执行该存储器中的计算机指令时，用于实现如第一方面任意一种实现方式。
本申请的又一方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储 有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的又一方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1a为本申请实施例中的一种应用场景示意图；
图1b为本申请实施例中查询策略的一个接口模型定义示意图；
图2为本申请实施例中用于终端的信息查询方法的一个实施例示意图；
图3a为本申请实施例中用于终端的信息查询方法的一种场景示意图；
图3b为本申请实施例中用于终端的信息查询方法的另一种场景示意图；
图3c为本申请实施例中用于终端的信息查询方法的另一种场景示意图；
图4a为本申请实施例中用于终端的信息查询方法的另一种场景示意图；
图4b为本申请实施例中用于终端的信息查询方法的另一种场景示意图；
图4c为本申请实施例中用于终端的信息查询方法的另一种场景示意图；
图5为本申请实施例中终端的一种结构示意图；
图6为本申请实施例中终端的另一种结构示意图；
图7为本申请实施例中终端的另一种结构示意图。
具体实施方式
本申请实施例提供了一种用于终端的信息查询方法及终端，用于在查询终端APP中的业务信息时，减少用户不必要的带宽流量，降低业务系统的处理压力。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例中的终端设置有查询策略，其中，该查询策略可以由管理员通过业务系统中的策略配置模块配置，也可以通过其他服务器配置，配置该查询策略的设备此处不做限定，该设备配置好查询策略后，将配置好的查询策略将发送至终端上。本实施例中以管理员通过业务系统中的策略配置模块配置查询策略为例对本申请中的方案进行说明。
如图1a所示，图1a为本申请实施例中的一个应用场景示意图，该应用场景示意图中包括终端200和业务系统300，其中，终端200包括客户端模块211和业务代理模块212；业务系统300包括策略配置模块311、策略库312、流量控制模块313和业务处理模块314。管理员在业务系统300中的策略配置模块311中设置查询策略，然后将设置好的查询策略存储于策略库312中，再将查询策略发送到终端200侧的业务代理模块212中。
其中，流量控制模块313用于对终端200侧的业务代理模块212发出的查询请求进行 统一的流量控制，提供以一个终端为单元，对一个终端上的多个APP的业务信息的查询请求进行流量控制。
业务处理模块314用于处理接收到的查询请求，并根据查询请求向业务代理模块212返回对应的业务信息。
客户端模块211中设置有多类APP，用户通过客户端模块211中的APP发送的查询请求将会先发送至业务代理模块212，再由业务代理模块212根据预置的查询策略确定是否将该查询请求发送到云侧的业务系统300中。
需要说明的是，终端200在接收查询请求之前，终端200会接收业务系统300发送的查询策略，该查询策略包括：判断终端200接收到的查询请求是否满足第一条件，若符合第一条件则向业务系统300请求处理该查询请求，若不符合第一条件则根据终端200内目标业务信息的存储时长确定在终端200处理该查询请求或者向业务系统请求处理该查询请求，其中，第一条件包括：终端200内不存有目标业务信息和/或目标业务信息的业务类型为第一业务类型，目标业务信息为与该查询请求对应的业务信息，第一业务类型为需要向业务系统请求的业务类型。
其中，本申请中查询策略的一个接口模型定义如图1b所示，查询策略中存有多种策略模型集合，该策略模型集合与业务类型对应(每一种业务类型对应一种策略模型集合，策略模型集合中包含多种查询模型)，策略模型集合中的每种策略模型对应一类APP，其中，图1b中的1和n的意思是一个和多个的意思，其中，策略模型包括：
1、若该存储时长大于第一预设时长且小于第二预设时长，则从终端中查询目标业务信息；
2、若该存储时长大于第二预设时长，则向业务系统请求处理该查询请求；
3、若该存储时长小于第二预设时长，则向第一APP返回请求失败信息，其中，第一APP为与该查询请求对应的APP。
需要说明的是，本申请实施例中的策略模型集合存储于与该策略模型集合对应的业务类型所对应的存储区域。
需要说明的是，本申请实施例中的查询策略还包括：查询策略所在终端适用的APP的范围。
需要说明的是，当业务系统300中的查询策略有更新时，更新后的查询策略会同步更新至终端200中的业务代理模块212中，当业务代理模块212中的查询策略更新完毕之后，业务代理模块212会向业务系统300返回查询策略更新成功的信息。
请参阅图2，本申请实施例中用于终端的信息查询方法的一个实施例包括：
201、终端接收第一请求。
本实施例中，当用户想查询安装在终端上的第一APP的目标业务信息时，用户会打开终端中的第一APP，并且通过第一APP查询第一APP的目标业务信息，其中，目标业务信息属于基本业务信息，基本业务信息包括：虚拟货币、用户积分、用户头像等；如图1a所示，终端客户端模块中的第一APP接收到用户的第一请求，然后将该第一请求发送至终端终端中的业务代理模块，让业务代理模块对第一请求进行处理。
例如，当第一APP为音乐APP，目标业务信息为用户积分信息时，具体操作如图3a所 示，图3a为用户对音乐APP进行打开操作的一个示意图。终端响应用户对音乐APP进行打开的操作，显示如图3b所示的页面。图3b为终端显示音乐APP的页面内容并进行打开“帐号”操作的一个示意图，终端相应打开“帐号”操作之后，显示如图3c所示的页面，再点击图3c中的“用户积分信息”，此时，终端便接收到了用户触发的第一请求。
202、终端判断第一请求是否满足第一条件；若满足第一条件，则执行步骤203至205，若不满足第一条件，则执行步骤206。
本实施例中，当终端中接收到第一请求之后，首先终端内的业务代理模块会判断该第一请求是否满足第一条件，即判断终端内是否已经存有与该第一请求对应的目标业务信息和/或该目标业务类型是否为第一业务类型，其中，第一业务类型为需要向业务系统请求的业务类型，例如心跳请求。
需要说明的是，在本申请实施例中，业务代理模块判断终端内是否存有与该第一请求对应的目标业务信息，和判断该目标业务类型是否为第一业务类型中的两个判断动作无先后顺序，业务代理模块只要判断第一请求满足其中一个条件就可以确定第一请求满足第一条件。
203、终端向业务系统发送第一请求。
本实施例中，当终端判断第一请求满足第一条件，即终端内不存有目标业务信息和/或目标业务类型为第一业务类型时，终端向业务系统发送第一请求，让业务系统来处理该第一请求。
204、终端接收业务系统发送的反馈信息。
本实施例中，当终端中的业务代理模块将第一请求发送至业务系统侧之后，业务系统会根据该第一请求发送反馈信息，其中，该反馈信息包括：目标业务信息或所述系统繁忙信息。
即当业务系统接收到该第一请求之后，业务系统会通过如图1a中的流量控制模块判断此时系统的处理能力，若第一请求超过了业务系统的处理能力时，由流量控制模块将第一请求丢弃，并返回系统繁忙的响应到终端中的业务代理模块中，业务代理模块将系统繁忙的接口返回到发起请求的第一APP中，此时终端界面可以如图4a所示，在界面上显示“系统繁忙，请稍后再试”；若业务系统的还有处理能力时，此时流量控制模块将第一请求发送至业务处理模块，业务处理模块根据接收到的第一请求向终端中的业务代理模块返回目标业务信息，其中，业务系统接收到第一请求之后的具体处理过程为现有技术，具体此处不做赘述。
205、终端存储接收到的目标业务信息以及记录所述目标业务信息的存储时刻。
本实施例中，当终端中的业务代理模块接收到的反馈信息为目标业务信息时，业务代理模块将存储该目标业务信息并记录该目标业务信息的存储时刻，然后业务代理模块将该目标业务信息返回到发起请求的第一APP中，此时终端界面可以如图4b所示，在界面上显示具体的用户积分信息“用户积分：3325分”。
需要说明的是，当终端中的业务代理模块接收到的反馈信息为系统繁忙信息时，附图2上没有列为单独的一个步骤，但是本领域技术人员可以理解。
206、终端确定目标业务信息在终端中的存储时长，若该存储时长大于第一预设时长且 小于第二预设时长，则执行步骤207；若该存储时长小于第一预设时长，则执行步骤208，若该存储时长大于第二预设时长，则执行步骤209至211。
本实施例中，当确定终端中存有目标业务信息，且第一请求对应的业务类型不为第一业务类型时，终端需要确定终端中存储的目标业务信息的存储时长。
终端确定目标业务信息在终端中的存储时长包括：终端确定目标业务信息的存储时刻与查询时刻的时间间隔，其中，存储时刻为终端接收第一请求的时刻。
当第一APP为音乐APP，目标业务信息为用户积分信息时，终端中的业务代理模块接收到第一请求之后，判断第一请求是否满足第一条件，若根据判断得知第一请求不满足第一条件时，业务代理模块根据第一请求对应的业务类型找到与该业务类型对应的策略模型集合，然后再根据第一APP的APP类型(音乐APP)在该策略模型集合中找到与第一APP对应的策略模型，其中，该策略模型为：
1、若用户积分信息的存储时长大于2秒且小于30秒时，从终端中查询目标业务信息；
2、若用户积分信息存储时长大于30秒时，则向业务系统请求处理该第一请求；
3、若用户积分信息存储时长小于2秒时，则向音乐APP返回请求失败信息。
若此时业务代理模块发现，终端本地缓存的用户积分信息的缓存时刻为12时12分30秒，而第一请求的查询时刻为12时12分40秒，用户积分信息的缓存时刻与查询时刻之间相差10秒，10秒大于2秒且小于30秒，此时，根据策略模型可知，此时终端中存有存储时长大于2秒且小于30秒的用户积分信息，则此时从终端中查询目标业务信息。
若此时业务代理模块发现，终端本地缓存的用户积分信息的缓存时刻为12时12分39秒，而第一请求的查询时刻为12时12分40秒，用户积分信息的缓存时刻与查询时刻之间相差1秒，1秒小于2秒，此时，根据策略模型可知，此时终端中存有存储时长小于2秒的用户积分信息，则此时向音乐APP返回请求失败信息。
若此时业务代理模块发现，终端本地缓存的用户积分信息的缓存时刻为为12时11分40秒，而第一请求的查询时刻为12时12分30秒，用户积分信息的缓存时刻与查询时刻之间相差50秒，50秒大于30秒，此时，根据策略模型可知，此时终端中存有存储时长大于30秒的用户积分信息，则此时向业务系统请求处理该第一请求。
其中，第一预设时长和第二预设时长的时间长度与第一请求对应的业务类型(目标业务信息的业务类型)以及第一请求对应的APP相对应，即同一个业务类型不同的APP中第一预设时长和第二预设时长的时间长度可能不一样，同一个APP中不同的业务类型第一预设时长和第二预设时长的时间长度也可能不一样。管理员会针对每种APP中的每种业务类型都会设置对应的第一预设时长和第二预设时长，第一预设时长与第二预设时长的值具体此处不做限定。
其中，在终端接收第一请求之前，终端还接收了第二请求，第二请求指示查询终端上的第二APP的所述目标业务信息，且终端根据该第二请求从业务系统中获取到了目标业务信息，且在终端中存储了该目标业务信息以及记录该目标业务信息的存储时刻。为节省存储资源，该目标业务信息将会在存储一定时间长度(例如40秒)后自动删除，并同时清除存储该目标业务信息的存储时刻，其中第二APP可以为与第一APP相同的APP，也可以为与第一APP不同的APP。
本实施例中，当终端接收到用户触发的第一请求之后，终端不会直接将该第一请求发送到云侧的业务系统中，而是首先由图1a中终端中的业务代理模块处理，业务代理模块中预置有查询策略，当业务代理模块接收到第一请求之后，会判断第一请求是否满足第一条件，若满足第一条件，则将该第一请求发送至业务系统中，若不满足第一条件，则会根据第一请求所对应的业务类型以及第一请求对应的APP调用相应的策略模型，然后根据该策略模型进行目标业务信息的查询。
207、终端从自身缓存中查询目标业务信息。
本实施例中，当终端中存有存储时长大于第一预设时长且小于第二预设时长的所述目标业务信息时，终端从自身缓存中提取该目标业务信息给第一APP，终端界面此时可以如图4b所示，终端响应第一请求，在界面上显示具体的用户积分信息“用户积分：3325分”。
其中，终端从自身缓存中提取该目标业务信息，终端不会再次记录该目标业务信息的存储时刻，只有终端从业务系统侧获取业务信息，终端才会存储该业务信息，并记录存储该业务信息的存储时刻。
当终端接收到第一请求之后，并不会直接将该查询请求转发至业务系统，而会根据业务代理模块中的查询策略确定是否将接收到的查询请求转发至业务系统，如本实施例，当根据查询策略得知，终端中存有存储时长大于第一预设时长且小于第二预设时长的该目标业务信息，则此时直接从终端自身缓存中提取目标业务信息。
208、终端向第一APP返回请求失败信息。
本实施例中，当终端根据步骤206得知，终端中存有存储时长小于第一预设时长的目标业务信息时(即此时终端中的其他APP或者第一APP在第一预设时长内曾经请求过与第一请求相同的业务信息)，则此时终端向第一APP返回请求失败信息，此时终端界面可以如图4c所示，在界面上显示具体的标识请求失败的信息“请求过于频繁，请稍后再试”。
209、终端向业务系统发送第一请求。
本实施例中，当终端根据步骤206得知，终端中目标业务信息的存储时长大于第二预设时长时(即该终端中的APP在第二预设时长之内都没有发送过请求目标业务信息的查询请求时)，业务代理模块将发送第一请求至业务系统。
当业务系统接收到该第一请求之后，业务系统会通过如图1a中的流量控制模块判断此时系统的处理能力，若第一请求超过了业务系统的处理能力时，由流量控制模块将第一请求丢弃，并返回系统繁忙的响应到终端中的业务代理模块中，业务代理模块将系统繁忙的接口返回到发起请求的第一APP中，此时终端界面可以如图4a所示，在界面上显示“系统繁忙，请稍后再试”；若业务系统的还有处理能力时，此时流量控制模块将第一请求发送至业务处理模块，业务处理模块根据接收到的第一请求向终端中的业务代理模块返回目标业务信息，其中，业务系统接收到第一请求之后的具体处理过程为现有技术，具体此处不做赘述。
210、终端接收业务系统发送的反馈信息。
211、终端存储接收到的目标业务信息以及记录所述目标业务信息的存储时刻。
本申请实施例中，步骤210至步骤211与步骤204至步骤205类似，具体此处不做赘述。
其中，本申请实施例中查询策略是可以更新的，并不是一成不变的，故具体的查询策略此处不做限定。
由于目标业务信息将会在存储一定时间长度后自动会删除，终端目标业务信息的存储时刻也同时删除，此时，业务代理模块接收到查询目标业务信息的第一请求时，便查询不到终端存有目标业务信息，此时，终端会将请求转发至业务系统。
本申请实施例中，终端接收第一请求，其中，该第一请求用于指示查询所述终端上的第一APP的目标业务信息；然后根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求。本申请实施例根据预置的查询策略查询目标业务信息，可以过滤部分查询请求，过滤掉的查询请求不需要发送至业务系统处，所以在查询终端APP中的业务信息时，可以有效减少用户不必要的带宽流量，降低业务系统的处理压力。
此外，本申请实施例还可以从端上避免APP恶意程序向业务系统发送大量的查询请求，大大减小了业务系统的处理压力，此外从用户的角度来说，多个APP之间同一类型的业务信息相同，业务系统为业务信息的查询实现了按用户终端为单位的控制查询能力，而不是以APP为单位查询，对用户的服务更为均衡，避免了一个用户终端上多APP短时间内向业务系统请求相同的业务信息，减少了用户不必要的带宽流量。且通过本地缓存快速返回终端内APP的查询结果，可以有效提升用户体验。
上面对本申请实施例中用于终端的信息查询方法进行了描述，下面对本申请实施例中的终端进行描述，请参阅图5，本申请实施例中终端的一个实施例包括：
第一接收单元501，用于接收第一请求，所述第一请求用于指示查询所述终端上的第一应用APP的目标业务信息；
确定单元502，用于根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求。
请参阅图6，本申请实施例中终端的另一个实施例包括：
第二接收单元601，用于根据第二请求接收目标业务信息，该第二请求指示查询终端上的第二APP的该目标业务信息；
存储单元602，用于存储该目标业务信息以及记录该目标业务信息的存储时刻。
第一接收单元603，用于接收第一请求，该第一请求用于指示查询该终端上的第一应用APP的目标业务信息；
确定单元604，用于根据该终端内预置的查询策略确定在该终端处理该第一请求或者向与该终端关联的业务系统请求处理该第一请求。
其中，确定单元604包括：
第一处理子单元6041，用于当该第一请求满足第一条件时，向该业务系统请求处理该第一请求，该第一条件包括：该终端内不存有该目标业务信息和/或该目标业务信息的业务类型为第一业务类型；
第二处理子单元6042，用于当该第一请求不满足该第一条件时，根据该终端内该目标业务信息的存储时长确定在该终端处理该第一请求或者向该业务系统请求处理该第一请求。
其中，该第二处理子单元6042包括：
第一确定模块60421，用于确定该存储时长是否大于第一预设时长且小于第二预设时长，该第一预设时长与该第二预设时长分别与该第一APP的该目标业务信息相对应；
查询模块60422，用于当该存储时长大于该第一预设时长且小于该第二预设时长时，从该终端中查询该目标业务信息。
其中，该第一确定模块60421具体用于：
确定该存储时刻与查询时刻之间的时间间隔是否大于第一预设时长且小于第二预设时长，该查询时刻为接收该第一请求的时刻。
或者，第二处理子单元6042包括：
第二确定模块60423，用于确定该存储时长是否大于第二预设时长，该第二预设时长与该第一APP的该目标业务信息相对应；
发送模块60424，用于当该存储时长大于该第二预设时长时，将该第一请求发送至该业务系统；
接收模块60425，用于接收该业务系统发送的该目标业务信息；
存储模块60426，用于存储该目标业务信息以及记录该目标业务信息的存储时刻。
其中，该第二确定模块60423具体用于：
确定该存储时刻与查询时刻之间的时间间隔是否大于该第二预设时长，该查询时刻为接收该第一请求的时刻。
或者，该第二处理子单元6042包括：
第三确定模块60427，用于确定该存储时长是否小于第一预设时长，该第一预设时长与该第一APP的该目标业务信息相对应；
返回模块60428，用于当小于该第一预设时长时，向该第一APP返回请求失败信息。
其中，该第三确定模块60427具体用于：
确定该存储时刻与查询时刻之间的时间间隔是否小于该第一预设时长，该查询时刻为接收该第一请求的时刻。
参阅图7所示，本申请实施例还提供一种终端700包括：一个或多个处理器702、接收器703、发送器704、存储器701以及总线705。其中，一个或多个处理器702、接收器703、发送器704、存储器701通过总线705相互连接。
其中，所述一个或多个处理器702，用于后台运行至少一个应用程序，并根据用户数据清理至少一个目标应用程序。其中，所述用户数据为基于用户使用应用的历史记录得到的统计数据；所述目标应用程序为根据所述用户数据确定的满足预设规则的应用程序。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
其中，所述存储器701中存储一个或多个程序。所述存储器701可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(Application，APP)等。存储数据区可存储根据终端700的使用所创建的数据等。此外，存储器701可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
其中，所述一个或多个处理器702可以是中央处理器(Central Processing Unit，CPU)， 通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
其中，所述接收器703和发送器704用于终端700和其他设备互相通信。
总线705可以是外设部件互连标准(Peripheral Component Interconnect，PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可 以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (25)

  1. 一种用于终端的信息查询方法，其特征在于，包括：
    接收第一请求，所述第一请求用于指示查询所述终端上的第一应用APP的目标业务信息；
    根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求。
  2. 根据权利要求1所述的方法，其特征在于，所述接收第一请求之前，所述方法还包括：
    根据第二请求接收所述目标业务信息，所述第二请求指示查询终端上的第二APP的所述目标业务信息；
    存储所述目标业务信息以及记录所述目标业务信息的存储时刻。
  3. 根据权利要求1或2所述的方法，其特征在于，所述根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求包括：
    当所述第一请求满足第一条件时，向所述业务系统请求处理所述第一请求，所述第一条件包括：所述终端内不存有所述目标业务信息和/或所述目标业务信息的业务类型为第一业务类型；
    当所述第一请求不满足所述第一条件时，根据所述终端内所述目标业务信息的存储时长确定在所述终端处理所述第一请求或者向所述业务系统请求处理所述第一请求。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述终端内所述目标业务信息的存储时长确定在所述终端处理所述第一请求或者向所述业务系统请求处理所述第一请求包括：
    确定所述存储时长是否大于第一预设时长且小于第二预设时长，所述第一预设时长与所述第二预设时长分别与所述第一APP的所述目标业务信息相对应；
    若大于所述第一预设时长且小于所述第二预设时长，则从所述终端中查询所述目标业务信息。
  5. 根据权利要求4所述的方法，其特征在于，所述确定所述存储时长是否大于第一预设时长且小于第二预设时长包括：
    确定所述存储时刻与查询时刻之间的时间间隔是否大于第一预设时长且小于第二预设时长，所述查询时刻为接收所述第一请求的时刻。
  6. 根据权利要求3所述的方法，其特征在于，所述根据所述终端内所述目标业务信息的存储时长确定在所述终端处理所述第一请求或者向所述业务系统请求处理所述第一请求包括：
    确定所述存储时长是否大于第二预设时长，所述第二预设时长与所述第一APP的所述目标业务信息相对应；
    若所述存储时长大于所述第二预设时长，则将所述第一请求发送至所述业务系统；
    接收所述业务系统发送的所述目标业务信息。
  7. 根据权利要求6所述的方法，其特征在于，所述确定所述存储时长是否大于第二预设时长包括：
    确定所述存储时刻与查询时刻之间的时间间隔是否大于所述第二预设时长，所述查询时刻为接收所述第一请求的时刻。
  8. 根据权利要求6所述的方法，其特征在于，所述接收所述业务系统发送的所述目标业务信息之后，所述方法还包括：
    存储所述目标业务信息以及记录所述目标业务信息的存储时刻。
  9. 根据权利要求3所述的方法，其特征在于，所述根据所述终端内所述目标业务信息的存储时长确定在所述终端处理所述第一请求或者向所述业务系统请求处理所述第一请求包括：
    确定所述存储时长是否小于第一预设时长，所述第一预设时长与所述第一APP的所述目标业务信息相对应；
    若小于所述第一预设时长，则向所述第一APP返回请求失败信息。
  10. 根据权利要求9所述的方法，其特征在于，所述确定所述存储时长是否小于第一预设时长包括：
    确定所述存储时刻与查询时刻之间的时间间隔是否小于所述第一预设时长，所述查询时刻为接收所述第一请求的时刻。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，所述查询策略还包括：所述查询策略在所述终端中适用的APP的范围。
  12. 一种终端，其特征在于，包括：
    第一接收单元，用于接收第一请求，所述第一请求用于指示查询所述终端上的第一应 用APP的目标业务信息；
    确定单元，用于根据所述终端内预置的查询策略确定在所述终端处理所述第一请求或者向与所述终端关联的业务系统请求处理所述第一请求。
  13. 根据权利要求12所述的终端，其特征在于，所述终端还包括：
    第二接收单元，用于根据第二请求接收所述目标业务信息，所述第二请求指示查询终端上的第二APP的所述目标业务信息；
    存储单元，用于存储所述目标业务信息以及记录所述目标业务信息的存储时刻。
  14. 根据权利要求12或13所述的终端，其特征在于，所述确定单元包括：
    第一处理子单元，用于当所述第一请求满足第一条件时，向所述业务系统请求处理所述第一请求，所述第一条件包括：所述终端内不存有所述目标业务信息和/或所述目标业务信息的业务类型为第一业务类型；
    第二处理子单元，用于当所述第一请求不满足所述第一条件时，根据所述终端内所述目标业务信息的存储时长确定在所述终端处理所述第一请求或者向所述业务系统请求处理所述第一请求。
  15. 根据权利要求14所述的终端，其特征在于，所述第二处理子单元包括：
    第一确定模块，用于确定所述存储时长是否大于第一预设时长且小于第二预设时长，所述第一预设时长与所述第二预设时长分别与所述第一APP的所述目标业务信息相对应；
    查询模块，用于当所述存储时长大于所述第一预设时长且小于所述第二预设时长时，从所述终端中查询所述目标业务信息。
  16. 根据权利要求15所述的终端，其特征在于，所述第一确定模块具体用于：
    确定所述存储时刻与查询时刻之间的时间间隔是否大于第一预设时长且小于第二预设时长，所述查询时刻为接收所述第一请求的时刻。
  17. 根据权利要求14所述的终端，其特征在于，所述第二处理子单元包括：
    第二确定模块，用于确定所述存储时长是否大于第二预设时长，所述第二预设时长与所述第一APP的所述目标业务信息相对应；
    发送模块，用于当所述存储时长大于所述第二预设时长时，将所述第一请求发送至所述业务系统；
    接收模块，用于接收所述业务系统发送的所述目标业务信息。
  18. 根据权利要求17所述的终端，其特征在于，所述第二确定模块具体用于：
    确定所述存储时刻与查询时刻之间的时间间隔是否大于所述第二预设时长，所述查询时刻为接收所述第一请求的时刻。
  19. 根据权利要求17所述的终端，其特征在于，所述第二处理子单元还包括：
    存储模块，用于存储所述目标业务信息以及记录所述目标业务信息的存储时刻。
  20. 根据权利要求14所述的终端，其特征在于，所述第二处理子单元包括：
    第三确定模块，用于确定所述存储时长是否小于第一预设时长，所述第一预设时长与所述第一APP的所述目标业务信息相对应；
    返回模块，用于当小于所述第一预设时长时，向所述第一APP返回请求失败信息。
  21. 根据权利要求20所述的终端，其特征在于，所述第三确定模块具体用于：
    确定所述存储时刻与查询时刻之间的时间间隔是否小于所述第一预设时长，所述查询时刻为接收所述第一请求的时刻。
  22. 根据权利要求12至21中任一项所述的终端，其特征在于，所述查询策略还包括：所述查询策略在所述终端中适用的APP的范围。
  23. 一种终端，其特征在于，所述终端包括：处理器、存储器、收发器，所述处理器、存储器以及收发器通过总线连接，所述存储器存储有计算机指令，所述处理器通过执行所述计算机指令，使得所述终端实现如权1至权11任意一项所述的信息查询方法。
  24. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求1至11中任一项所述的方法。
  25. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至11中任一项所述的方法。
PCT/CN2019/087703 2018-05-24 2019-05-21 一种用于终端的信息查询方法及终端 WO2019223667A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/053,796 US11650993B2 (en) 2018-05-24 2019-05-21 Information query method for terminal and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810511527.9A CN110598085B (zh) 2018-05-24 2018-05-24 一种用于终端的信息查询方法及终端
CN201810511527.9 2018-05-24

Publications (1)

Publication Number Publication Date
WO2019223667A1 true WO2019223667A1 (zh) 2019-11-28

Family

ID=68617154

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/087703 WO2019223667A1 (zh) 2018-05-24 2019-05-21 一种用于终端的信息查询方法及终端

Country Status (3)

Country Link
US (1) US11650993B2 (zh)
CN (1) CN110598085B (zh)
WO (1) WO2019223667A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117793675A (zh) * 2022-09-21 2024-03-29 华为技术有限公司 通信方法和通信装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102024010A (zh) * 2010-06-04 2011-04-20 西本新干线股份有限公司 数据处理系统及其处理方法
CN104021141A (zh) * 2014-05-12 2014-09-03 北京金山安全软件有限公司 数据处理和云服务的方法、装置及系统
CN104978278A (zh) * 2014-04-14 2015-10-14 阿里巴巴集团控股有限公司 数据处理方法和装置
US20150302185A1 (en) * 2014-04-16 2015-10-22 Baidu Online Network Technology (Beijing) Co., Ltd Method and apparatus for account intercommunication among apps
CN106130812A (zh) * 2016-06-02 2016-11-16 美的集团股份有限公司 一种提供设备状态的方法和装置
CN106658412A (zh) * 2016-12-14 2017-05-10 北京小米移动软件有限公司 定位方法及装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100010965A1 (en) * 2008-07-08 2010-01-14 International Business Machines Corporation Query Management Systems
US20100041391A1 (en) * 2008-08-12 2010-02-18 Anthony Wayne Spivey Embedded mobile analytics in a mobile device
ATE548870T1 (de) * 2009-01-08 2012-03-15 Mitsubishi Electric Corp Einstellung oder aufrechterhaltung einer bevorzugten bedingung für ein mobiles endgerät
JP5903783B2 (ja) * 2011-06-30 2016-04-13 ソニー株式会社 サーバ装置および情報処理装置
US10169571B1 (en) * 2012-07-18 2019-01-01 Sequitur Labs, Inc. System and method for secure, policy-based access control for mobile computing devices
US8646060B1 (en) * 2013-07-30 2014-02-04 Mourad Ben Ayed Method for adaptive authentication using a mobile device
CN106657367B (zh) * 2016-12-30 2019-09-17 北京三快在线科技有限公司 一种业务数据获取方法、装置及系统
EP3729848B1 (en) * 2017-12-18 2022-02-09 Convida Wireless, LLC Methods to enable context aware authorization for data or services in the iot/m2m service layer
CN110443059A (zh) * 2018-05-02 2019-11-12 中兴通讯股份有限公司 数据保护方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102024010A (zh) * 2010-06-04 2011-04-20 西本新干线股份有限公司 数据处理系统及其处理方法
CN104978278A (zh) * 2014-04-14 2015-10-14 阿里巴巴集团控股有限公司 数据处理方法和装置
US20150302185A1 (en) * 2014-04-16 2015-10-22 Baidu Online Network Technology (Beijing) Co., Ltd Method and apparatus for account intercommunication among apps
CN104021141A (zh) * 2014-05-12 2014-09-03 北京金山安全软件有限公司 数据处理和云服务的方法、装置及系统
CN106130812A (zh) * 2016-06-02 2016-11-16 美的集团股份有限公司 一种提供设备状态的方法和装置
CN106658412A (zh) * 2016-12-14 2017-05-10 北京小米移动软件有限公司 定位方法及装置

Also Published As

Publication number Publication date
CN110598085A (zh) 2019-12-20
CN110598085B (zh) 2023-11-10
US11650993B2 (en) 2023-05-16
US20210209113A1 (en) 2021-07-08

Similar Documents

Publication Publication Date Title
EP3668056B1 (en) Method and device for transmitting data processing request
CN110727617B (zh) 同时通过PCIe EP和网络接口访问双线SSD装置的方法和系统
US10795577B2 (en) De-duplication of client-side data cache for virtual disks
KR101378270B1 (ko) Ｓａｓ 확장기를 포함하는 저장 시스템에서 데이터 판독을 가능하게 하기 위한 방법, 시스템 및 ｓａｓ 확장기 디바이스
WO2022007470A1 (zh) 一种数据传输的方法、芯片和设备
TW201140430A (en) Allocating storage memory based on future use estimates
WO2017101576A1 (zh) 一种数据资源存储方法及装置
EP3974969A1 (en) System startup method and related device
US20220222016A1 (en) Method for accessing solid state disk and storage device
JP2022550401A (ja) データのアップロード方法、システム、装置及び電子機器
US20230384979A1 (en) Data processing method, apparatus, and system
WO2019223667A1 (zh) 一种用于终端的信息查询方法及终端
US11444998B2 (en) Bit rate reduction processing method for data file, and server
WO2016201998A1 (zh) 一种缓存分配、数据访问、数据发送方法、处理器及系统
US10002033B2 (en) Efficiently receiving messages across a large number of messaging entities
WO2023125380A1 (zh) 一种数据管理的方法及相应装置
WO2023174341A1 (zh) 数据读写方法、设备、存储节点及存储介质
CN110471627B (zh) 一种共享存储的方法、系统及装置
JP6368659B2 (ja) 基地局輻輳管理システム、及び基地局輻輳管理方法
US20180332134A1 (en) Access Record Feedback Method, Device, And System
US10171991B2 (en) Making subscriber data addressable as a device in a mobile data network
US20210099365A1 (en) Data management method and apparatus
CN111385327B (zh) 数据处理方法和系统
WO2017173844A1 (zh) 一种目录读取的方法、装置及系统
CN114610691B (zh) 存储对象的获取方法、存储对象的获取装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19807099

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19807099

Country of ref document: EP

Kind code of ref document: A1