WO2010092593A1 - Détermination de la présence d'une application client - Google Patents

Détermination de la présence d'une application client Download PDF

Info

Publication number
WO2010092593A1
WO2010092593A1 PCT/IN2010/000020 IN2010000020W WO2010092593A1 WO 2010092593 A1 WO2010092593 A1 WO 2010092593A1 IN 2010000020 W IN2010000020 W IN 2010000020W WO 2010092593 A1 WO2010092593 A1 WO 2010092593A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
client application
communication device
receipt
network element
Prior art date
Application number
PCT/IN2010/000020
Other languages
English (en)
Inventor
Ram Prakash Rustagi
Raja Narayana Moorthy
Original Assignee
Kirusa Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kirusa Inc. filed Critical Kirusa Inc.
Publication of WO2010092593A1 publication Critical patent/WO2010092593A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication

Definitions

  • a simple communication acknowledgement mechanism will not work in this case since it is quite likely that the mobile device is powered off and will not receive the communication from the server side application and hence cannot send an acknowledgement.
  • the server side application needs to differentiate between phones being powered off versus a specific client being absent.
  • CTXN carrier transaction manager
  • the method and system disclosed herein address the above stated need for determining presence of a client application on a communication device in real time.
  • the method and system disclosed herein also distinguishes between communication devices being powered off and a specific client application being absent.
  • the computer implemented method disclosed herein comprises: a) generating a message by a communication server and transmitting the generated message to a messaging network element; b) rendering the generated message to the communication device by the messaging network element; c) transmitting a confirmation message to the communication server by the messaging network element on rendering the generated message to the communication device, wherein the confirmation message indicates availability of the communication device; d) awaiting an acknowledgement message from the client application on receipt of the confirmation message by the communication server; and e) determining the presence of the client application on the communication device by the communication server on receipt of the acknowledgement message from the client application via the messaging network element, wherein the messaging network element receives the acknowledgement message from the client application and renders the acknowledgement message to the communication server.
  • the communication server determines unavailability of the communication device if the communication server does not receive the confirmation message from the messaging network element within a predefined period of time.
  • the communication server determines absence of the client application on the communication device if the communication server receives the confirmation message but does not receive an acknowledgement message from the client application within a predefined period of time.
  • the communication server configures timeout parameters that enable determination of receipt of the confirmation message from the messaging network element and receipt of the acknowledgement message from the client application.
  • the client application may be implemented on one or more hardware components, operating systems, development platforms, and runtime environments.
  • FIG. 1 illustrates a method for determining presence of a client application on a communication device.
  • FIG. 2 illustrates a system for determining presence of a client application on a communication device.
  • FIG. 3 exemplarily illustrates a computer system employed for determining the presence of a client application on a communication device.
  • FIGS. 4A-4B exemplarily illustrate a flowchart comprising the steps of determining the presence of a client application on a communication device.
  • FIG. 1 illustrates a method for determining presence of a client application on a communication device.
  • the communication device is, for example, a personal computer, a laptop, a mobile phone with internet capabilities, a personal digital assistant (PDA), etc.
  • client application refers to an application installed on the communication device for performing one or more specific functions.
  • a communication server generates 101 a message.
  • the term "communication server” refers to any combination of hardware and software designed to provide services to clients.
  • the message is, for example, a short message service (SMS) message.
  • SMS short message service
  • the communication server transmits 102 the generated message to a messaging network element.
  • the messaging network element is, for example, a short message service center (SMSC) which is a network element in a mobile telephone network that delivers SMS messages.
  • SMS short message service center
  • the messaging network element renders 103 the generated message to the communication device.
  • the messaging network element generates a confirmation message and transmits 104 the generated confirmation message to the communication server on rendering the message generated by the communication server to the communication device.
  • the confirmation message is transmitted, for example, using a short message peer-to-peer (SMPP) protocol.
  • SMPP short message peer-to-peer
  • the confirmation message indicates the availability of the communication device.
  • availability of the communication device refers to the communication device being reachable and contactable by, for example, a mobile communication service provider.
  • the communication server determines availability of the communication device on receipt of the confirmation message from the messaging network element within a predefined period of time.
  • the generated message is configured to expire after a predefined period of time.
  • the communication device may be unavailable, for example, due to the communication device being out of range of the mobile communication service provider, the communication device being switched off, etc.
  • the communication server determines the unavailability of the communication device on non-receipt of the confirmation message from the messaging network element within the predefined period of time.
  • the communication server awaits 105 an acknowledgement message from the client application on receipt of the confirmation message.
  • the client application on receiving the message generated by the communication server from the messaging network element generates an acknowledgement message and transmits the acknowledgement message to the communication server via the messaging network element.
  • the messaging network element receives the acknowledgement message from the client application and renders the acknowledgement message to the communication server.
  • the acknowledgement message is transmitted, for example, using a short message peer-to-peer (SMPP) protocol.
  • the communication server determines 106 the presence of the client application on the communication device on receipt of the acknowledgement message from the client application via the messaging network element.
  • the configuration of the communication server comprises two or more timeout parameters.
  • the first timeout parameter is a timeout value, for example, in seconds, minutes, hours, days, etc.
  • the second timeout parameter is a timeout value, for example, in seconds, minutes, hours, days, etc. for receiving the acknowledgement message from the client application.
  • the timeout parameters need to be defined explicitly or assumed implicitly by the implementation of the communication server.
  • FIG. 2 illustrates a system 200 for determining presence of a client application 209 on a communication device 208.
  • the system 200 comprises a communication server 201 and a messaging network element 207.
  • the communication server 201 comprises a messaging module 202, a message waiting module 203, an availability determination module 204, a presence determination module 205, and a timer module 206.
  • the messaging module 202 generates a message and transmits the generated message to the messaging network element 207.
  • the messaging network element 207 renders the generated message to a communication device 208, for example, a mobile phone.
  • the messaging network element 207 then generates a confirmation message and transmits the generated confirmation message to the communication server 201.
  • the message waiting module 203 of the communication server 201 awaits the confirmation message from the messaging network element 207.
  • the availability determination module 204 of the communication server 201 determines the availability of the communication device 208 on receipt of the confirmation message from the messaging network element 207 within a predefined period of time. In case of non-receipt of the confirmation message within the predefined period of time, the availability determination module 204 determines unavailability of the communication device 208.
  • the message waiting module 203 of the communication server 201 awaits an acknowledgement message from the client application 209 on receipt of the confirmation message.
  • a message processing engine 209a on the client application 209 generates the acknowledgement message and transmits the generated acknowledgement message to the communication server 201 via the messaging network element 207.
  • the messaging network element 207 receives the generated acknowledgement message from the client application 209 and renders the received acknowledgement message to the communication server 201.
  • the presence determination module 205 of the communication server 201 determines the presence of the client application 209 on the communication device 208 on receipt of the awaited acknowledgement message within a predefined period of time. In case of receipt of the confirmation message and non-receipt of the acknowledgement message within a predefined period of time, the presence determination module 205 determines absence of the client application 209 on the communication device 208.
  • the timer module 206 of the communication server 201 configures timeout parameters that enable determination of receipt of the confirmation message from the messaging network element 207 and receipt of the acknowledgement message from the client application 209 as disclosed in the detailed description of FIG. 1.
  • FIG. 3 exemplarily illustrates a computer system 300 employed for determining the presence of a client application 209 on a communication device 208 by a communication server 201.
  • the client application 209 is deployed on, for example, the computer system 300 of the communication device 208.
  • the communication server 201 may also employ the computer system 300 exemplarily illustrated in FIG. 3.
  • the communication server 201 and the communication device 208 communicate with each other via the messaging network element 207 connected to a communication network.
  • the communication network is, for example, a local area network (LAN), a wide area network (WAN), a cellular network, a satellite network, etc.
  • the computer system 300 comprises, for example, a processor 301, a memory unit 302 for storing programs and data, an input/output (I/O) controller 303, a network interface 304, a network bus 305, a display unit 306, input devices 307, a fixed media drive 308, a removable media drive 309, a baseband processor 310, etc.
  • the processor 301 is an electronic circuit that executes computer programs.
  • the memory unit 302 is used for storing programs and applications.
  • the memory unit 302 is, for example, a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by the processor 301.
  • the memory unit 302 also stores temporary variables and other intermediate information used during execution of the instructions by the processor 301.
  • the computer system 300 further comprises a read only memory (ROM) or another type of static storage device that stores static information and instructions for the processor 301.
  • the network interface 304 enables connection of the computer system 300 to the messaging network element 207 connected to a communication network
  • the network interface 304 connects the mobile computing device wirelessly to the messaging network element 207 connected to the communication network.
  • the mobile computing device further comprises a baseband processor 310 for processing communication functions and managing communication transactions with the messaging network element 207 connected to the communication network.
  • the I/O controller 303 controls the input and output actions performed by the communication server 201 and the communication device 208.
  • the network bus 305 permits communication between the modules, for example, 202, 203, 204, 205, and 206 of the communication server 201 and the message processing engine 209a of the client application 209.
  • the display unit 306 displays computed results and the input devices 307 are used for inputting data, for example, setting timeout parameters, into the computer system 300.
  • the input devices 307 are, for example, a keyboard 311 such as an alphanumeric keyboard, a joystick 312, a mouse 313, a touch pad 314, a light pen 315, etc.
  • the computer system 300 further comprises a fixed media drive 308 and a removable media drive 309 for receiving removable media.
  • Computer applications and programs are used for operating the computer system 300.
  • the programs are loaded onto the fixed media drive 308 and into the memory unit 302 of the computer system 300 via the removable media drive 309.
  • the computer applications and programs may be loaded directly through the communication network.
  • Computer applications and programs are executed by double clicking a related icon displayed on the display unit 306 using one of the input devices 307.
  • the computer system 300 of the communication server 201 and the communication device 208 employs operating systems for performing multiple tasks.
  • An operating system is responsible for the management and coordination of activities and the sharing of the resources of the computer system 300.
  • the operating system further manages security of the computer system 300, peripheral devices connected to the computer system 300, and network connections.
  • the operating system employed on the computer system 300 recognizes, for example, inputs provided using one of the input devices 307, the output display, files and directories stored locally on the fixed media drive 308, etc.
  • the operating system on the computer system 300 of the communication server 201 and the communication device 208 executes different programs initiated using the processor 301. Instructions for execution are retrieved by the processor 301 from the program memory in the form of signals. The location of the instructions in the program memory is determined by a program counter (PC).
  • PC program counter
  • the instructions fetched by the processor 301 from the program memory after being processed are decoded. After processing and decoding, the processor 301 executes the instructions.
  • the messaging module 202 of the communication server 201 defines instructions for generating a message to be transmitted to the messaging network element 207.
  • the availability determination module 204 defines instructions for determining availability or unavailability of the communication device 208 based on receipt and non-receipt of a confirmation message from the messaging network element 207 respectively.
  • the message waiting module 203 defines instructions for awaiting an acknowledgement message that indicates presence of the client application 209.
  • the timer module 206 defines instructions for configuring timeout parameters that enable determination of receipt of the confirmation message from the messaging network element 207 and receipt of the acknowledgement message from the client application 209.
  • the presence determination module 205 defines instructions for determining presence or absence of the client application 209 on the communication device 208 based on receipt and non-receipt of the acknowledgement message from the client application 209.
  • the message processing engine 209a of the client application 209 defines instructions for generating the acknowledgement message.
  • the defined instructions are stored in the program memory or received from a remote server.
  • the processor 301 on the communication server 201 retrieves the instructions defined by the messaging module 202, the message waiting module 203, the availability determination module 204, the presence determination module 205, and the timer module 206 and executes them.
  • the processor 301 on the communication device 208 retrieves the instructions defined by the message processing engine 209a and executes them.
  • the client application 209 may be implemented on operating systems for mobile devices, for example, Windows Mobile ® , Symbian, GoogleTM Android, or Apple ® iPhone. Mobile implementation uses similar algorithms but may involve different hardware interfaces.
  • FIGS. 4A-4B exemplarily illustrate a flowchart comprising the steps of determining the presence of a client application 209 on a communication device 208.
  • the communication server 201 generates 401 a message.
  • the communication server 201 transmits 402 the generated message to the messaging network element 207.
  • the messaging network element 207 scans to determine the availability of the communication device 208.
  • the messaging network element 207 renders 406 the generated message to the communication device 208.
  • the messaging network element 207 then transmits 407 a confirmation message to the communication server 201.
  • the communication server 201 determines 408 the availability of the communication device 208.
  • the messaging network element 207 discards 404 the generated message after a predefined period of time.
  • the communication server 201 determines 405 the unavailability of the communication device 208 on non-receipt of the confirmation message from the messaging network element 207 within the predefined period of time.
  • the communication server 201 awaits 409 an acknowledgement message from a client application 209 on the communication device 208 to determine 410 whether the client application 209 is present on the communication device 208. If the client application 209 is present on the communication device 208, the client application 209 generates 412 the acknowledgement message. The client application 209 then transmits 413 the generated acknowledgement message to the communication server 201 via the messaging network element 207. The communication server 201 on receipt of the transmitted acknowledgement message determines 414 the presence of the client application 209 on the communication device 208. If the client application 209 is not present on the communication device 208, the communication server 201 on receipt of the confirmation message and non-receipt of the acknowledgement message determines 411 the absence of the client application 209 from the communication device 208.
  • the communication server 201 determines the absence of the client application 209 on the communication device 208 on receipt of the confirmation message and non-receipt of the awaited acknowledgement message from the client application 209 within a predefined period of time.
  • the client application 209 may be absent from the communication device 208, for example, due to deletion or disabling of the client application 209. If the client application 209 is absent from the communication device 208, the communication server 201 may choose an alternative method of communicating with the communication device 208.
  • the communication server 201 communicates with the communication device 208 directly, for example, by transmitting a typical SMS message to the communication device 208, instead of sending a client specific SMS message.
  • the communication server 201 transmits an alert signal to the communication device 208.
  • the communication device 208 on receiving the SMS message or the alert signal, acts as per the device implementation. The end user, for example, a subscriber, may be informed of the communication.
  • a client application 209 for example, a web browser is installed on a communication device 208, for example, a mobile phone, of a user.
  • the client application 209 asynchronously communicates with the communication server 201, for example, a web server, via the messaging network element 207.
  • the communication server 201 If the communication server 201 chooses to determine the presence of the client application 209 on the communication device 208, the communication server 201 generates a message and transmits the generated message to the messaging network element 207.
  • the messaging network element 207 scans for the availability of the communication device 208. In a mobile/cellular network, the availability of the communication device 208 is known to the messaging network element 207 because the communication device 208 is connected to the messaging networking element 207 using, for example, radio signaling.
  • the messaging network element 207 is informed regarding the on/off state of the communication device 208 as per the established communication protocol between the communication device 208 and the messaging network element 207.
  • the messaging network element 207 renders the generated message to the communication device 208.
  • the messaging network element 207 then ' generates a confirmation message and transmits the generated confirmation message to the communication server 201 to indicate to the communication server 201 that the communication device 208 is available and the generated message has been rendered to the communication device 208.
  • the communication device 208 then awaits an acknowledgement message from the client application 209.
  • the client application 209 present on the communication device 208 now generates the acknowledgement message and transmits the generated acknowledgement message to the communication server 201 via the messaging network element 207.
  • the communication server 201 on receipt of the transmitted acknowledgement message determines presence of the client application 209 on the communication device 208.
  • a client application 209 is installed on communication device 208, for example, a mobile phone of a user, but the user has switched off the user's mobile phone.
  • the communication server 201 generates a message and transmits the generated message to the messaging network element 207.
  • the messaging network element 207 scans to determine the availability of the user's mobile phone for rendering the generated message to the user's mobile phone.
  • the messaging network element 207 determines the unavailability of the user ' s mobile phone since the user's mobile phone is switched off and discards the generated message after a predefined period of time.
  • the mobile phone's radio connectivity with the messaging network element 207 is broken. Therefore, in the absence of radio network connectivity between the communication device 208 and the messaging network element 207, the messaging network element 207 determines that the communication device 208 is not available.
  • the communication server 201 on non-receipt of a confirmation message from the messaging network element 207 determines the unavailability of the mobile phone after the predefined period of time.
  • the communication server 201 generates a message and transmits the generated message to the messaging network element 207.
  • the messaging network element 207 scans to determine the availability of the user's mobile phone and renders the generated message to the user's mobile phone.
  • the messaging network element 207 then generates a confirmation message and transmits the generated confirmation message to the communication server 201.
  • the communication server 201 determines presence of the mobile phone on receipt of the confirmation message.
  • the communication server 201 now awaits an acknowledgement message from the client application 209 via the messaging network element 207.
  • the communication server 201 determines absence of the client application 209 on non- receipt of the acknowledgement message after a predefined period of time. The communication server 201 then chooses an alternative method of communicating with the communication device 208.
  • the method and system 200 disclosed herein is applicable to the client application 209 and the communication server 201 implemented, for example, on multiple hardware components, multiple operating systems, development platforms, runtime environments, etc.
  • the hardware may be implemented on, for example, UNIX, Linux or its variants, Windows Server software, Mainframe, Mini and microcomputers, etc.
  • the client application 209 may be implemented on platforms, for example, JavaTM, BREW, MicrosoftTM, the iPhone ® of Apple Inc., etc. independently or in any combination thereof.
  • the method and system 200 disclosed herein uses SMS based communication
  • the method and system 200 disclosed herein may also be implemented in any communication setup using, for example, the communication server 201, a communication network, a client server, and the client application 209 using asynchronous communication.
  • a processor for example, one or more microprocessors will receive instructions from a memory or like device, and execute those instructions, thereby performing one or more processes defined by those instructions.
  • programs that implement such methods and algorithms may be stored and transmitted using a variety of media, for example, computer readable media in a number of manners.
  • the computer readable media has stored thereon multiple sequences of instructions which, when executed by a processor, cause the processor to perform the method disclosed herein.
  • hardwired circuitry or custom hardware may be used in place of, or in combination with, software instructions for implementation of the processes of various embodiments.
  • a “processor” means any one or more microprocessors, central processing unit (CPU) devices, computing devices, microcontrollers, digital signal processors or like devices.
  • Non volatile media include, for example, optical or magnetic disks and other persistent memory volatile media include dynamic random access memory (DRAM), which typically constitutes the main memory.
  • Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor.
  • Computer readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a compact disc-read only memory (CD-ROM), digital versatile disc (DVD), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a random access memory (RAM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a flash memory, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
  • the computer readable programs may be implemented in any programming language.
  • a computer program product comprising computer executable instructions embodied in a computer readable medium comprises computer parsable codes for the implementation of the processes of various embodiments.
  • the present invention can be configured to work in a network environment including a computer that is in communication, via a communications network, with one or more devices.
  • the computer may communicate with the devices directly or indirectly, via a wired or wireless medium such as the Internet, Local Area Network (LAN), Wide Area Network (WAN) or Ethernet, Token Ring, or via any appropriate communications means or combination of communications means.
  • Each of the devices may comprise computers, such as those based on the Intel ® processors, AMD ® processors, UltraSPARC ® processors, Sun ® processors, IBM ® processors, etc. that are adapted to communicate with the computer. Any number and type of machines may be in communication with the computer.

Abstract

L'invention concerne un procédé et un système permettant de déterminer la présence d'une application client (209) sur un dispositif de communication (208). Un serveur de communication (201) génère un message et transmet le message ainsi généré à un élément de réseau de messagerie (207). Ledit élément de réseau de messagerie (207) transmet un message de confirmation au serveur de communication (201) lors de la remise du message généré au dispositif de communication (208). Le message de confirmation indique la disponibilité du dispositif de communication (208). Le serveur de communication (201) attend un message d'accusé de réception provenant de l'application client (209) à la réception du message de confirmation. Le serveur de communication (201) détermine la présence de l'application client (209) à la réception du message d'accusé de réception provenant de l'application client (209) par l'intermédiaire de l'élément de réseau de messagerie (207) dans un laps de temps prédéfini. L'élément de réseau de messagerie (207) reçoit le message d'accusé de réception provenant de l'application client (209) et remet le message d'accusé de réception au serveur de communication (201). Le message d'accusé de réception indique la présence de l'application client (209) sur le dispositif de communication (208).
PCT/IN2010/000020 2009-01-12 2010-01-11 Détermination de la présence d'une application client WO2010092593A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN91/CHE/2009 2009-01-12
IN91CH2009 2009-01-12

Publications (1)

Publication Number Publication Date
WO2010092593A1 true WO2010092593A1 (fr) 2010-08-19

Family

ID=42561469

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2010/000020 WO2010092593A1 (fr) 2009-01-12 2010-01-11 Détermination de la présence d'une application client

Country Status (1)

Country Link
WO (1) WO2010092593A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11071325B2 (en) 2015-06-09 2021-07-27 Rai Strategic Holdings, Inc. Electronic smoking article including a heating apparatus implementing a solid aerosol generating source, and associated apparatus and method

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1248484A1 (fr) * 2001-03-08 2002-10-09 Openwave Systems Inc. Méthode et système pour fournir des informations de presence et de localisation de mobiles à des applications
US20060184623A1 (en) * 2002-09-10 2006-08-17 Zabawskyj Bohdan K Method and system for presence determination of mobile devices
US20080119204A1 (en) * 2002-03-28 2008-05-22 Hines Gordon J Location derived presence information

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1248484A1 (fr) * 2001-03-08 2002-10-09 Openwave Systems Inc. Méthode et système pour fournir des informations de presence et de localisation de mobiles à des applications
US20080119204A1 (en) * 2002-03-28 2008-05-22 Hines Gordon J Location derived presence information
US20060184623A1 (en) * 2002-09-10 2006-08-17 Zabawskyj Bohdan K Method and system for presence determination of mobile devices

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11071325B2 (en) 2015-06-09 2021-07-27 Rai Strategic Holdings, Inc. Electronic smoking article including a heating apparatus implementing a solid aerosol generating source, and associated apparatus and method
US11819060B2 (en) 2015-06-09 2023-11-21 Rai Strategic Holdings, Inc. Electronic smoking article including a heating apparatus implementing a solid aerosol generating source

Similar Documents

Publication Publication Date Title
USRE48669E1 (en) System and method for identifying and [assessing] remediating vulnerabilities on a mobile communications device
US10701183B2 (en) Configuring a computing device to automatically obtain data in response to a predetermined event
US20120079043A1 (en) Method, apparatus and system for accessing an application across a plurality of computers
JP4945141B2 (ja) 非同期ネットワーク要求の実行のために柔軟な属性を適用するためのシステムおよび方法
US20130124655A1 (en) Electronic Communication Clarification System
US8606850B2 (en) Method, apparatus and system for controlling transmission of an attachment to an email using a plurality of computers
CN112867988A (zh) 由移动设备实现合规设置以遵循配置场景
EP2852913A1 (fr) Procédé et appareil de détermination de programme malveillant
CN111090423B (zh) 一种webhook框架系统和实现主动调用、实现事件触发的方法
JP6788501B2 (ja) 使用量データを収集して複数の通信デバイス上でのユーザのアベイラビリティを決定するための方法、システム、およびコンピュータ・プログラム
US20200210200A1 (en) Multi-Operating System Device, Notification Device and Methods Thereof
US8819823B1 (en) Method and apparatus for notifying a recipient of a threat within previously communicated data
US8971183B1 (en) Control signal traffic profile based mobile application access management
CN112825096A (zh) 一种数据脱敏方法和装置
US20120079063A1 (en) Method, apparatus and system for providing event notifications across a plurality of computers
WO2010092593A1 (fr) Détermination de la présence d'une application client
CN107925607B (zh) 使用阴影代理对数据服务器进行连续监控
US11856060B2 (en) Planned message notification for IoT device based on activity
CN105446803A (zh) 一种应用程序管理方法和装置
EP2622880B1 (fr) Procédé, appareil et système permettant de transmettre une application à l'aide d'une pluralité d'ordinateurs
US20120079008A1 (en) Method, apparatus and system for providing event notifications across a plurality of computers
CN115134328B (zh) 角标的配置方法、装置、计算机设备及可读存储介质
US20240022552A1 (en) Sign-up authentication
KR20150105708A (ko) 클라우드 메시징 서비스 시스템 및 방법
CN117492975A (zh) 分布式任务数据处理方法、装置及电子设备

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: 10741013

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10741013

Country of ref document: EP

Kind code of ref document: A1