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

Gateway apparatus for heterogeneous push services and method for delivering push message Download PDF

Info

Publication number
KR102041134B1
KR102041134B1 KR1020130032485A KR20130032485A KR102041134B1 KR 102041134 B1 KR102041134 B1 KR 102041134B1 KR 1020130032485 A KR1020130032485 A KR 1020130032485A KR 20130032485 A KR20130032485 A KR 20130032485A KR 102041134 B1 KR102041134 B1 KR 102041134B1
Authority
KR
South Korea
Prior art keywords
push service
push
terminal
service gateway
gateway device
Prior art date
Application number
KR1020130032485A
Other languages
Korean (ko)
Other versions
KR20140117795A (en
Inventor
이정훈
Original Assignee
에스케이플래닛 주식회사
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 에스케이플래닛 주식회사 filed Critical 에스케이플래닛 주식회사
Priority to KR1020130032485A priority Critical patent/KR102041134B1/en
Publication of KR20140117795A publication Critical patent/KR20140117795A/en
Application granted granted Critical
Publication of KR102041134B1 publication Critical patent/KR102041134B1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

According to one embodiment presented herein, a push service gateway device for a first push service is provided. The push service gateway device may include a transceiver configured to establish a tunnel with another push service gateway device for heterogeneous second push services; When the message from the originating terminal is received through the transceiver, confirms whether the receiving terminal of the message corresponds to the subscriber of the first push service, and if the subscriber is not the subscriber of the first push service, the heterogeneous second push service; It may include a control unit for requesting the inquiry to the other push service gateway device through the transceiver unit whether the receiving terminal is subscribed. Here, when the receiving terminal is subscribed to the second push service, the transceiver may transmit the message to the other push service gateway device through the set tunnel.

Description

Gateway device and push message delivery method for heterogeneous push services {GATEWAY APPARATUS FOR HETEROGENEOUS PUSH SERVICES AND METHOD FOR DELIVERING PUSH MESSAGE}

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

Today, due to the rapid development of information and communication technology, the services provided by mobile communication systems are evolving into multicasting multimedia communication that transmits a large amount of data as well as voice service. As a large amount of data transmission is possible in a mobile communication system, it is possible to receive various information anytime and anywhere using a mobile terminal.

As such, with the evolution of mobile terminals including smartphones, services for synchronizing server data with mobile terminals are actively provided. For example, there may be real-time data synchronization such as mail service, calendar service, contact service, and the like.

In this way, a server transmits a message in synchronization with a mobile terminal, which is called a push service, and is currently applied to various types of services such as KakaoTalk, My People, and Viber.

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

As can be seen with reference to Fig. 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 apparatus 60 is connected to the operator's communication network.

The first terminal 10a may generate a push message and then transmit the generated push message to the push service providing apparatus 60 through the first base station 50a. Thus, the push service providing apparatus 60 transmits the push message. It may transmit to the second terminal 10b through the second base station 50b.

Meanwhile, 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.

As such, the push message may be generated and transmitted by the terminal, or may be generated and transmitted by the push service providing apparatus 60.

2 is an exemplary diagram illustrating a problem of a conventional push service.

The push service providing devices 60a, 60b, 60c,..., 60n, hereinafter referred to as 60, which provide a push service, shown in FIG. 2 may be, for example, KakaoTalk, My People, Naver Line, and Nate On Talk. . When there is a message to be transmitted to the terminal, the push service providing apparatus 60 may request transmission of a push message through a communication network operated by each operator.

For example, when there is a message to be transmitted to the terminals using the first push service provided by the first service providing apparatus 60a, the first push service providing apparatus 60a is an operator to which the terminals are subscribed. The push message is transmitted through the communication network of operator 1, the communication network of operator 2, and the communication network of operator 3.

However, in the case of providing a push service as in the related art, each push service providing apparatus 60 needs to access a communication network of each operator and transmit a push message. As the push service providing apparatus 60 increases, There is a disadvantage that the communication network of each operator is overloaded.

In addition, for example, it is assumed 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. In the related art, there is no method in which the first terminal 10a can transmit a push message to the second terminal 10b.

3 is an exemplary diagram illustrating another problem of a conventional push service.

As can be seen with reference to Figure 3, the terminal 10 is provided with services from the various push service providing devices (60a, 60b, 60c), for this purpose, each terminal 10 is provided with a respective push service providing devices Several push applications are installed.

In this case, each push application is running in the background in the terminal 10 to inform its status, for example, a push alive signal or a heart beat signal for each push service providing apparatus To the fields 60a, 60b, and 60c.

By the way, when the number of the terminal 10 increases, the transmission of the state signal increases exponentially, and the operator's communication network is overloaded.

The present invention has been made to solve the above problems, an embodiment of the present disclosure is to provide an apparatus and method for preventing overload of the operator's network as the various push services increase, have.

Another object of the present invention is to allow terminals subscribed to different heterogeneous push services to transmit and receive push messages.

To this end, according to one embodiment provided herein, a push service gateway device for a first push service is provided. The push service gateway device may include a transceiver configured to establish a tunnel with another push service gateway device for heterogeneous second push services; When the message from the originating terminal is received through the transceiver, confirms whether the receiving terminal of the message corresponds to the subscriber of the first push service, and if the subscriber is not the subscriber of the first push service, the heterogeneous second push service; It may include a control unit for requesting the inquiry to the other push service gateway device through the transceiver unit whether the receiving terminal is subscribed. Here, when the receiving terminal is subscribed to the second push service, the transceiver may transmit the message to the other push service gateway device through the set tunnel.

Meanwhile, according to an exemplary embodiment of the present disclosure, a method of transferring a message between heterogeneous push services at the push service gateway is also provided. The method comprises the steps of: establishing a tunnel with a second push service gateway device for a heterogeneous second push service by a first push service gateway device for a first push service of an originating terminal; Requesting, by the second push service gateway device, whether the receiving terminal is subscribed to the heterogeneous second push service when the receiving terminal of the message is not a subscriber of the first push service; If the receiving terminal is subscribed to the second push service, it may include transmitting the message to the second push service gateway device through the set tunnel.

After the inquiry request, the transceiver may receive the information of the receiving terminal. Here, the information of the receiving terminal may include one or more of identification information and information of the second push service.

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

The controller may convert the message according to the interface protocol of the heterogeneous second service and then transmit the message through the transceiver.

The controller may group the message together with other messages and transmit the message through the transceiver. In this case, the period of the group transmission may be negotiated with the other push service gateway device when establishing the tunnel.

Meanwhile, according to another embodiment of the present specification, a receiving side push service gateway device is also provided. The apparatus includes a transceiver for establishing a tunnel with another push service gateway apparatus for heterogeneous push services; When receiving an inquiry request for a receiving terminal from the other push service gateway device, it is searched whether the receiving terminal is subscribed to a service different from the heterogeneous push service to which the calling terminal is subscribed, and if the information is received, the information of the receiving terminal. It may include a control unit for controlling the transceiver to transmit to the originating push service gateway device. The control unit may transmit the message from the transmitting terminal to the receiving terminal through the set tunnel.

Meanwhile, according to another embodiment of the present disclosure, a method of transferring heterogeneous push service messages between push service gateway devices is also provided. The method includes establishing a tunnel between an originating push gateway device and a receiving push gateway device; Checking, at the calling push gateway device, whether a receiving terminal is a subscriber of a first push service when receiving a message from a calling terminal subscribed to a first push service; If the receiving terminal is not a subscriber of the first push service, transmitting an inquiry request for whether the receiving terminal is subscribed from the calling push gateway device to the receiving push gateway device through the set tunnel; If the receiving terminal is subscribed to a heterogeneous push service, transmitting the information of the receiving terminal from the receiving side push gateway device to the calling side push gateway device through the set tunnel; Converting the message to conform to the heterogeneous push service at the calling push gateway device; And transmitting the converted message from the originating push gateway device to the receiving side push gateway device through the established tunnel.

According to an exemplary embodiment of the present specification, terminals subscribed to heterogeneous push services may transmit and receive push messages.

In addition, according to one embodiment of the present specification, even if a user subscribes to a push service only once, a user can receive and transmit a message with a terminal subscribed to a heterogeneous push service, thereby improving convenience for a user.

1 is a diagram illustrating a basic architecture for implementing a conventional push service.
2 is an exemplary diagram illustrating a problem of a conventional push service.
3 is a diagram illustrating another problem of the conventional push service.
4 is a diagram illustrating a push service in a downward direction according to one embodiment of the present specification.
FIG. 5 is a diagram illustrating a push service in an upward direction according to one embodiment of the present specification. FIG.
6 is a flowchart illustrating a process of delivering a push message in a downward direction to a terminal according to an embodiment of the present specification.
7 is an exemplary view for explaining another embodiment of the present specification.
FIG. 8 is a signal flowchart for explaining the method illustrated in FIG. 7.
FIG. 9 illustrates an example of grouping messages transmitted through the tunnel shown in FIG. 8.
FIG. 10 is a diagram illustrating a configuration of a terminal and a push service gateway presented in one embodiment of the present specification.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The construction of the present invention and the effects thereof will be clearly understood through the following detailed description. Prior to the detailed description of the present invention, the same components will be denoted by the same reference numerals even if they are displayed on different drawings, and the detailed description will be omitted when it is determined that the well-known configuration may obscure the gist of the present invention. do.

4 is a diagram illustrating a push service in a downward direction according to one embodiment of the present specification.

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

The push service gateway (or push service hub 700) is interworked with a communication network of each operator, and when a push message transmission request is received from the push service providing apparatus 600, the push service gateway 700 is pushed through the communication network of the operator. You can pass a message.

The push service providing apparatus 600 may provide a real time service such as KakaoTalk, My People, Naver Line, Nate On Talk, and the like. In addition, the push service providing apparatus 600 may provide a real time service based on a web or a wireless application protocol (WAP).

When there is a push message to be transmitted to the terminal, the push 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 return flag, and the like. Here, the message PDU refers to an application identifier for identifying an application program to transmit a message among application programs included in the terminal, and the reply flag indicates whether a reply to the push service is required.

Here, service data and update data transmitted and received to provide a real-time service may be expressed in a hypertext markup language (HTML) or a wireless markup language (WML).

As described above, the service providing device 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 each operator's communication network. As a result, the overhead of the network of the overlayer can be reduced.

When the push service gateway 700 receives the message push request signal including the message and the terminal identification information from the service providing apparatus 600, the push service gateway 700 identifies the communication network of the operator using the terminal identification information and identifies the identification. The push message through the established communication network. In this case, there may be a push server node (not shown) that transmits an actual push message to each terminal in the communication network of each operator.

That is, when the push service gateway 700 receives the push request from the service providing apparatus 600, the push service gateway 700 checks the operators through the terminal identification information and sends a message to the push server node (not shown) in the confirmed operator's communication network. And a push request signal including corresponding terminal identification information. Here, the push request signal may be a signal for requesting a push of a message to a terminal corresponding to the terminal identification information. In this case, the push service gateway 700 may support various types of interface protocols in order to communicate with various types of push server nodes (not shown) that are responsible for transmitting push messages in each operator's communication network. In addition, the push service gateway 700 may convert a push request signal (or message) corresponding to a protocol format required by each push server node (not shown) and transmit the same to a push server node (not shown) of the corresponding operator. . That is, when a push server node (not shown) in each operator's communication network requires a specific type of interface or message format, the push service gateway 700 may generate a push request signal to satisfy the requested interface or message format. Transcoding can be done.

Such a 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 nodes (not shown) are terminals corresponding to the terminal identification information included in the push request signal. Send each message. In this case, when the terminal operates in the standby mode, the push server node (not shown) may perform a paging control function for paging the terminal and a push proxy function for transmitting a message using a push service. The terminal identification information includes a telephone number, ID, MAC address, and the like.

On the other hand, examples of the terminal includes a user terminal capable of network communication, such as PC, notebook, laptop, mobile phone, mobile phone, PDA, smart phone.

FIG. 5 is a diagram illustrating a push service in an upward direction according to one embodiment of the present specification. FIG.

As can be seen with reference to FIG. 5, the terminal 100 has various push applications installed in order to receive a service from each push service providing apparatus 600a, 600b, or 600c. In addition, 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 manager) is connected to the push service gateway 700 through tunneling.

Accordingly, each push application executes the push middleware (or the push service) while executing in the background in the terminal 100 to notify a status signal for informing its status, for example, a keep alive signal or a heart beat signal. Management).

In addition, the push middleware (or push service manager) groups each state signal and transmits the state signals to the push service gateway 700, thereby reducing the load on the communication network. The grouped state signals may be transmitted at regular intervals according to the setting of the push middleware (or push service manager). For example, push application 1 delivers a status signal to the push middleware (or push service manager) every 20 seconds, push application 2 delivers a status signal to the push middleware (or push service manager) every 5 seconds, When the push application 3 transmits a status signal to the push middleware (or push service manager) every 15 seconds, the push middleware (or push service manager) groups all status signals to the push service gateway 700 every 30 seconds. Can be delivered to.

When the push middleware (or push service manager) groups and transmits the status signals, for example, if there are 10 status signals received from each push application for 30 seconds, the 10 push signals are transmitted every 30 seconds. Although transmitted to the gateway 700, only one signal representing the ten status signals may be delivered to the push service gateway 700 every 30 seconds.

On the other hand, when grouping the state signals in this manner and transmits at regular intervals, additional modifications are required to allow the service providing apparatuses 600a, 600b, and 600c to operate normally. That is, each of the service providing apparatuses 600a, 600b, and 600c has received a status signal from each application at each set period. If the service signal is not received at the set period, the service application 600a, 600b, or 600c may determine that each push application does not operate normally. .

Accordingly, after the push service gateway 700 sets a period for transmitting and receiving a status signal with the push middleware (or the push service manager) of the terminal 100, the push service gateway 700 transmits the state signal to each of the push service providing apparatuses 600a, 600b, and 600c. Can be notified. Accordingly, the push service providing apparatuses 600a, 600b, and 600c may recognize that the push service providing apparatuses 600a, 600b, and 600c are not abnormal even if they have elapsed from a period in which a status signal should be received from each push application.

Alternatively, if the push service gateway 700 sets a period for transmitting and receiving a status signal with the push middleware (or push service manager) of the terminal 100, and receives the status signal in the set period, The push service providing apparatuses 600a, 600b, and 600c may transmit a status signal, respectively, in accordance with a period set between each push application and each push service providing apparatus 600a, 600b, or 600c. For example, when the push middleware of the terminal 100 groups all the state signals and transmits them to the push service gateway 700 every 30 seconds, the push service gateway 200 may provide a first push service providing apparatus 600a. ) May transmit a status signal every 20 seconds, the second push service providing apparatus 600b may transmit a status signal every 5 seconds, and the third push service providing apparatus 600c may transmit a status signal every 15 seconds.

6 is a flowchart illustrating a process of delivering a push message in a downward direction to a terminal according to an embodiment of the present specification.

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

Then, the push service gateway 700 checks the terminal identification information included in the signal (S602), and identifies the corresponding operator through the terminal identification information (S603). In this case, when the push service gateway 700 includes operator information in the signal and terminal identification information, the push service gateway 700 may immediately determine an operator. Otherwise, the push service gateway 700 determines whether the corresponding terminal is subscribed through the terminal identification information. Operators can be identified by searching through the database of each operator.

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

FIG. 7 is an exemplary view for explaining a method for enabling a message to be transmitted and received between heterogeneous push services according to another embodiment of the present specification, and FIG. 8 is a signal flowchart illustrating the method shown in FIG. 7 in detail. 9 shows an example of grouping messages transmitted through a tunnel.

As can be seen with reference to FIG. 7, assume that operator 1, operator 2, operator 3, and operator 4 exist.

The first push service providing apparatus 600a (for example, KakaoTalk) provides a push service in an area served by the operator 1 and the operator 4, and the second service providing apparatus 600b in an area served by the operator 2. Suppose that (for example, Google Talk) provides a push service, and a third service providing apparatus 600c (for example, a NAVER line service) provides a push service in an area served by Operator3. In addition, suppose that the services provided by the service providing apparatuses 600a, 600b, and 600c are heterogeneous services such as KakaoTalk, Naver Line, Google Talk, and the like.

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

In this case, the first terminal 100a receiving the first push service (eg, KakaoTalk) from the first push service providing apparatus 600a in the communication network of the operator 1 is located in the communication network of the third operator. There is no conventional method for transmitting a push message from the third push service providing apparatus 600c to the third terminal 100c receiving a third push service (eg, Google Talk).

However, according to the second embodiment of the present specification, this problem is solved through each push service gateway 700a, 700b, and 700c. Specifically, it will be described with reference to FIGS. 7 and 8 as follows.

First, the first push gateway 700a and the third push gateway 700c enter into an agreement with each other and generate a tunnel (S801).

The first terminal 100a and the second terminal 100b are subscribed to the first service of the first push service providing apparatus 600a, and the third terminal 100c is the first terminal of the third push service providing apparatus 600c. 3 is subscribed to the service (S802). Accordingly, each of the push service providing apparatuses 600a and 600c transmits the information of the terminal subscribed to them to the corresponding push service gateways 700a and 700c, respectively (S803). As a result, each push service gateway 700a and 700c may know whether any terminal is subscribed to the push service in charge of the terminal.

 Meanwhile, the first terminal 100a desires to deliver a push message to the third terminal 100c, and thus transmits the push message to the first push service gateway 700a (S804). In addition, the second terminal 100b also hopes to deliver a push message to the third terminal 100c, and thus transmits the push message to the first push service gateway 700a (S805). In this case, the first terminal 100a may insert identification information of the third terminal 100c which is known to the push message. For example, when 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 identification information of the third terminal 100c to receive the received push message (S806).

If the third terminal 100c is not subscribed to the first push service of the first push service providing apparatus 600a, the first push service gateway 700a receives the heterogeneous push service gateway. Request inquiry about whether the terminal is subscribed (S807). That is, the first push service gateway 700a transmits an inquiry request signal to the second push service gateway 700b and the third push service gateway 700c to the third terminal 100c which is a receiving terminal.

The push service gateways 700b and 700c receiving the inquiry request inquire whether the third terminal 100c is subscribed to the push service provided by the push service gateways 700b and 700c (S806).

When the third push service gateway 700c checks that the third terminal 100c is subscribed to the push service and the inquiry is completed, the third push service gateway 700c receives subscription confirmation information that notifies the receiving terminal of the third push service gateway 700. The first push service gateway 700a is transmitted to the first push service gateway 700a (S808).

In this case, the inquiry request signal and the subscription information are transmitted and received through the generated tunnel.

The subscription information includes terminal identification information and heterogeneous service information. The terminal identification number is information for identifying the receiving terminal in the third push service. The heterogeneous service information may include identification information of the heterogeneous service, interface protocol information of the heterogeneous service, and the like.

When the first push service gateway 700a receives the subscription confirmation information, the first push service gateway 700a confirms that the third terminal 100c is subscribed to the third push service providing apparatus 600c through the subscription confirmation information.

Subsequently, the first push service gateway 700a converts the received messages according to the interface protocol of the third push service providing apparatus 600c (S809). The converted message may include identification information of the heterogeneous service, that is, identification information of the third service (for example, identification information of the third push service providing apparatus). In addition, the converted message includes information for identifying the third terminal 100c which is the receiving terminal in the third push service.

When the conversion of the message is completed, the first push service gateway 700a transmits the message to the third push service gateway 700c and requests the third terminal 100c to transmit the message (S810). Here, the message may be transmitted through the generated tunnel.

That is, the third terminal 100c subscribed to the heterogeneous push service from the first terminal 100a which is the originating terminal transmits a message transmitted from the first terminal 100a to the first push service gateway 700a and the third. It may be delivered through the push service gateway 700c.

Here, when there are a plurality of terminals that are subscribed to the first push service and request message transmission to heterogeneous push services, several terminals are grouped, and the inquiry request for the receiving terminals is transmitted by group to reduce network load. Can be

Specifically, as can be seen with reference to Figure 9, between the push service gateway devices (700a, 700b, 700c) to enter into agreement with each other, when creating a tunnel (S801), each of the time interval to be transmitted can be set. .

In the set time period, for example, the first push service gateway apparatus 700a may group and transmit several messages at once. For example, as illustrated, the first push service gateway apparatus 700a may group several messages in a time interval to be transmitted and transmit them at once. In this case, each message may be divided into an ID (ie, identification information) part of a receiver to be received and a payload part containing the content of the corresponding message. For example, as described above, the ID portion of the receiver may include information for identifying the third terminal 100c which is the receiving terminal in the third service.

10 illustrates the configuration of the terminal 100 and the push service gateway 700 presented in the embodiments of the present disclosure, respectively.

As shown in FIG. 10, the terminal 100 refers to the above-described first terminal 100a, second terminal 100b, and third terminal 100c. The terminal 100 may include a transceiver 101, a controller 102, and a storage means 103.

Meanwhile, the push service gateway 700 includes a transmitter 701, a receiver 702, a controller 703, and a memory 704.

The transceiver 101 of the terminal 100 enables wireless communication or wired communication. The transceiver 101 may be implemented separately from the transmitter and the receiver, or may be implemented as a transmitter and the receiver.

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

The data communication module may be a wireless broadband (Wibro), a world interoperability for microwave access (Wimax), a high speed downlink packet access (HSDPA), a long term evolution (LTE), or the like.

The short range communication module refers to a module for short range communication. Short Range Communication (Wireless LAN) (Wi-Fi), Bluetooth (Bluetooth), Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee, etc. This can be used.

The storage means 103 stores data necessary for the operation of the terminal 100. The storage means 103 may include a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (for example, an SD or XD memory, etc.). ), Random Access Memory (RAM), Static Random Access Memory (SRAM), DRAM, Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EPEROM), Programmable Read-Only Memory (PROM) At least one type of storage medium may include a magnetic memory, a magnetic disk, and an optical disk.

The controller 102 may be one of a digital signal processor (DSP), an application processor (AP), a CPU, and the like. The controller 102 controls the connected components, that is, the transceiver 101 and the storage means 103, respectively.

Similarly, the transmitter 701 and receiver 702 of the push service gateway 700 enable wired or near field communication. The transmitter 701 and the receiver 702 may be implemented separately from the transmitter and the receiver, or may be implemented as a transmitter and the receiver.

In addition, the controller 704 executes the methods stored in the memory unit 704, and transmits and receives a signal through the transmitter 701 and the receiver 702.

More specifically, the receiving unit 702 of the push service gateway 700 receives a message from the calling terminal subscribed to the push service.

The control unit 703 checks whether the receiving terminal of the message is a subscriber of the first push service, and if it is not a subscriber of the first push service, requests that an inquiry is made to the heterogeneous push service. That is, the controller 703 controls the transmitter to transmit a signal for requesting whether the receiving terminal is subscribed to the heterogeneous push service to the device in charge of the heterogeneous push service.

The transmitter 702 transmits a message to the second push service when the information indicating that the receiving terminal is subscribed to the heterogeneous second push service through the receiver is received.

In addition, the reception unit 701 receives subscription confirmation information of the reception terminal from the heterogeneous push service manager. When the receiving terminal is subscribed to the heterogeneous push service responsible device, the information on the heterogeneous service is included. The heterogeneous service information may include identification information of the heterogeneous service, interface protocol information of the heterogeneous service, and the like.

On the other hand, when the receiving unit 701 of the push service gateway device receives the inquiry request for the receiving terminal from the heterogeneous push service gateway, the controller 704 determines that the receiving terminal is a subscriber of the heterogeneous second push service according to the inquiry request. And the receiving unit 701 and the transmitting unit 702 to transmit the subscription confirmation information of the receiving terminal to the calling push service gateway device, and to receive a message from the calling push service gateway device and transmit the message to the receiving terminal. To control.

The above description is merely illustrative of the present invention, and various modifications may be made by those skilled in the art without departing from the technical spirit of the present invention. Therefore, the embodiments disclosed in the specification of the present invention are not intended to limit the present invention. The scope of the present invention should be construed by the claims below, and all techniques within the scope equivalent thereto will be construed as being included in the scope of the present invention.

100, 100a, 100b, 100c: terminal
600, 600a, 600b, 600c: device for providing push service
700, 700a, 700b, 700c: push service gateway device

Claims (21)

