KR101800267B1 - Gateway apparatus for heterogeneous push services and method for delivering push message - Google Patents

Abstract

One embodiment of the present disclosure has a push service gateway (or push service hub) for integrating various push service providing apparatuses, thereby allowing a push message to be transmitted and received, thereby preventing an operator's communication network from being overloaded. In addition, another embodiment of the present invention provides an interface between push service gateways (or push service hubs), thereby enabling push terminals to transmit and receive push messages between terminals subscribed to different push services.

Description

[0001] GATEWAY APPARATUS FOR HETEROGENEOUS PUSH SERVICES AND METHOD FOR DELIVERING PUSH MESSAGE [0002]

The present invention relates to a push service provision system and method.

BACKGROUND ART [0002] With the rapid development of information and communication technology today, services provided by a mobile communication system are being developed not only for voice services but also for multicasting multimedia communication for transmitting a large amount of data. As a large amount of data transmission becomes possible in a mobile communication system, various information can be provided anytime and anywhere using a mobile terminal.

As a mobile terminal including a smart phone evolves, a service for synchronizing data of a server in a mobile terminal is actively provided. For example, there may be real-time data synchronization such as mail service, schedule service, and contact service.

In this way, pushing the service in synchronization with the mobile terminal on the server side is called Push service, and it is applied to various kinds of services such as KakaoTalk, MyPhone, and Viber.

FIG. 1 is a diagram illustrating a basic architecture for implementing a conventional push service.

1, the first terminal 10a is connected to the first base station 50a, and the second terminal 10b is connected to the second base station 50b. The push service providing device (or push service server) 60 is connected to the communication network of the operator.

The first terminal 10a may generate a push message and then transmit the push message to the push service providing apparatus 60 through the first base station 50a so that the push service providing apparatus 60 transmits the push message To the second terminal (10b) through the second base station (50b).

The push service providing apparatus 60 may also generate a push message and then transmit the push message to the second terminal 10b through the second base station 50b.

In this way, the push message may be generated by the terminal or transmitted by the terminal, or may be generated and transmitted by the push service provider (or service server) 60.

2 is an exemplary view showing a problem of the conventional push service.

The service providing apparatuses 60a, 60b, 60c,... 60n (hereinafter, referred to as "60") for providing a push service shown in FIG. 2 may be, for example, KakaoTalk, MyPhone, Naverline, . When there is a message to be transmitted to the terminal, the service providing apparatus 60 can request push message transmission through a communication network operated by each operator.

For example, when there is a message to be transmitted from the first service providing apparatus 60a to the terminals using the first service provided by the first service providing apparatus 60a, the first service providing apparatus 60a transmits the message to the first service providing apparatus 60a, A push message is transmitted through a communication network, a communication network of the operator 2, and a communication network of the operator 3.

However, when providing a push service as in the prior art, each service providing apparatus 60 has to transmit a push message by connecting to the communication network of each operator. As the service providing apparatus 60 increases, there is a disadvantage that an operator's communication network is overloaded.

Assuming that the first terminal 10a is subscribed to the service of the first push service providing apparatus 60a and the second terminal 10b is subscribed to the service of the second push service providing apparatus 60b , There is no way in the related art that the first terminal 10a can transmit a push message to the second terminal 10b.

3 is an exemplary view showing another problem of the conventional push service.

3, the terminal 10 is provided with services from a plurality of push service provision apparatuses 60a, 60b and 60c. To this end, various push applications are installed in the terminal 10 .

In this case, each push application is executed in the background in the terminal 10, and transmits a status signal, for example, a keep alive signal or a heart beat signal to each push service providing apparatus 60a, 60b, 60c, Lt; / RTI >

However, when the number of such terminals 10 is increased, the transmission of the status signal increases exponentially, and the operator's communication network is overloaded.

Therefore, one embodiment disclosed in the present specification aims at solving the above-mentioned problems.

Specifically, one embodiment disclosed herein aims to prevent an operator from overloading the communication network as the number of push services increases.

It is another object of the present invention to enable push terminals to transmit and receive push messages between terminals subscribed to different types of push services.

 In order to achieve the above object, an embodiment of the present invention has a push service gateway (or push service hub) that integrates a plurality of push service providing apparatuses so that push messages can be transmitted and received, Thereby preventing overloading.

According to another aspect of the present invention, there is provided an interface between push service gateways (or push service hubs) to allow a terminal subscribed to a different push service to transmit a push message To be able to transmit and receive.

According to another aspect of the present invention, there is provided a push service gateway apparatus for delivering messages between disparate push services. The gateway device comprises: a receiver for receiving a message from a calling terminal subscribed to a first push service; And a controller for checking whether the receiving terminal is a subscriber of the first push service and inquiring whether the subscriber is subscribed to the different push service if the subscriber is not the subscriber of the first push service. Here, if the receiving terminal is subscribed to the heterogeneous push service, the receiving terminal may be requested to join the first push service. The gateway device may further include a transmitter for transmitting the message when the receiving terminal is subscribed to the first push service.

The control unit may control the transmission unit to transmit a signal to the device responsible for the heterogeneous push service to inquire whether the receiving terminal is subscribed to the heterogeneous push service. After the transmission of the inquiry request signal, the receiver may receive the information of the receiving terminal from the heterogeneous push service provider.

The information of the receiving terminal may include at least one of identification information and information of the heterogeneous service. The heterogeneous service information may include at least one of identification information of the heterogeneous service and interface protocol information of the heterogeneous service.

The heterogeneous push service provider apparatus to which the inquiry request signal is transmitted may be the heterogeneous push service provider apparatus or the push service gateway apparatus for the heterogeneous push service provider apparatus.

According to another aspect of the present invention, there is provided a method of transmitting a message between different types of push services in a push service gateway. The method comprises the steps of: upon receipt of a message from an originating terminal subscribed to a first push service, confirming that the receiving terminal is a subscriber of the first push service; If the receiving terminal is not a subscriber of the first push service, inquiring whether the receiving terminal is subscribed to the heterogeneous push service. Here, if the receiving terminal is subscribed to the heterogeneous push service, the receiving terminal may be requested to join the first push service. Then, when the receiving terminal is subscribed to the first push service, the message can be delivered.

According to another aspect of the present invention, there is provided a receiving-side push service gateway apparatus for transmitting a message between different types of push services. The receiving-side push service gateway apparatus comprises: a transmitting / receiving unit for receiving an inquiry request for a receiving terminal from a calling-side push service gateway apparatus for a first push service of the calling terminal; The calling terminal searches for the subscriber of the second push service of the different kind according to the inquiry request, and transmits information of the receiving terminal to the calling push service gateway apparatus when the subscriber is a subscriber, And a controller for controlling the transceiver to transmit a request signal to subscribe to the first push service that is the same as the terminal.

According to another aspect of the present invention, there is also provided a method of transmitting a different push service message between push service gateway devices. The method comprises the steps of: when a source push gateway device receives a message from a calling terminal subscribed to a first push service, checking whether the receiving terminal is a subscriber of the first push service; Transmitting, from the calling-side push-gateway device to the receiving-side push-gateway device, a request for inquiry as to whether the receiving terminal is subscribed, when the receiving terminal is not a subscriber of the first push service; Transmitting the information of the receiving terminal from the receiving-side push-gateway apparatus to the calling-side push-gateway apparatus when the apparatus is subscribed to the different push service; Transmitting a request signal to subscribe to the first push service from the receiving-side push gateway device to the receiving terminal through the heterogeneous push service; And when the receiving terminal is subscribed to the first push service, transmitting the message from the calling-side push gateway apparatus to the receiving terminal through the first push service.

On the other hand, in order to achieve the above-mentioned object, according to another embodiment of the present invention, a medium for storing an executable computer program is also presented. Receiving a message from a calling terminal subscribed to a first push service, the method comprising the steps of: confirming whether the receiving terminal is a subscriber of the first push service; If the receiving terminal is not a subscriber of the first push service, it may include inquiring whether or not the receiving terminal is subscribed to the heterogeneous push service. Here, if the receiving terminal is subscribed to the heterogeneous push service, the receiving terminal may be requested to join the first push service. In addition, if the receiving terminal is subscribed to the first push service, the receiving terminal can forward the message.

According to an embodiment of the present invention, a push service gateway (or push service hub) interworking with each push service providing apparatus is provided so that each push service providing apparatus does not issue a plurality of push requests, It is possible to reduce the overload of the overpayers communication network.

In addition, according to another embodiment of the present invention, terminals subscribed to different types of push services can send and receive push messages.

FIG. 1 is a diagram illustrating a basic architecture for implementing a conventional push service.
2 is an exemplary view showing a problem of the conventional push service.
3 is an exemplary view showing another problem of the conventional push service.
4 is a diagram illustrating a downward push service according to one embodiment of the present disclosure;
5 is a diagram illustrating an upward push service according to an embodiment of the present invention.
6 is a flowchart illustrating a process of transmitting a downward push message to a terminal according to an embodiment of the present invention.
7 is an exemplary diagram for explaining another embodiment of the present invention.
FIG. 8 is a signal flow diagram specifically illustrating the solution shown in FIG.
FIG. 9 is a signal flow diagram specifically showing a modified example of the solution shown in FIG.
FIG. 10 shows a configuration of the terminal 100 and the push service gateway 700, respectively, presented in the embodiments of the present invention.

It is noted that the technical terms used herein are used only to describe specific embodiments and are not intended to limit the invention. It is also to be understood that the technical terms used herein are to be interpreted in a sense generally understood by a person skilled in the art to which the present invention belongs, Should not be construed to mean, or be interpreted in an excessively reduced sense. Further, when a technical term used herein is an erroneous technical term that does not accurately express the spirit of the present invention, it should be understood that technical terms that can be understood by a person skilled in the art are replaced. In addition, the general terms used in the present invention should be interpreted according to a predefined or prior context, and should not be construed as being excessively reduced.

Also, the singular forms "as used herein include plural referents unless the context clearly dictates otherwise. In the present application, the term "comprising" or "comprising" or the like should not be construed as necessarily including the various elements or steps described in the specification, Or may be further comprised of additional components or steps.

Further, the suffix "module" and "part" for components used in the present specification are given or mixed in consideration of ease of specification, and do not have their own meaning or role.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, wherein like reference numerals refer to like or similar elements throughout the several views, and redundant description thereof will be omitted.

In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. It is to be noted that the accompanying drawings are only for the purpose of facilitating understanding of the present invention, and should not be construed as limiting the scope of the present invention with reference to the accompanying drawings.

4 is a diagram illustrating a downward push service in accordance with one embodiment of the present disclosure;

Referring to FIG. 4, the push service providing system includes at least one push service providing apparatus 600a, 600b, 600c,... 600n, 600 hereinafter, a push service gateway (or push service hub 700) .

The push service gateway (or push service hub 700) is interlocked with the communication network of each operator, and when a push request transmission request is received from the push service providing apparatus 600, Message.

The service providing apparatus 600 can provide real-time services such as KakaoTalk, MyPhone, Naver Line, Nate OnTalk, and the like. The service providing apparatus 600 may provide a real-time service based on a Web or a WAP (Wireless Application Protocol).

When there is a push message to be transmitted to the terminal, the service providing apparatus 600 transmits a message push request signal including a message to be transmitted to the terminal and terminal identification information to the push service gateway 700. Here, the message push request signal may include a message to be transmitted to the terminal, a message PDU, terminal identification information, push service gateway identification information, a reply flag, and the like. Here, the message PDU refers to an application identifier for identifying an application program to which a message is to be transmitted among application programs included in the terminal, and a reply flag indicates whether a reply to the push service is required.

Here, the service data and the update data transmitted and received in order to provide a real-time service may be expressed in Hypertext Markup Language (HTML) or Wireless Markup Language (WML).

As described above, the service providing apparatus 600 provides a push service by transmitting only one push request to the push service gateway (or push service hub) 700 without directly making a plurality of push requests to the communication network of each operator The overload of the overrun communication network can be reduced.

When the push service gateway 700 receives a message push request signal including message and terminal identification information from the service providing apparatus 600, the push service gateway 700 identifies the communication network of the operator having the terminal identification information as a subscriber, RTI ID = 0.0 > network. ≪ / RTI > At this time, there may be a push server node (not shown) in each communication network of each operator for transmitting an actual push message to each terminal.

That is, when the push service gateway 700 receives a push request from the service providing apparatus 600, the push service gateway 700 confirms the operators through the terminal identification information and sends a message (not shown) to the push server node And a push request signal including the corresponding terminal identification information. Here, the push request signal may be a signal for requesting the terminal corresponding to the terminal identification information to push the message. At this time, the push service gateway 700 can support various types of interface protocols in order to communicate with various kinds of push server nodes (not shown) that are responsible for push message transmission in each operator's communication network. Also, the push service gateway 700 may convert a push request signal (or message) corresponding to a protocol format requested by each push server node (not shown) and transmit the push request signal (or message) to a push server node . That is, when a push server node (not shown) in the communication network of each operator requests a specific type of interface or message format, the push service gateway 700 transmits a push request signal so as to satisfy the requested interface or message format Transcoding can be done.

The push server node (not shown) is operated by each operator, and when a push request signal is received from the push service gateway 700, the push server node (not shown) is connected to the terminals corresponding to the terminal identification information included in the push request signal Message, respectively. In this case, when the terminal operates in the standby mode, the push server node (not shown) may perform a paging control function for performing paging to the corresponding terminal and a push proxy function for transmitting a message using the push service. The terminal identification information includes a telephone number, an ID, a MAC address, and the like.

Examples of the terminal include a user terminal capable of network communication such as a PC, a notebook, a laptop, a mobile phone, a mobile phone, a PDA, and a smart phone.

5 is a diagram illustrating an upward push service according to an embodiment of the present invention.

5, the terminal 100 is provided with various push applications to receive services from the push service provision apparatuses 600a, 600b, and 600c. Also, the terminal 100 includes a push middleware (or push service manager) that provides an integrated protocol interface for various push applications.

The push middleware (or push service management unit) is connected to the push service gateway 700 through tunneling.

Accordingly, each push application may transmit a status signal, such as a keep alive signal or a heart beat signal, to the push middleware (or push service management unit) for notifying the status of the push application while the terminal 100 is running in the background.

The push middleware (or the push service management unit) groups the respective status signals and transmits them to the push service gateway 700, thereby reducing the burden on the communication network. The grouped status signals may be transmitted at regular intervals according to the settings of the push middleware (or push service manager). For example, the push application 1 delivers a status signal to the push middleware (or push service manager) every 20 seconds, the push application 2 delivers a status signal to the push middleware (or push service manager) every 5 seconds, When the push application 3 transfers the status signal to the push middleware (or the push service manager) every 15 seconds, the push middleware (or the push service manager) groups all the status signals and transmits the status signal to the push service gateway 700 every 30 seconds. .

When the push middleware (or push service management unit) groups the status signals and transmits them, for example, 10 status signals received from each push application for 30 seconds, 10 status signals are transmitted every 30 seconds to the push service Gateway 700, but only one signal indicative of the 10 status signals may be transmitted to the push service gateway 700 every 30 seconds.

On the other hand, in order to group the status signals and transmit them every predetermined period, it is necessary to make additional modifications in order to allow each of the service providing apparatuses 600a, 600b, and 600c to operate normally. That is, each of the service providing apparatuses 600a, 600b, and 600c receives the status signal from each application for each set period, and if it can not receive the status signal during the set period, it can determine that each push application does not operate normally .

When the push service gateway 700 sets a period for transmitting and receiving a status signal to the push middleware (or the push service manager) of the terminal 100, the push service gateway 700 transmits the status signal to the push service providing apparatuses 600a, 600b and 600c Can notify. Accordingly, it can be recognized that each of the push service providing apparatuses 600a, 600b, and 600c is not abnormal even if a period for receiving a status signal from each push application has elapsed.

Alternatively, the push service gateway 700 may set a period for transmitting / receiving a status signal to / from the push middleware (or push service manager) of the terminal 100, and when receiving the status signal during the set period, The push service provision apparatuses 600a, 600b, and 600c can inherently transmit status signals to each push application and the push service provision apparatuses 600a, 600b, and 600c according to the set period. For example, when the push middleware of the terminal 100 groups all state signals and transmits them to the push service gateway 700 every 30 seconds, the push service gateway 200 transmits the first push service providing apparatus 600a The second push service providing apparatus 600b may transmit the status signal every 5 seconds and the third push service providing apparatus 600c may transmit the status signal every 15 seconds.

6 is a flowchart illustrating a process of transmitting a downward push message to a terminal according to an embodiment of the present invention.

Referring to FIG. 6, the push service providing apparatus 600 acquires terminal identification information for message transmission, transmits a push message transmission request including the obtained terminal identification information and the message to the push service gateway 700 (S601). That is, when there is a message to be transmitted to the terminal 100 using the service provided by the push service providing apparatus 600, the push service providing apparatus 600 obtains the terminal identification information using the service, And transmits a push message transmission request signal to the push service gateway 700.

Then, the push service gateway 700 identifies the terminal identification information included in the signal (S602), and identifies the operator through the terminal identification information (S603). At this time, if the signal includes the operator information in the terminal identification information, the push service gateway 700 can immediately determine the operator as the operator. Otherwise, the push service gateway 700 determines whether the terminal is subscribed through the terminal identification information By searching through the database of each operator, the operator can be identified.

Then, the push service gateway 700 can transmit a push message to the terminal through the searched operator's communication network (S604). Alternatively, the push service gateway 700 may retrieve the push server node of the operator as described above and send a push request signal to the retrieved push server node.

FIG. 7 is an exemplary diagram for explaining a method for transmitting / receiving a message between different types of push services according to another embodiment of the present invention, FIG. 8 is a signal flow diagram illustrating a method shown in FIG. 7, to be.

7, it is assumed that the operator 1, the operator 2, the operator 3, and the operator 4 exist.

The first push service providing apparatus 600a (for example, Kakaiktok) provides a push service in an area served by the operator 1 and the operator 4, and the second service providing apparatus 600b in the area served by the operator 2, (For example, Google Talk) provides the push service, and in the service area of the operator 3, the third service providing apparatus 600c (e.g., the neighbor line service) provides the push service. It is assumed that the services provided by the service providing apparatuses 600a, 600b, and 600c are mutually different services such as KakaoTalk, Naver Line, Google Talk, and the like.

The first push service gateway 700a exists in the area served by the operator 1 and the operator 4 and the second push service gateway 700b exists in the area served by the operator 2. In the area served by the operator 3, Assume that there is a third push service gateway 700c.

In this case, the first terminal 100a receiving the first push service (for example, kakao tok) from the first push service providing apparatus 600a in the communication network of the operator 1 can access the third push service There has conventionally been no method by which a push message can be transmitted from the third push service providing apparatus 600c to the third terminal 100c provided with the third push service (e.g., Google Talk).

However, according to the second embodiment of the present invention, it is assumed that such a problem is solved through the respective push service gateways 700a, 700b, and 700c. More specifically, referring to FIGS. 7 and 8 together, the following will be described.

The first terminal 100a is subscribed to the first service of the first push service providing apparatus 600a and the third terminal 100c is subscribed to the third service of the third push service providing apparatus 600c (S801). Each of the push service provision apparatuses 600a and 600c transmits the information of the subscription terminal to the push service gateways 700a and 700c (S802). As a result, each of the push service gateways 700a and 700c can know which terminal is subscribed to which push service.

 Meanwhile, the first terminal 100a desires to transmit a push message to the third terminal 100c, and thus transmits the push message to the first push service gateway 700a (S803). At this time, the first terminal 100a may insert arbitrary identification information of the third terminal 100c, which is known to the first terminal 100a, in the push message. For example, if the user of the first terminal 100a knows the telephone number of the third terminal 100c, the telephone number may be included in the push message.

Then, the first push service gateway 700a checks the identification information of the third terminal to receive the received push message (S804).

If the third terminal 100c is not subscribed to the first service of the first push service providing apparatus 600a, the first push service gateway 700a transmits the second push service gateway 700b, And the third push service gateway 700c transmits the inquiry request to the third terminal 100c which is the receiving terminal (S805).

The second push service gateway 700b inquires the third terminal 100c but notifies the third terminal 100c of the inquiry. On the other hand, if it is confirmed that the third push service gateway 700c is subscribed to the third push service providing apparatus 600c as a result of inquiring the third terminal 100c, the subscription information of the third terminal, And transmits the information of the subscribed push service to the first push service gateway 700a (S806). For example, the information of the subscribed push service may include information of the third push service providing apparatus 600c to which the third terminal 100c is subscribed and information of the third push service providing apparatus 600c to the third terminal 100c As shown in FIG.

When the subscription information is received, it is determined whether to request the third terminal 100c to subscribe to the push service (e.g., Kakao Talk) of the first push service providing apparatus 600a in order to deliver the push message (S807). At this time, the determination may be made by the first push service providing apparatus 600a or may be determined by the first push service gateway 700a.

When it is determined to join the third terminal 100c, a subscription request signal is transmitted to the third terminal 100c through the third push service gateway 700c (S808). At this time, the subscription request signal may be generated and transmitted by the first push service providing apparatus 600a or may be generated and transmitted by the first push service gateway 700a. At this time, the subscription request signal may be generated according to the interface protocol of the third push service providing apparatus 600c to which the third terminal 100c is subscribed.

In response, the third terminal 100c requests to join the first push service providing apparatus 600a (S809). Then, the first push service providing apparatus 600a may transmit the subscription information of the third terminal 100c to the first push service gateway 700a (S810).

When the subscription is completed as described above, the first push service gateway 700a can transmit the push message to the third terminal 100c (S811).

FIG. 9 is a signal flow diagram specifically showing a modified example of the solution shown in FIG.

The process of S901 to S906 shown in FIG. 9 is the same as the process of S801 to S805 shown in FIG. 8, and therefore, the process of S906 will be described below.

When the third push service gateway 700c determines that the third terminal 100c is subscribed to the third push service provision apparatus 600c, the third push service gateway 700c transmits the first And requests subscribing to the push service providing apparatus 600a (S906).

Then, the third push service providing apparatus 600c transmits information (for example, at least one of a telephone number, a USIM number, user information, a device ID, a push ID, a security key, etc.) Is transmitted to the first push service providing apparatus 600a (S909).

Then, the third terminal 100c joins the first push service providing apparatus 600a (S908), and the first push service gateway 700a transmits the push message to the third terminal 100c, (S909).

The above-described method can be implemented by various means. For example, embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.

For a hardware implementation, the method according to embodiments of the present invention may be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs) , Field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.

In the case of an implementation by firmware or software, the method according to embodiments of the present invention may be implemented in the form of a module, a procedure or a function for performing the functions or operations described above. The software code can be stored in memory and driven by the processor. The memory is located inside or outside the processor and can exchange data with the processor by various means already known.

FIG. 10 shows the configuration of the terminal 100 and the push service gateway 700, respectively, presented in the embodiments of the present invention.

10, the terminal 100 refers to both the first terminal 100a, the second terminal 100b and the third terminal 100c. The terminal 100 includes a transceiver 101, A controller 102, and a storage unit 103. [

The push service gateway 700 includes a transceiver unit 701, a controller 702, and a storage unit 703.

The transceiver 101 of the terminal 100 enables wireless communication or wired communication. The transmitting and receiving unit 101 may be implemented separately from the transmitting unit and the receiving unit, or the transmitting unit and the receiving unit may be implemented as a single unit.

For the wireless communication, the transceiver 101 may include, for example, a data communication module, a short-range communication module, and the like

The data communication module may be a wireless broadband (Wibro), a World Interoperability for Microwave Access (Wimax), a High Speed Downlink Packet Access (HSDPA), or a Long Term Evolution (LTE).

The short-range communication module is a module for short-range communication. Wireless LAN (Wi-Fi), Bluetooth, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee Can be used.

Similarly, the transmitting / receiving unit 701 of the push service gateway 700 enables wired communication or short-range wireless communication. The transmitting and receiving unit 701 may be implemented separately from the transmitting unit and the receiving unit, or the transmitting unit and the receiving unit may be implemented together.

The storage means 103 and 703 store the method shown in Figs. 4 to 9 and the above-described contents. The storage means 103 and 703 may be a flash memory type, a hard disk type, a multimedia card micro type, a card type memory XD memory), a random access memory (RAM), a static random access memory (SRAM), a DRAM, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM) Only memory), a magnetic memory, a magnetic disk, and an optical disk.

The controllers 102 and 702 may be one of a digital signal processor (DSP), an application processor (AP), a CPU, and the like. The controllers 102 and 702 control the transmission / reception units 101 and 701 and the storage units 103 and 703, respectively. Specifically, the controllers 102 and 702 execute the methods stored in the storage means 103 and 703, respectively. The controller (102, 702) transmits and receives signals through the transceiver.

The embodiments disclosed herein have been described with reference to the accompanying drawings. Thus, the embodiments shown in the drawings are not to be construed as limiting, and those skilled in the art will understand that the present invention can be combined with each other, and when combined, some of the components may be omitted.

Here, terms and words used in the present specification and claims should not be construed as limited to ordinary or dictionary meanings, but should be construed as meaning and concept consistent with the technical idea disclosed in the present specification.

Therefore, the embodiments described in the present specification and the configurations shown in the drawings are only examples described in the present specification, and not all of the technical ideas disclosed in the present specification are described. Therefore, various modifications It is to be understood that equivalents and modifications are possible.

100, 100a, 100b, and 100c:
600, 600a, 600b, 600c: Push service device
700, 700a, 700b, 700c: Push service gateway device

Claims (18)

A push service gateway device for delivering messages between different kinds of push services,
A receiving unit for receiving a message from a calling terminal subscribed to the first push service;
A control unit for checking whether the receiving terminal of the message is a subscriber of the first push service and inquiring whether the subscriber is subscribed to a different push service different from the first push service when the subscriber is not a subscriber of the first push service;
And a transmitter for transmitting the message when the receiving terminal is subscribed to the first push service,
Wherein the control unit causes a request signal to subscribe to the first push service to be transmitted to the reception terminal through the second push service when the reception terminal of the inquiry request is subscribed to the second push service of a different type,
Wherein the transmitting unit transmits the message to the receiving terminal through the first push service when the receiving terminal is subscribed to the first push service. [Claim 2 is abandoned upon payment of the registration fee.] The apparatus of claim 1, wherein the control unit
And controls the transmitting unit to transmit a signal requesting inquiry to the device responsible for the heterogeneous push service whether the receiving terminal is subscribed to the heterogeneous push service. [Claim 3 is abandoned upon payment of the registration fee.] 3. The method of claim 2, wherein after the transmission of the inquiry request signal
And the receiving unit receives the information of the receiving terminal from the heterogeneous push service charge device. [Claim 4 is abandoned upon payment of the registration fee.] 4. The method of claim 3, wherein the information of the receiving terminal
Identification information or information of the disparate push service. [Claim 5 is abandoned upon payment of registration fee.] 5. The method of claim 4, wherein the information of the different push service
The identification information of the different push service, and the interface protocol information of the different push service. [Claim 6 is abandoned due to the registration fee.] The method according to claim 2 or 3,
The heterogeneous push service provider apparatus to which the inquiry request signal is transmitted
Wherein the push service gateway device is the heterogeneous push service providing device or the push service gateway device for the heterogeneous push service providing device. [7] has been abandoned due to the registration fee. The method of claim 1, wherein the receiving terminal
And receives a subscription request signal including information of the first push service. A method for delivering messages between disparate push services in a push service gateway,
Upon receipt of a message from an originating terminal subscribed to the first push service, confirming whether the receiving terminal is a subscriber of the first push service;
An inquiry step of inquiring whether the receiving terminal is subscribed to a different push service different from the first push service when the receiving terminal is not a subscriber of the first push service;
Transmitting a request signal to join the first push service to the receiving terminal through the second push service when the receiving terminal is subscribed to the second push service of a different type; And
And when the receiving terminal is subscribed to the first push service, transmitting the message to the receiving terminal through the first push service. [Claim 9 is abandoned upon payment of registration fee.] 9. The method according to claim 8, wherein in the inquiring step
And a signal requesting inquiry about whether the receiving terminal is subscribed to the heterogeneous push service is transmitted to the apparatus responsible for the heterogeneous push service. [Claim 10 is abandoned upon payment of the registration fee.] 10. The method of claim 9, wherein after the transmission of the inquiry request signal
Further comprising the step of receiving information of the receiving terminal from the disparate push service charge device. [Claim 11 is abandoned upon payment of the registration fee.] 11. The method of claim 10, wherein the information of the receiving terminal
Identification information, and information of the dissimilar push service. [12] has been abandoned due to the registration fee. 12. The method of claim 11, wherein the information of the different push service
The identification information of the heterogeneous push service, and the interface protocol information of the heterogeneous push service. [13] has been abandoned due to the registration fee. 11. The method according to claim 9 or 10,
The heterogeneous push service provider apparatus to which the inquiry request signal is transmitted
Wherein the different push service providing apparatus is a push service gateway apparatus for the heterogeneous push service providing apparatus or the heterogeneous push service providing apparatus. delete delete delete [Claim 17 is abandoned upon payment of registration fee.] CLAIMS 1. A method for delivering disparate push service messages between push service gateway devices,
Upon receiving a message from an originating terminal subscribed to the first push service, in the originating push-gateway device, confirming that the receiving terminal is a subscriber of the first push service;
Transmitting, from the calling-side push-gateway device to the receiving-side push-gateway device, a request for inquiry as to whether the receiving terminal is subscribed, when the receiving terminal is not a subscriber of the first push service;
Transmitting the information of the receiving terminal from the receiving-side push-gateway device to the calling-side push-gateway device when the receiving terminal is subscribed to the disparate push service;
Transmitting a request signal to subscribe to the first push service from the receiving-side push gateway device to the receiving terminal through the heterogeneous push service;
When the receiving terminal is subscribed to the first push service, transmitting the message from the calling-side push gateway apparatus to the receiving terminal through the first push service. Of push service messages. [Claim 18 is abandoned upon payment of registration fee.] 1. A medium for storing an executable computer program,
Receiving a message from a calling terminal subscribed to the first push service, checking if the receiving terminal is a subscriber of the first push service;
If the receiving terminal is not a subscriber of the first push service, inquiring whether the subscriber is subscribed to a different push service different from the first push service;
Causing the receiving terminal to transmit a request signal to subscribe to the first push service to the receiving terminal through the second push service when the receiving terminal is subscribed to a different type of second push service; And
And transmitting the message to the receiving terminal through the first push service when the receiving terminal is subscribed to the first push service.

Images