CN112000518A - Application program fault risk processing method, device and system, terminal and equipment - Google Patents
Application program fault risk processing method, device and system, terminal and equipment Download PDFInfo
- Publication number
- CN112000518A CN112000518A CN202010813308.3A CN202010813308A CN112000518A CN 112000518 A CN112000518 A CN 112000518A CN 202010813308 A CN202010813308 A CN 202010813308A CN 112000518 A CN112000518 A CN 112000518A
- Authority
- CN
- China
- Prior art keywords
- domain name
- access
- application program
- name list
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses an application program fault risk processing method, which comprises the following steps: setting more than or equal to two WEB servers and different domain name lists which are positioned in different machine rooms corresponding to the application program; when an application program is started, selecting a candidate domain name list from a domain name list according to a preset server domain name selection strategy; detecting and selecting the network address state of each candidate domain name in the candidate domain name list according to a preset domain name state detection strategy, and generating an access domain name list in a normal domain name state; and selecting a normal domain name from the access domain name list to access the target interface website based on a domain name access strategy preset by an application program. The embodiment of the invention also discloses a device, a system, a terminal and equipment for processing the failure risk of the application program; the method can judge whether the domain name of the API interface is available, and select the normally available domain name in real time according to the resolution state of the domain name, thereby effectively solving the problem of software interface failure.
Description
Technical Field
The present invention relates to the field of interface failure handling. More specifically, the invention relates to a method, a device, a system, a terminal and equipment for processing application program interface failure risk.
Background
With the rise of the mobile internet, more convenient communication service is provided for the life and work of people. An Application program (APP for short) runs on the terminal device, can realize information interaction between the user terminal and the server, and has a visual user interface. Each application runs in an independent process and has an independent address space, and the boundaries of different applications are called process boundaries. The small program, such as the WeChat small program, is one of the small programs, is an application which can be used without downloading and installing, realizes the dream that the application is 'reachable by the touch' and can be opened by scanning or searching by a user. The concept of 'running after running' is also embodied, and a user does not need to be concerned about whether too many applications are installed.
The mobile Application program APP, the WeChat applet and the like call server data in an API mode, the API refers in particular to a data exchange Interface between a mobile network Application program (Application Programming Interface, abbreviated as API) and a WEB server, and the WEB Application program in the WEB server is responsible for data storage, query and logic processing. The mobile network application program requests the WEB server through the domain name, network faults may occur in the access process, the WEB server may have risks such as hardware faults and network faults, and the mobile network application program faults may be caused due to WEB application program faults and the like.
As described above, an Application program (e.g., a common APP, a wechat applet, or the like) on a terminal calls information data in a WEB server (usually, a WEB server) corresponding to the program in the form of an Application Programming Interface (API). However, due to the risk of server hardware failure, network failure, etc., the client often cannot access the application program interface and the corresponding website server through the domain name.
Therefore, how to provide a solution for making a user inaccessible to an application program due to a hardware failure of a server, a network failure, slow network congestion, and the like is a technical problem to be solved in the field.
Disclosure of Invention
An object of the present invention is to solve at least the above problems and to provide at least the advantages described later.
The embodiment of the invention at least discloses a method and a device for processing the failure risk of an application program interface; the problem of domain name access failure of the API can be solved, wherein the domain name failure at least comprises two conditions of slow access speed and no access. Setting more than or equal to two WEB servers which are positioned in different machine rooms of different regions or cities corresponding to an application program, and respectively setting different domain name lists corresponding to the application program in the WEB servers; therefore, the invention can effectively solve the problem of software interface failure.
The invention is realized by the following technical scheme:
first aspect of the invention
A first aspect provides an application failure risk processing method, which in some embodiments includes:
setting more than or equal to two WEB servers which correspond to the application program and are positioned in different machine rooms, and respectively setting different domain name lists corresponding to the application program in the WEB servers;
when the application program is started, selecting a candidate domain name list from the domain name list according to a preset server domain name selection strategy;
detecting the network address state of each candidate domain name in the selected candidate domain name list according to a preset domain name state detection strategy, and generating an access domain name list in a normal domain name state;
and selecting a normal domain name from the access domain name list to access a target interface website based on a domain name access strategy preset by the application program.
In some embodiments, the network address state of each candidate domain name in the selected candidate domain name list is detected according to a preset domain name state detection policy, and an access domain name list in a normal domain name state is generated, where the access domain name list is:
receiving attribute data for calling the application program from the WEB server;
selecting an access domain name from the selected candidate domain name list according to the attribute data and a preset access domain name selection strategy;
testing the network address resolution state of the access domain name, and if the access domain name is in an abnormal state, testing the network address resolution states of other candidate domain names in the candidate domain name list;
and generating an access domain name list in a normal domain name state after the test is finished.
In some embodiments, the network address resolution status of the visited domain name is tested as:
presetting a detection corresponding relation between an HTTP request and a feedback protocol state code in a normal state and/or characteristic characters based on the application program and the WEB server;
and sending an HTTP request to the WEB server through a website communication protocol based on the application program, and judging the network address resolution state of the access domain name according to the received protocol state code and/or characteristic characters and the detection corresponding relation.
In some embodiments, the method further comprises:
and if the HTTP request is judged to be not corresponding to the protocol state code and/or the characteristic character based on the detection corresponding relation, the access domain name is moved out of the selected candidate domain name list.
In some embodiments, the domain name access policy is:
and preferentially selecting the access domain name of the corresponding network operator according to the attribute of the access network operator of the application program.
Second aspect of the invention
A second aspect provides an apparatus for application failure risk handling, in some embodiments the apparatus comprising:
the domain name list setting module is used for setting more than or equal to two WEB servers which are positioned in different machine rooms and correspond to the application program, and different domain name lists corresponding to the application program are respectively set in the WEB servers;
the candidate domain name list acquisition module is connected with the domain name list setting module and used for selecting a candidate domain name list from the domain name list according to a preset server domain name selection strategy when the application program is started;
the candidate domain name list state detection module is connected with the candidate domain name list acquisition module and used for detecting the network address state of each candidate domain name in the selected candidate domain name list according to a preset domain name state detection strategy and generating an access domain name list in a normal domain name state;
and the domain name access target website judging module is connected with the candidate domain name list state detecting module and selects a normal domain name access target interface website from the access domain name list based on a domain name access strategy preset by the application program.
In some embodiments, the apparatus further comprises:
and the candidate domain name list building module is used for building the candidate domain name lists and respectively pre-storing the candidate domain name lists in the corresponding WEB servers.
In some embodiments, the candidate domain name list state detection module comprises: the device comprises a data receiving unit, an access domain name selecting unit, an access domain name detecting unit and an access domain name list generating unit; wherein the content of the first and second substances,
the data receiving unit is connected with the candidate domain name list acquiring module and receives attribute data for calling the application program from the WEB server;
the access domain name selection unit is connected with the data receiving unit and selects an access domain name from the selected candidate domain name list according to the attribute data and a preset access domain name selection strategy;
the access domain name detection unit is connected with the access domain name selection unit and is used for testing the network address resolution state of the access domain name, and if the access domain name is in an abnormal state, the network address resolution states of other candidate domain names in the candidate domain name list are tested;
and the access domain name list generating unit is connected with the access domain name detecting unit and generates an access domain name list in a normal domain name state after the test is finished.
Third aspect of the invention
A third aspect provides an application failure risk handling system, which in some embodiments comprises:
the system comprises more than or equal to two WEB servers which are positioned in different machine rooms and are used for prestoring a plurality of different domain name lists corresponding to application program interfaces of a target website server; and
at least one application failure risk handling device for performing the method of any of claims 1-5.
Fourth aspect of the invention
A fourth aspect provides an application failure risk handling terminal, in some embodiments, at least one application client, wherein,
the application client comprises an application failure risk processing device for executing the method according to the embodiments of the first aspect.
Fifth aspect of the invention
A fourth aspect provides an electronic device for application failure risk handling, comprising at least one processor and at least one storage medium;
wherein the storage medium has stored therein instructions for executing the method according to the embodiments of the first aspect, and the processor is configured to execute the instructions.
The technical effects of the embodiment of the invention at least comprise:
the invention adopts multiple servers to provide service, and the servers can be deployed in multiple computer rooms, thereby realizing the effects of high availability, high stability, load balance and the like, judging whether the domain name of the API interface is available at the client, switching to the available domain name in real time, and realizing real-time fault transfer. And by adding real-time fault judgment, the user cannot perceive the fault of the API interface, and fault transfer can realize fault non-inductive transfer. The available domain name is selected to read data, and the availability of the client can be ensured to a great extent due to the plurality of servers.
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention.
Drawings
FIG. 1 is a flowchart illustrating an embodiment of a method for risk of application failure according to the present invention;
FIG. 2 is a flowchart illustrating an embodiment of the application failure risk processing method applied to an applet according to the present invention;
FIG. 3 is a flowchart illustrating an embodiment of a method for processing application program failure risk according to the present invention for detecting an API domain name list;
FIG. 4 is a flowchart illustrating a method for risk management of application program failure according to a second embodiment of the present invention;
FIG. 5 is a flowchart illustrating a method for risk management of application program failures according to a third embodiment of the present invention;
FIG. 6 is a flowchart illustrating a fourth embodiment of a risk management method for application program failure according to the present invention;
FIG. 7 is a flowchart illustrating a method for risk management of application program failure according to a fifth embodiment of the present invention;
FIG. 8 is a schematic structural diagram of an embodiment of an application failure risk processing apparatus according to the present invention;
FIG. 9 is a schematic structural diagram of an apparatus for risk of application failure processing according to a second embodiment of the present invention;
FIG. 10 is a block diagram illustrating an embodiment of an application failure risk processing system according to the present invention;
FIG. 11 is exemplary instructions that can implement the application failure risk processing method of the present invention.
Detailed Description
The present invention is further described in detail below with reference to the attached drawings so that those skilled in the art can implement the invention by referring to the description text.
As shown in fig. 1, in some embodiments, a first aspect provides an application failure risk processing method, which is generally performed by a client of application software, the method including:
And 102, when the application program is started, selecting a candidate domain name list from the domain name list according to a preset server domain name selection strategy.
103, detecting the network address resolution state of each candidate domain name in a plurality of candidate domain name lists; the detection is to kick out the domain name in the abnormal state which cannot be used, and generate an access domain name list including all domain names in the normal resolution state.
And 104, selecting a normal domain name from the access domain name list to access the target interface website based on a domain name access strategy preset by an application program. And selecting a normal domain name from the visiting domain name list to visit the target website. And after the accessible normal domain name is acquired, the IP address of the target website server is acquired according to the domain name, and then the information content in the target website server can be accessed.
It should be noted that step 101-103 is usually performed by the client when the application software is started, and step 104 occurs each time the client accesses the target website server through the software interface.
The API refers specifically to a data exchange interface between a mobile network application (mobile APP, wechat applet, etc.) and a WEB server. And a WEB application program in the WEB server is responsible for data storage, query and logic processing.
The method of the invention sets a plurality of candidate domain name lists corresponding to the software interface of the target website server, and before accessing the target website server when the application program is started. The client detects the domain name firstly and then selects the normal domain name to access the target website, so that the problem that the target website cannot be accessed due to faults caused by software interfaces can be effectively solved.
More importantly, the invention adopts a plurality of candidate domain name lists, thus realizing the effects of high availability, high stability, load balance and the like, and adding real-time fault judgment, so that a user can not sense the API interface fault and can realize the non-sensing transfer of the interface fault.
In some embodiments, before obtaining the candidate domain name lists, a plurality of candidate domain name lists are constructed and pre-stored in a corresponding plurality of domain name servers respectively.
In this embodiment, the plurality of candidate domain name lists are respectively preset on a plurality of different WEB servers, so that the situation that the domain name lists cannot be provided due to a failure of one server is avoided, and the effectiveness of the method and the availability of the protection client can be improved.
Fig. 2 is a schematic flow chart of an embodiment of the application failure risk processing method applied to an applet. The method comprises the following steps:
The server A \ B is consistent in content and plays a role of redundant backup. The A \ B two servers are deployed in different machine rooms, so that physical faults of the servers, network faults and any faults between the servers and application programs can be avoided. Typically, two servers a \ B are deployed in machine rooms in different regions and cities.
And step 205, storing the normal API domain name. As long as the API domain name can be normally served, the API domain name is listed in an available domain name list and then randomly selected, and at the moment, the purpose of load balancing can be achieved.
As shown in fig. 3, a flowchart of a specific embodiment of detecting an API domain name list for an application failure risk processing method includes the following steps:
and step 304, selecting a normal API domain name and continuing the next step. Since the list of available domain names stored in step 201 and 205 may also fail, the client first checks whether the domain name is available before accessing the API. And if the domain name is unavailable, switching to the available domain name in real time to realize real-time fault transfer. The client generally only makes an interface without content, and only can see an interface without content if the server data is not called through the API. The API is a data interaction interface between the software and the server, and can obtain data through the API, or submit data through the API (e.g., when a user registers, data needs to be submitted).
When step 201-. The method of the embodiment comprises the following steps: API domain name acquisition, an API fault detection program, API link optimization, API domain name storage and error handling in the API calling process.
As shown in fig. 4, which is a flowchart illustrating a second embodiment of the application fault risk processing method, different from fig. 1, the method detects a network address state of each candidate domain name in a selected candidate domain name list according to a preset domain name state detection policy, and generates an access domain name list in a normal domain name state, where the method includes:
And step 402, selecting an access domain name from the candidate domain name selection list according to the attribute data and a preset access domain name selection strategy.
As shown in fig. 5, which is a flowchart illustrating a third embodiment of the application failure risk processing method, different from fig. 4, the step of testing the network address resolution status of the visited domain name is as follows:
As shown in fig. 6, which is a flowchart illustrating a fourth embodiment of an application failure risk processing method, different from fig. 5, the method further includes:
As shown in fig. 7, which is a schematic flow chart of a fifth embodiment of the application failure risk processing method, different from fig. 1, step 104 is:
And 142, selecting a normal domain name from the access domain name list to access the target interface website according to the priority of the access domain name of the network operator.
In some alternative embodiments, as shown in fig. 8, a schematic structural diagram of an embodiment of an application failure risk processing apparatus 800 is provided, which can be used to implement the application failure risk processing method described above. Specifically, the apparatus includes: a domain name list setting module 801, a candidate domain name list obtaining module 802, a candidate domain name list state detecting module 803, and a domain name access target website determining module 804.
The domain name list setting module 801 is configured to set, corresponding to an application program, two or more WEB servers located in different computer rooms, and set, in the WEB servers, different domain name lists corresponding to the application program respectively.
The candidate domain name list obtaining module 802 is connected to the domain name list setting module 801, and is configured to select a candidate domain name list from the domain name list according to a preset server domain name selection policy when the application program is started.
The candidate domain name list state detection module 803 is connected to the candidate domain name list acquisition module 802, and configured to detect a network address state of each candidate domain name in the selected candidate domain name list according to a preset domain name state detection policy, and generate an access domain name list in a normal domain name state.
And the domain name access target website determining module 804 is connected to the candidate domain name list state detecting module 803, and selects a normal domain name from the access domain name list to access the target interface website based on a domain name access policy preset by an application program.
In some optional embodiments, as shown in fig. 9, which is a schematic structural diagram of a second embodiment of the apparatus 900 for processing a risk of failure of an application, different from that in fig. 8, the candidate domain name list state detection module 803 includes: data receiving section 831, access domain name extracting section 832, access domain name detecting section 833 and access domain name list generating section 834.
The data receiving unit 831 is connected to the candidate domain name list obtaining module 802, and receives attribute data of an application program called from a WEB server.
The visited domain name selecting unit 832 is connected to the data receiving unit 831, and selects a visited domain name from the candidate domain name list according to the attribute data and a preset visited domain name selecting policy.
The visited domain name detecting unit 833 is connected to the visited domain name selecting unit 832, and tests the network address resolution status of the visited domain name, and if the visited domain name is in an abnormal status, tests the network address resolution status of other candidate domain names in the candidate domain name list.
The visited domain name list generating unit 834 is connected to the visited domain name detecting unit 833, and generates a visited domain name list in a normal domain name state after the test is completed.
In some alternative embodiments, as shown in fig. 10, a schematic structural diagram of an embodiment of an application failure risk processing system 1000 is shown. The method comprises the following steps: more than or equal to two WEB servers 1001 which are positioned in different machine rooms and are used for prestoring a plurality of different domain name lists corresponding to the application program interfaces of the target website server; and at least one application failure risk processing device 1002, which is used for executing the method for processing the application failure risk.
In some optional embodiments, there is further provided a software terminal, in some embodiments, the software terminal includes: at least one software client, wherein,
the software client comprises a software interface failure risk processing device, and the device is used for the method of each embodiment.
The software terminal can be mobile terminal software such as WeChat, QQ, Taobao and the like, and the software client can be an applet installed in the software terminal.
In some alternative embodiments, there is also provided an electronic device, which in some embodiments includes at least one processor and at least one storage medium;
wherein, the storage medium stores instructions for executing the method of the above embodiment, and the processor is used for executing the instructions.
An exemplary instruction segment capable of implementing the method of the above embodiment is as follows:
the corresponding flow chart is shown in fig. 11.
While embodiments of the invention have been described above, it is not limited to the applications set forth in the description and the embodiments, which are fully applicable in various fields of endeavor to which the invention pertains, and further modifications may readily be made by those skilled in the art, it being understood that the invention is not limited to the details shown and described herein without departing from the general concept defined by the appended claims and their equivalents.
Claims (10)
1. The application program fault risk processing method is characterized by comprising the following steps:
setting more than or equal to two WEB servers which correspond to the application program and are positioned in different machine rooms, and respectively setting different domain name lists corresponding to the application program in the WEB servers;
when the application program is started, selecting a candidate domain name list from the domain name list according to a preset server domain name selection strategy;
detecting the network address state of each candidate domain name in the selected candidate domain name list according to a preset domain name state detection strategy, and generating an access domain name list in a normal domain name state;
and selecting a normal domain name from the access domain name list to access a target interface website based on a domain name access strategy preset by the application program.
2. The method for processing the application program fault risk according to claim 1, wherein the network address state of each candidate domain name in the selected candidate domain name list is detected according to a preset domain name state detection policy, and an access domain name list in a normal domain name state is generated as follows:
receiving attribute data for calling the application program from the WEB server;
selecting an access domain name from the selected candidate domain name list according to the attribute data and a preset access domain name selection strategy;
testing the network address resolution state of the access domain name, and if the access domain name is in an abnormal state, testing the network address resolution states of other candidate domain names in the candidate domain name list;
and generating an access domain name list in a normal domain name state after the test is finished.
3. The method for processing application failure risk according to claim 2, wherein the testing of the network address resolution status of the visited domain name is:
presetting a detection corresponding relation between an HTTP request and a feedback protocol state code in a normal state and/or characteristic characters based on the application program and the WEB server;
and sending an HTTP request to the WEB server through a website communication protocol based on the application program, and judging the network address resolution state of the access domain name according to the received protocol state code and/or characteristic characters and the detection corresponding relation.
4. The method for processing the risk of application program failure according to claim 3, further comprising:
and if the HTTP request is judged to be not corresponding to the protocol state code and/or the characteristic character based on the detection corresponding relation, the access domain name is moved out of the selected candidate domain name list.
5. The method for processing application program failure risk according to any one of claims 1 to 4, wherein the domain name access policy is:
and preferentially selecting the access domain name of the corresponding network operator according to the attribute of the access network operator of the application program.
6. Application failure risk processing apparatus, characterized by comprising: the domain name list setting module, the candidate domain name list acquiring module, the candidate domain name list state detecting module and the domain name access target website judging module; wherein the content of the first and second substances,
the domain name list setting module is used for setting more than or equal to two WEB servers which are positioned in different machine rooms and correspond to the application program, and different domain name lists corresponding to the application program are respectively set in the WEB servers;
the candidate domain name list acquisition module is connected with the domain name list setting module and used for selecting a candidate domain name list from the domain name list according to a preset server domain name selection strategy when the application program is started;
the candidate domain name list state detection module is connected with the candidate domain name list acquisition module and used for detecting the network address state of each candidate domain name in the selected candidate domain name list according to a preset domain name state detection strategy and generating an access domain name list in a normal domain name state;
and the domain name access target website judging module is connected with the candidate domain name list state detecting module and selects a normal domain name access target interface website from the access domain name list based on a domain name access strategy preset by the application program.
7. The apparatus for processing risk of application failure according to claim 6, wherein the candidate domain name list state detection module comprises: the device comprises a data receiving unit, an access domain name selecting unit, an access domain name detecting unit and an access domain name list generating unit; wherein the content of the first and second substances,
the data receiving unit is connected with the candidate domain name list acquiring module and receives attribute data for calling the application program from the WEB server;
the access domain name selection unit is connected with the data receiving unit and selects an access domain name from the selected candidate domain name list according to the attribute data and a preset access domain name selection strategy;
the access domain name detection unit is connected with the access domain name selection unit and is used for testing the network address resolution state of the access domain name, and if the access domain name is in an abnormal state, the network address resolution states of other candidate domain names in the candidate domain name list are tested;
and the access domain name list generating unit is connected with the access domain name detecting unit and generates an access domain name list in a normal domain name state after the test is finished.
8. An application failure risk processing system, comprising:
the system comprises more than or equal to two WEB servers which are positioned in different machine rooms and are used for prestoring a plurality of different domain name lists corresponding to application program interfaces of a target website server; and
at least one application failure risk handling device for performing the method of any of claims 1-5.
9. A terminal, comprising: at least one application client, wherein,
the application client comprises application failure risk handling means for performing the method of any of claims 1-5.
10. An electronic device comprising at least one processor and at least one storage medium;
wherein the storage medium has stored therein instructions for performing the method of any of claims 1-5, the processor being configured to execute the instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813308.3A CN112000518A (en) | 2020-08-13 | 2020-08-13 | Application program fault risk processing method, device and system, terminal and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813308.3A CN112000518A (en) | 2020-08-13 | 2020-08-13 | Application program fault risk processing method, device and system, terminal and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112000518A true CN112000518A (en) | 2020-11-27 |
Family
ID=73472223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010813308.3A Pending CN112000518A (en) | 2020-08-13 | 2020-08-13 | Application program fault risk processing method, device and system, terminal and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000518A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113890866A (en) * | 2021-09-26 | 2022-01-04 | 恒安嘉新（北京）科技股份公司 | Illegal application software identification method, device, medium and electronic equipment |
| CN114465983A (en) * | 2022-01-25 | 2022-05-10 | 百融云创科技股份有限公司 | Multi-domain name based API call automatic switching method and system |
| CN116382809A (en) * | 2023-05-26 | 2023-07-04 | 荣耀终端有限公司 | Application program starting method and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110138476A1 (en) * | 2009-12-08 | 2011-06-09 | Microsoft Corporation | Software Fault Isolation Using Byte-Granularity Memory Protection |
| CN104092792A (en) * | 2014-07-15 | 2014-10-08 | 北京奇虎科技有限公司 | Method, system and client-side for achieving flow optimization based on domain name resolution request |
| CN104539462A (en) * | 2015-01-09 | 2015-04-22 | 北京京东尚科信息技术有限公司 | Method and device for switching disaster recovery application example |
| CN106210155A (en) * | 2015-04-29 | 2016-12-07 | 腾讯科技（深圳）有限公司 | The method and apparatus connecting application server |
| CN107426341A (en) * | 2017-09-13 | 2017-12-01 | 北京智芯微电子科技有限公司 | The system and method that APP interacts with service end |
| CN109150561A (en) * | 2017-06-16 | 2019-01-04 | 贵州白山云科技股份有限公司 | A kind of domain name system parsing configuration method, device and system |
-
2020
- 2020-08-13 CN CN202010813308.3A patent/CN112000518A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110138476A1 (en) * | 2009-12-08 | 2011-06-09 | Microsoft Corporation | Software Fault Isolation Using Byte-Granularity Memory Protection |
| CN104092792A (en) * | 2014-07-15 | 2014-10-08 | 北京奇虎科技有限公司 | Method, system and client-side for achieving flow optimization based on domain name resolution request |
| CN104539462A (en) * | 2015-01-09 | 2015-04-22 | 北京京东尚科信息技术有限公司 | Method and device for switching disaster recovery application example |
| CN106210155A (en) * | 2015-04-29 | 2016-12-07 | 腾讯科技（深圳）有限公司 | The method and apparatus connecting application server |
| CN109150561A (en) * | 2017-06-16 | 2019-01-04 | 贵州白山云科技股份有限公司 | A kind of domain name system parsing configuration method, device and system |
| CN107426341A (en) * | 2017-09-13 | 2017-12-01 | 北京智芯微电子科技有限公司 | The system and method that APP interacts with service end |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113890866A (en) * | 2021-09-26 | 2022-01-04 | 恒安嘉新（北京）科技股份公司 | Illegal application software identification method, device, medium and electronic equipment |
| CN113890866B (en) * | 2021-09-26 | 2024-03-12 | 恒安嘉新（北京）科技股份公司 | Illegal application software identification method, device, medium and electronic equipment |
| CN114465983A (en) * | 2022-01-25 | 2022-05-10 | 百融云创科技股份有限公司 | Multi-domain name based API call automatic switching method and system |
| CN114465983B (en) * | 2022-01-25 | 2024-04-05 | 百融云创科技股份有限公司 | Multi-domain name-based API call automatic switching method and system |
| CN116382809A (en) * | 2023-05-26 | 2023-07-04 | 荣耀终端有限公司 | Application program starting method and electronic equipment |
| CN116382809B (en) * | 2023-05-26 | 2023-10-20 | 荣耀终端有限公司 | Application program starting method and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112000518A (en) | Application program fault risk processing method, device and system, terminal and equipment | |
| US7398434B2 (en) | Computer generated documentation including diagram of computer system | |
| CN109714209B (en) | Method and system for diagnosing website access fault | |
| US20010025313A1 (en) | Method of balancing load among mirror servers | |
| CN108989355B (en) | Vulnerability detection method and device | |
| CN110311837B (en) | Online service availability detection method and device and computer equipment | |
| CN103546590A (en) | Method and device for choosing DNS (domain name server) | |
| WO2005093574A2 (en) | Anomaly management scheme for a multi-agent system | |
| US10389614B2 (en) | Web site reachability management for content browsing | |
| US7921335B2 (en) | System diagnostic utility | |
| CN106060004A (en) | Database access method and database agent node | |
| CN108076003A (en) | The detection method and device of Session Hijack | |
| US9485140B2 (en) | Automatic proxy setting modification | |
| CN110781083A (en) | H5 client code setting multi-environment testing method and system | |
| EP1387300A2 (en) | Establishment of network connections | |
| CN108089972B (en) | Interface test method and device | |
| US20050102392A1 (en) | Pattern based web services using caching | |
| CN110191203B (en) | Method for realizing dynamic access of server and electronic equipment | |
| CN109951549B (en) | Network page access method and device and computer readable storage medium | |
| US20040225708A1 (en) | Establishment of network connections | |
| CN110311978A (en) | Browser information processing method, device, equipment and storage medium | |
| CN106060124A (en) | Application program downloading method and mobile terminal | |
| CN115580658A (en) | Service access method and device, storage medium and electronic equipment | |
| CN112104513B (en) | Visual software load method, device, equipment and storage medium | |
| CN115361378A (en) | Test environment file searching method and system and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201127 |
|
| RJ01 | Rejection of invention patent application after publication |