A push service gateway device for a first push service,
A transmission / reception unit generating a tunnel in which time intervals to be transmitted are respectively set with another push service gateway device for heterogeneous second push services;
When the message from the originating terminal is received through the transceiver, confirms whether the receiving terminal of the message corresponds to the subscriber of the first push service, and if the subscriber is not the subscriber of the first push service, the heterogeneous second push service; Inquires whether the receiving terminal is subscribed to the other push service gateway device through the tunnel, and if the receiving terminal is subscribed to the second push service, delivers the message to the other push service gateway device through the tunnel. It includes a control unit;
Each of the push service gateway device and the other push service gateway device,
And a plurality of messages are grouped and transmitted to each other in a time interval set in each of the push service gateway device and the other push service gateway device in the tunnel. delete delete delete delete delete delete delete delete delete delete delete delete delete A receiving side push service gateway device for delivering heterogeneous different push service based messages,
A transmitter / receiver configured to generate a tunnel in which time intervals to be transmitted are previously set with another push service gateway apparatus for heterogeneous push services;
When the inquiry request for the receiving terminal is received from the other push service gateway device, the receiving terminal searches whether the receiving terminal is subscribed to a service different from the heterogeneous push service to which the calling terminal is subscribed, and if the receiving terminal is subscribed, the information of the receiving terminal is obtained. A control unit for transmitting to the calling terminal push service gateway device through the tunnel, and transmitting the received message to the receiving terminal when a message from the calling terminal is received through the tunnel;
Each of the receiving side push service gateway device and the other push service gateway device
Receiving side push service gateway device, characterized in that for transmitting a group of several messages in the time interval set in each of the receiving side push service gateway device and the other push service gateway device in the tunnel. delete delete delete delete delete delete
KR1020130032485A 2013-03-27 2013-03-27 Gateway apparatus for heterogeneous push services and method for delivering push message KR102041134B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020130032485A KR102041134B1 (en) 2013-03-27 2013-03-27 Gateway apparatus for heterogeneous push services and method for delivering push message

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020130032485A KR102041134B1 (en) 2013-03-27 2013-03-27 Gateway apparatus for heterogeneous push services and method for delivering push message

Publications (2)

Publication Number Publication Date
KR20140117795A KR20140117795A (en) 2014-10-08
KR102041134B1 true KR102041134B1 (en) 2019-11-06

Family

ID=51990773

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020130032485A KR102041134B1 (en) 2013-03-27 2013-03-27 Gateway apparatus for heterogeneous push services and method for delivering push message

Country Status (1)

Country Link
KR (1) KR102041134B1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100570283B1 (en) * 2004-05-03 2006-04-11 브이엘씨주식회사 Method and system to provide messenger service
KR100779012B1 (en) * 2006-09-15 2007-11-23 에스케이 텔레콤주식회사 System and method for communicating between different messengers

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100570283B1 (en) * 2004-05-03 2006-04-11 브이엘씨주식회사 Method and system to provide messenger service
KR100779012B1 (en) * 2006-09-15 2007-11-23 에스케이 텔레콤주식회사 System and method for communicating between different messengers

Also Published As

Publication number Publication date
KR20140117795A (en) 2014-10-08

Similar Documents

Publication Publication Date Title
US9125003B2 (en) Machine to machine service management device, network device, and method processing service system
KR102165255B1 (en) Registration management method for terminal accessing 5g network on non-3gpp
US10560929B2 (en) Resource request method and system, device, and network side node
EP3340563B1 (en) Method and apparatus for interworking between heterogeneous systems
WO2017202269A1 (en) Method for updating network slice identity, network element, terminal, and storage medium
RU2665894C2 (en) System and method for utilising stored higher layer information
RU2754682C1 (en) Object, network, and user equipment for v2x service, as well as v2x application
CN101237475B (en) Information push system, method and device
CN106714329B (en) Method and device for establishing data link
CN109804612B (en) Method and apparatus for inter-user equipment communication
US20160316395A1 (en) Service query method, apparatus and system, and station
WO2022095048A1 (en) Communication method and apparatus and computer readable storage medium
WO2024046169A1 (en) Positioning method, device, and storage medium
CN105404253B (en) Control instruction sending method, response method and device
US20160088076A1 (en) Method, device and system for obtaining mobile network data resources
KR102041134B1 (en) Gateway apparatus for heterogeneous push services and method for delivering push message
KR102061837B1 (en) Gateway apparatus for heterogeneous push services and method for delivering push message
EP3200550A1 (en) Method for sharing resources between mobile devices thanks to a location tracking server
CN109600237B (en) Multicast data processing method and device
WO2016183730A1 (en) Data transmission method and apparatus
KR101800267B1 (en) Gateway apparatus for heterogeneous push services and method for delivering push message
US10111081B2 (en) Local communication wireless network system and method thereof
WO2019074032A1 (en) Apparatus, method and program for transmitting and receiving data to and from iot device
CN114158079B (en) Communication method and device, electronic equipment and computer readable medium
JP6509413B1 (en) Device, method and program for transmitting and receiving data with IoT device

Legal Events

Date Code Title Description
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant