CN105763365A - Method and device for processing anomaly - Google Patents
Method and device for processing anomaly Download PDFInfo
- Publication number
- CN105763365A CN105763365A CN201610053762.7A CN201610053762A CN105763365A CN 105763365 A CN105763365 A CN 105763365A CN 201610053762 A CN201610053762 A CN 201610053762A CN 105763365 A CN105763365 A CN 105763365A
- Authority
- CN
- China
- Prior art keywords
- user operation
- client device
- server
- message
- user
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0253—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using browsers or web-pages for accessing management information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a method and a device for processing an anomaly. The method comprises steps: a service request message sent by a client device is received; whether the operation state of the server meets conditions for processing the service request message is judged; when the operation state can not meet the conditions for processing the service request message, a user operation strategy is set to be user operation prohibition; a user operation message is pushed to the client device, the user operation message carries the user operation strategy to prohibit the user from operating the client device when the user operation strategy is determined to be user operation prohibition by the client device. Frequency operation by the user when the server is abnormal can be effectively avoided, the burden of the server is lessened, and the user experience is enhanced.
Description
Technical field
The application relates to network communication technology field, particularly relates to a kind of abnormality eliminating method and device.
Background technology
C/S (client/server) framework is widely used in internet communication.In client with server interaction process, some abnormal conditions unavoidably occur, for instance, server process service request overlong time is not in time to client return information, now, user can think loss of data by mistake and frequent operation client device, thus having increased the weight of the burden of server.
Summary of the invention
In view of this, the application provides a kind of abnormality eliminating method and device.
Specifically, the application is achieved by the following technical solution:
The application provides a kind of abnormality eliminating method, is applied on server, and the method includes:
Receive the business request information that client device sends；
Judge whether the running status of described server meets the condition processing described business request information；
When described running status is unsatisfactory for the condition processing described business request information, user operation strategy is set for forbidding user operation；Push user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
The application also provides for a kind of abnormality eliminating method, is applied on client device, and the method includes:
Business request information is sent to server；
Receive the user operation message of described server push, described user operation message is carried the user operation strategy that described server is arranged according to self-operating state；
When described user operation strategy is for forbidding user operation, forbid user operation.
The application also provides for a kind of exception handling device, is applied on server, and this device includes:
Receive unit, for receiving the business request information that client device sends；
Judging unit, it is judged that whether the running status of described server meets the condition processing described business request information；
Policy unit, for when described running status is unsatisfactory for the condition processing described business request information, arranging user operation strategy for forbidding user operation；
Push unit, for pushing user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
The application also provides for a kind of exception handling device, is applied on client device, and this device includes:
Transmitting element, for sending business request information to server；
Receive unit, for receiving the user operation message of described server push, described user operation message is carried the user operation strategy that described server is arranged according to self-operating state；
Forbid unit, for when described user operation strategy is for forbidding user operation, forbidding user operation.
Be can be seen that by above description, the application is coordinated by server and client device, user operation client device is determined whether according to self-operating state by server, and inform client device, client device is when knowing that server does not allow user operation, forbid user operation, thus avoiding user's frequent operation to cause server burden.
Accompanying drawing explanation
Fig. 1 is a kind of abnormality eliminating method flow chart shown in the application one exemplary embodiment；
Fig. 2 is a kind of abnormality eliminating method flow chart shown in the application another exemplary embodiment；
Fig. 3 is the underlying hardware structural representation of a kind of exception handling device place equipment shown in the application one exemplary embodiment；
Fig. 4 is the structural representation of a kind of exception handling device shown in the application one exemplary embodiment；
Fig. 5 is the structural representation of a kind of exception handling device shown in the application another exemplary embodiment.
Detailed description of the invention
Here in detail exemplary embodiment being illustrated, its example representation is in the accompanying drawings.When as explained below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the application.On the contrary, they only with in appended claims describe in detail, the application some in the example of consistent apparatus and method.
It is only merely for the purpose describing specific embodiment at term used in this application, and is not intended to be limiting the application." one ", " described " and " being somebody's turn to do " of the singulative used in the application and appended claims is also intended to include most form, unless context clearly shows that other implications.It is also understood that term "and/or" used herein refers to and comprises any or all of one or more project of listing being associated and be likely to combination.
Although should be appreciated that and be likely to adopt term first, second, third, etc. to describe various information in the application, but these information should not necessarily be limited by these terms.These terms are only used for being distinguished from each other out same type of information.Such as, when without departing from the application scope, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.Depend on linguistic context, word as used in this " if " can be construed to " ... time " or " when ... " or " in response to determining ".
C/S framework is widely used in internet communication, for instance, Web client and Web server, user can pass through Web client and send request to Web server, Web server provide information needed for it.
In client with server interaction process, unavoidably there will be some abnormal conditions (such as, server internal error, server are busy or restart), now, server can return error message or long-time not return information to client.For a user, if server returns the information of similar " server internal error ", puzzlement can be brought to user, it is not known that how this operates, and such mistake often recovers normal after server normally starts, and therefore, is not required to prompt the user with.If server process user asks to need to expend for a long time, not returning any information to user again in processing procedure, user will be considered that server exception or loss of data, thus frequent operation client, increases the weight of the burden of server.
If increasing error trapping mechanism in client, the error message that server returns can be judged, thus distinguishing the error message of error message and the shielding needing prompting.But, the error message that server returns is of a great variety, and client is difficult to precognition or tests out all of error message, therefore, accurate seizure cannot be accomplished, still have part to need the error message of shielding to be prompted to user and the long-time frequent operation problem that return information does not cause of unresolved server.
For the problems referred to above, the embodiment of the present application proposes a kind of abnormality eliminating method, the method is determined whether user operation client device by server according to self-operating state, and inform client device, client device is when knowing that server does not allow user operation, forbid user operation, thus avoiding user's frequent operation to cause server burden.
Referring to Fig. 1, for an embodiment flow chart of the application abnormality eliminating method, exception procedure is described by this embodiment from server side.
Step 101, receives the business request information that client device sends.
In C/S framework, server proceeds by Business Processing based on the business request information of client device.
Step 102, it is judged that whether the running status of described server meets the condition processing described business request information.
In the embodiment of the present application, server constantly detects self-operating state, for instance, the business of current server too much excessively busy, the Business Processing progress of current server, server are upgraded, server is comparatively idle.Judge currently whether can process, according to testing result, the business request information that client device sends.
Step 103, when described running status is unsatisfactory for the condition processing described business request information, arranges user operation strategy for forbidding user operation；Push user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
When running status is unsatisfactory for the condition processing business request information, for instance, when server is upgraded, it is impossible to process service request, then server arranges user operation strategy for forbidding user operation.
Server pushes user operation message to client device, carries user operation strategy in this user operation message.Concrete propelling movement process can adopt more ripe existing techniques in realizing, such as, server push technology based on client Socket (socket), Server remote calling technology, or, based on the long server push technology etc. connected of HTTP (HyperTextTransferProtocol, HTML (Hypertext Markup Language)).
Client device, when determining user operation strategy for forbidding user operation, forbids user's repetitive operation, thus avoiding increasing burden to server.
In one preferably embodiment, when user operation strategy setting is for forbidding user operation, server also can carry the Business Processing progress that server is current in the user operation message pushed to client device, client device can prompt the user with the Business Processing progress of server by playing the mode such as frame or status bar, so that user grasps the operation conditions of server simple and clearly, no longer frequently repeat same operation.
When server detects the condition that running status meets process business request information, user operation strategy is set for allowing user operation, user operation message is pushed to client device, this user operation message carries user operation strategy, so that client device is when determining user operation strategy for allowing user operation, it is allowed to user operation client device.
The business request information that server process client device sends.In the processing procedure of business request information, in fact it could happen that various mistakes, for instance, server internal error, user's input error etc..Server needs error differentiating type, determines whether that client device pushes error message according to type of error.
Specifically, when mistake type of error belong to user be concerned about wrong time, to client device push error message, for instance, when mistake is user's input error, user should be pointed out, in order to user changes input information.When mistake type of error be not belonging to user be concerned about wrong time, forbid to client device push error message, for instance, when mistake is server internal error, this mistake need not prompt the user with, to avoid user is caused puzzlement.
Referring to Fig. 2, for another embodiment flow chart of the application abnormality eliminating method, exception handling procedure is described by this embodiment from client device side.
Step 201, sends business request information to server.
After sending business request information, client device forbids user operation, and waiting for server returns user operation message.
Step 202, receives the user operation message of described server push, carries the user operation strategy that described server is arranged according to self-operating state in described user operation message.
Step 203, when described user operation strategy is for forbidding user operation, forbids user operation.
When user operation strategy is for allowing user operation, it is allowed to user operation.
Additionally, can also carry, in the user operation message that server sends, the Business Processing progress that server is current；When user operation strategy is for forbidding user operation, prompt the user with the Business Processing progress of server.
Concrete processing procedure referring to the description of abovementioned steps 101～step 103, can not repeat them here.
By foregoing description it can be seen that the application is mainly carried out abnormality processing by server, determine whether user operation client device according to running status, and inform client device, it is to avoid user's frequent operation increases server burden；Meanwhile, server it is responsible for the filtration of error message, only the error message that user is concerned about is prompted to user, it is to avoid the mistake that will be unable to identify is left over to client device, simplifies the handling process of client device side.
Now to be managed for configuration by Web page, exception handling procedure is discussed in detail.
In a kind of application scenarios, router (being equivalent to server) is configured by user by web front end (being equivalent to client device).
It is specially, user inputs user name, password and network configuration information etc. in the Web page (hereinafter referred to as the configuration page) opened, then, the configuration request message (being equivalent to business request information) carrying above-mentioned information is sent to router.After sending configuration request message, forbid that user continues the operative configuration page.
The configuration request message received can be filtered processing by increase Web container under existing configuration management framework (the compatible original Web configuration flow of this Web container) by the router in the embodiment of the present application.Processing procedure is as follows:
Router constantly detects self-operating state, takes different processing modes according to different running statuses.
When router determines, according to current operating conditions, the condition not possessing the configuration request message processing web front end, shield configuration request message, and user operation strategy is set for forbidding user operation, and push user operation message to web front end, this user operation message carries user operation strategy.Web front end, when confirming user operation strategy for forbidding user operation, forbids user operation.In one preferably embodiment, router can calculate the process progress of current task further, Business Processing progress is carried in user operation message, is pushed to web front end, this Business Processing progress is pointed out user by web front end in the way of playing frame or status bar, makes the running status of user's more intuitive understanding router.
When the running status of router meets the condition of the configuration request message processing web front end, process the configuration request message received, and user operation strategy is set for allowing user operation, user operation strategy is carried in the user operation message pushed to client device.Web front end is when confirming user operation strategy for allowing user operation, and the operating right of releasing user, namely permission user continues configuration operation.
Wherein, router is likely to occur various mistake in processing configuration request message process.Such as, when resolving configuration request message, it has been found that the user name mistake of user's input, or network configuration information is incorrect, and now, router pushes error message to web front end, web front end points out above-mentioned error message by configuration page user oriented, so that user changes mistake in time.And the router interior mistake for occurring in processing procedure, then do not push to web front end, directly filter out.
Corresponding with the embodiment of aforementioned abnormality eliminating method, present invention also provides the embodiment of exception handling device.
The embodiment of the application exception handling device can be applied on server or client device.Device embodiment can be realized by software, it is also possible to is realized by the mode of hardware or software and hardware combining.Implemented in software for example, as the device on a logical meaning, it is formed by computer program instructions corresponding in the processor run memory of its place equipment.Say from hardware view, as shown in Figure 3, a kind of hardware structure diagram for the application exception handling device place equipment, except the processor shown in Fig. 3, network interface and memorizer, in embodiment, the equipment at device place is generally according to the actual functional capability of this equipment, other hardware can also be included, this is repeated no more.
Refer to Fig. 4, for the structural representation of the exception handling device in one embodiment of the application.This exception handling device includes receiving unit 401, judging unit 402, policy unit 403 and push unit 404, wherein:
Receive unit 401, for receiving the business request information that client device sends；
Judging unit 402, it is judged that whether the running status of described server meets the condition processing described business request information；
Policy unit 403, for when described running status is unsatisfactory for the condition processing described business request information, arranging user operation strategy for forbidding user operation；
Push unit 404, for pushing user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
Further,
Described push unit 404, is additionally operable to when described user operation strategy is for forbidding user operation, also carries current business and processes progress, so that described client device prompts the user with the Business Processing progress of described server in described user operation message.
Further,
Described policy unit 403, is additionally operable to when described running status meets the condition processing described business request information, arranges described user operation strategy for allowing user operation；
Described push unit 404, it is additionally operable to push user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for allowing user operation, it is allowed to client device described in user operation.
Processing unit, for processing the business request information that described client device sends；
According to the type of error of described mistake, error unit, for when finding mistake in processing procedure, determining whether that described client device pushes error message.
Further,
Described error unit, specifically for when the type of error of described mistake belong to user be concerned about wrong time, to described client device push error message；When the type of error of described mistake be not belonging to user be concerned about wrong time, forbid to described client device push error message.
Refer to Fig. 5, for the structural representation of the exception handling device in another embodiment of the application.This exception handling device includes transmitting element 501, receives unit 502 and forbid unit 503, wherein:
Transmitting element 501, for sending business request information to server；
Receive unit 502, for receiving the user operation message of described server push, described user operation message is carried the user operation strategy that described server is arranged according to self-operating state；
Forbid unit 503, for when described user operation strategy is for forbidding user operation, forbidding user operation.
Further,
Described forbid unit 503, be additionally operable to after sending described business request information to before receiving described user operation message, forbidding user operation.
Further, also carrying the Business Processing progress that described server is current in described user operation message, described device also includes:
Tip element, for when described user operation strategy is for forbidding user operation, prompting the user with the Business Processing progress of described server.
What in said apparatus, the function of unit and the process that realizes of effect specifically referred in said method corresponding step realizes process, does not repeat them here.
For device embodiment, owing to it corresponds essentially to embodiment of the method, so relevant part illustrates referring to the part of embodiment of the method.Device embodiment described above is merely schematic, the wherein said unit illustrated as separating component can be or may not be physically separate, the parts shown as unit can be or may not be physical location, namely may be located at a place, or can also be distributed on multiple NE.Some or all of module therein can be selected according to the actual needs to realize the purpose of the application scheme.Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.
The foregoing is only the preferred embodiment of the application, not in order to limit the application, all within spirit herein and principle, any amendment of making, equivalent replacements, improvement etc., should be included within the scope that the application protects.
Claims (14)
1. an abnormality eliminating method, is applied on server, it is characterised in that the method includes:
Receive the business request information that client device sends；
Judge whether the running status of described server meets the condition processing described business request information；
When described running status is unsatisfactory for the condition processing described business request information, user operation strategy is set for forbidding user operation；Push user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
2. the method for claim 1, it is characterised in that:
When described user operation strategy is for forbidding user operation, described user operation message is also carried current business and processes progress, so that described client device prompts the user with the Business Processing progress of described server.
3. method as claimed in claim 1 or 2, it is characterised in that described method also includes:
When described running status meets the condition processing described business request information, described user operation strategy is set for allowing user operation, user operation message is pushed to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for allowing user operation, it is allowed to client device described in user operation.
Process the business request information that described client device sends；
When finding mistake in processing procedure, determine whether that described client device pushes error message according to the type of error of described mistake.
4. method as claimed in claim 3, it is characterised in that the described type of error according to described mistake determines whether that described client device pushes error message, including:
When the type of error of described mistake belong to user be concerned about wrong time, to described client device push error message；When the type of error of described mistake be not belonging to user be concerned about wrong time, forbid to described client device push error message.
5. an abnormality eliminating method, is applied on client device, it is characterised in that the method includes:
Business request information is sent to server；
Receive the user operation message of described server push, described user operation message is carried the user operation strategy that described server is arranged according to self-operating state；
When described user operation strategy is for forbidding user operation, forbid user operation.
6. method as claimed in claim 5, it is characterised in that described method also includes:
Arrive after sending described business request information before receiving described user operation message, forbid user operation.
7. the method as described in claim 5 or 6, it is characterised in that:
Described user operation message is also carried the Business Processing progress that described server is current；
When described user operation strategy is for forbidding user operation, prompt the user with the Business Processing progress of described server.
8. an exception handling device, is applied on server, it is characterised in that this device includes:
Receive unit, for receiving the business request information that client device sends；
Judging unit, it is judged that whether the running status of described server meets the condition processing described business request information；
Policy unit, for when described running status is unsatisfactory for the condition processing described business request information, arranging user operation strategy for forbidding user operation；
Push unit, for pushing user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for forbidding user operation, forbids client device described in user operation.
9. device as claimed in claim 8, it is characterised in that:
Described push unit, is additionally operable to when described user operation strategy is for forbidding user operation, also carries current business and processes progress, so that described client device prompts the user with the Business Processing progress of described server in described user operation message.
10. device as claimed in claim 8 or 9, it is characterised in that:
Described policy unit, is additionally operable to when described running status meets the condition processing described business request information, arranges described user operation strategy for allowing user operation；
Described push unit, it is additionally operable to push user operation message to described client device, described user operation message is carried described user operation strategy, so that described client device is when determining described user operation strategy for allowing user operation, it is allowed to client device described in user operation.
Processing unit, for processing the business request information that described client device sends；
According to the type of error of described mistake, error unit, for when finding mistake in processing procedure, determining whether that described client device pushes error message.
11. device as claimed in claim 10, it is characterised in that:
Described error unit, specifically for when the type of error of described mistake belong to user be concerned about wrong time, to described client device push error message；When the type of error of described mistake be not belonging to user be concerned about wrong time, forbid to described client device push error message.
12. an exception handling device, it is applied on client device, it is characterised in that this device includes:
Transmitting element, for sending business request information to server；
Receive unit, for receiving the user operation message of described server push, described user operation message is carried the user operation strategy that described server is arranged according to self-operating state；
Forbid unit, for when described user operation strategy is for forbidding user operation, forbidding user operation.
13. device as claimed in claim 12, it is characterised in that:
Described forbid unit, be additionally operable to after sending described business request information to before receiving described user operation message, forbidding user operation.
14. the device as described in claim 12 or 13, it is characterised in that also carrying the Business Processing progress that described server is current in described user operation message, described device also includes:
Tip element, for when described user operation strategy is for forbidding user operation, prompting the user with the Business Processing progress of described server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610053762.7A CN105763365B (en) | 2016-01-26 | 2016-01-26 | Exception handling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610053762.7A CN105763365B (en) | 2016-01-26 | 2016-01-26 | Exception handling method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105763365A true CN105763365A (en) | 2016-07-13 |
| CN105763365B CN105763365B (en) | 2020-05-12 |
Family
ID=56342637
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610053762.7A Active CN105763365B (en) | 2016-01-26 | 2016-01-26 | Exception handling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105763365B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107547321A (en) * | 2017-06-28 | 2018-01-05 | 新华三技术有限公司 | Message processing method, device, associated electronic device and readable storage medium storing program for executing |
| CN107645517A (en) * | 2016-07-20 | 2018-01-30 | 腾讯科技（深圳）有限公司 | Data push method and device |
| CN107666543A (en) * | 2016-07-29 | 2018-02-06 | 中国移动通信集团江苏有限公司 | A kind of data processing method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040122917A1 (en) * | 2002-12-18 | 2004-06-24 | Menon Jaishankar Moothedath | Distributed storage system for data-sharing among client computers running defferent operating system types |
| CN101039332A (en) * | 2007-03-15 | 2007-09-19 | 华为技术有限公司 | Method, system and server for transmitting page data |
| CN101106480A (en) * | 2007-06-27 | 2008-01-16 | 杭州华三通信技术有限公司 | Configuration backup method, system and configuration file server and managed devices |
| CN101262485A (en) * | 2008-04-10 | 2008-09-10 | 华为技术有限公司 | Authentication method and system, server and client |
| CN102137444A (en) * | 2010-11-25 | 2011-07-27 | 华为技术有限公司 | Overload control method and device |
| CN102694850A (en) * | 2012-05-16 | 2012-09-26 | 浪潮齐鲁软件产业有限公司 | System integration method based on HttpClient technique |
| CN103580937A (en) * | 2012-07-24 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Web service simulating method and system and service agent system thereof |
-
2016
- 2016-01-26 CN CN201610053762.7A patent/CN105763365B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040122917A1 (en) * | 2002-12-18 | 2004-06-24 | Menon Jaishankar Moothedath | Distributed storage system for data-sharing among client computers running defferent operating system types |
| CN101039332A (en) * | 2007-03-15 | 2007-09-19 | 华为技术有限公司 | Method, system and server for transmitting page data |
| CN101106480A (en) * | 2007-06-27 | 2008-01-16 | 杭州华三通信技术有限公司 | Configuration backup method, system and configuration file server and managed devices |
| CN101262485A (en) * | 2008-04-10 | 2008-09-10 | 华为技术有限公司 | Authentication method and system, server and client |
| CN102137444A (en) * | 2010-11-25 | 2011-07-27 | 华为技术有限公司 | Overload control method and device |
| CN102694850A (en) * | 2012-05-16 | 2012-09-26 | 浪潮齐鲁软件产业有限公司 | System integration method based on HttpClient technique |
| CN103580937A (en) * | 2012-07-24 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Web service simulating method and system and service agent system thereof |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107645517A (en) * | 2016-07-20 | 2018-01-30 | 腾讯科技（深圳）有限公司 | Data push method and device |
| CN107645517B (en) * | 2016-07-20 | 2021-04-16 | 腾讯科技（深圳）有限公司 | Data pushing method and device |
| CN107666543A (en) * | 2016-07-29 | 2018-02-06 | 中国移动通信集团江苏有限公司 | A kind of data processing method and device |
| CN107666543B (en) * | 2016-07-29 | 2020-11-13 | 中国移动通信集团江苏有限公司 | Data processing method and device |
| CN107547321A (en) * | 2017-06-28 | 2018-01-05 | 新华三技术有限公司 | Message processing method, device, associated electronic device and readable storage medium storing program for executing |
| CN107547321B (en) * | 2017-06-28 | 2021-05-14 | 新华三技术有限公司 | Message processing method and device, related electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105763365B (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9647891B2 (en) | Managing network configurations | |
| JP6396887B2 (en) | System, method, apparatus, and non-transitory computer readable storage medium for providing mobile device support services | |
| RU2501073C2 (en) | System health and performance care of computing devices | |
| US11153346B2 (en) | Secure network device management in a telecommunications network | |
| US20140207929A1 (en) | Management apparatus and management method | |
| KR101416280B1 (en) | Event handling system and method | |
| US7716527B2 (en) | Repair system | |
| CN109639818B (en) | Service discovery method and device under cloud environment, server and storage medium | |
| US10970148B2 (en) | Method, device and computer program product for managing input/output stack | |
| CN105763365A (en) | Method and device for processing anomaly | |
| CN109361542A (en) | The fault handling method of client, device, system, terminal and server | |
| US20120317039A1 (en) | On-demand purchase of virtual image licenses in a cloud computing environment | |
| CN110472381B (en) | Root permission hiding method and system based on android system and storage medium | |
| CN110881224A (en) | Network long connection method, device, equipment and storage medium | |
| CN108650123A (en) | Fault message recording method, device, equipment and storage medium | |
| CN114726789A (en) | Method, device, equipment and medium for traffic management and traffic management policy configuration | |
| CN106060124A (en) | Application program downloading method and mobile terminal | |
| CN115859253A (en) | Service access control method, device, equipment and medium | |
| CN105162633B (en) | A kind of method and apparatus managing network in the multiple operating system based on container | |
| CN105760283A (en) | Log output method and device | |
| KR20080047248A (en) | Security testing apparatus and method of remote remote procedure call software | |
| CN109947630B (en) | Fault notification method, device and storage medium | |
| JP2006285453A (en) | Information processor, information processing method, and information processing program | |
| KR20040105588A (en) | Method with management of an opaque user identifier for checking complete delivery of a service using a set of servers | |
| CN111966367A (en) | Data deleting method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |