WO2012144828A2 - Procédé et appareil de gestion de service push - Google Patents

Procédé et appareil de gestion de service push Download PDF

Info

Publication number
WO2012144828A2
WO2012144828A2 PCT/KR2012/003013 KR2012003013W WO2012144828A2 WO 2012144828 A2 WO2012144828 A2 WO 2012144828A2 KR 2012003013 W KR2012003013 W KR 2012003013W WO 2012144828 A2 WO2012144828 A2 WO 2012144828A2
Authority
WO
WIPO (PCT)
Prior art keywords
push service
push
message
mobile station
application
Prior art date
Application number
PCT/KR2012/003013
Other languages
English (en)
Other versions
WO2012144828A3 (fr
Inventor
Myeong-Seong SEO
Jae-Min Ahn
Sang-Su Nam
Seong-Ho Cho
Kyoung-Yong Lee
Original Assignee
Samsung Electronics Co., Ltd.
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
Priority claimed from KR1020120038568A external-priority patent/KR101906410B1/ko
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2012144828A2 publication Critical patent/WO2012144828A2/fr
Publication of WO2012144828A3 publication Critical patent/WO2012144828A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1859—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast adapted to provide push services, e.g. data channels
    • 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/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present invention relates generally to an application service, and more particularly to an apparatus and a method for managing a push service used by an application, and a recording medium storing a program source for the method.
  • a push service for notifying a user of useful information, even without a request from the user, is becoming more important.
  • a push service when a specific event occurs at a preset time, specific information is sent to a user.
  • Schemes of providing a push service include a messaging push scheme using Short Message Service/Multimedia Message Service (SMS/MMS), an Internet Protocol (IP) push scheme in which a mobile station receives push data from a server in a state of maintaining a Transmission Control Protocol/Internet Protocol (TCP/IP)-based connection with the server, and a hybrid push scheme utilizing a combination of the SMS push scheme and the IP push scheme.
  • SMS/MMS Short Message Service/Multimedia Message Service
  • IP Internet Protocol
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the SMS push scheme is disadvantageous in that the SMS push scheme is limited by the length of data transmitted from a server to a mobile station, provides no feedback for reporting success or failure of reception, and imposes high transmission costs.
  • IP push scheme a connection with a server needs to be maintained. Further, in the IP push scheme, since data transmission/reception occurs frequently, an efficient management of data traffic and reduction of power consumption have been important issues.
  • FIG. 1 is a block diagram illustrating the conventional IP push scheme.
  • the mobile station 110 When there is a request for use of a push service from an application installed in a mobile station 110, the mobile station 110 transmits a message requesting registration of a push service for the application to a push server 120.
  • the message requesting registration of the push service includes an identifier of the mobile station 110 and information of a corresponding application, and the information of a corresponding application may include an identifier of the corresponding application and version information.
  • the mobile station 110 transmits a mobile station authentication identifier received from the push server 120, together with information of the corresponding application, to an application server 130.
  • the application server 130 transmits the push data, a mobile station authentication identifier, and application information to the push server 120. Then, the push server transmits the push data to the corresponding mobile station 110.
  • FIG. 2(a) illustrates a process flow of a message transmitted from a mobile station to a push server and an application server according to the conventional IP push scheme as described above.
  • FIG. 2(a) when there is a request for use of a push service from one application among applications App.1 and App.2 installed in the mobile station 110, the mobile station 110 generates a message requesting registration of the push service for the corresponding application and transmits the generated message to the push server 120.
  • FIG. 2(b) illustrates a construction of the message requesting registration of a push service.
  • the message requesting registration of a push service includes an IP header 202, a TCP 204, message type information 206, apparatus information 208, and information 210 of an application requesting registration of the push service.
  • FIG. 2(c) illustrates a construction of a message for requesting deregistration of the push service.
  • the message for requesting deregistration of the push service includes an IP header 202, a TCP header 204, message type information 206, apparatus information 208, and information 210 of an application requesting deregistration of the push service.
  • the mobile station 110 When information of the mobile station 110 has been registered to the push server 120 in response to the request for registration of the push service for one application among the applications installed in the mobile station 110, the mobile station 110 periodically transmits a periodic signal, known as “heartbeat”, to the push sever 120 for a continuous connection with the push server 120. This operation is illustrated in FIG. 3(a).
  • FIG. 3(a) a message expressed by “Type : H” indicates a heartbeat, and “period” refers to a transmission period of the heartbeat.
  • FIG. 3(b) illustrates a construction of the heartbeat.
  • the mobile station 110 when there is a request for use or interruption of the use of a push service from one application among the applications installed in the mobile station, the mobile station 110 generates a message (Push off notification or Push on notification) requesting deregistration or registration of the push service for the corresponding application and transmits the generated message to the push server 120.
  • a message Push off notification or Push on notification
  • the present invention has been made to solve the above-stated problems occurring in the prior art, and the present invention provides a scheme for managing a push service, which requires reduced power consumption.
  • Another aspect of present invention is to provide a message configuration scheme transmitted between a mobile station and a push server in order to efficiently manage a push service.
  • a method for managing a push service by a mobile station including when there is a request for use of a push service from at least one application installed in a mobile station, determining whether another application using the push service exists; determining a message type of a message to be transmitted to a push server in order to make a push service registration request depending on the determination of another application using the push service; and configuring a message for a push service registration request according to a determined message type and transmitting the configured message to the push server.
  • an apparatus for managing a push service by a mobile station including a controller for, when there is a request for use of a push service from at least one application installed in a mobile station, determining whether another application using the push service exists, determining a message type of a message to be transmitted to a push server in order to make a push service registration request depending on the determination of another application using the push service, and then configuring a message for a push service registration request according to a determined message type; and a transceiver for transmitting the configured message to the push server.
  • a recording medium readable by a processor, in which a program for executing a method for managing a push service by a mobile station, the method including when there is a request for use of a push service from at least one application installed in a mobile station, determining whether another application using the push service exists; determining a message type of a message to be transmitted to a push server in order to make a push service registration request depending on the determination of another application using the push service; and configuring a message for a push service registration request according to a determined message type and transmitting the configured message to the push server.
  • FIG. 1 is a block diagram illustrating a conventional IP push scheme
  • FIG. 2 is a diagram illustrating examples of a signal flow and constructions of messages transmitted from a mobile station for registration or deregistration of a push service according to an IP push scheme;
  • FIG. 3 is a diagram illustrating examples of signal flows and a construction of a heartbeat transmitted from a mobile station in the IP push scheme
  • FIG. 4 is a diagram illustrating examples of signal flows and constructions of messages transmitted from a mobile station for registration or deregistration of a push service according to an embodiment of the present invention
  • FIG. 5 is a signal flow diagram illustrating an example of a heartbeat transmitted from a mobile station according to an embodiment of the present invention
  • FIG. 6 is a flowchart illustrating an operation of managing a push service by a mobile station according to an embodiment of the present invention
  • FIG. 7 is a signal flow diagram illustrating an example of process flows and constructions of messages transmitted between a mobile station and a push server according to an embodiment of the present invention
  • FIG. 8 is a block diagram of a push service management apparatus according to an embodiment of the present invention.
  • FIG. 9 is a block diagram of a push server according to an embodiment of the present invention.
  • a push service management method in the related art requires too frequent signal transmission for registration or deregistration of the push service, is inefficient and greatly degrades the battery performance of a mobile station.
  • the present invention provides a scheme for minimizing the signals transmitted from a mobile station to a server, thereby improving battery performance.
  • the mobile station determines whether another application using the push service exists.
  • information of the application requesting use of the push service is transmitted to a push service through a heartbeat.
  • the fact that another application using the push service exists indicates that an application registered in a push server as an application using the push service exists.
  • the mobile station When another application using the push service does not exist, the mobile station generates a separate request message requesting registration of the push service distinguished from the heartbeat and then transmits the generated request message to the push server.
  • the fact that another application using the push service does not exist indicates that an application registered in a push server as an application using the push service does not exist.
  • the mobile station determines whether another application using a push service exists. When another application using the push service exists, the mobile station transmits information of an application requesting interruption of the use of the push service to the push service through a heartbeat. When another application using a push service does not exist, the mobile station generates a separate request message requesting deregistration of the push service distinguished from the heartbeat and then transmits the generated request message to the push server.
  • a mobile station makes a request for registration or deregistration of the push service either by using a heartbeat, or by using a separate message distinguished from the heartbeat.
  • FIG. 4(a) The message flow from a mobile station to a push server and an application server according to an embodiment of the present invention is described referring to FIG. 4(a).
  • the following description referring to FIG. 4(a) is based on, for convenience of description, an assumption that two applications App. 1 and App. 2 have been installed in the mobile station.
  • the mobile station 410 In a state in which the applications App. 1 and App. 2 installed in a mobile station 410 do not include an application using the push service, when there is a request for use of the push service from the application App. 1, the mobile station 410 generates a message (Type : R) requesting registration of a push service and then transmits the generated message to a push server 420.
  • FIG. 4(b) illustrates a construction of the message transmitted to the push server.
  • the message requesting use of a push service includes an IP header 402, a TCP header 404, message type information 406, mobile station information 408, a request ID 410, and application information 412.
  • the IP header 402 and the TCP 404 include addresses and port numbers of a starting point and a destination of the message.
  • the message type information 406 indicates the type of the corresponding message, that is, it indicates whether the message is for a push service registration request or for a push service deregistration request, or corresponds to a heartbeat message.
  • the mobile station information 408 is used for identifying the corresponding mobile station and may be, for example, an IMEI (International Mobile Equipment Identity) or IMSI (International Mobile Subscriber Identity) of the mobile station.
  • the request ID 410 corresponds to an identifier of a corresponding packet and can be expressed by a cyclic bit.
  • the request ID 410 may be used to identify a response message received from the push server.
  • the application information 412 corresponds to information of the application requesting use of the push service, and may include an identifier and version information of the application.
  • the mobile station 410 transmits corresponding application information and mobile station authentication information received from the push sever 420 to application server 430a.
  • the mobile station 410 stores information of the application App. 2 in a memory.
  • the mobile station 410 does not transmit a separate request message requesting registration of the push service to the push server 420. But, the mobile station 410 transmits corresponding application information and mobile station authentication information received from the push server 420 to application server 430b.
  • the mobile station 410 In the state in which both the applications App.1 and App. 2 installed in the mobile station 410 are using the push service, when there is a request for interruption of the use of the push service from the application App. 2, the mobile station 410 stores the information of the application App. 2 in the memory. The mobile station 410 does not transmit a separate request message requesting deregistration of the push service to the push server 420.
  • FIG. 4(c) illustrates a construction of the message for requesting deregistration of the push service transmitted to the push server.
  • the message for requesting deregistration of the push service includes an IP header 402, a TCP header 404, message type information 406, mobile station information 408, and a request ID 410.
  • Respective fields of the message requesting deregistration of the push service are equal to those described above with reference to FIG. 4(b), excluding only the differences that the message type information 406 indicates a message requesting deregistration of the push service and the fields do not include the application information.
  • the mobile station After requesting registration or deregistration of the push service to the push server, the mobile station receives a signal reporting information on whether the corresponding request has been processed. Then, based on a report by the received signal, if the corresponding request has not been processed, the mobile station processes the corresponding request again.
  • FIG. 4(d) illustrates a construction of the message reported by the signal received from the push server.
  • the message reported by the signal received from the push server includes an IP header 402, a TCP header 404, message type information 406, a request ID 410, and information 414 indicating whether the request for registration or deregistration of the push service has been successfully processed.
  • the message type information 406 of “rsp.” indicates that the corresponding message is a response message to the request for registration or deregistration of the push service.
  • the mobile station when there is a request for use of the push service or interruption of the use of the push service, if there is another application using the push service, the mobile station does not transmit a separate message requesting registration or deregistration of the push service to the push server 420, unlike described above with reference to FIG. 2(a), and therefore the present invention can reduce separately transmitted messages, so as to reduce the power consumption.
  • the mobile station When another application using the push service exists, the mobile station does not transmit a separate message requesting registration or deregistration of the push service to the push server 420 and instead stores information of the application requesting use of the push service or interruption of the use of the push service, and later transmits the corresponding request by using the heartbeat, as described in more detail with reference to FIG. 5.
  • FIG. 5 is a signal flow diagram illustrating an example of a process of requesting registration or deregistration of the push service by using a heartbeat.
  • FIG. 5 illustrates a situation in which heartbeats are being transmitted between a mobile station and a server since an application using the push service exists.
  • the mobile station when there is a request for use of the push service or interruption of the use of the push service and another application using the push service exists, transmits information requesting registration or deregistration of the push service by piggybacking the information onto the heartbeat.
  • a message expressed by “Type : H” is a heartbeat and “period” refers to a transmission period.
  • FIG. 6 is a flowchart illustrating an operation of managing a push service by a mobile station according to an embodiment of the present invention.
  • Step 601 when there is an application requesting use of the push service or interruption of the use of the push service, the mobile station proceeds to Step 603.
  • Step 603 the mobile station determines whether the request of the corresponding application is a request for use of the push service. When the request is a request for use of the push service, the mobile station proceeds to Step 605. Otherwise, the mobile station proceeds to Step 625.
  • Step 605 the mobile station determines whether another application using the push service exists, i.e. whether an application registered in the push server exists. When another application using the push service does not exist, the mobile station proceeds to Step 607. When another application using the push service exists, the mobile station proceeds to Step 617.
  • Step 607 the mobile station generates a request message requesting registration of the push service for the corresponding application and transmits the generated request message to the push server, and then proceeds to Step 609.
  • the request message requesting registration of the push service includes information of the corresponding mobile station and information of the corresponding application.
  • Step 609 based on a signal received from the push server, the mobile station determines whether registration of the push service request has been successfully processed. When registration of the push service request has been successfully processed, the mobile station proceeds to Step 601. Otherwise, the mobile station proceeds to Step 607, in which the mobile station makes a request for registration of the push service.
  • Step 617 to which the mobile station has proceeded based on a determination in Step 605 that another application using the push service exists, the mobile station stores information of the application currently requesting use of the push service in a memory, and then transmits the stored information of the application by piggybacking the information onto the heartbeat at the time of transmitting the heartbeat. That is, the mobile station performs registration of the push service request for the corresponding application by using the heartbeat.
  • Step 625 to which the mobile station has proceeded based on a result of the determination in Step 603 that the request from the corresponding application is not a request for use of the push service but a request for interruption of the use of the push service, the mobile station determines whether another application using the push service exists. When another application using the push service does not exist, the mobile station proceeds to Step 627. When another application using the push service exists, the mobile station proceeds to Step 637.
  • Step 627 the mobile station generates a request message requesting deregistration of the push service and transmits the generated request message to the push server, and then proceeds to Step 629.
  • the message requesting deregistration of the push service includes the corresponding mobile station information without including the application information.
  • Step 629 based on a signal received from the push server, the mobile station determines whether the push service deregistration request has been successfully processed. When the push service deregistration request has been successfully processed, the mobile station proceeds to Step 601. Otherwise, the mobile station proceeds to Step 627, and makes a request for deregistration of the push service to the push server again.
  • Step 637 the mobile station stores information of the application currently requesting interruption of the push service to the memory, then transmits the corresponding application information by piggybacking the corresponding application information onto the heartbeat with reference to the information stored in the memory at the time of transmitting the heartbeat. That is, the mobile station performs the push service deregistration request for the corresponding application by using the heartbeat. Instead of piggybacking information of the corresponding application onto the heartbeat, the mobile station may piggyback and transmit bitmap information requesting deregistration of the push service for the corresponding application.
  • a push service management method performed by the mobile station has been described above with reference to FIG. 6.
  • process flows and constructions of messages transmitted between the mobile station and the push server will be described in more detail with reference to the related drawings.
  • FIG. 7 is a signal flow diagram illustrating an example of process flows and constructions of messages transmitted between a mobile station and a push server according to an embodiment of the present invention. In the following description with reference to FIG. 7, it is assumed that two applications App.1 and App. 2 have been installed in the mobile station.
  • the mobile station when one application App. 1 among the applications installed in the mobile station makes a request for use of the push service, the mobile station generates a message requesting registration of the push service and transmits the generated message to the push server.
  • the message includes type information of the corresponding message, mobile station information, and information of the corresponding application.
  • the push server analyzes the received message, performs an authentication process for the corresponding mobile station, and performs registration of the push service for the application App. 1.
  • the heartbeat is periodically transmitted from the mobile station to the push server for the consistent connection between the mobile station and the push server.
  • the mobile station stores information of the application App. 2 in the memory, and then transmits the information of the application App. 2 to the push server by loading the information on the heartbeat at the time of transmitting the heartbeat. That is, the mobile station performs a request for registration of the push service for the application App. 2 by using the heartbeat.
  • the push server receives the message transmitted using the heartbeat, and performs the registration of the push service for the corresponding application App. 2 by analyzing the received message.
  • the transmitted message may further include bitmap type information.
  • the bitmap type information refers to information indicating whether the applications registered in the push server have been set as applications using the push service in the mobile station, i.e. information indicating a push service use state in the mobile station. For example, when information of the bitmap type for an application indicates “0”, it indicates that the application has made a request for non-use of the push service in the mobile station.
  • the bitmap type information may indicate only the state of use of the push service of the applications, which has been changed after previous transmission of the heartbeat. The state of use of the push service is piggybacked, together with the information of the applications having a changed state of use of the push service, onto the heartbeat.
  • the push server sequentially stores information of the applications having made the request for use of the push service from the mobile station. Therefore, the push server determines the state of use of the push service for the corresponding application by analyzing the bitmap type information of the received message, then manages the state of use of the push service.
  • the mobile station stores the information of the corresponding application App. 2 in the memory, then transmits the information of the application App. 2 to the push server at the time of next transmission of the heartbeat.
  • the message transmitted through the heartbeat may further include information indicating the state of use of the push service of all applications registered in the push server, and this information may be piggybacked in a bitmap type onto the heartbeat.
  • the information of the application App. 2 may not be separately piggybacked.
  • the message transmitting using the heartbeat may include only information on the state of use of the push service by the applications, which has been changed after previous transmission of the heartbeat.
  • the information of the application App. 2 is also piggybacked.
  • the mobile station when the application App. 1 makes a request for interruption of the use of the push service, i.e. a request for interruption of the use of the push service in all applications installed in the mobile station, the mobile station generates a request message requesting deregistration of the push service and transmits the generated request message to the push server.
  • the transmitted request message does not include information on the application.
  • the push server terminates all the push service for the corresponding mobile station, and deletes both the information of the corresponding mobile station and the information of all application for the corresponding mobile station.
  • FIG. 8 is a block diagram illustrating a push service management apparatus according to an embodiment of the present invention.
  • the push service management apparatus includes a controller 810, a transceiver 820, and a memory 830.
  • the controller 810 determines whether another application using the push service exists, and determines a message type of a message to be transmitted to a push server in order to make a push service registration request depending on the determination of another application using the push service. Determining the message type of the message to be transmitted to the push server refers to determining whether to use the heartbeat or a separate message in the push service registration request. Further, the controller 810 configures a message requesting registration of the push service according to the determined message type.
  • the controller 810 When there is a request for use of the push service from at least one application installed in the mobile station and another application using the push service exists, the controller 810 stores information of the application requesting use of the push service in the memory 830. In addition, at the time of transmitting the next heartbeat, the controller 810 reads the information of the corresponding application requesting use of the push service from the memory 830, and then transmits the read information by piggybacking the read information onto a heartbeat. Information indicating the state of use of the push service in the mobile station for the application made the push service registration request, i.e. the application registered in the push server, may be further piggybacked.
  • only the information indicating the state of use of the push service in the mobile station for the applications, which has been changed after transmission of the previous heartbeat, among the applications registered in the push server may be piggybacked.
  • the controller 810 also piggybacks the information of the corresponding applications onto the heartbeat.
  • the information indicating the state of use of the push service may be transmitted in the bitmap format. In order to transmit the information in the bitmap format, the mobile station stores and manages the information of the applications requesting use of the push service in the same order as that in which the information is stored in the push server.
  • the controller 810 when there is a request for use of a push service from at least one application installed in the mobile station and another application using the push service does not exist, the controller 810 generates a separate request message for a push service registration request.
  • the controller 810 determines whether another application using the push service exists, and determines a message type of a message to be transmitted to the push server in order to make a push service deregistration request depending on the determination of another application using the push service. Determining the message type of the message to be transmitted to the push server refers to determining whether to use the heartbeat or a separate message in the push service deregistration request. Further, the controller 810 configures a message requesting deregistration of the push service according to the determined message type.
  • the controller 810 When there is a request for interruption of the use of the push service from at least one application installed in the mobile station and another application using the push service exists, the controller 810 stores information of the application requesting interruption of the use of the push service in the memory 830. In addition, at the time of transmitting the next heartbeat, the controller 810 transmits the information of the corresponding application requesting interruption of the use of the push service by piggybacking the information onto a heartbeat. Information indicating the state of use of the push service in the mobile station for all applications making the push service registration request, i.e. all applications registered in the push server, may be further piggybacked. Information of the application making the push service deregistration request may not be separately piggybacked.
  • only the information indicating the state of use of the push service in the mobile station for the applications, which has been changed after transmission of the previous heartbeat, among the applications having made the push service registration request, i.e. the applications registered in the push server, may be piggybacked.
  • the information of the corresponding applications is piggybacked together.
  • the controller 810 when there is a request for interruption of the use of the push service from at least one application installed in the mobile station and another application using the push service does not exist, the controller 810 generates a separate request message for a push service deregistration request.
  • the message is configured not to include information on the application.
  • the transceiver 820 transmits a message received from the controller 810 to the push server and transfers a message received from the push server to the controller 810.
  • the memory 830 stores information of the application under the control of the controller 810. The stored information of the application is read out and transmitted to the push server at the time when the next heartbeat is transmitted. Further, when there is a request for interruption of the use of a push service from at least one application installed in the mobile station and another application using the push service exists, the memory 830 stores information of the application under the control of the controller 810. The stored information of the application is read out at the time when the next heartbeat is transmitted, so as to be used for a push service deregistration request.
  • FIG. 9 is a block diagram illustrating a push server according to an embodiment of the present invention.
  • the push server includes a controller 910, a transceiver 920, and a memory 930.
  • the controller 910 analyzes a message received through the transceiver 920 from the mobile station and determines whether the received message is a message making a push service registration request or a push service deregistration request.
  • the controller 910 When the received message is a message for a push service registration request and is a separate message that does not use a heartbeat, the controller 910 performs registration of the push service for the corresponding application and stores information of the corresponding application in the memory 930.
  • the controller 910 When the received message is a message for a push service registration request and is a message using a heartbeat, the controller 910 performs registration of the push service for the corresponding application according to the application information included in the message and stores information of the corresponding application in the memory 930.
  • the controller 910 manages the state of use of the push service of the applications registered in the push service based on the bitmap type information.
  • the controller 910 manages the state of use of the push service of the applications registered in the push service based on the bitmap type information included in the message.
  • the controller 910 When the received message is a message for a push service deregistration request and is a separate message that does not use a heartbeat, the controller 910 performs deregistration of the push service for all the applications of the mobile station and deletes information of all the applications and information of the mobile station.
  • Embodiments of the present invention described above may be implemented in various ways.
  • embodiments of the present invention may be implemented using hardware, software, or a combination thereof.
  • software it can be implemented as software executed on a processor using various operation systems or platforms.
  • such software may be programmed in any one among a plurality of appropriate programming languages, and may be compiled as machine code or source code executed in a framework or virtual machine.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Un appareil et un procédé destinés à la gestion d'un service push utilisé par une application, et un support d'enregistrement stockant une source de programme pour le procédé qui consiste à : lorsqu'une application installée dans une station mobile émet une demande d'utiliser un service push, déterminer s'il existe une autre application utilisant le service push ; déterminer le type d'un message devant être transmis à un serveur push afin de rendre une demande d'inscription à un service push dépendante de la détermination de l'autre application utilisant le service push ; et configurer un message pour une demande d'inscription à un service push selon un type de message déterminé et transmettre le message configuré au serveur push.
PCT/KR2012/003013 2011-04-19 2012-04-19 Procédé et appareil de gestion de service push WO2012144828A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201161477012P 2011-04-19 2011-04-19
US61/477,012 2011-04-19
KR1020120038568A KR101906410B1 (ko) 2011-04-19 2012-04-13 푸쉬 서비스 관리 방법 및 장치와 그 방법에 대한 프로그램 소스를 저장한 기록 매체
KR10-2012-0038568 2012-04-13

Publications (2)

Publication Number Publication Date
WO2012144828A2 true WO2012144828A2 (fr) 2012-10-26
WO2012144828A3 WO2012144828A3 (fr) 2013-01-17

Family

ID=63896010

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/003013 WO2012144828A2 (fr) 2011-04-19 2012-04-19 Procédé et appareil de gestion de service push

Country Status (1)

Country Link
WO (1) WO2012144828A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015041455A1 (fr) * 2013-09-17 2015-03-26 Samsung Electronics Co., Ltd. Dispositif électronique, procédé de transmission d'informations par dispositif électronique, et système de transmission d'informations
CN109803359A (zh) * 2013-11-15 2019-05-24 华为终端有限公司 一种唤醒终端系统的方法及终端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100788245B1 (ko) * 2006-10-19 2007-12-27 (주)인트로모바일 통합 푸시 서비스 시스템 및 제공방법
WO2009080605A1 (fr) * 2007-12-21 2009-07-02 Nokia Siemens Networks Oy Mécanisme de messagerie
KR20100090201A (ko) * 2009-02-05 2010-08-13 삼성전자주식회사 무선통신시스템에서 메시지 푸쉬 서비스를 제공하기 위한 시스템 및 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100788245B1 (ko) * 2006-10-19 2007-12-27 (주)인트로모바일 통합 푸시 서비스 시스템 및 제공방법
WO2009080605A1 (fr) * 2007-12-21 2009-07-02 Nokia Siemens Networks Oy Mécanisme de messagerie
KR20100090201A (ko) * 2009-02-05 2010-08-13 삼성전자주식회사 무선통신시스템에서 메시지 푸쉬 서비스를 제공하기 위한 시스템 및 방법

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015041455A1 (fr) * 2013-09-17 2015-03-26 Samsung Electronics Co., Ltd. Dispositif électronique, procédé de transmission d'informations par dispositif électronique, et système de transmission d'informations
US10432495B2 (en) 2013-09-17 2019-10-01 Samsung Electronics Co., Ltd. Electronic device, method of transmitting log information by electronic device, and system for receiving the log information
CN109803359A (zh) * 2013-11-15 2019-05-24 华为终端有限公司 一种唤醒终端系统的方法及终端

Also Published As

Publication number Publication date
WO2012144828A3 (fr) 2013-01-17

Similar Documents

Publication Publication Date Title
WO2013094895A1 (fr) Procédé et appareil de traitement de messages
WO2014163383A1 (fr) Procédé et appareil d'acheminement de message de service basé sur la proximité dans un système de communication sans fil
WO2012074198A1 (fr) Terminal et nœud intermédiaire dans un environnement de réseautage orienté contenu et procédé de communication de terminal et de nœud intermédiaire
WO2013062384A1 (fr) Appareil et procédé de transmission et de réception d'informations de changement de planification persistante dans un système de communication sans fil
WO2019035638A1 (fr) Procédé de vérification d'une modification d'un type de connexion sans fil d'un terminal dans un serveur d'applications tiers
WO2013085310A1 (fr) Appareil et procédé de distribution efficace de service de message court dans système de communication sans fil
WO2011078474A2 (fr) Système de diffusion groupée mobile pour prise en charge de mobilité au niveau réseau et procédé correspondant
WO2014142390A1 (fr) Procédé et appareil de radiomessagerie d'appel terminé dans un système de communication mobile
WO2011078573A2 (fr) Procédé et appareil pour réentrée en réseau de station mobile dans un système de communication sans fil
WO2013036068A1 (fr) Procédé pour fournir un service m2m, et procédé et appareil pour une communication m2m
WO2013122418A1 (fr) Procédé et appareil pour prendre en charge des communications de dispositif à dispositif
WO2012050293A1 (fr) Procédé et appareil permettant de partager des contenus à l'aide d'informations de changement de groupe dans un environnement de réseau orienté contenu
WO2012093915A2 (fr) Appareil et procédé permettant la prise en charge d'un service à contrôle de temps dans un système de communication entre machines
WO2013035954A1 (fr) Procédé de mise à jour d'identificateur de groupe de terminaux en communication de machine-à-machine
US8744500B2 (en) Method and apparatus for managing push service
WO2010126298A2 (fr) Dispositif de gestion de porteuse pour une station de base, procédé de gestion de porteuse, station mobile et procédé de gestion de porteuse pour une station mobile
WO2012118266A1 (fr) Procédé de communication d'un terminal cible et d'un point d'accès pour gestion d'identificateur de groupe en transmission mu-mimo
WO2015016659A1 (fr) Procédé et dispositif de découverte de proximité parmi des ue
WO2020004753A1 (fr) Procédé, appareil, et programme pour sélectionner automatiquement un canal de transmission de message et transmettre un message
WO2011152669A2 (fr) Procédé et appareil pour émettre et recevoir un message de radiomessagerie à l'aide d'informations de bande dans un système de communication sans fil
WO2012144828A2 (fr) Procédé et appareil de gestion de service push
WO2020085539A1 (fr) Procédé d'établissement d'une session de service d'homologue à homologue sur une liaison d'infrastructure
WO2014010787A1 (fr) Procédé de mise à jour de zone de suivi, procédé de mise en phase, et appareil de traitement de signal numérique les prenant en charge
EP3577916A1 (fr) Procédé et appareil de transmission et de réception de données dans un système de communication de données critiques de mission
WO2012173398A2 (fr) Procédé de fonctionnement en mode inactif et appareil m2m

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

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12773776

Country of ref document: EP

Kind code of ref document: A2