CN108282405B - Application program interface cache management method, application server and storage medium - Google Patents

Application program interface cache management method, application server and storage medium Download PDF

Info

Publication number
CN108282405B
CN108282405B CN201711440777.XA CN201711440777A CN108282405B CN 108282405 B CN108282405 B CN 108282405B CN 201711440777 A CN201711440777 A CN 201711440777A CN 108282405 B CN108282405 B CN 108282405B
Authority
CN
China
Prior art keywords
interface
target
router
cache
time period
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201711440777.XA
Other languages
Chinese (zh)
Other versions
CN108282405A (en
Inventor
倪秉炬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
HAOHUO (KUNSHAN) NETWORK TECHNOLOGY Co.,Ltd.
Original Assignee
Haohuo Kunshan Network Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Haohuo Kunshan Network Technology Co ltd filed Critical Haohuo Kunshan Network Technology Co ltd
Priority to CN201711440777.XA priority Critical patent/CN108282405B/en
Publication of CN108282405A publication Critical patent/CN108282405A/en
Application granted granted Critical
Publication of CN108282405B publication Critical patent/CN108282405B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/742—Route cache; Operation thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1014—Server selection for load balancing based on the content of a request
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The invention discloses an application program interface cache management method, an application server and a computer readable storage medium, and belongs to the technical field of communication. The method comprises the following steps: receiving interface calling requests sent by each terminal in real time; counting all interface calling requests received within a preset time period to determine a target interface; acquiring all interface call request records of the target interface in the preset time period to determine a target router; and sending the cache data containing the return value of the target interface to the target router to be cached by the target router. Compared with the prior art, the method and the device have the advantages that the return values of part of frequently called interfaces are stored in the router, so that the terminal can directly obtain the return values of the interfaces through the router when calling the part of the interfaces, and communication links required to be passed by interface calling requests are reduced. The speed of interface calling is improved, the power consumption of the terminal is reduced, the application experience of a user is improved, and meanwhile the caching cost of the server side is reduced.

Description

Application program interface cache management method, application server and storage medium
Technical Field
The present invention relates to the field of terminal technologies, and in particular, to an application program interface cache management method, an application server, and a storage medium.
Background
When the application program is started, a plurality of interfaces are called to load resources. Specifically, the multiple interfaces respectively initiate HTTP requests to the application server and then receive resources returned by the server. With the development of the mobile internet, more and more terminals are provided, and the amount of data requested by each application program (client) on the terminal to the application server is larger and larger. In order to increase the running speed of the application, the cache service required by the application server is also increasing. In the process of requesting the server interface, the client needs more links for communication, and the efficiency is not high enough. The problems existing in the prior interface caching technology are as follows: 1. the cost of increasing the cache service space is high. 2. When the interface requests the process for more communication links, although buffers are used, the speed is still affected. 3. When the communication link is more, the power consumption of the terminal is also improved to a certain extent.
Therefore, it is desirable to provide an application program interface cache management method, an application server and a storage medium to solve the above technical problems.
Disclosure of Invention
The invention mainly aims to provide an application program interface cache management method, an application server and a storage medium, and aims to solve the problems that the existing interface cache technology is high in cost, low in response speed and affects terminal power consumption.
Firstly, in order to achieve the above object, the present invention provides an application program interface cache management method, which is applied to an application server side, and comprises the following steps:
receiving interface calling requests sent by each terminal in real time;
counting all interface calling requests received within a preset time period to determine a target interface;
acquiring all interface call request records of the target interface in the preset time period to determine a target router;
and sending the cache data containing the return value of the target interface to the target router to be cached by the target router.
Optionally, the step of counting all interface call requests received within a preset time period to determine a target interface specifically includes:
recording an interface called by each received interface calling request;
counting according to the called times of each interface in the preset time period and sequencing the interfaces from more to less according to the times;
and determining the interfaces with the preset number in the front sequence as target interfaces.
Optionally, the step of obtaining all interface call request records of the target interface in the preset time period to determine the target router specifically includes:
acquiring all routing information corresponding to all interface calling requests of the target interface in the preset time period;
determining a source routing address corresponding to each piece of routing information;
and taking the routers corresponding to all the source routing addresses as target routers.
Optionally, the step of sending the cache data including the target interface return value to the target router and caching by the target router specifically includes:
determining a return value corresponding to the target interface;
packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
and when receiving an interface calling request from the target router, returning the cache data to the target router.
Optionally, the method further comprises:
when detecting that the return value corresponding to the target interface is updated, updating the cache data;
pushing an update prompt to a terminal corresponding to the target router so that the terminal carries a preset cache update identifier when sending an interface calling request;
and when an interface calling request containing the preset cache updating identifier is received, returning the updated cache data to the target router.
Meanwhile, the invention also provides an application server, which comprises a memory, a processor and an application program interface cache management program stored on the memory and capable of running on the processor, wherein when the application program interface cache management program is executed by the processor, the following steps are realized:
receiving interface calling requests sent by each terminal in real time;
counting all interface calling requests received within a preset time period to determine a target interface;
acquiring all interface call request records of the target interface in the preset time period to determine a target router;
and sending the cache data containing the return value of the target interface to the target router to be cached by the target router.
Optionally, the step of executing the application program interface cache management program by the processor to count all interface call requests received within a preset time period to determine a target interface specifically includes:
recording an interface called by each received interface calling request;
counting according to the called times of each interface in the preset time period and sequencing the interfaces from more to less according to the times;
and determining the interfaces with the preset number in the front sequence as target interfaces.
Optionally, the step of executing the application program interface cache management program by the processor to obtain all interface call request records of the target interface in the preset time period to determine the target router specifically includes:
acquiring all routing information corresponding to all interface calling requests of the target interface in the preset time period;
determining a source routing address corresponding to each piece of routing information;
and taking the routers corresponding to all the source routing addresses as target routers.
Optionally, the step of the processor executing the application program interface cache management program to send the cache data including the target interface return value to the target router and cache the cache data by the target router specifically includes:
determining a return value corresponding to the target interface;
packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
and when receiving an interface calling request from the target router, returning the cache data to the target router.
In addition, to achieve the above object, the present invention further provides a computer readable storage medium, wherein an application program interface cache management program is stored on the computer readable storage medium, and when being executed by a processor, the application program interface cache management program implements the steps of the application program interface cache management method as described above.
Compared with the prior art, the application program interface cache management method, the application server and the computer readable storage medium provided by the invention receive the interface calling requests sent by each terminal in real time; counting all interface calling requests received within a preset time period to determine a target interface; acquiring all interface call request records of the target interface in the preset time period to determine a target router; and sending the cache data containing the return value of the target interface to the target router to be cached by the target router. Compared with the prior art, the method and the device have the advantages that the return values of part of frequently called interfaces are stored in the router, so that the terminal can directly obtain the return values of the interfaces through the router when calling the part of the interfaces, and communication links required to be passed by interface calling requests are reduced. The speed of interface calling is improved, the power consumption of the terminal is reduced, the application experience of a user is improved, and meanwhile the caching cost of the server side is reduced.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of an optional terminal for implementing various embodiments of the present invention;
fig. 2 is a diagram of a communication network system architecture according to an embodiment of the present invention;
FIG. 3 is a diagram of another architecture of a communication network system according to an embodiment of the present invention
FIG. 4 is a flowchart illustrating an implementation of a method for managing application program interface caches according to a first embodiment of the present invention;
FIG. 5 is a detailed flowchart of step S402 in FIG. 4;
FIG. 6 is a detailed flowchart of step S403 in FIG. 4;
FIG. 7 is a detailed flowchart of step S404 in FIG. 4;
FIG. 8 is a schematic diagram of a communication link when a call request is issued by a terminal interface according to the present invention;
FIG. 9 is a diagram illustrating an alternative hardware configuration of an application server for implementing various embodiments of the invention
FIG. 10 is a functional block diagram illustrating API cache management according to a second embodiment of the present invention.
Reference numerals:
Figure BDA0001526625910000051
Figure BDA0001526625910000061
the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.
It will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for moving purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a terminal for implementing various embodiments of the present invention, the terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the terminal configuration shown in fig. 1 is not intended to be limiting, and that the terminal may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes the various components of the terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex-Long Term Evolution), and TDD-LTE (Time Division duplex-Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The terminal 100 also includes at least one sensor 105, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of 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 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 100 or may be used to transmit data between the terminal 100 and the external device.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The processor 110 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system.
Although not shown in fig. 1, the terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the terminal of the present invention is based is described below.
Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present invention, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.
Specifically, the UE201 may be the terminal 100 described above, and is not described herein again.
The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Among them, the eNodeB2021 may be connected with other eNodeB2022 through backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.
The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and charging functions Entity) 2036, and the like. The MME2031 is a control node that handles signaling between the UE201 and the EPC203, and provides bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.
Although the LTE system is described as an example, it should be understood by those skilled in the art that the present invention is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Fig. 3 is a schematic structural diagram of another communication system implementing a message pushing method according to various embodiments of the present invention.
The communication system includes a plurality of terminals 100 (only one is shown), a plurality of application servers 200, and a cache server 300.
In the prior art, a terminal 100 is installed with various applications, each application corresponds to one application server 200, when an interface needs to be called by one application on any terminal, the terminal 100 sends an interface calling request to the application server 200 of the application, after receiving the interface calling request of the application, the application server 200 returns an interface return value to the application in response to the request, and the interface return value includes a return parameter, i.e., a return value, corresponding to the interface calling request. Since the data amount requested by the terminal to the application server is large, the application server 200 generally stores and manages the return value uniformly by the cache service provided by the cache server 300, and returns the required interface return value from the cache server 300 when receiving the interface call request, and therefore, the cache server 300 is mainly responsible for providing the cache service to the application server 200.
It is understood that, in the present invention, the server may be a single server, or may be a server cluster composed of a plurality of servers.
Based on the above hardware structure of the terminal 100 and the communication network system, various embodiments of the method of the present invention are proposed.
The first embodiment is as follows:
first, the present invention provides an application program interface cache management method, which is applied to the application server 200 shown in fig. 3. In this embodiment, according to different requirements, the execution order of the steps in the flowchart shown in fig. 4 may be changed, and some steps may be omitted, and the method for managing an application program interface cache includes the following steps:
step S401, receiving interface calling requests sent by each terminal in real time;
step S402, counting all interface calling requests received in a preset time period to determine a target interface;
specifically, in this embodiment, the terminal mainly refers to the terminal shown in fig. 1 to 3. When the application program on each terminal needs to call the interface, the terminal sends an interface calling request to the corresponding application server. The application server counts all the interface calling requests received in a preset time period according to the received interface calling requests, so that the calling condition of each interface can be determined, which interfaces are frequently called, which interfaces are called less frequently, and the interface which is called more frequently can be selected as a target interface. The number of the target interfaces may be multiple, and the specific number may be set on the application server by the corresponding application provider according to the storage space of the general router and the data size of the interface return value, so as to ensure that the router storage space can accommodate the return value of the target interface as a standard.
It is understood that the preset time period may be set by the application provider according to the traffic level of the data request, and if the total amount of data requested is huge and the number of interface call requests is huge in a certain period of time, the corresponding preset time period may be short, for example, one week or several days. On the contrary, if the total data amount of the request is small and the number of the interface call requests is not large in a certain period, the corresponding preset time period may be long, for example, one month, and the like, which is not particularly limited by the present invention.
Further, please refer to fig. 5 at the same time, which shows a detailed flowchart of step S402 in fig. 3, in this embodiment, step S402 specifically includes:
step S501, recording an interface called by each received interface calling request;
step S502, counting according to the called times of each interface in the preset time period and sequencing each interface from multiple times to multiple times;
step S503, determining the preset number of interfaces ranked in the top as the target interfaces.
Specifically, the application server records each interface call. Each time an interface call request is received, the number of times of call of the interface corresponding to the request is correspondingly increased, and it can be understood that the effective duration of the record may be a preset time period. Therefore, the called times of each interface on the application server in the preset time period can be determined one by one, the application server sorts the interfaces according to the called times, and sorts the interfaces in sequence from the largest to the smallest, and if the called times are more, the interfaces are sorted in the front. And then selecting the interfaces with the preset number in the front sequence as target interfaces. As described above, the preset number may be set on the application server by the corresponding application provider according to the storage space of the general router and the data size of the interface return value, so as to ensure that the storage space of the router can accommodate the return value of the target interface as a standard, and a minimum threshold value may be set as a default value.
Step S403, acquiring all interface call request records of the target interface in the preset time period to determine a target router;
specifically, after the target interface is determined, the return value of the target interface needs to be cached in the corresponding target router. Therefore, a target router needs to be determined. It can be understood that the target router is necessarily a certain router on a communication link through which the interface request corresponding to the target interface passes, and therefore, the application server needs to obtain corresponding routing information according to all interface call request records corresponding to the target interface within a preset time period, and then can determine the target router according to the routing information. It is understood that the selection of the target router is based on the side close to the terminal, that is, the first router through which each interface invocation request passes after being sent from the terminal is selected as the target router.
Further, referring to fig. 6, a detailed flowchart of step S403 in the present invention is shown, in this embodiment, step S403 specifically includes the following steps:
step S601, acquiring all routing information corresponding to all interface calling requests of the target interface in the preset time period;
step S602, determining a source routing address corresponding to each piece of routing information;
step S603, the routers corresponding to all the source routing addresses are used as the target routers.
Specifically, when receiving each interface call request, the application server may also synchronously parse the interface call request to obtain corresponding routing information, and synchronously record the obtained routing information and request time to a request routing table corresponding to the interface, where the routing information records IP addresses of all routing nodes through which the interface request passes after reaching the application server from the terminal. After the target interface is determined, because the statistical time is the preset time period, only all the routing information corresponding to all the interface call requests of the target interface in the preset time period, that is, all the routing information in the preset time period from the request routing table of the target interface, can be obtained. In this embodiment, the first router through which each interface call request is sent from the terminal is selected as the target router, and after determining the source routing address from the routing information corresponding to the source routing address in the routing information, the source router may be determined as the target router. All source routers of the target interface within a preset time period are target routers. It is understood that there may be multiple terminals under one target router, that is, the first router on the communication link of the interface call requests sent by multiple terminals is the same. For example, for an end user in a local area network, any interface invocation requests issued by all terminals may pass through the same router local area network, and then the source routers of these interface invocation requests are the same router.
It should be noted that the request routing table is a record table stored in the application server for recording routing information of different interface call requests, and the specific record form is not limited in the present invention.
Referring also to fig. 8, a schematic diagram of a communication link for a terminal interface invocation request to reach an application server via a target router is shown, as shown, it is assumed that an application on the terminal calls interface 1, and at this time an interface call request needs to be sent to the application server, the interface calling request is sent from the terminal, and then sequentially passes through the router A, the router B and the router C, and finally reaches the application server, after receiving the interface calling request, the application server analyzes the interface calling request to obtain routing information and request time, wherein the routing information comprises IP addresses of the router A, the router B, the router C and the terminal A, these pieces of information are recorded in the request routing table of the interface 1, and assuming that the interface 1 called by the interface call request is just confirmed as the target interface, the router a closest to the terminal is the target router.
Step S404, sending the cache data containing the target interface return value to the target router to be cached by the target router.
Specifically, after the target interface is determined, the application server transmits a return value of the target interface to the target router for caching, and when the return value is transmitted, data needs to be encapsulated and corresponding identification information needs to be added, so that the target router can match the identification information and the request information when receiving the interface calling request to determine whether the return value is the return value needed by the interface calling request, and if the return value is the return value, the interface calling request does not need to be transmitted forward, and the return value is directly fed back to the terminal. It is understood that, here, the identification information may include information having an identification function, such as an application name and an interface name, so as to distinguish different cache data. In the prior art, because the router does not store the return value, each time the router receives an interface call request, the router needs to transmit the interface call request to the next node until the application server receives the interface call request, and then the application server feeds back the return value corresponding to the request in the original path, and after receiving the fed-back return value, the router does not store the return value but directly matches with the request information, and directly returns the return value to the terminal if the return value is successful, and discards the return value if the return value is unsuccessful.
Further, referring to fig. 7, a detailed flowchart of step S404 in the present invention is shown, in this embodiment, step S404 specifically includes the following steps:
step S701, determining a return value corresponding to the target interface;
step S702, packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
step S703, when receiving the interface call request from the target router, returns the cache data to the target router.
Specifically, each return value corresponding to the target interface has a corresponding content identifier, and when the application server packages the return value corresponding to the target interface and the corresponding content identifier, the packaged content includes an application name, an interface name, a parameter value (i.e., the return value), and a cache validity period, where the name, the interface name, and the cache validity period are the content identifier corresponding to the return value. The cache validity period, i.e. the residence time of the cache data in the router, may be set by the application provider according to the actual situation, but the cache validity period is longer than the validity period of the return value in the cache server. After the cache data is obtained, the application server needs to transmit the cache data to the target router for storage, and since the application server and the target router do not actively communicate with each other, the cache data can be sent to the target router as feedback data in response to the interface when an interface call request from the router is received next time.
It can be understood that, after the return value of a certain target interface is already sent to the target server as cache data, the corresponding cache on the cache server may be deleted after being retained for a certain time. And if the return value corresponding to the target interface is updated, the reapplication server informs the cache server to cache again.
Further, in this embodiment, the method further includes the following steps:
when detecting that the return value corresponding to the target interface is updated, updating the cache data;
pushing an update prompt to a terminal corresponding to the target router so that the terminal carries a preset cache update identifier when sending an interface calling request;
and when an interface calling request containing the preset cache updating identifier is received, returning the updated cache data to the target router.
Specifically, since the application server cannot actively push the updated return value to the router, when the application server finds that the return value of a certain target interface is updated, the application server needs to push the update message to the terminal under the target router in a push manner, so that when the terminal calls the target interface next time, a cache update identifier is added in the interface call request to indicate that the feedback data requested here can only be obtained from the application server, and thus, when communicating with the target router, if the cache update identifier is found, the cache data in the target router cannot be obtained, but the interface request is directly transmitted to the application server, the application server obtains the updated interface return value from the cache server and returns the value through the original route again to the terminal, so that the updated cache data is also transmitted to the target router at the same time, to ensure that the cached data in the target router is up-to-date.
The application program interface cache management method provided by the embodiment receives interface calling requests sent by each terminal in real time; counting all interface calling requests received within a preset time period to determine a target interface; acquiring all interface call request records of the target interface in the preset time period to determine a target router; and sending the cache data containing the return value of the target interface to the target router to be cached by the target router. Compared with the prior art, the method and the device have the advantages that the return values of part of frequently called interfaces are stored in the router, so that the terminal can directly obtain the return values of the interfaces through the router when calling the part of the interfaces, and communication links required to be passed by interface calling requests are reduced. The speed of interface calling is improved, the power consumption of the terminal is reduced, the application experience of a user is improved, and meanwhile the caching cost of the server side is reduced.
Example two:
in addition, the present invention provides an application program interface cache management program 10.
Fig. 9 is a schematic diagram of a hardware structure of an optional application server according to various embodiments of the present invention. Application server 200 includes a process 210, a memory 211, and a communication bus 212. Wherein the communication bus 212 is used for enabling connection communication between the processor 210 and the memory 211. Fig. 10 is a schematic functional module diagram of an application program interface cache management program 10 according to a second embodiment of the present invention. In this embodiment, the application program interface cache management program 10 may be divided into one or more modules, and the one or more modules are stored in the memory of the application server 200 and executed by one or more processors to implement the present invention. For example, in fig. 10, the application program interface cache management program 10 may be divided into a request receiving module 11, a call statistics module 12, a record obtaining module 13, and a cache pushing module 14. The module referred to in the present invention is a series of readable computer program instruction segments capable of performing specific functions, and is more suitable than a computer program for describing the execution process of software in the application server 200. The specific functions of the above-described functional modules 11 to 14 will be described in detail below. Wherein:
a request receiving module 11, configured to receive, in real time, interface call requests sent by each terminal;
the calling statistic module 12 is configured to count all interface calling requests received within a preset time period to determine a target interface;
specifically, in this embodiment, the terminal mainly refers to the terminal shown in fig. 1 to 3. When the application program on each terminal needs to call the interface, the terminal sends an interface calling request to the corresponding application server. The calling statistical module 12 may determine the calling condition of each interface by counting all the interface calling requests received within a preset time period according to the received interface calling requests, which interfaces are frequently called and which interfaces are called less frequently, and may select the interface which is called more frequently as a target interface. The number of the target interfaces may be multiple, and the specific number may be set on the application server by the corresponding application provider according to the storage space of the general router and the data size of the interface return value, so as to ensure that the router storage space can accommodate the return value of the target interface as a standard.
It is understood that the preset time period may be set by the application provider according to the traffic level of the data request, and if the total amount of data requested is huge and the number of interface call requests is huge in a certain period of time, the corresponding preset time period may be short, for example, one week or several days. On the contrary, if the total data amount of the request is small and the number of the interface call requests is not large in a certain period, the corresponding preset time period may be long, for example, one month, and the like, which is not particularly limited by the present invention.
Further, in this embodiment, the calling the statistics module 12 specifically includes:
the recording unit is used for recording the interfaces called by each received interface calling request;
the sorting unit is used for counting according to the called times of each interface in the preset time period and sorting each interface from at least according to the times;
and the determining unit is used for determining the interfaces with the preset number in the front sequence as target interfaces.
Specifically, the recording unit records each interface call. Each time an interface call request is received, the number of times of call of the interface corresponding to the request is correspondingly increased, and it can be understood that the effective duration of the record may be a preset time period. Therefore, the called times of each interface on the application server in the preset time period can be determined one by one, the sequencing unit sequences the interfaces according to the called times, and sequences the interfaces from the top to the bottom in sequence, and if the called times are more, the sequencing is performed in the front. Then, the determining unit selects a preset number of interfaces ranked in the front as target interfaces. As described above, the preset number may be set on the application server by the corresponding application provider according to the storage space of the general router and the data size of the interface return value, so as to ensure that the storage space of the router can accommodate the return value of the target interface as a standard, and a minimum threshold value may be set as a default value.
A record obtaining module 13, configured to obtain all interface call request records of the target interface in the preset time period to determine a target router;
specifically, after the target interface is determined, the return value of the target interface needs to be cached in the corresponding target router. Therefore, a target router needs to be determined. It can be understood that the target router is necessarily a certain router on a communication link through which the interface request corresponding to the target interface passes, and therefore, the record obtaining module 13 needs to obtain corresponding routing information according to all the interface call request records corresponding to the target interface within a preset time period, and then, may determine the target router according to the routing information. It is understood that the selection of the target router is based on the side close to the terminal, that is, the first router through which each interface invocation request passes after being sent from the terminal is selected as the target router.
Further, in this embodiment, the record obtaining module 13 specifically includes:
the route obtaining unit is used for obtaining all route information corresponding to all interface calling requests of the target interface in the preset time period;
the address determining unit is used for determining a source routing address corresponding to each piece of routing information;
and the target determining unit is used for taking the routers corresponding to all the source routing addresses as target routers.
Specifically, when receiving each interface call request, the application server may also synchronously parse the interface call request to obtain corresponding routing information, and synchronously record the obtained routing information and request time to a request routing table corresponding to the interface, where the routing information records IP addresses of all routing nodes through which the interface request passes after reaching the application server from the terminal. After the target interface is determined, because the statistical time is a preset time period, the route obtaining unit may only obtain all the route information corresponding to all the interface call requests of the target interface in the preset time period, that is, all the route information in the preset time period from the request route table of the target interface. In this embodiment, the target determining unit selects a first router through which each interface call request is sent from the terminal as the target router, and corresponds to the source routing address in the routing information, and after determining the source routing address from the routing information, the address determining unit may determine the source router as the target router. All source routers of the target interface within a preset time period are target routers. It is understood that there may be multiple terminals under one target router, that is, the first router on the communication link of the interface call requests sent by multiple terminals is the same. For example, for an end user in a local area network, any interface invocation requests issued by all terminals may pass through the same router local area network, and then the source routers of these interface invocation requests are the same router.
It should be noted that the request routing table is a record table stored in the application server for recording routing information of different interface call requests, and the specific record form is not limited in the present invention.
Referring also to fig. 8, a schematic diagram of a communication link for a terminal interface invocation request to reach an application server via a target router is shown, as shown, it is assumed that an application on the terminal calls interface 1, and at this time an interface call request needs to be sent to the application server, the interface calling request is sent from the terminal, and then sequentially passes through the router A, the router B and the router C, and finally reaches the application server, after receiving the interface calling request, the application server analyzes the interface calling request to obtain routing information and request time, wherein the routing information comprises IP addresses of the router A, the router B, the router C and the terminal A, these pieces of information are recorded in the request routing table of the interface 1, and assuming that the interface 1 called by the interface call request is just confirmed as the target interface, the router a closest to the terminal is the target router.
And the cache pushing module 14 is configured to send the cache data including the target interface return value to the target router, and cache the cache data by the target router.
Specifically, after the target interface is determined, the cache push module 14 transmits the return value of the target interface to the target router for caching, and when the target interface is determined, the data needs to be encapsulated and corresponding identification information needs to be added, so that the target router can determine whether the return value is the return value needed by the interface calling request according to matching between the identification information and the request information when receiving the interface calling request, and if so, the target router does not need to forward transmit the interface calling request and directly feeds back the return value to the terminal. It is understood that, here, the identification information may include information having an identification function, such as an application name and an interface name, so as to distinguish different cache data. In the prior art, because the router does not store the return value, each time the router receives an interface call request, the router needs to transmit the interface call request to the next node until the application server receives the interface call request, and then the application server feeds back the return value corresponding to the request in the original path, and after receiving the fed-back return value, the router does not store the return value but directly matches with the request information, and directly returns the return value to the terminal if the return value is successful, and discards the return value if the return value is unsuccessful.
Further, in this embodiment, the cache push module 14 specifically includes:
a return value determining unit, configured to determine a return value corresponding to the target interface;
the data packaging unit is used for packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
and the data sending unit returns the cache data to the target router when receiving the interface calling request from the target router.
Specifically, each return value corresponding to the target interface has a corresponding content identifier, and when the data encapsulation unit encapsulates the return value corresponding to the target interface and the corresponding content identifier, the encapsulated content includes an application name, an interface name, a parameter value (i.e., the return value), and a cache validity period, where the name, the interface name, and the cache validity period are the content identifiers corresponding to the return values. The cache validity period, i.e. the residence time of the cache data in the router, may be set by the application provider according to the actual situation, but the cache validity period is longer than the validity period of the return value in the cache server. After the cache data is obtained, the data sending unit needs to transmit the cache data to the target router for storage, and since the application server and the target router do not actively communicate with each other, the cache data can be sent to the target router as feedback data in response to the interface when an interface call request from the router is received next time.
It can be understood that, after the return value of a certain target interface is already sent to the target server as cache data, the corresponding cache on the cache server may be deleted after being retained for a certain time. And if the return value corresponding to the target interface is updated, the reapplication server informs the cache server to cache again.
Further, in this embodiment, the application program interface cache management program 10 further includes:
the data updating module is used for updating the cache data when detecting that the return value corresponding to the target interface is updated;
the update pushing module is used for pushing an update prompt to a terminal corresponding to the target router so that the terminal carries a preset cache update identifier when sending an interface calling request;
the cache push module 14 is further configured to, when receiving an interface call request including the preset cache update identifier, return the updated cache data to the target router.
Specifically, since the application server cannot actively push the updated return value to the router, when the data update module finds that the return value of a certain target interface is updated, the update push module needs to push the update message to the terminal under the target router in a push manner, so that when the terminal next calls the target interface, a cache update identifier is added to the interface call request to indicate that the feedback data requested here can only be obtained from the application server, so that when communicating with the target router, if the cache update identifier is found to exist, the cache data in the target router cannot be obtained, but the interface request is directly transmitted to the application server, the cache push module 14 obtains the updated interface return value from the cache server and returns the value through the original route again to be fed back to the terminal, therefore, the updated cache data is also transmitted to the target router at the same time, so as to ensure that the cache data in the target router is all up-to-date.
Receiving interface calling requests sent by each terminal in real time by executing the application program interface cache management program of the embodiment; counting all interface calling requests received within a preset time period to determine a target interface; acquiring all interface call request records of the target interface in the preset time period to determine a target router; and sending the cache data containing the return value of the target interface to the target router to be cached by the target router. Compared with the prior art, the method and the device have the advantages that the return values of part of frequently called interfaces are stored in the router, so that the terminal can directly obtain the return values of the interfaces through the router when calling the part of the interfaces, and communication links required to be passed by interface calling requests are reduced. The speed of interface calling is improved, the power consumption of the terminal is reduced, the application experience of a user is improved, and meanwhile the caching cost of the server side is reduced.
The present invention further provides a computer-readable storage medium, on which the above-mentioned application program interface cache management program is stored, and when being executed by a processor, the application program interface cache management program implements the application program interface cache management method as described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (4)

