WO2013185642A1 - 用于处理应用代理客户端异常的方法和装置 - Google Patents
用于处理应用代理客户端异常的方法和装置 Download PDFInfo
- Publication number
- WO2013185642A1 WO2013185642A1 PCT/CN2013/077307 CN2013077307W WO2013185642A1 WO 2013185642 A1 WO2013185642 A1 WO 2013185642A1 CN 2013077307 W CN2013077307 W CN 2013077307W WO 2013185642 A1 WO2013185642 A1 WO 2013185642A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- application
- server
- proxy
- proxy server
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 101
- 238000012545 processing Methods 0.000 title claims abstract description 18
- 230000005856 abnormality Effects 0.000 title description 2
- 230000004044 response Effects 0.000 claims description 47
- 238000004891 communication Methods 0.000 claims description 19
- 230000015654 memory Effects 0.000 claims description 13
- 230000002618 waking effect Effects 0.000 claims description 10
- 230000001960 triggered effect Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 30
- 230000002159 abnormal effect Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 15
- 230000011664 signaling Effects 0.000 description 5
- 238000001994 activation Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000002372 labelling Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000007420 reactivation Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- 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/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/564—Enhancement of application control based on intercepted application data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/668—Internet protocol [IP] address subnets
Definitions
- the present invention relates to a wireless communication system, and more particularly to a method and apparatus for processing an abnormality of an application proxy client on a terminal. Background technique
- IP Internet Protocol
- the packet data protocol (PDP, Packet Data Protocol) connection of the mobile terminal releases the PDP connection when there is no data transmission for a period of time; however, when there is data transmission, the PDP connection needs to be reestablished. In this way, a large number of terminals continuously perform PDP connection establishment in order to transmit the above heartbeat signaling. The process of release, therefore, creates so-called signaling storms that severely consume wireless communication resources of the mobile communication network.
- PDP Packet Data Protocol
- a push (Push) solution to solve the problem of signaling storms.
- a specific proxy server on the network side such as an AOI (Always Online Infrastructure) server or a Push server
- AOI middleware or a Push client By setting up a specific application proxy client on the terminal, such as an AOI middleware or a Push client, on the terminal. Maintaining the connection between the application proxy client and the proxy server on the network side, and maintaining the connection between the proxy server and the application server, instead of the application client such as IM, Email, SNS, etc.
- the IP connection enables the application client and the associated application server to communicate information through the connection between the application proxy client and the proxy server, so that the application client on the terminal and the associated application server do not It is necessary to maintain the IP connection and thus no longer need to continuously transmit the heartbeat signaling, thereby avoiding the continuous connection establishment and release process of the terminal PDP connection, thereby reducing the network burden.
- the application proxy client on the terminal may have some abnormal conditions during use. For example, the user may uninstall the application proxy client from the mobile phone, and the application proxy client and the proxy server cannot be established due to long-time shutdown or out of the service area. The connection between, and so on.
- an AOI middleware is taken as an example of an application proxy client
- an AOI server is used as an example of an application server.
- the specific implementation of the application proxy client and application server is not limited to AOI middleware and AOI servers.
- the detection methods for abnormal conditions such as terminal uninstallation of AOI middleware are as follows:
- the AOI server detects that the terminal connection is abnormal, and sends a wake-up message to the terminal;
- the terminal After the terminal elapses time T1, it is not connected to the AOI server, and the AOI server re-sends the wake-up message to the terminal;
- the AOI server has re-sent the wake-up message N1 times to the terminal, and the terminal is not connected to the AOI server; the AOI server adjusts the state of the terminal to be offline. In this state, if an application server wishes to push a service message to the terminal through the AOI server, The AOI server returns a push failure message to the application server, and the failure reason is that the terminal is offline.
- the terminal After the time T2, the terminal is still not connected to the AOI server.
- the AOI server determines that the user may have uninstalled the middleware and adjusts its status to the middleware has been uninstalled. In this state, if an application service wants to push the service message to the terminal through the AOI server. The AOI server returns a push failure message to the application server. The reason for the failure is that the middleware has been uninstalled, and the application server receives such a failure reason, You should try to push business messages to this user again.
- the AOI server can only judge whether the terminal has been deleted according to a specific operation.
- the AOI middleware causes the AOI server to not know the reachability status of the terminal in time, which in turn affects the service quality of the application server.
- the terminal cannot know the following information: The AOI server has been deleted on the terminal.
- AOI middleware terminal related information has been deleted on the AOI server, and which application servers have considered to delete AOI middleware on the terminal.
- the above information can further improve the processing efficiency between the terminal, the AOI server and the application server, save network resources, and improve the service quality of the related application client on the terminal. Therefore, there is a need in the art to further improve the method of handling AOI middleware anomalies. Summary of the invention
- the embodiment of the present invention provides an improved method for processing an application proxy client exception on the terminal side and the network side, thereby further improving processing efficiency between the terminal, the AOI server, and the application server, saving network resources, and improving the application client and the application.
- an embodiment of the present invention provides a processing method for an application proxy client, where the method includes: determining, on the terminal, that the application proxy client is uninstalled; from the terminal to the application proxy client The corresponding proxy server sends an uninstallation indication message indicating that the application proxy client has been uninstalled on the terminal.
- an embodiment of the present invention provides a method for learning that an application proxy client has been uninstalled on a terminal, the method comprising: receiving an uninstall indication message from the terminal on a proxy server, where the uninstall indication message indicates The application proxy client is uninstalled on the terminal; the status of the terminal is marked on the proxy server according to the uninstall indication message as the application proxy client has been uninstalled on the terminal.
- an embodiment of the present invention provides a method for waking up a terminal, where the method includes: sending a wakeup message from a proxy server to a terminal; and determining, on the proxy server, whether the terminal receives the wakeup message; When it is determined that the terminal does not receive the wake-up message, the status of the terminal is marked as unreachable on the proxy server; when it is determined that the terminal receives the wake-up message, Determining, by the proxy server, an uninstallation indication message sent by the terminal, where the uninstallation indication message includes an indication that the application proxy client has been uninstalled on the terminal; and determining to receive the uninstallation sent by the terminal When the message is indicated, the end will be on the proxy server The status of the end is indicated as the application proxy client has been uninstalled on the terminal.
- an embodiment of the present invention provides a method for waking up a terminal, the method comprising: receiving a wakeup message from a proxy server on the terminal; determining, on the terminal, whether the terminal has uninstalled the Applying a proxy client; if it is determined that the application proxy client has been uninstalled on the terminal, sending an uninstallation indication message from the terminal to the proxy server, the message indicating that the application proxy has been uninstalled on the terminal Client.
- an embodiment of the present invention provides a method for terminal re-registration, the method comprising: receiving a registration request from the terminal on a proxy server; and determining, according to the identifier of the terminal included in the registration request, (ID) determining whether the information of the terminal is stored on the proxy server; if it is determined that the information of the terminal is stored on the proxy server, determining that the proxy service is determined to be in the proxy
- the server has marked the status of the terminal as having uninstalled the application proxy client on the terminal, and sends a registration response from the proxy server to the terminal, the registration response including an uninstall indication and an application server list, where
- the uninstall indication is used to indicate that the status of the terminal has been marked on the proxy server as an application proxy client has been uninstalled on the terminal, and the application server in the list has been notified by the proxy server.
- the application server of the application proxy client is uninstalled on the terminal.
- an embodiment of the present invention provides a method for terminal re-registration, the method comprising: sending a registration request from the terminal to a proxy server; receiving, by the terminal, the registration from the proxy server a registration response of the request, the registration response including an uninstallation indication and an application server list, wherein the uninstallation indication is used to indicate that the status of the terminal has been marked on the proxy server as an application proxy client has been uninstalled on the terminal End, the application server in the list is an application server that has been notified by the proxy server that the application proxy client has been uninstalled on the terminal; triggering an application client associated with the application server in the list on the terminal The end registers with the corresponding application server in the list.
- an embodiment of the present invention provides a processing apparatus for an application proxy client, where the apparatus includes: a determining unit, configured to determine, on the terminal, that the application proxy client is uninstalled; and a sending unit, configured to The terminal sends an uninstallation indication message to a proxy server corresponding to the application proxy client, where the uninstallation indication message indicates that the application proxy client has been uninstalled on the terminal.
- an embodiment of the present invention provides an application agent for knowing that an application agent has been uninstalled on the terminal.
- a device of the client comprising: a receiving unit, configured to receive, on the proxy server, an uninstallation indication message from the terminal, the uninstallation indication message indicating that the application proxy client has been uninstalled on the terminal;
- the device according to the present invention provides an apparatus for waking up a terminal, and the apparatus includes: a sending unit, configured to use the proxy server to the terminal Sending a wake-up message; a determining unit, configured to determine, on the proxy server, whether the terminal receives the wake-up message; and a marking unit, configured to: when it is determined that the terminal does not receive the wake-up message, in the And indicating, by the proxy server, that the terminal is unreachable; wherein, when it is determined that the terminal receives the wakeup message, the determining unit determines whether the uninstallation indication message sent by the terminal is received,
- the uninstallation indication message includes an indication that the application proxy client has
- an embodiment of the present invention provides an apparatus for waking up a terminal, where the apparatus includes: a receiving unit, configured to receive a wakeup message from a proxy server on the terminal; and a determining unit, configured to be used on the terminal Determining whether the application proxy client has been uninstalled on the terminal; and sending, if it is determined that the application proxy client has been uninstalled on the terminal, sending an uninstall indication from the terminal to the proxy server A message indicating that the application proxy client has been uninstalled on the terminal.
- an embodiment of the present invention provides an apparatus for performing terminal re-registration, where the apparatus includes: a receiving unit, configured to receive a registration request from the terminal on a proxy server; Determining, by the identifier (ID) of the terminal included in the registration request, whether information of the terminal is stored on the proxy server, and if it is determined that the information of the terminal is saved on the proxy server, determining Whether the status of the terminal has been marked as being uninstalled by the application proxy client on the terminal, and the sending unit is configured to determine, at the determining unit, that the terminal has been a status indicating that when the application proxy client is uninstalled on the terminal, a registration response is sent from the proxy server to the terminal, the registration response including an uninstall indication and an application server list, wherein the uninstall indication is used to indicate The status of the terminal has been marked on the proxy server as an application proxy client has been uninstalled on the terminal The list of application servers that have been notified of the proxy server has been uninstalled on the passenger terminal
- an embodiment of the present invention provides an apparatus for performing terminal re-registration, where the apparatus includes: a registration unit, configured to send a registration request from the terminal to a proxy server; and a receiving unit, configured to be at the terminal Receiving a registration response from the proxy server, the registration response including an uninstall indication and an application server list, wherein the uninstall indication is used to indicate that the status of the terminal has been marked as being on the terminal on the proxy server
- the application proxy client has been uninstalled, and the application server in the list is notified by the proxy server that the application client associated with the application proxy client application server has been uninstalled on the terminal to the corresponding application in the list.
- the server is registered.
- an embodiment of the present invention provides a wireless communication device, including: a memory, configured to store data and instructions; a processor coupled to the memory, configured to use the data and instructions in the memory The operation is such that the wireless communication device is capable of performing the above method of the present invention.
- embodiments of the present invention provide a machine readable medium storing instructions that, when executed by a machine, enable the machine to perform the above method of the present invention.
- embodiments of the present invention provide a computer program for performing the above method of the present invention.
- FIG. 1 is a schematic diagram of a reactivation process of an AOI middleware in the prior art.
- FIG. 2 is a schematic diagram of an initial activation flow of an AOI middleware in the prior art.
- 3A through 3C are diagrams showing an exemplary processing flow when an AOI middleware is uninstalled on a terminal according to an embodiment of the present invention.
- FIG. 4A is a schematic diagram of an exemplary processing flow when an AOI middleware is uninstalled on a terminal in accordance with an embodiment of the present invention.
- 4B is a schematic diagram of an exemplary process flow for learning to offload AOI middleware on a terminal, in accordance with an embodiment of the present invention.
- 5A and 5B are diagrams showing an exemplary process flow on a terminal and an AOI server in the process of waking up a terminal by an AOI server, in accordance with an embodiment of the present invention.
- FIGS. 6A and 6B are diagrams showing an exemplary processing flow on an AOI server and a terminal in a process in which a terminal initiates a re-registration request to an AOI server, according to an embodiment of the present invention.
- FIG. 7 is a schematic block diagram of a terminal in accordance with an embodiment of the present invention.
- Figure 8 is a schematic block diagram of an AOI server in accordance with an embodiment of the present invention.
- FIG. 9 is a schematic diagram illustrating an exemplary communication device to which embodiments of the present invention may be applied.
- the AOI middleware is used as an example of an application proxy client
- the AOI server is used as an example of an application server.
- the specific implementation of the application proxy client and the proxy server is not limited to the AOI middleware and the AOI server.
- the application proxy client may be an AOI middleware or a Push client
- the proxy server may be an AOI server or The Push server, regardless of the specific name, should be considered as being within the scope of the present invention as long as it conforms to the embodiments of the present invention.
- Figure 1 shows the reactivation process of the AOI middleware on the terminal in the prior art.
- the activation process is performed, for example, in the following scenario:
- the terminal has previously established a connection with the AOI server and
- the middleware on the terminal is not unloaded, and the AOI middleware on the terminal or terminal sends a re-registration request to the AOI server when, for example, the terminal is powered off or no signal is turned on or re-launched for a period of time.
- step S110 the terminal 110 sends a registration request to the AOI server 120, which carries the application identifier (ID, identification) of all application clients associated with the AOI client on the terminal 110.
- the application client associated with the AOI client is an application client that implements communication with the corresponding application server 130 through the AOI client and the AOI server 120, such as IM, Email, SNS, and the like.
- the AOI server 120 modifies the user status to normal and returns a response message to the terminal 110.
- the AOI server 120 if there is a new application in the terminal 110, the AOI server 120 generates a token for the new application, and returns the newly generated token to the terminal 110 in the response message.
- step S130 all related application clients on the terminal 110 initiate a login request to the application server 130 for which the service is provided, and carry the token assigned to the AOI server 120 to the user in the login request, and the application server 130 modifies the user status of the terminal as normal.
- the application server 130 can learn to communicate with the terminal 110 via the AOI server 120 based on the token in the login request. For example, the application server 130 sends the message to the AOI server 120 and is sent by the AOI server 120 to the corresponding terminal 110.
- Figure 2 shows the initial activation flow of AOI middleware on the terminal in the prior art.
- the activation process is performed, for example, in the following scenario: The terminal first installs the AOI middleware, or reinstalls the AOI middleware before uninstalling the previously installed AOI middleware on the terminal. At this time, the terminal does not have the AOI server. Establish information about the connection.
- step S210 the terminal 210 registers a short message with an AOI Domain Name System (DNS), which includes an international mobile user of a Subscriber Identity Module (SIM) associated with the terminal 210.
- DNS AOI Domain Name System
- IMSI International Mobile Subscriber Identification Number
- MSISDN Mobile Subscriber International ISDN/PSTN number
- step S220 the terminal 210 sends a registration request to the AOI DNS 240, which includes the IMSI digest of the terminal 210.
- step S230 the AOI DNS 240 returns a registration response to the terminal 210, which carries the response message.
- AOI server address information with terminal 210.
- step S240 the terminal 210 initiates a registration request to the AOI server 220, where the request message includes an IMSI digest of the terminal 210 and an application ID of the application client to be registered by the terminal.
- step S250 if the AOI server 220 finds that there is no end user information corresponding to the IMSI digest locally, it sends a request message for acquiring the terminal identity information to the AOI DNS 240, where the message includes the IMSI digest of the terminal 210.
- step S260 the AOI DNS 240 returns a response message for acquiring the terminal identity information to the AOI server 220, the response message including the MSISDN number corresponding to the IMSI digest of the terminal 210.
- step S270 the AOI server 220 authenticates the user of the terminal 210, and generates a token for the related application on the terminal 210, and then returns a registration response to the terminal 210, where the response message carries the application client allocated on the terminal 210. Token.
- step S280 all related application clients on the terminal 210 respectively initiate a login request to the application server 230 for which the service is provided, and carry the token assigned to the AOI server 220 to the user in the login request, and the application server 230 modifies the user status to be normal. And then send information to the terminal via the AOI server 220.
- 3A through 3C are diagrams showing an exemplary processing flow when an AOI middleware is uninstalled on a terminal according to an embodiment of the present invention.
- FIG. 3A illustrates a method for offloading AOI middleware on a terminal, such as terminal 110 or 210 of Figures 1 and 2, in accordance with one embodiment of the present invention.
- step S3A10 it is determined on the terminal that the AOI middleware is unloaded.
- the unloading operation on the AOI middleware may be performed, for example, on the terminal in accordance with an unloading instruction input by the user.
- the offloading of the AOI middleware can be determined by detecting an unload instruction for the AOI middleware.
- the offloading of AOI middleware can be determined by monitoring the processes of the terminal operating system associated with the unloading operation.
- the operating system used by the terminal such as a smartphone
- the specific manner for determining the uninstallation of the AOI middleware may be different, and the scope of the present invention is not limited by the specific manner.
- a determination can be made as to whether the AOI middleware is unloaded after receiving a wakeup message from the AOI server on the terminal. For example, after receiving the wake-up message on the terminal, it can be determined whether the AOI middleware is installed on the terminal, and when not installed, it is determined that the AOI middleware has been uninstalled on the terminal.
- step 3A20 when the AOI middleware is uninstalled on the terminal, it is judged whether the terminal currently has an IP bearer available for connection to the AOI server. If it is determined in step 3A20 that the terminal currently has an IP bearer, proceed to step S3A50, and the slave terminal transmits an uninstallation indication message to the AOI server through the IP bearer, the uninstall indication message indicating that the AOI middleware has been uninstalled on the terminal.
- the uninstall indication message may specifically be a notification message, an indication message, or the like.
- the uninstall indication message here does not specifically represent the name of a message, but represents that the role of the message is to inform the AOI server terminal that the AOI middleware has been uninstalled.
- the AOI server can know the reachable state of the terminal in time, without having to be based on the existing method.
- the specific operation of the AOI server on the network side determines whether the terminal has deleted the middleware, thereby simplifying the operation on the network side and alleviating the AOI server in the process of constantly trying to wake up the terminal that has deleted the AOI middleware.
- the resource consumption comes.
- the AOI server can improve the service quality of the application server in time by accurately knowing the status of the AOI middleware that the terminal has uninstalled.
- the AOI server can notify the AOI server in time.
- the application server has deleted the AOI middleware, so that the application server does not continue to send data to the AOI server to the terminal.
- step S3A30 save (for example, temporarily save) the indication information that the terminal has uninstalled the AOI middleware on the terminal, and then proceed to step S3A40 to determine whether the terminal has an IP bearer. For example, it may be periodically determined whether the terminal has an IP bearer.
- step S3 A40 the slave terminal transmits an uninstall indication message to the AOI server through the IP bearer.
- step S3A60 when the terminal has an IP bearer, one or more application clients associated with the AOI middleware are triggered on the terminal to initiate re-registration to one or more application servers serving the application client through the IP bearer.
- the registration request initiated to the application server may be referred to as an application registration request.
- the Token information assigned by the AOI server to the application client is not carried in the re-registration request.
- Each application server can learn that the AOI server does not communicate with the terminal according to the fact that the Token is not carried in the re-registration request.
- FIG. 3B illustrates a method for offloading AOI middleware on a terminal, such as terminal 110 or 210 of FIGS. 1 and 2, in accordance with another embodiment of the present invention.
- Steps S3B10, S3B20, S3B50, and S3B60 in this embodiment are the same as steps S3A10, S3A20, S3A50, and S3A60 of FIG. 3A, and therefore will not be described in detail.
- step S3B10 it is determined on the terminal that the AOI middleware is unloaded.
- step 3B20 it is judged whether the terminal has an IP bearer when the AOI middleware is uninstalled on the terminal. If it is determined in step 3B20 that the terminal currently has an IP bearer, proceed to step S3B50, and the terminal transmits an uninstall indication message to the AOI server through the IP bearer, the uninstall indication message indicating that the AOI middleware has been uninstalled on the terminal. Then, proceeding from step S3B50 to step S3B60, one or more application clients associated with the AOI middleware are triggered on the terminal to initiate a re-registration request or a registration request to the corresponding one or more application servers through the IP bearer. The Token information assigned by the AOI server to the application client is not carried in the re-registration request.
- step 3B20 If it is determined in step 3B20 that the terminal does not currently have an IP bearer, it proceeds to step S3B30, and the slave terminal transmits an uninstall indication message to the AOI server through the short message service (SMS).
- SMS short message service
- the AOI server may send a notification message to each application server serving the terminal, the notification message including an indication that the AOI middleware has been uninstalled on the terminal.
- the terminal can notify the AOI server of the uninstallation situation in time when the AOI middleware is uninstalled without the IP bearer, so that the AOI server can compare with the AOI server.
- SMS short message service
- the 3A knows the reachable state of the terminal in a more timely manner, thereby more effectively avoiding the situation in which the terminal determines whether the terminal has deleted the middleware according to the specific operation of the AOI server on the network side.
- the AOI server receives the uninstallation indication message sent by the terminal through the SMS, the AOI server notifies the application server of the uninstallation indication, so that the application server knows the status of the AOI middleware that the terminal has uninstalled in time. Send information to the AOI server to improve network side operations.
- step S3B40 it is determined whether the terminal has an IP bearer.
- the process proceeds to step S3B60, and the application clients associated with the AOI middleware are triggered on the terminal to pass the IP bearer direction.
- Each application server that provides the service initiates a re-registration request or a registration request.
- the Token information assigned by the AOI server to the application client is not carried in the re-registration request.
- 3C illustrates a method for offloading AOI middleware on a terminal in accordance with another embodiment of the present invention.
- the terminal is, for example, terminals 110 and 210 in Figures 1 and 2.
- Steps S3C10, S3C20, S3C50, and S3C60 in this embodiment are the same as steps S3A10, S3A20, S3A50, and S3A60 of FIG. 3A, and therefore will not be described in detail.
- step S3C10 it is determined on the terminal that the AOI middleware is unloaded.
- step 3C20 it is judged whether the terminal has an IP bearer when the AOI middleware is uninstalled on the terminal. If it is determined in step 3C20 that the terminal currently has an IP bearer, proceed to step S3C50, and the terminal sends an uninstall indication message to the AOI server through the IP bearer, the uninstall indication message indicating that the AOI middleware has been uninstalled on the terminal. Then, proceeding from step S3C50 to step S3C60, one or more application clients associated with the AOI middleware are triggered on the terminal to initiate a re-registration request or a registration request to the corresponding one or more application servers through the IP bearer. The Token information assigned by the AOI server to the application client is not carried in the re-registration request.
- step 3C20 If it is determined in step 3C20 that the terminal does not currently have an IP bearer, proceed to step S3C30, and send, on the terminal, uninstall indication information to each application client associated with the AOI middleware, where the uninstall indication information is included in the middle of the AOI that has been uninstalled on the terminal. Instructions for the pieces.
- step S3C40 it is determined whether the terminal has an IP bearer.
- each application client associated with the AOI middleware passes the IP bearer direction.
- Each application server that provides the service initiates a re-registration request or a registration request.
- the Token information assigned by the AOI server to the application client is not carried in the re-registration request.
- FIGS. 4A illustrates a method for offloading AOI middleware on a terminal, such as terminal 110 or 210 of FIGS. 1 and 2, in accordance with one embodiment of the present invention.
- step S4A10 it is determined on the terminal that the application proxy client is uninstalled.
- the application proxy client is, for example, the AOI middleware or Push client described above.
- the unloading operation may be performed, for example, on the terminal in accordance with an unloading instruction input by the user.
- step S4A20 the slave terminal sends an uninstallation indication message to the proxy server corresponding to the application proxy client, the message indicating that the application proxy client has been uninstalled on the terminal.
- the terminal is notified to the proxy server that the terminal has uninstalled the application proxy client, so that the proxy server can know the reachable state of the terminal in time without having to be as in the existing method.
- it is judged whether the terminal has deleted the application proxy client, thereby simplifying the operation on the network side and reducing the constantity of the proxy server. Attempting to wake up the resource consumption caused by the process of deleting the terminal of the application proxy client.
- the proxy server can improve the service quality of the application server in time by accurately knowing the status of the application agent client that is uninstalled by the terminal, for example, when an application server sends data to the terminal to the proxy server, the proxy server can notify the agent in time.
- the application server has deleted the application proxy client, so that the application server no longer sends data to the proxy server to the terminal.
- step S4A30 when the terminal has an IP bearer, one or more application clients associated with the application proxy client are triggered to initiate a registration request or a re-registration request to the corresponding one or more application servers through the IP bearer.
- the Token information assigned by the proxy server to the application client is not carried in the registration request.
- Each application server can learn that the token does not carry the Token according to the registration request.
- the AOI middleware is uninstalled in the step S4A30, the related application client is triggered to perform the registration process or the re-registration process with the application server, so that the connection between the application client and the corresponding application server can be established in time to improve the user experience. And enabling the application server to know in time that the terminal has deleted the application proxy client, and no longer sends information to the proxy server, improving the operation on the network side.
- Figure 4B illustrates a method for learning that an application proxy client has been uninstalled on a terminal in accordance with one embodiment of the present invention.
- an uninstallation indication message is received from the terminal on the proxy server, indicating that the application proxy client has been uninstalled on the terminal.
- the proxy server is, for example, the AOI server 120 or 220 of Figures 1 and 2, or the proxy server is a Push server, such as the terminal 110 or 210 of Figures 1 and 2, such as an AOI middleware or Push client.
- the status of the terminal is indicated on the proxy server as the application proxy client has been uninstalled on the terminal.
- the proxy server can know the reachable state of the terminal in time, without having to judge whether the terminal has deleted the application proxy client according to the specific operation of the proxy server on the network side as in the existing method. , which simplifies the operation on the network side and alleviates the resources brought by the proxy server in the process of constantly trying to wake up the terminal that has deleted the application proxy client: i % consumption.
- the proxy server may send an uninstall notification message to each application server serving the terminal, the notification message including an indication that the application proxy client has been uninstalled on the terminal.
- the proxy server receives the uninstallation indication message sent by the terminal, The uninstallation indication is notified to the application server, so that the application server knows in a timely and accurate manner that the terminal has uninstalled the application proxy client state, and no longer sends information to the proxy server, thereby improving the operation on the network side.
- Figure 5A shows a schematic diagram of a method for execution by a terminal in an attempt by an AOI server to wake up a terminal, in accordance with one embodiment of the present invention.
- a wakeup message is received from the AOI server on the terminal, the wakeup message being used to instruct the AOI middleware on the terminal to establish an IP connection with the AOI server.
- the AOI server transmits the wakeup message to the terminal by, for example, SMS.
- the AOI server finds that the IP connection between the AOI server and the terminal is abnormal, the AOI server transmits the wakeup message to the terminal by, for example, SMS.
- step S5A20 after receiving the wake-up message, it is judged whether the AOI middleware has been uninstalled on the terminal. For example, the determination may be made by judging whether the AOI middleware is installed on the terminal. When not installed, it is judged that the AOI middleware has been uninstalled on the terminal; when installed, it is judged that the AOI middleware is not uninstalled on the terminal. In this example, when it is determined in the above steps S3A10, S3B10, S3C10 that the AOI middleware is uninstalled on the terminal, as an alternative manner, the uninstallation may not be performed as early as the embodiment shown in FIGS. 3A to 3C.
- the indication message is sent to the AOI server, but after the terminal receives the wake-up message, it is judged whether the AOI middleware has been uninstalled on the terminal, and the uninstallation indication message is sent to the AOI server when it is judged that the AOI middleware has been uninstalled on the terminal.
- the embodiment shown in FIG. 3A-3B and the embodiment shown in FIG. 5A are not mutually exclusive, and they can be implemented separately as different implementations or as compatible implementations. At the same time.
- the determination may be made in step S5A20 based on whether or not an instruction to uninstall the AOI middleware on the terminal is stored on the terminal.
- the uninstallation indication message is not sent to the AOI server as early as the embodiment shown in FIGS. 3A to 3C, but An indication that the AOI middleware has been uninstalled on the terminal is saved on the terminal.
- the saved indication can be cleared, for example, the value of the indication is cleared, or set to indicate that other values of the AOI middleware are not unloaded.
- the uninstallation instruction message is transmitted to the AOI server in step S5A30.
- the advantage of using the above method is, for example, if The user uninstalled the AOI middleware, and installed the AOI middleware after a short period of time. For the AOI server, it is very likely that the change of the AOI middleware on the terminal side is not realized, so by avoiding the above method, it can be avoided. In this case, the AOI middleware uninstallation indication is unnecessarily notified to the AOI server and possibly the application server.
- step S5A30 the slave terminal transmits an uninstallation indication message to the AOI server indicating that the AOI middleware has been uninstalled on the terminal.
- an uninstall indication message can be sent to the AOI server via SMS.
- step S5A20 If it is determined in step S5A20 that the AOI middleware is not uninstalled on the terminal, then in step S5A40, a connection is initiated to the AOI server on the terminal in accordance with the existing manner.
- Figure 5B shows a schematic diagram of a method performed by an AOI server during an attempt by an AOI server to wake up a terminal, in accordance with one embodiment of the present invention.
- a wakeup message is sent from the AOI server to the terminal, and the wakeup message is used to indicate that the AOI middleware on the terminal establishes an IP connection with the AOI server.
- the wakeup message can be sent from the AOI server to the terminal via SMS.
- step S5B20 it is judged on the AOI server whether the terminal receives the wakeup message. For example, when the waking message is sent from the AOI server to the terminal through the SMS, if the terminal successfully receives the SMS message, the terminal sends a short message receipt to the AOI server, so that the AOI server can determine whether the terminal receives the message according to whether the short message receipt from the terminal is received. To wake up the message.
- step S5B30 the status of the terminal is marked as unreachable on the AOI server.
- step S5B40 When it is determined on the AOI server that the terminal receives the wakeup message, then in step S5B40,
- the AOI server determines whether an uninstallation indication message sent by the terminal is received, and the uninstall indication message indicates that the AOI middleware has been uninstalled on the terminal.
- the uninstallation indication message can be sent from the terminal to the AOI server via SMS.
- step S5B50 When it is determined on the AOI server that the uninstallation indication message sent by the terminal is received, in step S5B50, the status of the terminal is marked on the AOI server as the AOI middleware has been uninstalled on the terminal.
- step S5B60 an uninstall notification message is sent from the AOI server to one or more application servers serving the one or more application clients associated with the AOI middleware on the terminal, the message indicating that the AOI middleware has been uninstalled on the terminal .
- the processing is performed on the AOI server in an existing manner in step S5B70.
- Figure 6A shows a schematic diagram of a method performed by an AOI server in a process in which a terminal initiates a re-registration or registration to an AOI server, in accordance with one embodiment of the present invention.
- the implementation scenario of the embodiment may be: When the terminal does not signal or shut down for a period of time, the AOI server initiates a re-registration request or a registration request to the AOI server when the terminal is brought back online or powered on.
- a registration request from the terminal is received on the AOI server.
- step S6A20 it is determined whether the information of the terminal is stored on the AOI server according to the identifier (ID) of the terminal included in the registration request, and the identifier of the terminal is, for example, an IMSI summary, and the information of the terminal is included between the terminal and the AOI server. Establish information about the connection.
- step S6A20 When it is determined in step S6A20 that the information of the terminal is stored on the AOI server, it proceeds to step S6A30 to determine whether the state of the terminal has been marked as being unloaded on the terminal on the AOI server.
- step S6A30 When it is determined in step S6A30 that the status of the terminal has been marked on the AOI server as the AOI middleware has been uninstalled on the terminal, proceeding to step S6A40, a registration response is sent from the AOI server to the terminal, the registration response being included on the AOI server.
- the status of the terminal is indicated as an indication that the AOI middleware has been uninstalled on the terminal and includes an application server list, wherein the application server in the list is an application server to which the AOI server has notified the AOI middleware that the host has been uninstalled.
- the terminal needs to re-register all application servers during the re-registration process.
- the AOI middleware is learned from the AOI server, and the application server that has not sent the data does not perceive the AOI middleware.
- the AOI server marks the terminal as being uninstalled AOI middleware, that is, the application server that has not sent data still considers the state of the terminal to be normal.
- the terminal By transmitting an indication of the uninstalled state of the terminal indicated on the AOI server and the list of application servers notified of the uninstalled state of the terminal to the terminal in step S6A40, the terminal only needs to initiate a re-registration request to the application server given in the list. Or register the request without initiating a re-registration request to other application servers that do not consider the terminal to have uninstalled the AOI middleware, thus reducing the waste of network resources.
- step S6A30 When it is determined in step S6A30 that the state of the terminal is not marked on the AOI server as the application proxy client has been uninstalled on the terminal, that is, the state of the terminal is normal, proceeding to step S6A50, from The AOI server sends a regular registration response to the terminal. In this case, the UE may not have to re-register with the application server.
- step S6A20 When it is determined in step S6A20 that the information of the terminal is not stored in the AOI server, a response message is transmitted from the AOI server to the terminal, the response message including an indication that the information of the terminal does not exist on the AOI server.
- Figure 6B shows a schematic diagram of a method for execution by a terminal in a process in which a terminal initiates a re-registration or registration to an AOI server, in accordance with one embodiment of the present invention.
- the implementation scenario of this embodiment may be: Since the terminal has no signal or shutdown for a period of time, the AOI server initiates a re-registration request or a registration request to the AOI server when the terminal is marked or turned on.
- step S6B10 the slave terminal sends a registration request to the AOI server.
- step S6B20 the registration response from the AOI server is received at the terminal.
- the registration response includes an indication that the status of the terminal has been marked on the AOI server as an indication that the AOI middleware has been uninstalled on the terminal, and the registration response further includes an application server list, wherein the application server in the list is The AOI server has notified it to the application server that has uninstalled the AOI middleware on the terminal.
- the application client associated with the application server in the list is triggered on the terminal to re-login or re-register with the corresponding application server in the list.
- the application client on the terminal sends a re-registration request to the application server serving the service
- the re-registration request includes a Token assigned by the AOI server to the application client, and the Token is used to indicate that the application server is connected to the AOI server.
- Application client communication on the terminal By initiating the re-registration request only to the application server given in the list in step S6B30, there is no need to initiate a re-registration request to other application servers that do not think that the terminal has uninstalled the AOI middleware, compared to the existing re-registration process. Re-registration to all application servers reduces the waste of network resources.
- the response message is a regular registration response from the AOI server.
- the terminal does not have to re-register the request with the application server.
- step S6B40 is not actually performed in the terminal, but this step is shown in Fig. 6B for convenience of description.
- the response message includes an indication that the terminal does not have information on the AOI server.
- the response message includes an indication that the terminal does not have information on the AOI server.
- the process is re-registered, for example, according to the process shown in Figure 2.
- FIG. 7 shows a communication device 7000 in accordance with an embodiment of the present invention.
- the device may be a terminal, such as the terminal 110 or 210 in FIG. 1 and 2, or may be a component implemented on the terminal, and the component may be a software module implemented by a program, or may be a hardware module implemented by hardware.
- functional modules can be implemented by various implementations well known to those skilled in the art.
- device 7000 is a processing device 7000 for an application proxy client.
- the device 7000 includes a determining unit 7100 and a transmitting unit 7200.
- the determining unit 7100 is configured to determine that the AOI middleware is unloaded on the terminal
- the transmitting unit 7200 is configured to send an uninstallation indication message from the terminal to the AOI server corresponding to the AOI middleware, the message indicating that the AOI middleware has been uninstalled on the terminal.
- the apparatus 7000 further includes a registration unit 7300, configured to trigger, when the terminal has an IP bearer, one or more application clients associated with the AOI middleware to use the IP bearer to the corresponding one or more applications.
- the server initiates a registration request.
- the registration request does not carry a Token assigned by the AOI server to the one or more application clients.
- the Token is used to indicate that the one or more application servers communicate with the terminal via the AOI server or communicate with the one or more application clients of the terminal.
- the one or more application servers can learn not to The one or more application clients of the terminal communicate via the AOI server.
- the apparatus 7000 further includes a receiving unit 7500 for receiving a wake-up message from the proxy server on the terminal. After receiving the wake-up message, the determining unit 7100 determines on the terminal that the application proxy client has been uninstalled.
- the apparatus 7000 further includes a determining unit 7400 for determining whether the terminal has an IP bearer when the AOI middleware is uninstalled. If the determining unit 7400 determines that the terminal has an IP bearer when uninstalling the AOI middleware, the sending unit 7200 sends an uninstallation indication message to the AOI server through the IP bearer; if the determining unit 7400 determines that the terminal does not have the IP bearer when uninstalling the AOI middleware The sending unit 7200 performs one of the following operations: saving, on the terminal, the indication that the AOI middleware has been uninstalled on the terminal, and when the terminal has an IP bearer, sending an uninstall indication message to the AOI server by using the IP bearer; Alternatively, an uninstall indication message is sent to the AOI server through the SMS.
- the apparatus 7000 includes a determining unit 7100, a determining unit 7400, a transmitting unit 7200, and a registration unit 7300.
- the determining unit 7100 is configured to determine, on the terminal, that the AOI middleware is uninstalled; the determining unit 7400 is configured to determine whether the terminal has an IP bearer when uninstalling the AOI middleware; If the determining unit 7400 determines that the terminal has an IP bearer when uninstalling the AOI middleware, the sending unit 7200 transmits an uninstallation indication message to the AOI server through the IP bearer, the message indicating that the AOI middleware has been uninstalled on the terminal, and the registration unit
- the 7300 triggers one or more application clients associated with the AOI middleware to initiate a registration request to the corresponding one or more application servers, where the registration request does not carry a Token assigned by the AOI server to the one or more application clients; If the determining unit 7400 determines that the terminal does not have an IP bearer
- device 7000 can be device 7000 for waking up the terminal.
- the apparatus 7000 includes a receiving unit 7500, a determining unit 7400, and a transmitting unit 7200.
- the receiving unit 7500 is configured to receive, on the terminal, an awake message from the AOI server, where the awake message is used to indicate that the AOI middleware on the terminal establishes an IP connection with the AOI server;
- the determining unit 7400 is configured to determine the terminal after the receiving unit 7500 receives the awake message.
- the sending unit 7500 is configured to send an uninstallation indication message to the AOI server from the terminal if the determining unit 7400 determines that the AOI middleware has been uninstalled on the terminal, the message indicating that the AOI middleware has been uninstalled on the terminal .
- device 7000 can be a device for performing terminal re-registration.
- the apparatus 7000 includes a registration unit 7300 and a receiving unit 7500.
- the registration unit 7300 is configured to send a registration request from the terminal to the AOI server;
- the receiving unit 7500 is configured to receive, at the terminal, a registration response from the AOI server, the registration response including an uninstall indication and an application server list, the uninstall indication being used to indicate on the AOI server
- the status of the terminal has been marked as having uninstalled the AOI middleware on the terminal, and the application server in the list is an application server to which the AOI server has notified the AOI middleware that the AOI middleware has been uninstalled on the terminal; wherein the registration unit 7300 is on the terminal An application client that is associated with an application server in the list is triggered to register with the corresponding application server in the list.
- the registration unit 7300 triggers the application client to send a registration request to the corresponding application server in the list on the terminal, where the registration request includes a Token assigned by the AOI server to the application client, and the Token is used to indicate that the application server is via the AOI.
- the server communicates with the terminal or with an application client on the terminal.
- the apparatus of the embodiment and the unit included in the apparatus may perform the corresponding steps in the method embodiment as shown in FIG. 4A and FIGS. 3A-3C, 5A and 6B, and details are not described herein again.
- the device 7000 is depicted in FIG. 7 as including a plurality of units 7100-7500, in different embodiments, in order to implement the present invention, it is possible for the device 7000 to only include some of the units therein, without necessarily including All shown units.
- FIG. 8 shows a communication device 8000 in accordance with an embodiment of the present invention.
- the device may be an AOI server, such as the AOI servers 120 and 220 in FIGS. 1 and 2, or may be a component implemented on the AOI server, the component may be a software module implemented by a program, or may be implemented by hardware.
- a hardware module, or a functional module that can also be implemented by various implementations well known to those skilled in the art.
- device 8000 is a device 8000 for learning that the terminal has unloaded AOI middleware.
- device 8000 includes a receiving unit 8100 and a labeling unit 8200.
- the receiving unit 8100 is configured to receive an uninstall indication message from the terminal on the AOI server, the message indicating that the AOI middleware has been uninstalled on the terminal.
- the labeling unit 8200 is configured to mark the status of the terminal on the AOI server as having uninstalled the AOI middleware on the terminal according to the uninstall indication message received by the receiving unit 8100.
- the apparatus 800 further includes a sending unit 8300 for transmitting an uninstall notification message from the AOI server to one or more application servers that provide services for one or more application clients associated with the AOI middleware on the terminal, This message indicates that the AOI middleware has been uninstalled on the terminal.
- the sending unit 8300 is further configured to send a wake-up message from the AOI server to the terminal, where the wake-up message is used to indicate that the AOI middleware on the terminal establishes an IP connection with the AOI server.
- the receiving unit 8100 is further configured to receive, from the terminal, an uninstall indication message in response to the wakeup message on the AOI server.
- device 8000 is a device for waking up a terminal.
- the apparatus 8000 includes a transmitting unit 8300, a determining unit 8400, and a marking unit 8200.
- the sending unit 8300 is configured to send, from the AOI server, a wakeup message to the terminal, where the awake message is used to indicate that the AOI middleware on the terminal establishes an IP connection with the AOI server, and the determining unit 8400 is configured to determine, on the AOI server, whether the terminal receives the wakeup message.
- the marking unit 8200 is configured to indicate, when the terminal does not receive the awake message, the status of the terminal on the AOI server as the terminal unreachable; wherein, when it is determined that the terminal receives the awake message, the determining unit 8400 determines whether the terminal is received.
- An uninstallation indication message sent by the terminal the uninstallation indication message indicating that the AOI middleware has been uninstalled on the terminal; wherein, when it is determined to be
- the labeling unit 8200 marks the status of the terminal on the AOI server as having uninstalled the AOI middleware on the terminal.
- the sending unit 8300 can also be configured to send an uninstall notification message from the AOI server to one or more application servers that provide services for one or more application clients associated with the AOI middleware on the terminal, the message Indicates that the AOI middleware has been uninstalled on the terminal.
- device 8000 is a device for performing terminal re-registration.
- the apparatus 8000 includes a receiving unit 8100, a determining unit 8400, and a transmitting unit 8300.
- the receiving unit 8100 is configured to receive a registration request from the terminal on the AOI server.
- the determining unit 8400 is configured to determine, according to the identifier (ID) of the terminal included in the registration request, whether the information of the terminal is saved on the AOI server, if it is determined to be If the information of the terminal is saved on the AOI server, it is determined whether the status of the terminal has been marked on the AOI server as the AOI middleware has been uninstalled on the terminal; the sending unit 8300 is configured to determine that the determining unit 8400 is on the AOI server.
- ID the identifier
- the status of the terminal has been marked as having uninstalled the AOI middleware on the terminal, and then the registration response is sent from the AOI server to the terminal, and the registration response includes indicating that the status of the terminal on the AOI server is that the AOI middleware has been uninstalled on the terminal.
- An indication and an application server list wherein the application server in the list is an application server to which the AOI server has notified the AOI middleware that the component has been uninstalled on the terminal.
- the sending unit 8300 is further configured to: when it is determined that the information of the terminal is not saved on the AOI server, send a response message from the AOI server to the terminal, where the response message includes the terminal not present on the AOI server. Instructions for the information.
- the device of the embodiment of FIG. 8 and the unit included in the device can perform as shown in FIG. 4B and
- the device 8000 is depicted in FIG. 8 as including a plurality of units 8100-8400, in different embodiments, in order to implement the present invention, it is possible for the device 8000 to only include some of the units therein, without necessarily including All shown units.
- the various units in Figures 7 and 8 may comprise processors, electronics devices, hardware devices, electronic components, logic circuits, memories, or any combination thereof, or the like, or may be implemented with the devices described above. Those skilled in the art will appreciate that the various units illustrated in Figures 7-8 can perform the corresponding processing in the methods described above in connection with Figures 3A-6B.
- Figure 9 illustrates a communication device 9000, which may be a terminal or proxy server suitable for use with the present invention, such as an AOI server or Push service, in accordance with an embodiment of the present invention.
- Cry may be a terminal or proxy server suitable for use with the present invention, such as an AOI server or Push service, in accordance with an embodiment of the present invention.
- Communication device 9000 includes various components connected by bus 9400, such as processor 9300, memory 9100, and transceiver 9200.
- Data 9110 and instructions 9120 can be stored in memory 9100.
- the processor 9300 can implement the apparatus disclosed by the present invention by executing the instruction 9120 and using the data 9110.
- Transceiver 9200 includes a transmitter 9210 and a receiver 9220 to allow transmission and reception of signals between the communication device and other communication devices.
- the communication device shown in FIG. 9 may be a terminal, including a processor 9300 and a memory 9100 connected to the processor, the processor configured to: determine, on the terminal, that the application proxy client is uninstalled; the slave terminal An uninstallation indication message is sent to the proxy server corresponding to the application proxy client, the message indicating that the application proxy client has been uninstalled on the terminal.
- processor may be further configured to perform the operations of the various embodiments described above in connection with Figures 3A-3C, 4A, 5A, and 6B.
- the communication device shown in FIG. 9 may be a proxy server, including a processor 9300 and a memory 9100 connected to the processor, the processor configured to: receive an uninstall indication message from the terminal on the proxy server, The message indicates that the application proxy client has been uninstalled on the terminal; the status of the terminal is marked on the proxy server as the application proxy client has been uninstalled on the terminal.
- the processor may be further configured to perform the operations of the various embodiments described above in connection with Figures 4B, 5B, and 6A.
- the program stored in the memory 9100 can be executed by the processor 9300, and the process described above in connection with FIGS. 3A-6B can be performed and described in conjunction with FIGS. 7-8. The corresponding processing in the device.
- Embodiments of the invention may also be implemented as a computer program that, when executed, may implement the various method flows described above in connection with Figures 3A-6B.
- Embodiments of the invention may also be embodied as a machine readable medium having executable instructions stored thereon that, when executed, cause the machine to perform the various method flows described above in connection with Figures 3A-6B.
- the steps of the apparatus described herein may be embodied directly in hardware, software executed by a processor, or a combination of both, and the software may be located in a storage medium.
- the technical solution of the present invention may be embodied in the form of a software product in the form of a software product, or a part of the technical solution, which is stored in a storage medium, including a plurality of instructions.
- a computer device which may be a personal computer, server, or network device, etc. performs all or part of the steps of the apparatus in accordance with various embodiments of the present invention.
- the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code.
- the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a hardware product, such as an ASIC (Application Specific Integrated) well known in the art. Circuit technology, Field Programmable Gate Array (FPGA), Complex Programmable Logic Device (CPLD) and other technologies are used to implement the technical solution of the present invention as a dedicated hardware module.
- ASIC Application Specific Integrated
- FPGA Field Programmable Gate Array
- CPLD Complex Programmable Logic Device
- each unit included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding function can be implemented;
- the specific names are also for convenience of distinguishing from each other and are not intended to limit the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Environmental & Geological Engineering (AREA)
- Stored Programmes (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
提供了一种关于应用代理客户端的处理方法和装置,该方法包括:在终端上确定应用代理客户端被卸载;从终端向与应用代理客户端对应的代理服务器发送卸载指示消息,该卸载指示消息指示在终端上已卸载应用代理客户端。通过本发明的方法,能够使代理服务器及时获知用户侧的应用代理客户端异常的情况,从而避免了代理服务器在试图唤醒终端的过程中带来的问题。
Description
用于处理应用代理客户端异常的方法和装置 本申请要求于 2012 年 6 月 15 日提交中国专利局、 申请号为 201210201580.1、 名称为 "用于处理应用代理客户端异常的方法和装置" 的中 国专利申请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信系统,具体涉及用于处理终端上的应用代理客户端出 现异常情况的方法和装置。 背景技术
虽然这通信技术的日益发展, 越来越多的应用出现在终端设备上。 例如, 目前的智能手机上的应用,特别是一些和移动互联网相关的应用客户端, 包括 即时通信( IM, Instant Messenger )、 电子邮件( Email )、社交网络服务( SNS, Social Networking Service )等, 需要实时地同网络侧的服务器或者其他智能手 机的应用客户端进行通信。 目前实现这种实时通信所釆用的方式是: 基于固定 网络和个人计算机 (PC , Personal Computer ) 的客户机 /服务器 ( C/S , Client/Server ) 业务运营模式, 按照 PC 固定接入因特网 (Internet ) 的方式来 实现。在整个业务开展的过程当中,将智能手机和应用服务器之间的移动通信 网络作为连接的管道, 并将应用针对移动网络进行了透明化的处理,使得服务 器不感知移动终端和固定终端的差别。
移动终端需要一直保持因特网协议(IP, Internet Protocol )连接, 如同固 定网络一样, 时刻准备接收和发送数据包。 同时, 在应用程序运行在移动终端 上的过程当中, 终端和服务器之间以较小的时间间隔发送心跳信令,从而保证 对端信息的时刻刷新, 并利用这个机制维持 IP连接长时间有效, 以通过这个 IP连接发送所有业务数据。
移动终端的分组数据协议(PDP, Packet Data Protocol )连接在一段时间 没有数据发送时, 会释放 PDP连接; 但是当有数据发送时, 需要重建 PDP连 接。 这样, 大量的终端为了发送上述心跳信令会不断的进行 PDP连接建立和
释放的过程, 因此会产生所谓的信令风暴,严重地消耗移动通信网络的无线通 信资源。
目前业界提出了推送(Push )的方案来解决信令风暴的问题。 通过在网络 侧设置特定的代理服务器, 例如始终在线构架 (AOI , Always Online Infrastructure )服务器或 Push服务器, 以及在终端上设置特定的应用代理客户 端, 例如 AOI中间件或 Push客户端, 由终端上的应用代理客户端和网络侧的 代理服务器之间维护连接以及由代理服务器和应用服务器之间维护连接,代替 终端上的诸如 IM、 Email, SNS等的应用客户端与相关联的应用服务器之间的 IP 连接, 使得应用客户端和相关联的应用服务器之间通过应用代理客户端和 代理服务器间的连接实现信息通信,从而终端上的应用客户端与相关联的应用 月良务器之间不再需要维持 IP连接进而不再需要不断地传送心跳信令, 避免了 终端的 PDP连接不断连接建立和释放过程, 减轻了网络负担。
终端上的应用代理客户端有可能在使用过程中出现一些异常情况,例如用 户可能从手机中卸载该应用代理客户端,由于长时间关机或不在服务区而无法 建立应用代理客户端与代理服务器之间的连接, 等等。 下文中, 为了描述的方 便, 以 AOI中间件作为应用代理客户端的例子、 以 AOI服务器作为应用服务 器的例子进行描述。本领域技术人员应该理解,应用代理客户端和应用服务器 的具体实现方式不限于 AOI中间件和 AOI服务器。
目前业界对终端卸载 AOI中间件等异常情况的检测方法如下:
AOI服务器检测到终端连接异常, 向该终端发送唤醒短信;
终端经过时间 T1后未连接到 AOI服务器, AOI服务器向该终端重发唤醒 短信;
AOI服务器已向该终端重发唤醒短信 N1次, 终端未连接到 AOI服务器; AOI服务器将该终端的状态调整为不在线,此状态下若某应用服务器希望 通过 AOI服务器向该终端推送业务消息, AOI服务器向该应用服务器返回推 送失败的消息, 失败原因为终端不在线;
经过时间 T2后终端仍未连接到 AOI服务器, AOI服务器判断该用户可能 已卸载中间件,将其状态调整为中间件已卸载, 此状态下若某应用服务希望通 过 AOI服务器向该终端推送业务消息, AOI服务器向该应用服务器返回推送 失败的消息, 失败原因为中间件已卸载, 该应用服务器收到此类失败原因, 不
应再尝试向此用户推送业务消息。
在现有的流程中, AOI服务器只能根据特定的操作来判断终端是否已删除
AOI中间件, 导致 AOI服务器不能及时获知终端的可达状态, 进而影响应用 服务器的服务质量; 另外, 在现有的流程中, 终端不能够获知例如以下信息: AOI服务器已认为在终端上删除了 AOI中间件、 在 AOI服务器上已删除终端 相关信息、 以及哪些应用服务器已认为在终端上删除了 AOI中间件等。 而以 上信息的获得能够进一步改进终端、 AOI服务器和应用服务器之间的处理效 率, 节省网络资源, 改进终端上相关应用客户端的服务质量。 因此本领域中, 需要进一步改进处理 AOI中间件异常的方法。 发明内容
本发明实施例在终端侧和网络侧提供了改进的处理应用代理客户端异常 的方法,从而能够进一步改进终端、 AOI服务器和应用服务器之间的处理效率, 节省网络资源, 改进应用客户端和应用服务器能够提供给用户的服务质量。
一方面, 本发明实施例提供了一种关于应用代理客户端的处理方法, 该方 法包括: 在所述终端上确定所述应用代理客户端被卸载; 从所述终端向与所述 应用代理客户端对应的代理服务器发送卸载指示消息,该卸载指示消息指示在 所述终端上已卸载所述应用代理客户端。
另一方面,本发明实施例提供了一种用于获知在终端上已卸载应用代理客 户端的方法, 该方法包括: 在代理服务器上从所述终端接收卸载指示消息, 该 卸载指示消息指示在所述终端上已卸载所述应用代理客户端;根据所述卸载指 示消息在所述代理服务器上将所述终端的状态标示为在所述终端上已卸载所 述应用代理客户端。
另一方面, 本发明实施例提供了一种用于唤醒终端的方法, 该方法包括: 从代理服务器向终端发送唤醒消息;在所述代理服务器上判断所述终端是否收 到所述唤醒消息; 当判断为所述终端没有收到所述唤醒消息时, 在所述代理服 务器上将所述终端的状态标示为终端不可达;当判断为所述终端接收到所述唤 醒消息时, 在所述代理服务器上判断是否收到所述终端发送的卸载指示消息, 所述卸载指示消息包含在所述终端上已卸载所述应用代理客户端的指示;当判 断为收到所述终端发送的所述卸载指示消息时,在所述代理服务器上将所述终
端的状态标示为在所述终端上已卸载所述应用代理客户端。
另一方面, 本发明实施例提供了一种用于唤醒终端的方法, 该方法包括: 在所述终端上从代理服务器接收唤醒消息;在所述终端上判断所述终端上是否 已卸载所述应用代理客户端;如果判断为所述终端上已卸载所述应用代理客户 端, 则从所述终端向所述代理服务器发送卸载指示消息, 该消息指示在所述终 端上已卸载所述应用代理客户端。
另一方面,本发明实施例提供了一种用于终端重注册的方法,该方法包括: 在代理服务器上接收来自所述终端的注册请求;根据所述注册请求中包含的所 述终端的标识(ID )判断在所述代理服务器上是否保存有所述终端的信息; 如 果判断为在所述代理服务器上保存有所述终端的信息,则判断在所述代理服务 果判断为在所述代理服务器上已将所述终端的状态标示为在所述终端上已卸 载应用代理客户端,从所述代理服务器向所述终端发送注册响应, 该注册响应 包含卸载指示以及应用服务器列表, 其中, 所述卸载指示用于指示在所述代理 服务器上已将所述终端的状态标示为在所述终端上已卸载应用代理客户端,所 述列表中的应用服务器是已被所述代理服务器通知了在所述终端上已卸载应 用代理客户端的应用服务器。
另一方面,本发明实施例提供了一种用于终端重注册的方法,该方法包括: 从所述终端向代理服务器发送注册请求;在所述终端接收来自所述代理服务器 的对所述注册请求的注册响应, 该注册响应包含卸载指示以及应用服务器列 表, 其中, 所述卸载指示用于指示在所述代理服务器上已将所述终端的状态标 示为在所述终端上已卸载应用代理客户端,所述列表中的应用服务器是已被所 述代理服务器通知了在所述终端上已卸载应用代理客户端的应用服务器;在所 述终端上触发与所述列表中的应用服务器关联的应用客户端向所述列表中的 相应的应用服务器进行注册。
另一方面, 本发明实施例提供了一种关于应用代理客户端的处理装置, 该 装置包括: 确定单元, 用于在所述终端上确定所述应用代理客户端被卸载; 发 送单元,用于从所述终端向与所述应用代理客户端对应的代理服务器发送卸载 指示消息, 该卸载指示消息指示在所述终端上已卸载所述应用代理客户端。
另一方面,本发明实施例提供了一种用于获知在终端上已卸载应用代理客
户端的装置, 该装置包括: 接收单元, 用于在代理服务器上从所述终端接收卸 载指示消息, 该卸载指示消息指示在所述终端上已卸载所述应用代理客户端; 标示单元,用于根据所述接收单元接收的所述卸载指示消息在所述代理服务器 另一方面, 本发明实施例提供了一种用于唤醒终端的装置, 该装置包括: 发送单元, 用于从代理服务器向终端发送唤醒消息; 判断单元, 用于在所述代 理服务器上判断所述终端是否收到所述唤醒消息; 标示单元, 用于当判断为所 述终端没有收到所述唤醒消息时,在所述代理服务器上将所述终端的状态标示 为终端不可达; 其中, 当判断为所述终端接收到所述唤醒消息时, 所述判断单 元判断是否收到所述终端发送的卸载指示消息,所述卸载指示消息包含在所述 终端上已卸载所述应用代理客户端的指示; 其中, 当判断为收到所述终端发送 的所述卸载指示消息时,所述标示单元在所述代理服务器上将所述终端的状态 标示为在所述终端上已卸载所述应用代理客户端。
另一方面, 本发明实施例提供了一种用于唤醒终端的装置, 该装置包括: 接收单元, 用于在所述终端上从代理服务器接收唤醒消息; 判断单元, 用于在 所述终端上判断所述终端上是否已卸载所述应用代理客户端; 发送单元, 用于 如果判断为在所述终端上已卸载所述应用代理客户端,则从所述终端向所述代 理服务器发送卸载指示消息,该消息指示在所述终端上已卸载所述应用代理客 户端。
另一方面, 本发明实施例提供了一种用于进行终端重注册的装置, 该装置 包括: 接收单元, 用于在代理服务器上接收来自所述终端的注册请求; 判断单 元, 用于根据所述注册请求中包含的所述终端的标识 ( ID )判断在所述代理服 务器上是否保存有所述终端的信息,如果判断为在所述代理服务器上保存有所 述终端的信息,则判断在所述代理服务器上是否已将所述终端的状态标示为在 所述终端上已卸载应用代理客户端; 发送单元, 用于在所述判断单元判断为在 所述代理服务器上已将所述终端的状态标示为在所述终端上已卸载应用代理 客户端时,从所述代理服务器向所述终端发送注册响应, 该注册响应包含卸载 指示以及应用服务器列表, 其中, 所述卸载指示用于指示在所述代理服务器上 已将所述终端的状态标示为在所述终端上已卸载应用代理客户端,所述列表中 的应用服务器是已被所述代理服务器通知了在所述终端上已卸载应用代理客
户端的应用服务器。
另一方面, 本发明实施例提供了一种用于进行终端重注册的装置, 该装置 包括: 注册单元, 用于从所述终端向代理服务器发送注册请求; 接收单元, 用 于在所述终端接收来自所述代理服务器的注册响应,该注册响应包含卸载指示 以及应用服务器列表, 其中, 所述卸载指示用于指示在所述代理服务器上已将 所述终端的状态标示为在所述终端上已卸载应用代理客户端,所述列表中的应 用服务器是已被所述代理服务器通知了在所述终端上已卸载应用代理客户端 应用服务器关联的应用客户端向所述列表中的相应的应用服务器进行注册。
另一方面, 本发明实施例提供了一种无线通信设备, 包括: 存储器, 用于 存储数据及指令; 与所述存储器耦合的处理器, 用于根据所述存储器中的所述 数据及指令来运行, 以使得该无线通信设备能够执行本发明的上述方法。
另一方面, 本发明实施例提供了一种机器可读介质, 其中存储指令, 当机 器执行该指令时, 使得该机器能够执行本发明的上述方法。
另一方面, 本发明实施例提供了一种计算机程序, 该计算机程序用于执行 本发明的上述方法。
通过参考以下结合附图的说明以及权利要求书中的内容,并且随着对本发 明实施例的更全面的理解,本发明的其他目的及效果将变得更加清楚和易于理 解。 附图说明
以下将参照附图, 通过实施例详细地描述本发明, 其中:
图 1是现有技术中 AOI中间件的重新激活流程的示意图。
图 2是现有技术中 AOI中间件的初始激活流程的示意图。
图 3A到 3C是才艮据本发明实施例的在终端上卸载 AOI中间件时的示例性 处理流程的示意图。
图 4A是 居本发明实施例的在终端上卸载 AOI中间件时的示例性处理流 程的示意图。
图 4B是根据本发明实施例的用于获知在终端上卸载 AOI中间件的示例性 处理流程的示意图。
图 5A和 5B是根据本发明实施例的用于在 AOI服务器唤醒终端的过程中 在终端和 AOI服务器上的示例性处理流程的示意图。
图 6A和 6B是根据本发明实施例的在终端向 AOI服务器发起重注册请求 的过程中在 AOI服务器和终端上的示例性处理流程的示意图。
图 7是根据本发明实施例的终端的示意框图。
图 8是根据本发明实施例的 AOI服务器的示意框图。
图 9是说明可应用本发明实施方式的示例性通信设备的示意图。
在所有附图中, 相同的标号表示相似或相应的特征或功能。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。基于本发明中的实施例, 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本领域技术人员应该理解,在以下具体实施例的描述中, 不同的术语代表 相同或相似的含义, 只是为了适应不同的具体语境所釆用的不同表述方式。例 如, 在下面的实施例中可能提到的 "应用" 、 "应用客户端" 、 "应用软件" 、 "应用程序"等表示相同或相似的含义, 在下面的实施例中可能提到的 "应用 代理客户端" 、 "应用代理软件" 、 "中间件" 等表示相同或相似的含义, 在 在下面的实施例中可能提到的 "注册" 、 "登录" 、 "重注册" 、 "重登录" 等表示相同或相似的含义。
本领域技术人员应该理解,在以下具体实施例的描述中,为了描述的方便, 以 AOI中间件作为应用代理客户端的例子、 以 AOI服务器作为应用服务器的 例子进行描述。本领域技术人员应该理解,应用代理客户端和代理服务器的具 体实现方式不限于 AOI中间件和 AOI服务器, 例如, 应用代理客户端可以是 AOI中间件或 Push客户端, 代理服务器可以是 AOI服务器或 Push服务器, 无论具体的名称为何, 只要符合本发明的实施方式, 都应该视为在本发明的保 护范围之内。
图 1示出了现有技术中终端上的 AOI中间件的重新激活流程。 该激活流 程是在例如如下场景下进行的: 终端之前已经建立了与 AOI服务器的连接且
终端上的中间件未被卸载,在例如终端关机或没有信号一段时间之后开机或重 新上线时, 终端或者说终端上的 AOI中间件向 AOI服务器发送重注册请求。
如图 1所示, 在步骤 S110, 终端 110向 AOI服务器 120发出注册请求, 该请求消息中携带了终端 110上与 AOI客户端相关联的所有应用客户端的应 用标识(ID, identification ) 。 这里, 与 AOI客户端相关联的应用客户端是通 过该 AOI客户端和 AOI服务器 120实现与相应的应用服务器 130的通信的应 用客户端, 例如 IM、 Email, SNS等应用软件。
在步骤 S120 , AOI服务器 120将用户状态修改为正常并向终端 110返回 响应消息。 该步骤中, 若终端 110中有新的应用, 则 AOI服务器 120为新的 应用生成令牌(token ) , 并在响应消息中将该新生成的令牌返回给终端 110。
在步骤 S130 , 终端 110上的所有相关的应用客户端向为其提供服务的应 用服务器 130发起登录请求并在登录请求中携带 AOI服务器 120分配给自己 的 token, 应用服务器 130修改终端的用户状态为正常。 应用服务器 130根据 登录请求中的 token能够获悉经由 AOI服务器 120与终端 110进行通信,例如, 应用服务器 130将消息发送到 AOI服务器 120并由 AOI服务器 120发送到相 应的终端 110。
图 2示出了现有技术中终端上的 AOI中间件的初始激活流程。 该激活流 程是在例如如下场景下进行的: 终端首次安装了 AOI中间件, 或者在终端上 卸载了之前安装的 AOI中间件后之前重新安装 AOI中间件, 此时, 终端上不 具备与 AOI服务器建立连接有关的信息。
如图 2所示,在步骤 S210,终端 210向 AOI域名系统( DNS, Domain Name System ) 240注册短信, 该短信包含与终端 210关联的用户识别模块 (SIM, Subscriber Identity Module)卡的国际移动用户识别码 ( IMSI , International Mobile Subscriber Identification Number)摘要, IMSI摘要例如是 IMSI的一部分, 用于唯一地识别用户。 DNS记录该终端 IMSI摘要和移动用户国际综合业务数 字网号码( MSISDN, Mobile Subscriber International ISDN/PSTN number)的对 应关系。
在步骤 S220 , 终端 210向 AOI DNS 240发送注册请求, 该请求消息中包 含终端 210的 IMSI摘要。
在步骤 S230 , AOI DNS 240向终端 210返回注册响应, 该响应消息中携
带终端 210的 AOI服务器地址信息。
在步骤 S240 , 终端 210向 AOI服务器 220发起注册请求, 该请求消息中 包含终端 210的 IMSI摘要和终端要注册的应用客户端的应用 ID。
在步骤 S250, 如果 AOI服务器 220发现本地没有与该 IMSI摘要对应的 终端用户信息, 则向 AOI DNS 240发送获取终端身份信息的请求消息, 该消 息中包含终端 210的 IMSI摘要。
在步骤 S260, AOI DNS 240向 AOI服务器 220返回获取终端身份信息的 响应消息, 该响应消息中包含与终端 210的 IMSI摘要对应的 MSISDN号码。
在步骤 S270, AOI服务器 220对终端 210的用户进行鉴权,并为终端 210 上的相关的应用生成 token, 然后向终端 210返回注册响应, 该响应消息中携 带为终端 210上的应用客户端分配的 token。
在步骤 S280, 终端 210上的所有相关的应用客户端分别向为其提供服务 的应用服务器 230发起登录请求并在登录请求中携带 AOI服务器 220分配给 自己的 token, 应用服务器 230修改用户状态为正常, 并在随后经由 AOI服务 器 220向终端发送信息。
图 3A到 3C是根据本发明实施例的在终端上卸载 AOI中间件时的示例性 处理流程的示意图。
图 3A示出了根据本发明一个实施例的用于在终端上卸载 AOI中间件的方 法,该终端例如是图 1和 2中的终端 110或 210。如图 3A所示,在步骤 S3A10, 在终端上确定 AOI中间件被卸载。 对 AOI中间件的卸载操作例如可以是在终 端上根据用户输入的卸载指令而执行的。 例如, 可以通过检测针对 AOI 中间 件的卸载指令而确定对 AOI中间件的卸载。 例如, 可以通过监视终端操作系 统的与卸载操作有关的进程, 来确定对 AOI中间件的卸载。 本领域技术人员 应该清楚, 终端例如智能手机釆用的操作系统可能不同, 相应地用于确定对 AOI中间件的卸载的具体方式也可能不同,本发明的范围不受各种具体方式的 限制。 又例如, 可以在终端上从 AOI服务器接收唤醒消息后来进行 AOI中间 件是否被卸载的确定。 例如, 在终端上接收到唤醒消息后, 可以判断终端上是 否安装有 AOI中间件, 当没有安装时, 则确定终端上已卸载 AOI中间件。
在步骤 3A20, 当在终端上卸载 AOI 中间件时, 判断终端当前是否有 IP 承载可用于到 AOI服务器的连接。
如果在步骤 3A20判断为终端当前有 IP承载, 则进行到步骤 S3A50, 从 终端通过该 IP承载向 AOI服务器发送卸载指示消息, 该卸载指示消息指示在 终端上已卸载 AOI中间件。卸载指示消息具体可以是通知(Notification )消息、 指示 (Indication ) 消息等。 这里的卸载指示消息不具体代表一个消息的名称, 而是代表消息的作用是用于告知 AOI服务器终端上已卸载了 AOI中间件。
通过在步骤 S3A50中由终端在卸载 AOI中间件时主动向 AOI服务器通知 终端已卸载 AOI中间件的情况, 使得 AOI服务器能够及时获知终端的可达状 态, 而不必像现有方法中那样只能根据 AOI服务器在网络侧特定的操作来自 行判断终端是否已删除中间件, 从而简化了网络侧的操作并且减轻了 AOI月良 务器在不断试图唤醒已删除了 AOI中间件的终端的过程中所带来的资源消耗。 AOI服务器通过及时准确地获知终端已卸载 AOI中间件的状态, 进而又能够 及时改善应用服务器的服务质量, 例如当某应用服务器向 AOI服务器发送去 往该终端的数据时, AOI服务器能够及时通知该应用服务器该终端已删除 AOI 中间件, 使得该应用服务器不再继续向 AOI服务器发送去往该终端的数据。
如果在步骤 3A20判断为终端当前没有 IP承载, 则进行到步骤 S3A30, 在终端上保存(例如, 暂时保存)终端已卸载 AOI 中间件的指示信息, 然后 进行到步骤 S3A40, 判断终端是否有 IP承载, 例如, 可以定期地判断终端是 否有 IP承载,当在步骤 S3 A40判断为终端具有 IP承载时,则进行到步骤 S3 A50 从终端通过该 IP承载向 AOI服务器发送卸载指示消息。
在步骤 S3A60, 当终端具有 IP承载时, 在终端上触发与 AOI中间件相关 联的一个或多个应用客户端通过该 IP承载向为应用客户端提供服务的一个或 多个应用服务器发起重注册请求或者说注册请求。 这里, 不失一般性, 为了表 述上的区分, 可以将向应用服务器发起的注册请求称为应用注册请求。根据一 个实施例, 在该重注册请求中不携带 AOI服务器分配给应用客户端的 Token 信息。 各应用服务器根据重注册请求中未携带 Token可以获知后续不再经过 AOI服务器与终端进行通信。 通过在步骤 S3A60中在卸载 AOI中间件时触发 相关的应用客户端进行与应用服务器的重注册过程或者说注册过程,能够及时 地建立应用客户端与相应应用服务器之间的连接, 改进用户的使用感受, 并能 够使应用服务器及时获知终端已删除 AOI中间件的情况, 不再向 AOI服务器 发送信息, 改进网络侧的操作。
图 3B示出了根据本发明另一个实施例的用于在终端上卸载 AOI中间件的 方法,该终端例如是图 1和 2中的终端 110或 210。该实施例中的步骤 S3B10、 S3B20、 S3B50、 S3B60与图 3A的步骤 S3A10、 S3A20、 S3A50、 S3A60相同, 因此不再进行详细说明。
如图 3B所示, 在步骤 S3B10, 在终端上确定 AOI中间件被卸载。
在步骤 3B20, 判断当在终端上卸载 AOI中间件时终端是否有 IP承载。 如果在步骤 3B20判断为终端当前有 IP承载, 则进行到步骤 S3B50,从终 端通过该 IP承载向 AOI服务器发送卸载指示消息, 该卸载指示消息指示在终 端上已卸载 AOI中间件。 然后从步骤 S3B50进行到步骤 S3B60, 在终端上触 发与 AOI中间件相关联的一个或多个应用客户端通过该 IP承载向对应的一个 或多个应用服务器发起重注册请求或者说注册请求。在该重注册请求中不携带 AOI服务器分配给应用客户端的 Token信息。
如果在步骤 3B20判断为终端当前没有 IP承载, 则进行到步骤 S3B30,从 终端通过短信服务(SMS ) 向 AOI服务器发送卸载指示消息。 作为可选的操 作, AOI服务器在接收到该卸载指示消息时,可以向为该终端提供服务的各应 用服务器发送通知消息, 该通知消息包含在终端上已卸载 AOI中间件的指示。 通过在步骤 S3B30中利用 SMS向 AOI服务器发送卸载指示消息,终端在当卸 载 AOI 中间件时不具备 IP承载的情况下, 可以及时地将该卸载情况通知给 AOI服务器,使得 AOI服务器能够相比于图 3A所示的实施例更加及时地获知 终端的可达状态, 从而更有效地避免了根据 AOI服务器在网络侧特定的操作 来自行判断终端是否已删除中间件的情况。 而通过上述可选的操作, AOI服务 器在收到终端通过 SMS发送的卸载指示消息时, 将该卸载指示通知给应用服 务器, 使得应用服务器及时准确地获知终端已卸载 AOI中间件的状态, 不再 向 AOI服务器发送信息, 改进网络侧的操作。
在步骤 S3B40, 判断终端是否有 IP承载, 当在步骤 S3B40判断为终端具 有 IP承载时, 则进行到步骤 S3B60, 在终端上触发与 AOI中间件相关联的各 应用客户端通过该 IP承载向为其提供服务的各应用服务器发起重注册请求或 者说注册请求。 根据一个实施例, 在该重注册请求中不携带 AOI服务器分配 给应用客户端的 Token信息。
图 3C示出了根据本发明另一个实施例的用于在终端上卸载 AOI中间件的
方法,该终端例如是图 1和 2中的终端 110和 210。该实施例中的步骤 S3C10、 S3C20、 S3C50、 S3C60与图 3A的步骤 S3A10、 S3A20、 S3A50、 S3A60相同, 因此不再进行详细说明。
如图 3C所示, 在步骤 S3C10, 在终端上确定 AOI中间件被卸载。
在步骤 3C20, 判断当在终端上卸载 AOI中间件时终端是否有 IP承载。 如果在步骤 3C20判断为终端当前有 IP承载, 则进行到步骤 S3C50,从终 端通过该 IP承载向 AOI服务器发送卸载指示消息, 该卸载指示消息指示在终 端上已卸载 AOI中间件。 然后从步骤 S3C50进行到步骤 S3C60, 在终端上触 发与 AOI中间件相关联的一个或多个应用客户端通过该 IP承载向对应的一个 或多个应用服务器发起重注册请求或者说注册请求。在该重注册请求中不携带 AOI服务器分配给应用客户端的 Token信息。
如果在步骤 3C20判断为终端当前没有 IP承载, 则进行到步骤 S3C30,在 终端上向与 AOI中间件相关联的各应用客户端发送卸载指示信息, 该卸载指 示信息包含在终端上已卸载 AOI中间件的指示。
在步骤 S3C40, 判断终端是否有 IP承载, 当在步骤 S3B40判断为终端具 有 IP承载时, 则进行到步骤 S3C60, 在终端上触发与 AOI中间件相关联的各 应用客户端通过该 IP承载向为其提供服务的各应用服务器发起重注册请求或 者说注册请求。 根据一个实施例, 在该重注册请求中不携带 AOI服务器分配 给应用客户端的 Token信息。
图 4A示出了根据本发明一个实施例的用于在终端上卸载 AOI中间件的方 法, 该终端例如是图 1和 2中的终端 110或 210。
如图 4A所示, 在步骤 S4A10, 在终端上确定应用代理客户端被卸载。 该 应用代理客户端例如上述 AOI中间件或 Push客户端。 该卸载操作例如可以是 在终端上根据用户输入的卸载指令而执行的。
在步骤 S4A20,从终端向与应用代理客户端对应的代理服务器发送卸载指 示消息, 该消息指示在终端上已卸载应用代理客户端。 通过在步骤 S4A20 中 由终端在卸载应用代理客户端后主动向代理服务器通知终端已卸载应用代理 客户端的情况,使得代理服务器能够及时获知终端的可达状态, 而不必像现有 方法中那样只能根据代理服务器在网络侧特定的操作来自行判断终端是否已 删除应用代理客户端,从而简化了网络侧的操作并且减轻了代理服务器在不断
试图唤醒已删除了应用代理客户端的终端的过程中所带来的资源消耗。代理服 务器通过及时准确地获知终端已卸载应用代理客户端的状态,进而又能够及时 改善应用服务器的服务质量,例如当某应用服务器向代理服务器发送去往该终 端的数据时,代理服务器能够及时通知该应用服务器该终端已删除应用代理客 户端, 使得该应用服务器不再继续向代理服务器发送去往该终端的数据。
在步骤 S4A30, 当终端具有 IP承载时, 触发与应用代理客户端相关联的 一个或多个应用客户端通过该 IP承载向对应的一个或多个应用服务器发起注 册请求或者说重注册请求。根据一个实施例,在该注册请求中不携带代理服务 器分配给应用客户端的 Token信息。 各应用服务器根据注册请求中未携带 Token 可以获知后续不再经过代理服务器与终端进行通信。 通过步骤 S4A30 中在卸载 AOI中间件时触发相关的应用客户端进行与应用服务器的注册过程 或者说重注册过程, 能够及时地建立应用客户端与相应应用服务器之间的连 接, 改进用户的使用感受, 并能够使应用服务器及时获知终端已删除应用代理 客户端的情况, 不再向代理服务器发送信息, 改进网络侧的操作。
图 4B示出了根据本发明一个实施例的用于获知在终端上已卸载应用代理 客户端的方法。
如图 4B所示,在步骤 S4B10,在代理服务器上从终端接收卸载指示消息, 该消息指示在终端上已卸载应用代理客户端。 该代理服务器例如是图 1 和 2 中的 AOI服务器 120或 220, 或该代理服务器是 Push服务器, 该终端例如是 图 1和 2中的终端 110或 210, 该应用代理客户端例如 AOI中间件或 Push客 户端。
在步骤 S4B20,在代理服务器上将该终端的状态标示为在该终端上已卸载 应用代理客户端。 通过在步骤 S4B10和 S4B20的操作, 代理服务器能够及时 获知终端的可达状态,而不必像现有方法中那样只能根据代理服务器在网络侧 特定的操作来自行判断终端是否已删除应用代理客户端,从而简化了网络侧的 操作并且减轻了代理服务器在不断试图唤醒已删除了应用代理客户端的终端 的过程中所带来的资源: i %耗。
在步骤 S4B30,代理服务器可以向为该终端提供服务的各应用服务器发送 卸载通知消息, 该通知消息包含在该终端上已卸载应用代理客户端的指示。通 过步骤 S4B30 的操作, 代理服务器在收到终端发送的卸载指示消息时, 将该
卸载指示通知给应用服务器,使得应用服务器及时准确地获知终端已卸载应用 代理客户端的状态, 不再向代理服务器发送信息, 改进网络侧的操作。
图 5A示出了根据本发明一个实施例的用于在 AOI服务器试图唤醒终端的 过程中由终端执行的方法的示意图。
在步骤 S5A10, 在终端上从 AOI服务器接收唤醒消息, 该唤醒消息用于 指示终端上的 AOI中间件建立与 AOI服务器的 IP连接。 例如, 当 AOI服务 器有消息要发送到终端但是发现 AOI服务器和终端之间的 IP连接中断时, AOI 服务器通过例如 SMS向终端发送该唤醒消息。 例如, 当 AOI服务器发现 AOI 服务器和终端之间的 IP连接异常时, AOI服务器通过例如 SMS向终端发送该 唤醒消息。
在步骤 S5A20, 在接收到唤醒消息后, 判断终端上是否已卸载 AOI中间 件。 例如, 可以通过判断终端上是否安装有 AOI中间件来进行该判断, 当没 有安装时, 则判断终端上已卸载 AOI 中间件; 当安装了时, 则判断终端上未 卸载 AOI中间件。 在该例中, 当在上述步骤 S3A10、 S3B10、 S3C10中确定在 终端上卸载了 AOI中间件时, 作为一种可选的方式, 可以不是如图 3A到 3C 所示实施例那样尽早地将卸载指示消息发送给 AOI服务器, 而是在终端接收 到唤醒消息后再判断终端上是否已卸载 AOI中间件, 并且在判断终端上已卸 载 AOI中间件时才向 AOI服务器发送卸载指示消息。 当然, 本领域技术人员 应该理解,图 3A-3B所示的实施方式和图 5A所示的实施方式并不是互相排斥 的, 它们既可以作为不同的实施方式分别实现,也可以作为兼容的实施方式同 时实现。
又例如,在步骤 S5A20中可以根据终端上是否保存有在终端上已卸载 AOI 中间件的指示来进行该判断。在该例中, 当在上述步骤 S3A10、 S3B10、 S3C10 中确定在终端上卸载了 AOI中间件时, 不是如图 3A到 3C所示实施例那样尽 早地将卸载指示消息发送给 AOI服务器, 而是在终端上保存在终端上已卸载 AOI中间件的指示。 当随后在终端上又安装了 AOI中间件后, 可以清除所保 存的该指示, 例如, 将该指示的值清零, 或者设置为表示未卸载 AOI中间件 的其他值。 当在步骤 S5A10中接收到唤醒消息后, 根据所保存的已卸载 AOI 中间件的指示来判断当前已经卸载了 AOI中间件, 并且此时才在步骤 S5A30 中向 AOI服务器发送卸载指示消息。 釆用上述方式的好处是, 例如, 如果用
户卸载了 AOI中间件, 而在较短的时间后又安装了 AOI中间件, 对于 AOI服 务器来说, 很有可能意识不到终端侧 AOI中间件的变化, 因此通过釆用上述 方式, 可以避免在这种情形下不必要地向 AOI服务器以及可能的应用服务器 通知该 AOI中间件卸载指示。
如果在步骤 S5A20判断为终端上已卸载 AOI中间件, 则在步骤 S5A30, 从终端向 AOI服务器发送卸载指示消息, 该消息指示在终端上已卸载 AOI中 间件。 例如, 可以通过 SMS向 AOI服务器发送卸载指示消息。
如果在步骤 S5A20判断为终端上未卸载 AOI中间件, 则在步骤 S5A40, 按照现有的方式, 在终端上向 AOI服务器发起连接。
图 5B示出了根据本发明一个实施例的用于在 AOI服务器试图唤醒终端的 过程中由 AOI服务器执行的方法的示意图。
在步骤 5B10, 从 AOI服务器向终端发送唤醒消息, 该唤醒消息用于指示 终端上的 AOI中间件建立与 AOI服务器的 IP连接。 可以通过 SMS从 AOI服 务器向终端发送该唤醒消息。
在步骤 S5B20, 在 AOI服务器上判断终端是否收到唤醒消息。 例如, 当 通过 SMS从 AOI服务器向终端发送唤醒消息时,如果终端成功接收到该 SMS 消息, 会向 AOI服务器发送短信回执, 从而 AOI服务器可以根据是否收到来 自终端的短信回执来判断终端是否收到唤醒消息。
当在 AOI服务器上判断为终端未收到唤醒消息时, 确定终端已经关机或 者不在服务区, 即确定终端不可达, 则在步骤 S5B30, 在 AOI服务器上将终 端的状态标示为终端不可达。
当在 AOI服务器上判断为终端接收到唤醒消息时, 则在步骤 S5B40, 在
AOI服务器上判断是否收到终端发送的卸载指示消息,该卸载指示消息指示在 终端上已卸载 AOI中间件。可以通过 SMS从终端向 AOI服务器发送该卸载指 示消息。
当在 AOI 服务器上判断为收到终端发送的卸载指示消息时, 在步骤 S5B50, 在 AOI服务器上将终端的状态标示为在终端上已卸载 AOI中间件。
在步骤 S5B60, 从 AOI服务器向为终端上的与 AOI中间件关联的一个或 多个应用客户端提供服务的一个或多个应用服务器发送卸载通知消息,该消息 指示在终端上已卸载 AOI中间件。
当在 AOI服务器上判断为未收到终端发送的卸载指示消息时, 在步骤 S5B70, 在 AOI服务器上按照现有的方式进行处理。
图 6A示出了根据本发明一个实施例的用于在终端向 AOI服务器发起重注 册或者说注册的过程中由 AOI服务器执行的方法的示意图。 例如, 该实施例 的实现场景可以是: 由于终端一段时间没有信号或者关机, AOI服务器将终端 重新上线或者开机时, 向 AOI服务器发起重注册请求或者说注册请求。
在步骤 S6A10, 在 AOI服务器上接收来自终端的注册请求。
在步骤 S6A20, 根据注册请求中包含的终端的标识(ID )判断在 AOI服 务器上是否保存有终端的信息, 该终端的标识例如是 IMSI摘要, 该终端的信 息包含与在终端和 AOI服务器之间建立连接有关的信息。
当在步骤 S6A20判断为在 AOI服务器上保存有终端的信息, 则进行到步 骤 S6A30, 判断在 AOI服务器上是否已将终端的状态标示为在终端上已卸载
AOI中间件。
当在步骤 S6A30判断为在 AOI服务器上已将终端的状态标示为在终端上 已卸载 AOI中间件, 则进行到步骤 S6A40, 从 AOI服务器向终端发送注册响 应, 该注册响应包含在 AOI服务器上已将终端的状态标示为在终端上已卸载 AOI 中间件的指示以及包含应用服务器列表, 其中该列表中的应用服务器是 AOI服务器已经向其通知了在终端上已卸载 AOI中间件的应用服务器。 在例 如图 1和 2所示的现有流程中,终端在重注册过程中需要向所有的应用服务器 都重新注册一遍。 然而, 在本实施例的场景下, 只有当应用服务器在终端不在 线期间向 UE发送过数据时才会从 AOI服务器处获知终端已卸载 AOI中间件, 而未发送过数据的应用服务器感知不到 AOI服务器将终端标示为已卸载 AOI 中间件, 即未发送过数据的应用服务器仍然认为终端的状态是正常的。通过在 步骤 S6A40将在 AOI服务器上标示的终端已卸载状态的指示和被通知了该终 端已卸载状态的应用服务器的列表发送给终端,终端只需要向列表中给出的应 用服务器发起重注册请求或者说注册请求, 而无需向其他未认为终端已卸载 AOI中间件的应用服务器发起重注册请求, 因此减少了网络资源的浪费。
当在步骤 S6A30判断为在 AOI服务器上未将终端的状态标示为在终端上 已卸载应用代理客户端, 即终端的状态为正常时, 则进行到步骤 S6A50, 从
AOI服务器向终端发送常规的注册响应。 这种情况下, UE可不必向应用服务 器进行重注册。
当在步骤 S6A20判断为在 AOI服务器未保存有终端的信息时,从 AOI服 务器向终端发送应答消息, 该应答消息包含在 AOI服务器上不存在终端的信 息的指示。
图 6B示出了根据本发明一个实施例的用于在终端向 AOI服务器发起重注 册或者说注册的过程中由终端执行的方法的示意图。例如, 该实施例的实现场 景可以是: 由于终端一段时间没有信号或者关机, AOI服务器将终端的状态标 或者开机时, 向 AOI服务器发起重注册请求或者说注册请求。
在步骤 S6B10, 从终端向 AOI服务器发送注册请求。
在步骤 S6B20, 在终端接收来自 AOI服务器的注册响应。
在一种情况下, 该注册响应包含在 AOI服务器上已将终端的状态标示为 在终端上已卸载 AOI中间件的指示, 以及该注册响应还包含应用服务器列表, 其中该列表中的应用服务器是 AOI服务器已经向其通知了在终端上已卸载 AOI中间件的应用服务器。 在这种情况下, 进行到步骤 S6B30, 在终端上触发 与列表中的应用服务器关联的应用客户端向列表中的相应应用服务器进行重 登录或者说重注册。根据一个实施例, 终端上的应用客户端向为其提供服务的 应用服务器发送重注册请求, 该重注册请求包含 AOI服务器分配给该应用客 户端的 Token, 该 Token用于指示应用服务器经由 AOI服务器与终端上的应 用客户端通信。 通过在步骤 S6B30终端只向列表中给出的应用服务器发起重 注册请求, 无需向其他未认为终端已卸载 AOI中间件的应用服务器发起重注 册请求, 相比于现有的重注册流程中终端需要向所有的应用服务器进行重注 册, 减少了网络资源的浪费。
在另一种情况下, 该响应消息是来自 AOI服务器的常规的注册响应。 在 这种情况下, 终端可不必再向应用服务器进行重注册请求。 需要说明的是, 实 际上在终端中没有执行步骤 S6B40, 只是为了描述的方便在图 6B中示出了该 步骤。
在另一种情况下, 该响应消息包含 AOI服务器上不存在终端的信息的指 示。 在这种情况下, 进入到步骤 S6B50, 在终端上根据该指示, 按照初始入网
的流程进行重注册过程, 例如按照图 2所示的流程进行重注册。
图 7示出了根据本发明实施例的通信装置 7000。 该装置可以是终端, 例 如图 1和 2中的终端 110或 210,也可以是在终端上实现的部件, 该部件可以 是通过程序实现的软件模块,也可以是通过硬件方式实现的硬件模块, 或者也 可以通过本领域技术人员熟知的各种实现方式来实现的功能模块。
根据一个方面, 装置 7000是关于应用代理客户端的处理装置 7000。
根据一个实施例, 装置 7000包括确定单元 7100、 发送单元 7200。 确定单 元 7100用于在终端上确定 AOI中间件被卸载, 发送单元 7200用于从终端向 与 AOI中间件对应的 AOI服务器发送卸载指示消息, 该消息指示在终端上已 卸载 AOI中间件。
根据另一个实施例, 装置 7000还包括注册单元 7300, 用于当终端具有 IP 承载时, 触发与 AOI中间件相关联的一个或多个应用客户端通过该 IP承载向 对应的一个或多个应用服务器发起注册请求。 例如, 该注册请求中不携带由 AOI服务器分配给上述一个或多个应用客户端的 Token。该 Token用于指示该 一个或多个应用服务器经由 AOI服务器与终端通信或者说与终端的该一个或 多个应用客户端通信, 当不携带该 Token时,该一个或多个应用服务器可以获 悉不经由 AOI服务器与终端的该一个或多个应用客户端通信。
根据另一个实施例, 装置 7000还包括接收单元 7500, 用于在终端上从代 理服务器接收唤醒消息。 确定单元 7100在接收单元 7500接收到唤醒消息后, 在终端上确定已卸载所述应用代理客户端。
根据另一个实施例, 装置 7000还包括判断单元 7400, 用于判断终端在卸 载 AOI中间件时是否具有 IP承载。如果判断单元 7400判断为终端在卸载 AOI 中间件时具有 IP承载, 则发送单元 7200通过该 IP承载向 AOI服务器发送卸 载指示消息; 如果判断单元 7400判断为终端在卸载 AOI中间件时不具有 IP 承载, 则发送单元 7200执行以下操作中的之一: 在终端上保存所述在终端上 已卸载 AOI中间件的指示, 并且当终端有 IP承载时, 通过该 IP承载向 AOI 服务器发送卸载指示消息;或者,通过 SMS向 AOI服务器发送卸载指示消息。
根据另一个实施例, 装置 7000包括确定单元 7100、 判断单元 7400、 发送 单元 7200和注册单元 7300。 确定单元 7100用于在终端上确定 AOI中间件被 卸载; 判断单元 7400用于判断终端在卸载 AOI中间件时是否具有 IP承载;
如果判断单元 7400判断为终端在卸载 AOI中间件时具有 IP承载, 则所述发 送单元 7200通过该 IP承载向 AOI服务器发送卸载指示消息, 该消息指示在 终端上已卸载 AOI中间件,并且注册单元 7300触发与 AOI中间件相关联的一 个或多个应用客户端向对应的一个或多个应用服务器发起注册请求,该注册请 求中不携带由 AOI服务器分配给上述一个或多个应用客户端的 Token;如果判 断单元 7400判断为终端在卸载 AOI中间件时不具有 IP承载,则发送单元 7200 在终端上向与 AOI中间件相关联的一个或多个应用客户端发送卸载指示信息, 该卸载指示信息包含在终端上已卸载 AOI中间件的指示, 并且当终端具有 IP 承载时, 注册单元 7300触发与 AOI中间件相关联的一个或多个应用客户端向 对应的一个或多个应用服务器发送注册请求, 该注册请求中不携带由 AOI服 务器分配给上述一个或多个应用客户端的 Token。 。
根据另一个方面, 装置 7000可以是用于唤醒终端的装置 7000。 根据一个 实施例, 该装置 7000包括接收单元 7500、 判断单元 7400和发送单元 7200。 接收单元 7500用于在终端上从 AOI服务器接收唤醒消息, 该唤醒消息用于指 示终端上的 AOI中间件建立与 AOI服务器的 IP连接; 判断单元 7400用于在 接收单元 7500接收唤醒消息后判断终端上是否已卸载 AOI中间件; 发送单元 7500用于如果判断单元 7400判断为在终端上已卸载 AOI中间件,则从终端向 AOI服务器发送卸载指示消息, 该消息指示在终端上已卸载 AOI中间件。
根据另一个方面, 装置 7000可以是用于进行终端重注册的装置。 根据一 个实施例, 该装置 7000包括注册单元 7300、 接收单元 7500。 注册单元 7300 用于从终端向 AOI服务器发送注册请求; 接收单元 7500用于在终端接收来自 AOI服务器的注册响应,该注册响应包含卸载指示以及应用服务器列表,该卸 载指示用于指示在 AOI服务器上已将终端的状态标示为在终端上已卸载 AOI 中间件, 该列表中的应用服务器是 AOI服务器已经向其通知了在终端上已卸 载 AOI中间件的应用服务器; 其中, 注册单元 7300在终端上触发与列表中的 应用服务器关联的应用客户端向列表中的相应的应用服务器进行注册。
根据另一个实施例, 注册单元 7300在终端上触发应用客户端向列表中的 相应的应用服务器发送注册请求, 该注册请求包含 AOI服务器分配给应用客 户端的 Token, 该 Token用于指示应用服务器经由 AOI服务器与终端通信或 者说与终端上的应用客户端通信。
图 Ί 所述实施例的装置以及该装置包括的单元可以执行如图 4Α 以及图 3A-3C、 5A和 6B所述方法实施例中的对应的步骤, 在此不再赘述。
需要说明的是, 虽然在图 7中描绘了装置 7000包括多个单元 7100-7500, 但是在不同的实施例中, 为了实现本发明, 装置 7000有可能只需要包括其中 的部分单元, 而不必包含所有示出的单元。
图 8示出了根据本发明实施例的通信装置 8000。 该装置可以是 AOI服务 器, 例如图 1和 2中的 AOI服务器 120和 220, 也可以是在 AOI服务器上实 现的部件, 该部件可以是通过程序实现的软件模块,也可以是通过硬件方式实 现的硬件模块,或者也可以通过本领域技术人员熟知的各种实现方式来实现的 功能模块。
根据一个方面,装置 8000是用于获知终端已卸载 AOI中间件的装置 8000。 根据一个实施例, 装置 8000包括接收单元 8100和标示单元 8200。 接收 单元 8100用于在 AOI服务器上从终端接收卸载指示消息, 该消息指示在终端 上已卸载 AOI中间件。 标示单元 8200用于根据接收单元 8100接收的卸载指 示消息,在 AOI服务器上将该终端的状态标示为在终端上已卸载 AOI中间件。
根据一个实施例, 装置 800还包括发送单元 8300, 用于从 AOI服务器向 为终端上的与 AOI 中间件关联的一个或多个应用客户端提供服务的一个或多 个应用服务器发送卸载通知消息, 该消息指示在终端上已卸载 AOI中间件。
根据一个实施例,发送单元 8300还用于从 AOI服务器向终端发送唤醒消 息, 该唤醒消息用于指示终端上的 AOI中间件建立与 AOI服务器的 IP连接。 接收单元 8100还用于在 AOI服务器上从终端接收响应于该唤醒消息的卸载指 示消息。
根据另一个方面, 装置 8000是一种用于唤醒终端的装置。 根据一个实施 例, 装置 8000包括发送单元 8300、 判断单元 8400和标示单元 8200。 发送单 元 8300用于从 AOI服务器向终端发送唤醒消息, 该唤醒消息用于指示终端上 的 AOI中间件建立与 AOI服务器的 IP连接; 判断单元 8400用于在 AOI服务 器上判断终端是否收到唤醒消息; 标示单元 8200用于当判断为终端没有收到 唤醒消息时, 在 AOI服务器上将终端的状态标示为终端不可达; 其中, 当判 断为终端接收到唤醒消息时, 判断单元 8400判断是否收到终端发送的卸载指 示消息, 该卸载指示消息指示在终端上已卸载 AOI 中间件; 其中, 当判断为
收到终端发送的卸载指示消息时, 标示单元 8200在 AOI服务器上将终端的状 态标示为在终端上已卸载 AOI中间件。
根据另一个实施例, 发送单元 8300还可以用于从 AOI服务器向为终端上 的与 AOI中间件关联的一个或多个应用客户端提供服务的一个或多个应用服 务器发送卸载通知消息, 该消息指示在终端上已卸载 AOI中间件。
根据另一个方面, 装置 8000是用于进行终端重注册的装置。 根据一个实 施例, 该装置 8000包括接收单元 8100、 判断单元 8400和发送单元 8300。 接 收单元 8100用于在 AOI服务器上接收来自终端的注册请求; 判断单元 8400 用于根据该注册请求中包含的终端的标识(ID )判断在 AOI服务器上是否保 存有该终端的信息, 如果判断为在 AOI服务器上保存有该终端的信息, 则判 断在 AOI服务器上是否已将该终端的状态标示为在终端上已卸载 AOI中间件; 发送单元 8300用于如果判断单元 8400判断为在 AOI服务器上已将终端的状 态标示为在终端上已卸载 AOI中间件,则从 AOI服务器向终端发送注册响应, 该注册响应包含在 AOI服务器上已将终端的状态标示为在终端上已卸载 AOI 中间件的指示以及应用服务器列表, 其中该列表中的应用服务器是 AOI服务 器已经向其通知了在终端上已卸载 AOI中间件的应用服务器。
根据另一个实施例, 发送单元 8300还用于当判断为在 AOI服务器上未保 存有该终端的信息时, 从 AOI服务器向该终端发送应答消息, 该应答消息包 含在 AOI服务器上不存在该终端的信息的指示。
图 8 所述实施例的装置以及该装置包括的单元可以执行如图 4B 以及图
5B和 6A所述方法实施例中的对应的步骤, 在此不再赘述。
需要说明的是, 虽然在图 8中描绘了装置 8000包括多个单元 8100-8400, 但是在不同的实施例中, 为了实现本发明, 装置 8000有可能只需要包括其中 的部分单元, 而不必包含所有示出的单元。
图 7和 8中的各个单元可以包括处理器、电子设备、硬件设备、电子部件、 逻辑电路、 存储器、 或其任意组合等, 或者可以用上述设备实现。 本领域技术 人员应该理解,图 7-8中所示的各个单元可以执行上文中结合图 3A-6B所描述 的方法中的相应处理过程。
图 9示出了根据本发明实施例的通信设备 9000, 该通信设备可以是适用 于本发明的终端或代理服务器, 该代理服务器例如是 AOI服务器或 Push服务
哭
通信设备 9000包括通过总线 9400相连的各个部件, 例如处理器 9300、 存储器 9100和收发机 9200。 存储器 9100中可以存储数据 9110和指令 9120。 处理器 9300可以通过执行该指令 9120以及使用该数据 9110实现本发明所公 开的装置。 收发机 9200包含发射机 9210和接收机 9220, 以允许在通信设备 和其他通信设备之间发送和接收信号。
根据一个实施例, 图 9所示的通信设备可以是终端, 其包括处理器 9300 和与该处理器相连的存储器 9100, 该处理器配置为: 在终端上确定应用代理 客户端被卸载;从终端向与应用代理客户端对应的代理服务器发送卸载指示消 息, 该消息指示在终端上已卸载所述应用代理客户端。
本领域技术人员应该理解,该处理器还可以进一步配置为进行上文中结合 图 3A-3C、 4A、 5A和 6B所描述的各个实施例中的操作。
根据一个实施例, 图 9所示的通信设备可以是代理服务器, 其包括处理器 9300和与该处理器相连的存储器 9100 , 该处理器配置为: 在代理服务器上从 终端接收卸载指示消息, 该消息指示在终端上已卸载应用代理客户端; 在代理 服务器上将该终端的状态标示为在终端上已卸载应用代理客户端。本领域技术 人员应该理解,该处理器还可以进一步配置为进行上文中结合图 4B、 5B和 6A 所描述的各个实施例中的操作。
本领域技术人员应该理解,图 9中所示无线通信设备中,通过处理器 9300 执行存储器 9100中存储的程序, 可以执行上文中结合图 3A-6B所描述的流程 以及结合图 7-8所描述的装置中的相应处理过程。
本发明的实施例还可以实现为计算机程序 ,该计算机程序当执行时可以实 现上文中结合图 3A-6B所描述的各种方法流程。
本发明的实施例还可以实现为机器可读介质, 其上存储有可执行指令, 当 该可执行指令被执行时, 使得机器执行上文中结合图 3A-6B所描述的各种方 法流程。
本文所描述的装置的步骤可直接体现为硬件、由处理器执行的软件或两者 的组合,软件可以位于存储介质中。本发明的技术方案本质上或者说对现有技 术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现 出来, 该计算机软件产品存储在一个存储介质中, 包括若干指令用以使得一台
计算机设备(可以是个人计算机, 服务器, 或者网络设备等)执行本发明各个 实施例该装置的全部或部分步骤。 而前述的存储介质包括: U盘、 移动硬盘、 只读存储器(ROM, Read-Only Memory )、 随机存取存储器 ( RAM, Random Access Memory ) 、 磁碟或者光盘等各种可以存储程序代码的介质。 本发明的 技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或 部分可以以硬件产品的形式体现出来, 例如通过本领域熟知的专用集成电路 ( ASIC, Application Specific Integrated Circuit )、 现场可编程门阵列 (FPGA, Field Programmable Gate Array ) 、 复杂可编程逻辑器件 (CPLD , Complex Programmable Logic Device)等技术来将本发明技术方案实现为专用的硬件模 块。
值得注意的是, 上述终端和服务器的实施例中, 所包括的各个单元只是按 照功能逻辑进行划分的,但并不局限于上述的划分, 只要能够实现相应的功能 即可; 另外, 各功能单元的具体名称也只是为了便于相互区分, 并不用于限制 本发明的保护范围。
为了使本领域的任何技术人员能够实现或使用本发明,在上文提供了本发 明具体实施例的描述。 然而,对本发明实施例所作出的符合本发明总体原理的 各种修改也包含在本发明的保护范围内。
Claims
1、 一种关于应用代理客户端的处理方法, 其特征在于, 所述方法包括: 在终端上确定所述应用代理客户端被卸载;
从所述终端向与所述应用代理客户端对应的代理服务器发送卸载指示消 息, 该卸载指示消息指示在所述终端上已卸载所述应用代理客户端。
2、 如权利要求 1所述的方法, 其特征在于, 所述方法进一步包括: 当所述终端具有互联网协议 IP承载时, 触发与所述应用代理客户端相关 联的一个或多个应用客户端通过所述 IP 7 载向对应的一个或多个应用月良务器 发起注册请求, 其中, 所述注册请求中不携带由所述代理服务器分别分配给所 述一个或多个应用客户端的令牌,所述令牌用于指示所述一个或多个应用服务 器经由所述代理服务器与所述终端通信。
3、 如权利要求 1所述的方法, 其特征在于, 所述方法进一步包括: 在所 述终端上从所述代理服务器接收唤醒消息,
其中, 所述在所述终端上确定所述应用代理客户端被卸载具体为: 接收到 所述唤醒消息后, 在所述终端上确定已卸载所述应用代理客户端。
4、 如权利要求 1所述的方法, 其特征在于, 所述方法进一步包括: 在终 端上确定所述应用代理客户端被卸载后,在所述终端上保存在所述终端上已卸 载所述应用代理客户端的指示;
所述方法进一步包括: 在所述终端上从所述代理服务器接收唤醒消息; 其中 ,所述从所述终端向与所述应用代理客户端对应的代理服务器发送卸 载指示消息具体为: 在所述终端上从所述代理服务器接收唤醒消息后,根据所 保存的在所述终端上已卸载所述应用代理客户端的指示,从所述终端向与所述 应用代理客户端对应的代理服务器发送卸载指示消息。
5、 如权利要求 1到 4中的一个所述的方法, 其特征在于, 所述从所述终 端向与所述应用代理客户端对应的代理服务器发送卸载指示消息包括:
在确定所述终端在卸载所述应用代理客户端时具有 IP承载的情况下, 通 过该 IP承载向所述代理服务器发送所述卸载指示消息;
如果所述终端在卸载所述应用代理客户端时不具有 IP承载, 则在所述终 端上保存所述在所述终端上已卸载所述应用代理客户端的指示,并且当所述终 端有 IP承载时, 通过该 IP承载向所述代理服务器发送所述卸载指示消息。
6、 如权利要求 1到 4中的一个所述的方法, 其特征在于, 所述从所述终 端向与所述应用代理客户端对应的代理服务器发送卸载指示消息包括:
通过短信服务 SMS向所述代理服务器发送所述卸载指示消息; 或者 在确定所述终端在卸载所述应用代理客户端时不具有 IP承载的情况下, 在所述终端上保存所述在所述终端上已卸载所述应用代理客户端的指示,并且 当所述终端有 IP承载时, 通过该 IP承载向所述代理服务器发送所述卸载指示 消息。
7、 一种用于获知在终端上已卸载应用代理客户端的方法, 其特征在于, 所述方法包括:
在代理服务器上从所述终端接收卸载指示消息,该卸载指示消息指示在所 述终端上已卸载所述应用代理客户端;
根据所述卸载指示消息在所述代理服务器上将所述终端的状态标示为在 所述终端上已卸载所述应用代理客户端。
8、 如权利要求 7所述的方法, 其特征在于, 所述方法进一步包括: 根据所述卸载指示消息从所述代理服务器向一个或多个应用服务器发送 卸载通知消息,所述一个或多个应用服务器是为一个或多个应用客户端提供服 务的服务器,所述一个或多个应用客户端在所述终端上与所述应用代理客户端 相关联, 所述卸载通知消息指示在所述终端上已卸载所述应用代理客户端。
9、 如权利要求 7或 8所述的方法, 其特征在于, 所述方法进一步包括: 从所述代理服务器向所述终端发送唤醒消息;
所述在所述代理服务器上从所述终端接收卸载指示消息具体为:在所述代
理服务器上从所述终端接收响应于所述唤醒消息的所述卸载指示消息。
10、 如权利要求 7到 9中的一个所述的方法, 其特征在于, 所述在代理服 务器上从所述终端接收卸载指示消息具体为:在所述代理服务器上通过互联网 协议 IP承载或短信服务 SMS从所述终端接收卸载指示消息。
11、 一种用于唤醒终端的方法, 其特征在于, 所述方法包括:
从代理服务器向终端发送唤醒消息;
在所述代理服务器上判断所述终端是否收到所述唤醒消息;
当判断为所述终端没有收到所述唤醒消息时 ,在所述代理服务器上将所述 终端的状态标示为终端不可达;
当判断为所述终端接收到所述唤醒消息时,在所述代理服务器上判断是否 收到所述终端发送的卸载指示消息,所述卸载指示消息包含在所述终端上已卸 载所述应用代理客户端的指示;
当判断为收到所述终端发送的所述卸载指示消息时,在所述代理服务器上
12、 一种用于终端重注册的方法, 其特征在于, 所述方法包括: 在代理服务器上接收来自所述终端的注册请求;
根据所述注册请求中包含的所述终端的标识 ID判断在所述代理服务器上 是否保存有所述终端的信息;
如果判断为在所述代理服务器上保存有所述终端的信息,则判断在所述代 户端;
如果判断为在所述代理服务器上已将所述终端的状态标示为在所述终端 上已卸载应用代理客户端,从所述代理服务器向所述终端发送注册响应, 该注 册响应包含卸载指示以及应用服务器列表, 其中, 所述卸载指示用于指示在所 述代理服务器上已将所述终端的状态标示为在所述终端上已卸载应用代理客 户端,所述列表中的应用服务器是已被所述代理服务器通知了在所述终端上已 卸载应用代理客户端的应用服务器。
13、 如权利要求 12所述的方法, 其特征在于, 所述方法进一步包括: 当判断为在所述代理服务器上未保存有所述终端的信息时,从所述代理服 务器向所述终端发送应答消息,该应答消息包含在所述代理服务器上不存在所 述终端的信息的指示。
14、 一种用于终端重注册的方法, 其特征在于, 所述方法包括: 从所述终端向代理服务器发送注册请求;
在所述终端上接收来自所述代理服务器对所述注册请求的注册响应,该注 册响应包含卸载指示以及应用服务器列表, 其中, 所述卸载指示用于指示在所 述代理服务器上已将所述终端的状态标示为在所述终端上已卸载应用代理客 户端,所述列表中的应用服务器是已被所述代理服务器通知了在所述终端上已 卸载应用代理客户端的应用服务器;
在所述终端上触发与所述列表中的应用服务器关联的应用客户端向所述 列表中的相应的应用服务器进行注册。
15、 如权利要求 14所述的方法, 其特征在于, 所述在所述终端上触发与 所述列表中的应用服务器关联的应用客户端向相应的应用服务器进行注册包 括:
所述应用客户端向所述相应的应用服务器发送应用注册请求,该应用注册 请求包含所述代理服务器分配给所述应用客户端的令牌,所述令牌用于指示所 述应用服务器经由所述代理服务器与所述终端上的所述应用客户端通信。
16、 如权利要求 1到 15中的一个所述的方法, 其特征在于, 所述代理服 务器是始终在线构架 AOI服务器和推送 PUSH服务器中的至少之一, 所述应 用代理客户端是 AOI中间件和推送客户端中的至少之一。
17、 一种关于应用代理客户端的处理装置, 其特征在于, 所述装置包括: 确定单元, 用于在终端上确定所述应用代理客户端被卸载;
发送单元,用于从所述终端向与所述应用代理客户端对应的代理服务器发
送卸载指示消息,该卸载指示消息指示在所述终端上已卸载所述应用代理客户 端。
18、 如权利要求 17所述的装置, 其特征在于, 所述装置进一步包括: 注册单元, 用于当所述终端具有互联网协议 IP承载时, 触发与所述应用 代理客户端相关联的一个或多个应用客户端通过所述 IP 7 载向对应的一个或 多个应用服务器发起注册请求, 其中, 所述注册请求中不携带由所述代理服务 器分别分配给所述一个或多个应用客户端的令牌,所述令牌用于指示所述一个 或多个应用服务器经由所述代理服务器与所述终端的所述一个或多个应用客 户端通信。
19、 如权利要求 17所述的装置, 其特征在于, 所述装置进一步包括接收 单元, 用于在所述终端上从所述代理服务器接收唤醒消息,
其中, 所述确定单元具体用于: 在所述接收单元接收到所述唤醒消息后, 在所述终端上确定已卸载所述应用代理客户端。
20、 如权利要求 17所述的装置, 其特征在于, 所述确定单元进一步用于: 在终端上确定所述应用代理客户端被卸载后,在所述终端上保存在所述终端上 已卸载所述应用代理客户端的指示;
所述装置进一步包括接收单元,用于在所述终端上从所述代理服务器接收 唤醒消息;
其中, 所述发送单元具体用于: 在所述接收单元从所述代理服务器接收唤 醒消息后,根据所保存的在所述终端上已卸载所述应用代理客户端的指示,从 所述终端向与所述应用代理客户端对应的代理服务器发送卸载指示消息。
21、 如权利要求 17到 20中的一个所述的装置, 其特征在于, 所述装置进 一步包括判断单元,用于判断所述终端在卸载所述应用代理客户端时是否具有 IP承载;
其中, 所述发送单元具体用于:
在所述判断单元判断所述终端在卸载所述应用代理客户端时具有 IP承载
时, 通过该 IP承载向所述代理服务器发送所述卸载指示消息。
22、 如权利要求 17到 20中的一个所述的装置, 其特征在于, 所述装置进 一步包括判断单元,用于判断所述终端在卸载所述应用代理客户端时是否具有 IP承载;
其中, 所述发送单元具体用于:
通过短信服务 SMS向所述代理服务器发送所述卸载指示消息, 或者, 在 所述判断单元判断所述终端在卸载所述应用代理客户端时不具有 IP承载时, 在所述终端上保存所述在所述终端上已卸载所述应用代理客户端的指示,并且 当所述终端有 IP承载时, 通过该 IP承载向所述代理服务器发送所述卸载指示 消息。
23、 一种用于获知在终端上已卸载应用代理客户端的装置, 其特征在于, 所述装置包括:
接收单元, 用于在代理服务器上从所述终端接收卸载指示消息, 该卸载指 示消息指示在所述终端上已卸载所述应用代理客户端;
标示单元,用于根据所述接收单元接收的所述卸载指示消息在所述代理服 务器上将所述终端的状态标示为在所述终端上已卸载所述应用代理客户端。
24、 如权利要求 23所述的装置, 其特征在于, 所述装置进一步包括: 发送单元,用于根据所述卸载指示消息从所述代理服务器向一个或多个应 用服务器发送卸载通知消息,所述一个或多个应用服务器是为一个或多个应用 客户端提供服务的服务器,所述一个或多个应用客户端在所述终端上与所述应 用代理客户端相关联,所述卸载通知消息指示在所述终端上已卸载所述应用代 理客户端。
25、 如权利要求 23或 24所述的装置, 其特征在于,
所述发送单元进一步用于从所述代理服务器向所述终端发送唤醒消息; 所述接收单元具体用于在所述代理服务器上从所述终端接收响应于所述 唤醒消息的所述卸载指示消息。
26、 如权利要求 23到 25中的一个所述的装置, 其特征在于, 所述接收单 元具体用于通过互联网协议 IP承载或短信服务 SMS从所述终端接收卸载指示 消息。
27、 一种用于唤醒终端的装置, 其特征在于, 所述装置包括:
发送单元, 用于从代理服务器向终端发送唤醒消息;
判断单元, 用于在所述代理服务器上判断所述终端是否收到所述唤醒消 息;
标示单元, 用于当判断为所述终端没有收到所述唤醒消息时,在所述代理 服务器上将所述终端的状态标示为终端不可达;
其中, 当判断为所述终端接收到所述唤醒消息时, 所述判断单元判断是否 收到所述终端发送的卸载指示消息,所述卸载指示消息包含在所述终端上已卸 载所述应用代理客户端的指示;
其中, 当判断为收到所述终端发送的所述卸载指示消息时, 所述标示单元 在所述代理服务器上将所述终端的状态标示为在所述终端上已卸载所述应用 代理客户端。
28、 一种用于进行终端重注册的装置, 其特征在于, 所述装置包括: 接收单元, 用于在代理服务器上接收来自所述终端的注册请求; 判断单元, 用于根据所述注册请求中包含的所述终端的标识 ID判断在所 述代理服务器上是否保存有所述终端的信息,如果判断为在所述代理服务器上 保存有所述终端的信息,则判断在所述代理服务器上是否已将所述终端的状态 标示为在所述终端上已卸载应用代理客户端;
发送单元,用于在所述判断单元判断在所述代理服务器上已将所述终端的 状态标示为在所述终端上已卸载应用代理客户端时,从所述代理服务器向所述 终端发送注册响应, 该注册响应包含卸载指示以及应用服务器列表, 其中, 所 述卸载指示用于指示在所述代理服务器上已将所述终端的状态标示为在所述 终端上已卸载应用代理客户端,所述列表中的应用服务器是已被所述代理服务 器通知了在所述终端上已卸载应用代理客户端的应用服务器。
29、 如权利要求 28所述的装置, 其特征在于,
所述发送单元进一步用于,当判断为在所述代理服务器上未保存有所述终 端的信息时,从所述代理服务器向所述终端发送应答消息, 该应答消息包含在 所述代理服务器上不存在所述终端的信息的指示。
30、 一种用于进行终端重注册的装置, 其特征在于, 所述装置包括: 注册单元, 用于从所述终端向代理服务器发送注册请求;
接收单元,用于在所述终端接收来自所述代理服务器对所述注册请求的注 册响应, 该注册响应包含卸载指示以及应用服务器列表, 其中, 所述卸载指示 用于指示在所述代理服务器上已将所述终端的状态标示为在所述终端上已卸 载应用代理客户端,所述列表中的应用服务器是已被所述代理服务器通知了在 所述终端上已卸载应用代理客户端的应用服务器; 关联的应用客户端向所述列表中的相应的应用服务器进行注册。
31、 如权利要求 30所述的装置, 其特征在于, 所述注册单元具体用于在 所述终端上触发所述应用客户端向所述列表中的所述相应的应用服务器发送 应用注册请求,该应用注册请求包含所述代理服务器分配给所述应用客户端的 令牌,所述令牌用于指示所述应用服务器经由所述代理服务器与所述终端上的 所述应用客户端通信。
32、 如权利要求 17到 31中的一个所述的装置, 其特征在于, 所述代理服 务器是始终在线构架 AOI服务器和推送 PUSH服务器中的至少之一, 所述应 用代理客户端是 AOI中间件和推送客户端中的至少之一。
33、 一种通信装置, 包括
存储器, 用于存储数据及指令;
处理器, 与所述存储器耦合,根据所述存储器中的所述数据及指令执行权 利要求 1到 16中的一个所述的方法。
34、 一种计算机程序产品, 包括计算机可执行指令, 所述指令当被所述计 算机执行时用于实现权利要求 1到 16中的一个所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP13804333.6A EP2854430B1 (en) | 2012-06-15 | 2013-06-17 | Method and device for processing abnormality of application proxy client terminal |
US14/569,082 US10069671B2 (en) | 2012-06-15 | 2014-12-12 | Method and apparatus for processing abnormality of application proxy client |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210201580.1A CN103517250B (zh) | 2012-06-15 | 2012-06-15 | 用于处理应用代理客户端异常的方法和装置 |
CN201210201580.1 | 2012-06-15 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/569,082 Continuation US10069671B2 (en) | 2012-06-15 | 2014-12-12 | Method and apparatus for processing abnormality of application proxy client |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013185642A1 true WO2013185642A1 (zh) | 2013-12-19 |
Family
ID=49757548
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/077307 WO2013185642A1 (zh) | 2012-06-15 | 2013-06-17 | 用于处理应用代理客户端异常的方法和装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10069671B2 (zh) |
EP (1) | EP2854430B1 (zh) |
CN (1) | CN103517250B (zh) |
WO (1) | WO2013185642A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106452878B (zh) * | 2016-10-19 | 2019-09-10 | 北京悦畅科技有限公司 | 一种局域网中服务切换方法、装置和系统 |
CN107480179B (zh) * | 2017-07-04 | 2020-06-16 | 阿里巴巴集团控股有限公司 | 检测方法及装置和电子设备 |
CN107819871B (zh) * | 2017-11-22 | 2020-12-25 | 北京小米移动软件有限公司 | 应用状态确定方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050228848A1 (en) * | 2004-03-22 | 2005-10-13 | Thurston Stacy D | Method and system for operating a peer network |
CN102223257A (zh) * | 2011-07-25 | 2011-10-19 | 莫雅静 | 一种心跳间隔调整方法、服务器、客户端及通信系统 |
CN102395119A (zh) * | 2011-11-15 | 2012-03-28 | 华为技术有限公司 | 一种支持应用客户端永久在线的方法、系统及装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030061333A1 (en) * | 2001-05-04 | 2003-03-27 | Stephen Dean | System and method for universal networked device management |
JP4756994B2 (ja) * | 2005-10-27 | 2011-08-24 | キヤノン株式会社 | ネットワークプリントシステム及びネットワーク周辺装置及び情報処理装置とプログラム |
US8862746B2 (en) * | 2006-05-17 | 2014-10-14 | Sonim Technologies, Inc. | Systems and methods for integrating applications on user equipment utilizing special URI control messages |
US8364123B2 (en) * | 2009-02-25 | 2013-01-29 | Apple Inc. | Managing notification messages |
CN101662478B (zh) | 2009-09-18 | 2012-08-08 | 深圳市万兴软件有限公司 | 一种软件下载、安装和卸载的跟踪方法及系统 |
US8561055B2 (en) * | 2009-10-15 | 2013-10-15 | Blackberry Limited | Method, system and apparatus for management of push content |
CN102469124B (zh) * | 2010-11-09 | 2015-08-12 | 中兴通讯股份有限公司 | 基于aog的移动互联网业务的实现方法、网关、代理及系统 |
US8909792B2 (en) * | 2010-11-12 | 2014-12-09 | Socialware, Inc. | Method, system, and computer program product for identifying and tracking social identities |
-
2012
- 2012-06-15 CN CN201210201580.1A patent/CN103517250B/zh active Active
-
2013
- 2013-06-17 WO PCT/CN2013/077307 patent/WO2013185642A1/zh unknown
- 2013-06-17 EP EP13804333.6A patent/EP2854430B1/en active Active
-
2014
- 2014-12-12 US US14/569,082 patent/US10069671B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050228848A1 (en) * | 2004-03-22 | 2005-10-13 | Thurston Stacy D | Method and system for operating a peer network |
CN102223257A (zh) * | 2011-07-25 | 2011-10-19 | 莫雅静 | 一种心跳间隔调整方法、服务器、客户端及通信系统 |
CN102395119A (zh) * | 2011-11-15 | 2012-03-28 | 华为技术有限公司 | 一种支持应用客户端永久在线的方法、系统及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2854430A4 * |
Also Published As
Publication number | Publication date |
---|---|
US10069671B2 (en) | 2018-09-04 |
EP2854430B1 (en) | 2020-01-15 |
EP2854430A1 (en) | 2015-04-01 |
CN103517250A (zh) | 2014-01-15 |
EP2854430A4 (en) | 2015-12-23 |
US20150100690A1 (en) | 2015-04-09 |
CN103517250B (zh) | 2017-10-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9571952B2 (en) | Offloading of data to wireless local area network | |
EP3226481B1 (en) | Method for heartbeat packet processing by using proxy, apparatus, and communications system | |
WO2018112897A1 (zh) | 一种会话激活方法及装置和系统 | |
CN107637049B (zh) | 操作客户端设备的方法和操作服务器的方法 | |
JP2023065402A (ja) | 再開要求の拒否に伴うue挙動 | |
JP2019525553A (ja) | 低頻度の小さいデータのための効率的な送達方法および装置 | |
WO2018045810A1 (zh) | 一种基于csfb的主叫方法及装置 | |
WO2021096411A1 (en) | Integrity protection of radio resource control message | |
US9693265B2 (en) | Method and apparatus for mobile terminal mobility | |
JP5768017B2 (ja) | 通信端末、通信方法および通信プログラム | |
WO2013185642A1 (zh) | 用于处理应用代理客户端异常的方法和装置 | |
WO2017128185A1 (zh) | 控制服务连接的方法和终端 | |
US8838775B2 (en) | Release of resources in a communication system | |
WO2022143070A1 (zh) | 一种通信方法和通信系统 | |
US12114392B2 (en) | Methods, wireless device, network node and core node for managing reachability of the wireless device | |
JP6251210B2 (ja) | 端末装置、通信セッション確立方法、及び、プログラム | |
JP6469203B2 (ja) | 端末装置、通信セッション確立方法、及び、プログラム | |
KR102090493B1 (ko) | 무선 통신 네트워크에서 http 프로토콜의 전송 지연과 http 서버의 프로세싱 부하를 줄이는 장치 및 방법 | |
WO2021006805A1 (en) | Network-based interface setup assistance | |
US9143386B1 (en) | Remote keep-alive message management in a wireless communication network | |
WO2023098993A1 (en) | Early acknowledgement for data transmitted from wireless device | |
CN111541610A (zh) | 通信方法、装置、网络设备及计算机可读存储介质 | |
JP2015181253A (ja) | 通信端末、通信方法および通信プログラム | |
KR20150052494A (ko) | 단말의 파워 세이빙 방법 및 단말 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13804333 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |