CN108173910B - Method and system for managing application - Google Patents
Method and system for managing application Download PDFInfo
- Publication number
- CN108173910B CN108173910B CN201711362535.3A CN201711362535A CN108173910B CN 108173910 B CN108173910 B CN 108173910B CN 201711362535 A CN201711362535 A CN 201711362535A CN 108173910 B CN108173910 B CN 108173910B
- Authority
- CN
- China
- Prior art keywords
- application
- long connection
- target
- identifier
- target terminal
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000012545 processing Methods 0.000 abstract description 11
- 238000004891 communication Methods 0.000 abstract description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Abstract
The invention discloses a method and a system for managing application, and belongs to the technical field of network communication. The method comprises the following steps: when a preset management condition for a first application installed on a target terminal is met, a first server corresponding to the first application determines a target long connection currently maintained by the target terminal, the first server sends an application management message for the first application to a second server corresponding to the target long connection, the second server sends the application management message to the target terminal through the target long connection, and the target terminal receives the application management message through a second application corresponding to the installed second server and manages the first application based on the application management message. By adopting the invention, the occupancy rate of the terminal processing resources during the management application can be reduced.
Description
Technical Field
The present invention relates to the field of network communication technologies, and in particular, to a method and a system for managing applications.
Background
With the rapid development of network technologies, network services are also more diverse and complex. At present, network services based on TCP (Transmission Control Protocol) connection may include two connection modes, i.e., long connection and short connection.
Long connections are often used for frequent, point-to-point communications. After a user installs an application on a terminal, a server of the application can establish TCP connection with the terminal and keep the TCP connection not disconnected, so that long connection can be maintained between the server and the terminal. Therefore, when the server needs to perform real-time management such as software updating, state detection and the like on the application installed on the terminal, the server can directly send corresponding application management information to the terminal based on the established TCP connection without repeatedly establishing the TCP connection.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
if the server of a plurality of applications installed on the terminal needs to manage the applications in real time, the terminal needs to maintain long connections with the plurality of servers at the same time, and therefore the occupancy rate of the processing resources of the terminal is high.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a method and system for managing an application. The technical scheme is as follows:
in a first aspect, a method for managing an application is provided, the method including:
when a preset management condition for a first application installed on a target terminal is met, a first server corresponding to the first application determines a target long connection currently maintained by the target terminal;
the first server sends an application management message for the first application to a second server corresponding to the target long connection;
the second server sends the application management message to the target terminal through the target long connection;
and the target terminal receives the application management message through a second application corresponding to the installed second server, and manages the first application based on the application management message.
Optionally, the sending, by the first server, an application management message for the first application to a second server corresponding to the target long connection includes:
the first server side determines the identifier of a second application corresponding to the identifier of the target long connection in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier;
and the first server sends the application management message of the first application to a second server corresponding to the second application.
Optionally, the method further includes:
the target terminal establishes the target long connection with the second server through the second application;
the target terminal sends a long connection newly-added message to the first service terminal through the first application, wherein the long connection newly-added message at least carries an identifier of the target long connection;
the first server determines the identifier of the target terminal and the identifier of the second application according to the identifier of the target long connection;
and the first service end records that the target terminal is maintaining the target long connection, and correspondingly adds the identification of the target long connection, the identification of the target terminal and the identification of the second application into the corresponding relationship.
Optionally, the method further includes:
when the target long connection is detected to be disconnected, the target terminal sends a long connection disconnection message to the first service terminal through the first application, wherein the long connection disconnection message at least carries an identifier of the target long connection;
and the first service end records that the target terminal stops maintaining the target long connection.
Optionally, the application management message at least carries an identifier of the target long connection;
the target terminal receives the application management message through a second application corresponding to the installed second server, and manages the first application based on the application management message, including:
the target terminal receives the application management message through a second application corresponding to the installed second server;
and if the identification of the target long connection is consistent with the locally stored long connection identification associated with the first application, the target terminal manages the first application based on the application management message.
In a second aspect, a system for managing applications is provided, where the system includes a target terminal, a first service end and a second service end, the target terminal is installed with a first application and a second application, the first service end is a background service end of the first application, and the second service end is a background service end of the second application, where:
the first server is used for determining the target long connection currently maintained by the target terminal when the preset management condition for the first application is met;
the first service end is further configured to send an application management message for the first application to a second service end corresponding to the target long connection;
the second server is used for sending the application management message to the target terminal through the target long connection;
the target terminal is used for receiving the application management message through the second application and managing the first application based on the application management message.
Optionally, the first service end is specifically configured to:
determining the identifier of a second application corresponding to the identifier of the target long connection in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier;
and sending an application management message for the first application to a second server corresponding to the second application.
Optionally, the target terminal is further configured to establish the target long connection with the second server through the second application;
the target terminal is further configured to send a long connection newly-added message to the first service end through the first application, where the long connection newly-added message at least carries an identifier of the target long connection;
the first service end is further configured to determine an identifier of the target terminal and an identifier of the second application according to the identifier of the target long connection;
the first service end is further configured to record that the target terminal is maintaining the target long connection, and add the identifier of the target long connection, the identifier of the target terminal, and the identifier of the second application to the corresponding relationship.
Optionally, the target terminal is further configured to send a long connection disconnection message to the first service end through the first application when detecting that the target long connection is disconnected, where the long connection disconnection message at least carries an identifier of the target long connection;
the first service end is further configured to record that the target terminal has stopped maintaining the target long connection.
Optionally, the application management message at least carries an identifier of the target long connection;
the target terminal is specifically configured to:
receiving, by the second application, the application management message;
and if the identification of the target long connection is consistent with the locally stored long connection identification associated with the first application, managing the first application based on the application management message.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, when the preset management condition of a first application installed on a target terminal is met, a first service end corresponding to the first application determines a target long connection currently maintained by the target terminal, the first service end sends an application management message for the first application to a second service end corresponding to the target long connection, the second service end sends the application management message to the target terminal through the target long connection, and the target terminal receives the application management message through a second application corresponding to the installed second service end and manages the first application based on the application management message. Therefore, when the server side of the first application needs to manage the first application in real time, the application management message can be transmitted through the long connection established between the target terminal and the second server side, and a new long connection does not need to be established with the target terminal.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a scenario framework of a management application according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for managing applications according to an embodiment of the present invention;
FIG. 3 is a flow chart of a process for a new growth connection according to an embodiment of the present invention;
fig. 4 is a flowchart of a process of long disconnection according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The embodiment of the invention provides a method for managing applications, which can be realized by a terminal and a plurality of service terminals together, wherein the terminal can be user equipment provided with a large number of applications, such as a smart phone, a tablet personal computer and the like, each service terminal can be a background service terminal corresponding to a certain application arranged on the terminal, and the terminal can establish long connection with the service terminals through a wireless network and transmit data and messages through the long connection. Each server can establish network connection with any other server and transmit data and messages through the network connection. The scene framework of the present embodiment may be as shown in fig. 1. The terminal and the server may each include a processor, a memory, and a transceiver, where the processor may be configured to perform processing of a management application in the following process, the memory may be configured to store data required and generated in the following process, and the transceiver may be configured to receive and transmit related data in the following process.
The process flow shown in fig. 2 will be described in detail below with reference to the specific embodiments, and the contents may be as follows:
In implementation, after a user installs a certain application on a terminal, a server corresponding to the application may perform real-time management on the application installed on the terminal, such as software update, status detection, and the like, for this, a technician at the server side may preset a trigger condition (i.e., a preset management condition) of the management operation according to a service requirement of each application, and configure the preset management condition in the server, where the preset management condition may be various, and may be detecting that the application installed on the terminal is started, or may reach a preset management time point, or may be allowing the technician at the server side to manually input a management instruction, and the like.
In this way, taking the first application as an example, when a preset management condition for the first application installed on the target terminal is met, the first service end corresponding to the first application may start to perform real-time management operation on the first application on the target terminal, and specifically, the first service end may first determine a target long connection currently maintained by the target terminal. Here, the first service end may also record a long connection being maintained by each terminal installed with the first application. It should be noted that, for the first applications on different terminals, the preset management conditions configured at the first service end may be the same or different.
In implementation, after determining the target long connection currently maintained by the target terminal, the first server may first determine a second server corresponding to the target long connection, and then may send an application management message for the first application to the second server.
Optionally, the first service end may store a corresponding relationship between the long connection identifier, the terminal identifier, and the application identifier, and further, the processing in step 202 may be as follows: the first server side determines a second application identifier corresponding to the target long connection identifier in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier; and the first server sends the application management message for the first application to a second server corresponding to the second application.
In implementation, the first service end may store a corresponding relationship between the long connection identifier, the terminal identifier, and the application identifier in advance, where the corresponding relationship records all terminals and applications corresponding to the long connection that have been determined by the first service end, and specifically refer to table 1:
TABLE 1
| Long connection mark | Terminal identification | Application identification |
| A1 | A | 1 |
| A2 | A | 2 |
| B2 | B | 2 |
| … | … | … |
In this way, after determining the target long connection currently maintained by the target terminal, the first server may determine, in the correspondence relationship between the locally stored long connection identifier, the terminal identifier, and the application identifier, the identifier of the second application corresponding to the identifier of the target long connection. The first server may then send an application management message for the first application to a second server corresponding to the second application.
And step 203, the second server sends the application management message to the target terminal through the target long connection.
In implementation, after the first server sends the application management message for the first application to the second server, the second server may receive the corresponding application management message. Then, the second server may perform operations such as data parsing and format conversion on the application management message, and convert the application management message into a data transmission format suitable for the second server. Meanwhile, the second server can also determine the target long connection established between the second server and the target terminal based on the target terminal pointed by the application management message. And further, the second server side can send the application management message to the target terminal through the target long connection.
And 204, the target terminal receives the application management message through a second application corresponding to the installed second server, and manages the first application based on the application management message.
In implementation, after the second server sends the application management message to the target terminal, the target terminal may receive the application management message through the second application corresponding to the installed second server. Then, the target terminal may analyze the application management message, and after determining that the application management message is an application management message of the first application by the first service end, the target terminal may manage the first application based on the application management message.
Optionally, the application management message at least carries an identifier of the target long connection, and accordingly, the processing in step 204 may specifically be as follows: the target terminal receives the application management message through a second application corresponding to the installed second server; and if the identification of the target long connection is consistent with the long connection identification associated with the first application stored locally, the target terminal manages the first application based on the application management message.
In implementation, after the target terminal establishes the target long connection with the second server, the target terminal may associate the identifier of the target long connection with the first application. In this way, after the target terminal receives the application management message sent by the second server through the installed second application, the target terminal can acquire the identifier of the target long connection carried in the application management message. Then, after determining that the application management message is an application management message of the first application, the target terminal may obtain a locally stored long connection identifier associated with the first application, and if the identifier of the target long connection matches the long connection identifier associated with the first application, the target terminal may manage the first application based on the application management message. It is easy to think that if the identifier of the target long connection is not consistent with the long connection identifier associated with the first application, the target terminal may feed back an authentication error message to the second server through the target long connection, and then the second server may forward the authentication error message to the first server.
In a specific embodiment of the present invention, the first application may be an SDK (Software Development Kit) component installed on the target terminal, the first service end is an SDK backend management system, the second application is a specific application installed on the target terminal, and the second service end is a backend management system of the second application. The second application may enable transmission of the management message by invoking the SDK interface.
Optionally, this embodiment further provides a processing flow of a newly-grown connection, as shown in fig. 3, the detailed content may be as follows:
In implementation, the target terminal may be pre-installed with a second application, and when a background server (i.e., a second server) of the second application needs to manage the second application on the target terminal in real time, the target terminal may establish a target long connection with the second server through the second application.
Wherein, the long connection newly added message at least carries the identification of the target long connection.
In implementation, after establishing a long target connection with a second server, a target terminal may send a long connection addition message to the first server through the first application, where the long connection addition message may carry an identifier of the long target connection.
In implementation, after receiving the long connection addition message sent by the target terminal, the first service end may determine the identifier of the target terminal and the identifier of the second application according to the identifier of the target long connection carried in the long connection addition message. It should be noted that when the terminal establishes the long connection with the server, the terminal generally creates the long connection identifier based on the terminal identifier and the application identifier, and therefore, the first server may infer the identifier of the target terminal and the identifier of the second application based on the identifier of the target long connection. In another case, of course, if the terminal identifier and the application identifier cannot be embodied in the long connection identifier, the identifier of the target terminal and the identifier of the second application may be added to the long connection addition message.
And step 304, the first service end records that the target terminal is maintaining the target long connection, and correspondingly adds the identifier of the target long connection, the identifier of the target terminal and the identifier of the second application into the corresponding relation.
In implementation, after the first server determines the identifier of the target terminal and the identifier of the second application, it may record that the target terminal is maintaining the target long connection. Meanwhile, the first server can also search whether a corresponding item of the target long connection identifier exists in the corresponding relationship among the locally stored long connection identifier, the terminal identifier and the application identifier, and if the corresponding item does not exist, the target long connection identifier, the target terminal identifier and the second application identifier can be correspondingly added to the corresponding relationship. If so, no processing may be performed.
Optionally, this embodiment further provides a processing flow of long disconnection, as shown in fig. 4, the detailed content may be as follows:
Wherein, the long connection disconnection message at least carries the identification of the target long connection.
In implementation, after the target terminal establishes the target long connection with the second server, if it is detected that the target long connection is disconnected, the target terminal may send a long connection disconnection message carrying an identifier of the target long connection to the first server through the first application, so as to notify the first server that the target long connection is unavailable.
In implementation, after receiving the long connection disconnection message sent by the target terminal, the first service end may record that the target terminal has stopped maintaining the target long connection.
It should be noted that, the first application and the second application may have a long connection multiplexing relationship in advance, that is, the long connection established between the first application and the first service end may be used to transmit the message between the second application and the second service end, and similarly, the long connection established between the second application and the second service end may also be used to transmit the message between the first application and the first service end. The long connection multiplexing relationship may be set after being agreed by technicians of the first service end and the second service end. Further, the long connection multiplexing relationship may be applicable to any number of applications, that is, as long as technicians at the background servers of the multiple applications agree without errors, the long connection multiplexing relationship may be established between the multiple applications at the same time. Therefore, in this embodiment, the related processing of the first application and the first server is also applicable to other applications and their background servers that have a long connection multiplexing relationship with the second application.
In addition, in step 201, if the first server determines that the target terminal currently maintains a plurality of long connections, as in table 1, the target terminal a simultaneously maintains two long connections, i.e., a1 and a2, the first server may determine one target long connection from the plurality of long connections according to a preset selection rule by a technician. The preset selection rules are various, and may be selection of the long connection with the highest link communication quality, selection of the corresponding long connection with the lowest server load, random selection, and the like.
In the embodiment of the invention, when the preset management condition of a first application installed on a target terminal is met, a first service end corresponding to the first application determines a target long connection currently maintained by the target terminal, the first service end sends an application management message for the first application to a second service end corresponding to the target long connection, the second service end sends the application management message to the target terminal through the target long connection, and the target terminal receives the application management message through a second application corresponding to the installed second service end and manages the first application based on the application management message. Therefore, when the server side of the first application needs to manage the first application in real time, the application management message can be transmitted through the long connection established between the target terminal and the second server side, and a new long connection does not need to be established with the target terminal, so that the occupancy rate of the terminal processing resources during application management can be reduced.
Based on the same technical concept, an embodiment of the present invention further provides a system for managing applications, where the system includes a target terminal, a first service end and a second service end, the target terminal is installed with a first application and a second application, the first service end is a background service end of the first application, and the second service end is a background service end of the second application, where:
the first server is used for determining the target long connection currently maintained by the target terminal when the preset management condition for the first application is met;
the first service end is further configured to send an application management message for the first application to a second service end corresponding to the target long connection;
the second server is used for sending the application management message to the target terminal through the target long connection;
the target terminal is used for receiving the application management message through the second application and managing the first application based on the application management message.
Optionally, the first service end is specifically configured to:
determining the identifier of a second application corresponding to the identifier of the target long connection in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier;
and sending an application management message for the first application to a second server corresponding to the second application.
Optionally, the target terminal is further configured to establish the target long connection with the second server through the second application;
the target terminal is further configured to send a long connection newly-added message to the first service end through the first application, where the long connection newly-added message at least carries an identifier of the target long connection;
the first service end is further configured to determine an identifier of the target terminal and an identifier of the second application according to the identifier of the target long connection;
the first service end is further configured to record that the target terminal is maintaining the target long connection, and add the identifier of the target long connection, the identifier of the target terminal, and the identifier of the second application to the corresponding relationship.
Optionally, the target terminal is further configured to send a long connection disconnection message to the first service end through the first application when detecting that the target long connection is disconnected, where the long connection disconnection message at least carries an identifier of the target long connection;
the first service end is further configured to record that the target terminal has stopped maintaining the target long connection.
Optionally, the application management message at least carries an identifier of the target long connection;
the target terminal is specifically configured to:
receiving, by the second application, the application management message;
and if the identification of the target long connection is consistent with the locally stored long connection identification associated with the first application, managing the first application based on the application management message.
In the embodiment of the invention, when the preset management condition of a first application installed on a target terminal is met, a first service end corresponding to the first application determines a target long connection currently maintained by the target terminal, the first service end sends an application management message for the first application to a second service end corresponding to the target long connection, the second service end sends the application management message to the target terminal through the target long connection, and the target terminal receives the application management message through a second application corresponding to the installed second service end and manages the first application based on the application management message. Therefore, when the server side of the first application needs to manage the first application in real time, the application management message can be transmitted through the long connection established between the target terminal and the second server side, and a new long connection does not need to be established with the target terminal, so that the occupancy rate of the terminal processing resources during application management can be reduced.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A method of managing applications, the method comprising:
when a preset management condition for a first application installed on a target terminal is met, a first server corresponding to the first application determines a target long connection from currently maintained long connections of the target terminal according to a preset selection rule;
the first server sends an application management message for the first application to a second server corresponding to the target long connection;
the second server sends the application management message to the target terminal through the target long connection;
the target terminal receives the application management message through a second application corresponding to the installed second server, and manages the first application based on the application management message;
the second service end manages the second application in the target terminal, and the first service end manages the first application in the target terminal.
2. The method of claim 1, wherein sending, by the first server, an application management message for the first application to a second server corresponding to the target long connection comprises:
the first server side determines the identifier of a second application corresponding to the identifier of the target long connection in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier;
and the first server sends the application management message of the first application to a second server corresponding to the second application.
3. The method of claim 2, further comprising:
the target terminal establishes the target long connection with the second server through the second application;
the target terminal sends a long connection newly-added message to the first service terminal through the first application, wherein the long connection newly-added message at least carries an identifier of the target long connection;
the first server determines the identifier of the target terminal and the identifier of the second application according to the identifier of the target long connection;
and the first service end records that the target terminal is maintaining the target long connection, and correspondingly adds the identification of the target long connection, the identification of the target terminal and the identification of the second application into the corresponding relationship.
4. The method of claim 2, further comprising:
when the target long connection is detected to be disconnected, the target terminal sends a long connection disconnection message to the first service terminal through the first application, wherein the long connection disconnection message at least carries an identifier of the target long connection;
and the first service end records that the target terminal stops maintaining the target long connection.
5. The method according to claim 1, wherein the application management message carries at least an identifier of the target long connection;
the target terminal receives the application management message through a second application corresponding to the installed second server, and manages the first application based on the application management message, including:
the target terminal receives the application management message through a second application corresponding to the installed second server;
and if the identification of the target long connection is consistent with the locally stored long connection identification associated with the first application, the target terminal manages the first application based on the application management message.
6. The system for managing the application is characterized by comprising a target terminal, a first service end and a second service end, wherein the target terminal is provided with a first application and a second application, the first service end is a background service end of the first application, and the second service end is a background service end of the second application, wherein:
the first server is used for determining a target long connection from the currently maintained long connections of the target terminal according to a preset selection rule when a preset management condition for the first application is met;
the first service end is further configured to send an application management message for the first application to a second service end corresponding to the target long connection;
the second server is used for sending the application management message to the target terminal through the target long connection;
the target terminal is used for receiving the application management message through the second application and managing the first application based on the application management message.
7. The system of claim 6, wherein the first service end is specifically configured to:
determining the identifier of a second application corresponding to the identifier of the target long connection in the corresponding relation among the locally stored long connection identifier, the terminal identifier and the application identifier;
and sending an application management message for the first application to a second server corresponding to the second application.
8. The system of claim 7, wherein the target terminal is further configured to establish the target long connection with the second server through the second application;
the target terminal is further configured to send a long connection newly-added message to the first service end through the first application, where the long connection newly-added message at least carries an identifier of the target long connection;
the first service end is further configured to determine an identifier of the target terminal and an identifier of the second application according to the identifier of the target long connection;
the first service end is further configured to record that the target terminal is maintaining the target long connection, and add the identifier of the target long connection, the identifier of the target terminal, and the identifier of the second application to the corresponding relationship.
9. The system according to claim 7, wherein the target terminal is further configured to send a long connection disconnection message to the first service end through the first application when detecting that the target long connection is disconnected, where the long connection disconnection message carries at least an identifier of the target long connection;
the first service end is further configured to record that the target terminal has stopped maintaining the target long connection.
10. The system according to claim 6, wherein said application management message carries at least an identifier of said target long connection;
the target terminal is specifically configured to:
receiving, by the second application, the application management message;
and if the identification of the target long connection is consistent with the locally stored long connection identification associated with the first application, managing the first application based on the application management message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711362535.3A CN108173910B (en) | 2017-12-18 | 2017-12-18 | Method and system for managing application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711362535.3A CN108173910B (en) | 2017-12-18 | 2017-12-18 | Method and system for managing application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108173910A CN108173910A (en) | 2018-06-15 |
| CN108173910B true CN108173910B (en) | 2021-06-22 |
Family
ID=62522170
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711362535.3A Expired - Fee Related CN108173910B (en) | 2017-12-18 | 2017-12-18 | Method and system for managing application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108173910B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487847A (en) * | 2015-08-28 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of information processing method and transfer server |
| CN107256170A (en) * | 2017-06-16 | 2017-10-17 | 北京百度网讯科技有限公司 | Method and apparatus for the activation input method setting option of terminal device |
| CN107332880A (en) * | 2017-06-05 | 2017-11-07 | 深圳市酷开网络科技有限公司 | Method, device and computer-readable recording medium that information is pushed |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102291808B (en) * | 2011-06-03 | 2013-12-04 | 莫雅静 | Network communication method, communication equipment and middleware of communication equipment |
| CN105337961B (en) * | 2012-11-02 | 2018-09-04 | 北京奇虎科技有限公司 | The method and server communicated with client |
| CN103916442A (en) * | 2013-01-07 | 2014-07-09 | 阿里巴巴集团控股有限公司 | Message pushing achieving method, mobile terminal and message pushing system |
| CN103973737A (en) * | 2013-01-30 | 2014-08-06 | 腾讯科技（深圳）有限公司 | Method, server and browser for actively pushing messages |
| CN104113564A (en) * | 2013-04-17 | 2014-10-22 | 中国移动通信集团公司 | Hyper text transfer protocol connection multiplexing method, device, system, and terminal |
| CN104993980B (en) * | 2015-08-11 | 2018-01-16 | 上海斐讯数据通信技术有限公司 | A kind of security control method and system of long connection application access |
| CN107484232A (en) * | 2017-08-21 | 2017-12-15 | 奇酷互联网络科技（深圳）有限公司 | Message method, system, the network equipment and readable storage medium storing program for executing |
-
2017
- 2017-12-18 CN CN201711362535.3A patent/CN108173910B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487847A (en) * | 2015-08-28 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of information processing method and transfer server |
| CN107332880A (en) * | 2017-06-05 | 2017-11-07 | 深圳市酷开网络科技有限公司 | Method, device and computer-readable recording medium that information is pushed |
| CN107256170A (en) * | 2017-06-16 | 2017-10-17 | 北京百度网讯科技有限公司 | Method and apparatus for the activation input method setting option of terminal device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108173910A (en) | 2018-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109347934B (en) | Message pushing method and system, server, storage medium and electronic device | |
| CN110808948B (en) | Remote procedure calling method, device and system | |
| CN108881354B (en) | Push information storage method and device, server and computer storage medium | |
| US20160285754A1 (en) | Packet Processing Method, Device and System | |
| US8738770B2 (en) | Sending synchronous responses to requests from frontend applications | |
| CN103890808A (en) | Method for operating interactive messaging service providing reception confirmation | |
| CN106210049B (en) | Cluster communication method and system based on message queue | |
| CN103547342A (en) | Information sending method, information reading and notifying method, information receiving method and device | |
| CN113391979A (en) | Processing method, equipment and system for monitoring data display and storage medium | |
| CN110912805B (en) | Message reading state synchronization method, terminal, server and system | |
| CN111431790A (en) | Instant messaging method, device, system and storage medium | |
| CN111884875A (en) | Offline device determination method and device | |
| CN109348434A (en) | A kind of sending method of scene information, sending device and terminal device | |
| CN106411713B (en) | State notification method and server | |
| CN106302093B (en) | Communication method, system and server | |
| CN105281940B (en) | Method, equipment and system for HELLO message interaction based on NETCONF protocol | |
| CN108173910B (en) | Method and system for managing application | |
| CN105634931A (en) | Messaging service processing method and instant messaging server | |
| CN102986173B (en) | Method for setting message status and converged internet protocol message (CPM) traffic server | |
| CN115567388A (en) | Method, system, device and storage medium for automatically updating network slice configuration | |
| CN109981796B (en) | Connection method and device | |
| CN109962962B (en) | Socket connection method and device | |
| CN112422305B (en) | Upgrading method and device of communication equipment | |
| CN114095759B (en) | Stream media redirection method and related device | |
| CN112055098B (en) | Method for establishing long IP data connection, 5G gateway equipment and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210622 |