1. An application program interface cache management method is applied to an application server side, and is characterized in that the application program interface cache management method comprises the following steps:
receiving interface calling requests sent by each terminal in real time;
counting all interface calling requests received within a preset time period to determine a target interface;
acquiring all interface call request records of the target interface in the preset time period to determine a target router;
sending the cache data containing the target interface return value to the target router, and caching by the target router;
the step of counting all interface call requests received within a preset time period to determine a target interface specifically includes:
recording an interface called by each received interface calling request;
counting according to the called times of each interface in the preset time period and sequencing the interfaces from more to less according to the times;
determining a preset number of interfaces sequenced at the front as target interfaces;
the step of obtaining all interface call request records of the target interface in the preset time period to determine the target router specifically includes:
acquiring all routing information corresponding to all interface calling requests of the target interface in the preset time period;
determining a source routing address corresponding to each piece of routing information;
taking routers corresponding to all source routing addresses as target routers;
the step of sending the cache data containing the target interface return value to the target router for caching by the target router specifically includes:
determining a return value corresponding to the target interface;
packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
and when receiving an interface calling request from the target router, returning the cache data to the target router.
2. The application program interface cache management method of claim 1, wherein the method further comprises:
when detecting that the return value corresponding to the target interface is updated, updating the cache data;
pushing an update prompt to a terminal corresponding to the target router so that the terminal carries a preset cache update identifier when sending an interface calling request;
and when an interface calling request containing the preset cache updating identifier is received, returning the updated cache data to the target router.
3. An application server comprising a memory, a processor, and an application program interface cache manager stored on the memory and operable on the processor, the application program interface cache manager when executed by the processor performing the steps of:
receiving interface calling requests sent by each terminal in real time;
counting all interface calling requests received within a preset time period to determine a target interface;
acquiring all interface call request records of the target interface in the preset time period to determine a target router;
sending the cache data containing the target interface return value to the target router, and caching by the target router;
the step of executing the application program interface cache management program by the processor to count all interface call requests received within a preset time period to determine a target interface specifically includes:
recording an interface called by each received interface calling request;
counting according to the called times of each interface in the preset time period and sequencing the interfaces from more to less according to the times;
determining a preset number of interfaces sequenced at the front as target interfaces;
the step of executing the application program interface cache management program by the processor to obtain all interface call request records of the target interface in the preset time period to determine the target router specifically includes:
acquiring all routing information corresponding to all interface calling requests of the target interface in the preset time period;
determining a source routing address corresponding to each piece of routing information;
taking routers corresponding to all source routing addresses as target routers;
the step of the processor executing the application program interface cache management program to send the cache data containing the target interface return value to the target router for caching by the target router specifically includes:
determining a return value corresponding to the target interface;
packaging the return value and a corresponding content identifier to obtain cache data, wherein the content identifier comprises a cache validity period;
and when receiving an interface calling request from the target router, returning the cache data to the target router.
4. A computer-readable storage medium, having an api cache management program stored thereon, which when executed by a processor implements the steps of the api cache management method according to any one of claims 1 to 2.
CN201711440777.XA 2017-12-27 2017-12-27 Application program interface cache management method, application server and storage medium Active CN108282405B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711440777.XA CN108282405B (en) 2017-12-27 2017-12-27 Application program interface cache management method, application server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711440777.XA CN108282405B (en) 2017-12-27 2017-12-27 Application program interface cache management method, application server and storage medium

Publications (2)

Publication Number Publication Date
CN108282405A CN108282405A (en) 2018-07-13
CN108282405B true CN108282405B (en) 2020-09-18

Family

ID=62802300

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711440777.XA Active CN108282405B (en) 2017-12-27 2017-12-27 Application program interface cache management method, application server and storage medium

Country Status (1)

Country Link
CN (1) CN108282405B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109189509B (en) * 2018-09-03 2024-04-26 中国平安人寿保险股份有限公司 Interface calling method, interface calling response method and server
CN111367683A (en) * 2018-12-25 2020-07-03 华为技术有限公司 Result obtaining method, device and equipment
CN110865876A (en) * 2019-09-23 2020-03-06 珠海格力电器股份有限公司 Scheduling method and device for service dependent resources
CN113590699B (en) * 2021-07-14 2023-12-01 车智互联（北京）科技有限公司 Interface request processing method, system and computing device
CN115145712A (en) * 2022-09-06 2022-10-04 云账户技术(天津)有限公司 Interface calling method, device, equipment and medium for external service platform

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7263712B2 (en) * 2001-05-29 2007-08-28 Intel Corporation Enabling a PC-DTV receiver to share the resource cache with multiple clients
US8930632B2 (en) * 2012-11-14 2015-01-06 Ebay Inc. Methods and systems for application controlled pre-fetch
US9229743B2 (en) * 2011-09-23 2016-01-05 International Business Machines Corporation Prevention of classloader memory leaks in multitier enterprise applications
CN105701164A (en) * 2015-12-30 2016-06-22 广东欧珀移动通信有限公司 Statistical method and device for web hits
CN106648873A (en) * 2016-12-29 2017-05-10 努比亚技术有限公司 System service data acquiring device and method
CN107317855A (en) * 2017-06-21 2017-11-03 努比亚技术有限公司 A kind of data cache method, data request method and server
CN107341052A (en) * 2017-06-07 2017-11-10 努比亚技术有限公司 A kind of message treatment method and device
CN107346307A (en) * 2016-05-04 2017-11-14 北京京东尚科信息技术有限公司 Distributed cache system and method
CN108304302A (en) * 2017-12-22 2018-07-20 努比亚技术有限公司 A kind of interface merging method, equipment and computer readable storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10200493B2 (en) * 2011-10-17 2019-02-05 Microsoft Technology Licensing, Llc High-density multi-tenant distributed cache as a service

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7263712B2 (en) * 2001-05-29 2007-08-28 Intel Corporation Enabling a PC-DTV receiver to share the resource cache with multiple clients
US9229743B2 (en) * 2011-09-23 2016-01-05 International Business Machines Corporation Prevention of classloader memory leaks in multitier enterprise applications
US8930632B2 (en) * 2012-11-14 2015-01-06 Ebay Inc. Methods and systems for application controlled pre-fetch
CN105701164A (en) * 2015-12-30 2016-06-22 广东欧珀移动通信有限公司 Statistical method and device for web hits
CN107346307A (en) * 2016-05-04 2017-11-14 北京京东尚科信息技术有限公司 Distributed cache system and method
CN106648873A (en) * 2016-12-29 2017-05-10 努比亚技术有限公司 System service data acquiring device and method
CN107341052A (en) * 2017-06-07 2017-11-10 努比亚技术有限公司 A kind of message treatment method and device
CN107317855A (en) * 2017-06-21 2017-11-03 努比亚技术有限公司 A kind of data cache method, data request method and server
CN108304302A (en) * 2017-12-22 2018-07-20 努比亚技术有限公司 A kind of interface merging method, equipment and computer readable storage medium

Also Published As

Publication number Publication date
CN108282405A (en) 2018-07-13

Similar Documents

Publication Publication Date Title
CN108282405B (en) Application program interface cache management method, application server and storage medium
CN107967322B (en) File classification display method, mobile terminal and computer readable storage medium
CN108768775B (en) Information processing method, electronic device, and computer storage medium
CN107038245B (en) Page switching method, mobile terminal and storage medium
CN112799577B (en) Method, terminal and storage medium for projecting small window
CN108600516B (en) Data acquisition method, mobile terminal and computer readable storage medium
CN107862217B (en) Position information acquisition method, mobile terminal and computer storage medium
CN107220132B (en) Method, equipment and storage medium for monitoring file creation information
CN107317855B (en) Data caching method, data requesting method and server
CN109151216B (en) Application starting method, mobile terminal, server and computer readable storage medium
CN108011937B (en) Message pushing method, server, intelligent terminal and computer readable storage medium
CN112597115A (en) Container mirror image compression method and device, terminal equipment and medium
CN108040116B (en) Message pushing method, router and computer readable storage medium
CN109522276B (en) Application icon management method, terminal and computer-readable storage medium
CN109445945B (en) Memory allocation method of application program, mobile terminal, server and storage medium
CN108306856B (en) Interface merging method, client, server and computer readable storage medium
CN108063863B (en) Information browsing method, terminal, server and computer readable storage medium
CN107734012B (en) Message pushing method, system and computer readable storage medium
CN112437472B (en) Network switching method, equipment and computer readable storage medium
CN111970738B (en) Network switching control method, device and computer readable storage medium
CN109462829B (en) Call transfer method, device and computer readable storage medium
CN109062688B (en) Memory allocation method, server and mobile terminal
CN108183833B (en) Response processing method and device and computer readable storage medium
CN108040330B (en) WiFi directional transmission method, mobile terminal and readable storage medium
CN107404568B (en) Control switch management method and mobile terminal

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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20200825

Address after: Room 1008, comprehensive south building, room 9, No. 1699, Zuchongzhi South Road, Yushan Town, Kunshan City, Suzhou City, Jiangsu Province

Applicant after: HAOHUO (KUNSHAN) NETWORK TECHNOLOGY Co.,Ltd.

Address before: 518057 Dazu Innovation Building A Area 6-8 Floors, 10-11 Floors, B Area 6 Floors, C Area 6-10 Floors, 9018 North Ring Avenue, Nanshan District, Shenzhen City, Guangdong Province

Applicant before: NUBIA TECHNOLOGY Co.,Ltd.

GR01 Patent grant
GR01 Patent grant