WO2013105809A1 - Communication system and method for providing push service in said communication system - Google Patents
Communication system and method for providing push service in said communication system Download PDFInfo
- Publication number
- WO2013105809A1 WO2013105809A1 PCT/KR2013/000241 KR2013000241W WO2013105809A1 WO 2013105809 A1 WO2013105809 A1 WO 2013105809A1 KR 2013000241 W KR2013000241 W KR 2013000241W WO 2013105809 A1 WO2013105809 A1 WO 2013105809A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- push
- registration
- application
- terminal
- Prior art date
- Legal status (The legal status 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 status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- 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
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
Definitions
- the present invention relates to a communication system and a method for providing a push service in the communication system.
- the present invention provides a push service by easily changing a registration procedure between servers constituting the communication system to transmit a push message to a terminal.
- Two methods are typical for receiving data based on the Internet network.
- One is the pull based communication method, and the other is the push based communication method.
- the pull based communication method is performed through the following process.
- the terminal connects to an application server provided by the data service provider.
- the terminal periodically performs keep alive with the application server.
- the terminal periodically transmits an uplink request for data retrieval to the application server.
- Push based communication method is performed by the following process. First, the terminal registers with the application server provided by the data service provider. The terminal then connects to a push server connected to the application server. Next, the push server periodically transmits a push notification to the terminal. The terminal periodically performs connection management with the push server.
- FIG. 1 is a diagram illustrating a push service providing method according to the prior art.
- the application server transmits a server registration request to a push server in step 110 to provide a push service.
- the server registration request includes address information indicating the location of the push server and information on the providing application.
- the push server stores address information of the corresponding application server and information on the application.
- the push server then sends a server registration response to the application server.
- the push server carries the server authentication code together.
- step 120 the terminal installs an application from an app market or an operator server.
- step 125 the terminal requests an application registration from the push server.
- the terminal transmits all or part of the application ID, the terminal ID, and the user ID to the push server.
- the push server transmits a registration response to the terminal along with the registration ID.
- the terminal transmits a registration confirmation including the registration ID transmitted from the push server to the application server in step 135.
- the application server receiving this checks the registration ID in step 140 and completes the registration.
- the application server triggers a message due to application update or data change in step 145.
- the application server transmits a push request including a server authentication code, a registration ID, and data for triggering to the push server.
- the push server transmits a push notification including the application ID and data corresponding to the registration ID to the terminal.
- a push server that provides various push alarm services.
- the push server is configured by various push service providers. Apple, for example, offers a separate push server called Apple Push Notification Service (APNS). And in the case of goolge's Android, it provides a push server called C2DM (Android Cloud To Device Messaging Framework).
- APNS Apple Push Notification Service
- C2DM Android Cloud To Device Messaging Framework
- a push server may be provided for each mobile service provider server providing a service to a terminal.
- APSN In the case of APSN, only an application used in a specific terminal provided by Apple can provide a push service. In the case of C2DM, the data that can be transmitted is limited, and the number of uses is limited.
- a push server is configured for a specific mobile operator server, the push service is provided only to a specific application that is contracted with the corresponding operator server.
- push messages provided to the terminal are also applied only to a specific application that is contracted with the corresponding push service provider. Therefore, it is necessary to develop a separate software for the application service provider to connect to the push server for each region or for each push service provider or mobile service provider.
- the push service of the corresponding application is provided only in the mobile communication provider in which the terminal is registered. That is, when the terminal roams to another country, there is a problem that the push service of the application is not provided.
- the present invention proposes a mobile communication system and a method for providing an efficient push service when there are multiple push service providers in the mobile communication system.
- a method of providing a push service of a communication system includes a process in which a terminal requests registration with a push server when an application is installed, and a registration response is received from the push server. Transmitting a registration confirmation to a server, the application server requesting a server registration to the push server, the push server requesting a server registration to a public authentication server, and receiving a server registration response from the public authentication server And when a message for a push service is triggered, the application server requesting a push to the push server, and the push server transmitting a push notification according to the push request to the terminal. It features.
- the process of transmitting the registration confirmation in the present invention is characterized in that it comprises the step of transmitting the push server information stored in advance received from the operator server.
- the process of requesting the server registration is characterized in that the application server comprises the step of transmitting a server authentication code received in advance from the public authentication server.
- the step of receiving the server registration response is characterized in that the push server comprises the step of transmitting the server authentication code received from the application server to the public authentication server.
- the push service providing system requests a registration to a push server when an application is installed, and receives a registration response from the push server, and transmits a registration confirmation to an application server.
- the push server for transmitting a push notification to the terminal according to the push request received from the application server, and transmits a server authentication code to the application server,
- server registration requests received from the push server Transmitting a different response is characterized by including the common authentication server.
- the terminal is characterized in that it receives from the operator server to transmit previously stored push server information to the application server.
- the application server is characterized in that for transmitting the server authentication code to the push server, when the server registration request.
- the push server is characterized in that for transmitting the server authentication code received from the application server to the public authentication server.
- a push server may be configured for each mobile operator server providing a service to a terminal. Accordingly, the terminal may receive a push service while roaming to another mobile communication provider.
- the operator server by connecting the operator server and the network, it is possible to prevent traffic overload and optimize the data communication environment.
- the procedures for using a push server of a mobile service provider or a push service provider are the same, it is possible to solve the difficulty of application development.
- FIG. 1 is a diagram illustrating a push service providing method according to the prior art.
- FIG. 2 is a diagram illustrating a communication system configuration according to an embodiment of the present invention.
- FIG. 3 is a diagram illustrating a method for obtaining push server information according to an embodiment of the present invention.
- FIG. 4 is a diagram illustrating a push server authentication method according to an embodiment of the present invention.
- FIG. 5 is a diagram illustrating a push service providing method according to an embodiment of the present invention.
- FIG. 6 is a diagram showing a push service providing method according to another embodiment of the present invention.
- FIG. 7 is a diagram illustrating a push service providing method in a terminal according to an embodiment of the present invention.
- 'Push service' is a service in which the server automatically provides the data desired by the user. It is a webcasting service of two-way communication in which various information is provided according to an individual's interests by time zone and subject.
- 'Terminal' is an information processing apparatus that can process data transmitted and received from the outside, and includes a computer, a smartphone, a tablet PC, and the like.
- FIG. 2 is a diagram illustrating a communication system configuration according to an embodiment of the present invention.
- the communication system includes a terminal, a push server, an application server, and a public authentication server.
- the terminal receives the push server information including the address indicating the location of the push server provided by the provider after the registration step or successful registration for use of the communication service provided by the mobile communication service provider.
- the terminal installs the application, and requests the application registration and issuance of the registration ID installed in the corresponding push server through the received push server information.
- the terminal delivers the registration ID and the push server information issued to the application server.
- the push server When the push server receives a push request including a push message from the application server, the push server delivers it to the terminal.
- the push server issues a registration ID when a registration request is received from the terminal.
- the push server receives a server registration request including a server authentication code from the application server, the push server transmits it to the public authentication server to confirm application authentication.
- the push server receives the push request from the authenticated application server. The push server notifies the terminal of this.
- An application server is a server managed by a provider that provides an application.
- the application server requests server registration from the public authentication server in advance.
- the application server stores the server authentication code received with the server registration response from the public authentication server.
- the application server receives the push server information and the registration ID for the push server address from the terminal, the application server requests the server registration with the server authentication code to the push server.
- the application server sends a message requesting this to the push server.
- the common authentication server issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the application, for each application server.
- the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).
- the terminal requests application registration installed by the push server in step 210.
- the terminal transmits a registration request message including a user ID, an ID assigned to the terminal, and an installed application ID.
- the push server issues a registration ID for this to the terminal.
- the terminal transmits the push server address and the registration ID to the application server in step 220.
- the push server address is push server information received from the operator server by the terminal and is included in the information on the push server transmitting the push message.
- the registration between the application server and the push server is performed in step 230. That is, the application server requests a server registration from the push server using the push server address received from the terminal.
- the application server transmits the server authentication code received in advance through the public authentication server.
- the push server transmits the server authentication code received from the application server in step 240 to the public authentication server.
- the push server confirms the application server authentication requesting registration through the public authentication server.
- FIG. 3 is a diagram illustrating a method of obtaining push server information according to an embodiment of the present invention.
- the terminal needs to know the address of the push server in order to request an application registration installed by the push server. To this end, the terminal receives information related to the push server from the operator server.
- the operator server refers to a server managed by an operator providing a communication service to a terminal.
- the operator server delivers the push server information providing the push service to the terminal.
- the push server information includes information on an address of a push server and information on an application for which a push message is provided by the corresponding push server.
- the terminal receives the push server information from the operator server in step 310 after the terminal authentication procedure for using a communication service from the mobile operator.
- the terminal checks the address of the corresponding push server using the push server information received from the operator in step 320.
- the terminal requests registration and issuance of a registration ID for receiving a push message corresponding to the application to the confirmed push server.
- the push server then issues a registration ID of the terminal and delivers it to the terminal.
- FIG. 4 is a diagram illustrating a push server authentication method according to an embodiment of the present invention.
- the push server and the application server do not register and authenticate the application, but are performed between the application server and the public authentication server.
- the common authentication server registers an application provided by an application server managed by an application provider, and issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the corresponding application, for each application server.
- the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).
- the application server requests the application registration provided by the application server to the public authentication server in step 410.
- the public authentication server then issues a server authentication code, which is an authentication key for the application, and sends it to the application server.
- FIG. 5 is a diagram illustrating a push service providing method according to an embodiment of the present invention.
- step 510 the application server requests server registration with a public authentication server.
- the public authentication server then transmits a server registration response to the application server in step 515.
- the public authentication server authenticates the application server and transmits a server authentication code for transmitting a push message.
- the terminal installs the application.
- the terminal receives the push server information for transmitting a push message for the application from the operator server.
- the push server information includes information on the address of the push server.
- the terminal stores the push server information received in step 520.
- the terminal requests registration with the push server of the address verified through the push server information received in step 525.
- the terminal delivers the terminal ID, the user ID, and the installed application ID to the push server.
- the push server checks this in step 530 and transmits a registration response to the terminal.
- the push server issues a registration ID and delivers it to the terminal.
- the terminal Upon receiving the registration response, the terminal transmits a registration confirmation message to the application server in step 535.
- the registration confirmation message includes the push server information including the registration ID received from the push server and the address of the push server.
- the application server receiving this is registered in step 540.
- the application server requests a server registration to the push server in step 545.
- the application server transmits the server authentication code received from the public authentication server together to the push server.
- the push server transmits a server registration request including a server authentication code received from the application server to the public authentication server.
- the public authentication server checks the server authentication code received from the push server in step 560 and transmits a response to the push server.
- the application server triggers a message according to the application update or data change in step 565.
- the application server transmits a push request to the push server.
- the application server transmits the server authentication code received from the common authentication server, the registration ID received from the terminal and the data to push.
- the push server checks the registration ID to identify the corresponding terminal, and notifies the terminal of the push message including the application ID and data to be pushed to the checked terminal according to the received push request.
- FIG. 6 is a diagram illustrating a push service providing method according to another embodiment of the present invention.
- push server 1 is a push server that delivers a push message before roaming
- push server 2 represents a push server changed by roaming.
- step 610 the terminal stores the changed push server information from the operator server.
- step 615 the terminal requests registration with the push server 1.
- the terminal transmits the push server information including the user ID, the terminal ID and the push server address received from the operator server.
- push server 1 requests registration confirmation to push server 2 in step 620.
- the push server 1 transmits a user ID and a device ID together.
- the push server 2 transmits a registration confirmation response to the push server 1 in step 625.
- the ID of the applications provided by the push server 2, the registration ID, and the ID of the application server registered on the push server 2 are transmitted together in the registration confirmation response.
- the push server 1 transmits a registration response received from the push server 2 to the terminal in step 630. At this time, the push server 1 transmits the registration ID received from the push server 2 to the terminal. In step 635, the terminal receives the registration confirmation message to the application server.
- the registration confirmation message includes the registration ID sent from push server 2 and the push server information for the address of push server 2.
- the application server triggers a push message according to the application change or data update in step 640.
- the application server then sends a push request to push server 2 in step 645.
- the application server transmits the server authentication code, registration ID, and data to be pushed together.
- the push server 2 notifies the terminal of the push message for the corresponding application in step 650.
- the push server 2 transmits the application ID and the data to be pushed together to the terminal.
- FIG. 7 is a diagram illustrating a push service providing method in a terminal according to an embodiment of the present invention.
- the terminal requests subscription and authentication for a mobile service provider to use a communication service.
- the terminal receives and stores push server information from the operator server.
- the push server information includes the address of the push server, and the operator server knows all of the addresses for each push server.
- the terminal requests registration with a push server in step 730.
- the terminal transmits the user ID using the terminal, the ID assigned to the terminal, and the address of the push server transmitted from the operator server together with the registration request.
- step 740 the terminal receives the registration ID from the push server.
- operation 750 the terminal transmits a registration confirmation including the registration ID to the application server. At this time, the terminal transmits the address of the push server with registration confirmation.
- the terminal receives a push message from the push server in step 760.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
λ³Έ λ°λͺ μ ν΅μ μμ€ν λ° κ·Έ ν΅μ μμ€ν μμ νΈμ μλΉμ€λ₯Ό μ 곡νλ λ°©λ²μ κ΄ν κ²μΌλ‘, λ¨λ§λ‘ μ λ¬λλ νΈμ λ©μμ§λ₯Ό μ μ‘νκΈ° μν΄ ν΅μ μμ€ν μ ꡬμ±νλ κ° μλ² κ°μ λ±λ‘ μ μ°¨λ₯Ό μ©μ΄νκ² λ³κ²½νμ¬ νΈμ μλΉμ€λ₯Ό μ 곡νλ λ°©λ² λ° κ·Έλ₯Ό μννλ ν΅μ μμ€ν μ κ΄ν κ²μ΄λ€.The present invention relates to a communication system and a method for providing a push service in the communication system. The present invention provides a push service by easily changing a registration procedure between servers constituting the communication system to transmit a push message to a terminal. A method and a communication system for performing the same.
μΈν°λ· λ§μ κΈ°λ°μΌλ‘ λ°μ΄ν°λ₯Ό μμ νλ λ°©λ²μΌλ‘ λ κ°μ§ λ°©λ²μ΄ λνμ μ΄λ€. νλλ pull based communication λ°©λ²μ΄κ³ , λ€λ₯Έ νλλ push based communication λ°©λ²μ΄λ€. Two methods are typical for receiving data based on the Internet network. One is the pull based communication method, and the other is the push based communication method.
pull based communication λ°©λ²μ λ€μκ³Ό κ°μ κ³Όμ μ ν΅ν΄ μνλλ€. μ°μ λ¨λ§μ λ°μ΄ν° μλΉμ€ μ 곡μκ° μ 곡νλ μ΄ν리μΌμ΄μ μλ²μ μ°κ²°νλ€. κ·Έλ¦¬κ³ λ¨λ§μ μ΄ν리μΌμ΄μ μλ²μ μ£ΌκΈ°μ μΌλ‘ μ°κ²° κ΄λ¦¬(keep alive)λ₯Ό μννλ€. μ΄λ λ¨λ§μ μ΄ν리μΌμ΄μ μλ²λ‘ λ°μ΄ν° retrieveλ₯Ό μν΄ μ£ΌκΈ°μ μΌλ‘ uplink Requestλ₯Ό μ μ‘νλ€. μ΄μ pull based communication λ°©λ²μ κ²½μ°, μ°κ²° κ΄λ¦¬ λ° uplink Requestμ λ°λ₯Έ μ€λ²λ‘λκ° λ§λ€. The pull based communication method is performed through the following process. First, the terminal connects to an application server provided by the data service provider. The terminal periodically performs keep alive with the application server. In this case, the terminal periodically transmits an uplink request for data retrieval to the application server. In the pull based communication method, there are many overloads according to connection management and uplink request.
push based communication λ°©λ²μ λ€μκ³Ό κ°μ κ³Όμ μ ν΅ν΄ μνλλ€. μ°μ λ¨λ§μ λ°μ΄ν° μλΉμ€ μ 곡μκ° μ 곡νλ μ΄ν리μΌμ΄μ μλ²μ λ±λ‘νλ€. κ·Έλ¦¬κ³ λ¨λ§μ μ΄ν리μΌμ΄μ μλ²μ μ°κ²°λ νΈμ μλ²μ μ°κ²°νλ€. λ€μμΌλ‘ νΈμ μλ²λ μ£ΌκΈ°μ μΌλ‘ νΈμ ν΅μ§(Push Notification)μ λ¨λ§μ μ μ‘νλ€. κ·Έλ¦¬κ³ λ¨λ§μ μ£ΌκΈ°μ μΌλ‘ νΈμ μλ²μ μ°κ²° κ΄λ¦¬λ₯Ό μννλ€. Push based communication method is performed by the following process. First, the terminal registers with the application server provided by the data service provider. The terminal then connects to a push server connected to the application server. Next, the push server periodically transmits a push notification to the terminal. The terminal periodically performs connection management with the push server.
λ 1μ μ’ λ κΈ°μ μ λ°λΌ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄μ΄λ€.1 is a diagram illustrating a push service providing method according to the prior art.
λ 1μ μ°Έμ‘°νλ©΄, μ΄ν리μΌμ΄μ μλ²λ 110λ¨κ³μμ νΈμ μλΉμ€λ₯Ό μ 곡νκΈ° μν΄ μλ² λ±λ‘ μμ²μ νΈμ μλ²λ‘ μ μ‘νλ€. μλ² λ±λ‘ μμ²μ νΈμ μλ²μ μμΉλ₯Ό λνλ΄λ μ£Όμ μ 보 λ° μ 곡νλ μ΄ν리μΌμ΄μ μ λν μ 보λ₯Ό ν¬ν¨νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 115λ¨κ³μμ ν΄λΉ μ΄ν리μΌμ΄μ μλ²μ μ£Όμ μ 보 λ° μ΄ν리μΌμ΄μ μ λν μ 보λ₯Ό μ μ₯νλ€. λ€μμΌλ‘ νΈμ μλ²λ μλ² λ±λ‘ μλ΅μ μ΄ν리μΌμ΄μ μλ²λ‘ μ μ‘νλ€. μ¬κΈ°μ νΈμ μλ²λ μλ² μΈμ¦ μ½λλ₯Ό ν¨κ» μ λ¬νλ€. Referring to FIG. 1, the application server transmits a server registration request to a push server in step 110 to provide a push service. The server registration request includes address information indicating the location of the push server and information on the providing application. In operation 115, the push server stores address information of the corresponding application server and information on the application. The push server then sends a server registration response to the application server. Here the push server carries the server authentication code together.
λ¨λ§μ 120λ¨κ³μμ μ± λ§μΌ λλ μ¬μ
μ μλ²λ‘λΆν° μ΄ν리μΌμ΄μ
μ μΈμ€ν¨νλ€. κ·Έλ¦¬κ³ λ¨λ§μ 125λ¨κ³μμ μ΄ν리μΌμ΄μ
λ±λ‘μ νΈμ μλ²λ‘ μμ²νλ€. μ΄λ λ¨λ§μ νΈμ μλ²λ‘ μ΄ν리μΌμ΄μ
ID, λ¨λ§ ID λ° μ¬μ©μ IDλ₯Ό λͺ¨λ λ€ ν¬ν¨νκ±°λ μΌλΆλ§ ν¬ν¨νμ¬ ν¨κ» μ λ¬νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 130λ¨κ³μμ λ±λ‘ IDμ ν¨κ» λ¨λ§λ‘ λ±λ‘ μλ΅μ μ λ¬νλ€. In
νΈμ μλ²λ‘λΆν° λ±λ‘ μλ΅μ΄ μμ λλ©΄, λ¨λ§μ 135λ¨κ³μμ νΈμ μλ²λ‘λΆν° μ μ‘λ λ±λ‘ IDλ₯Ό ν¬ν¨ν λ±λ‘ νμΈμ μ΄ν리μΌμ΄μ
μλ²λ‘ μ μ‘νλ€. μ΄λ₯Ό μμ ν μ΄ν리μΌμ΄μ
μλ²λ 140λ¨κ³μμ λ±λ‘ IDλ₯Ό νμΈνκ³ , λ±λ‘μ μλ£νλ€. μ΄ν리μΌμ΄μ
μλ²λ 145λ¨κ³μμ μ΄ν리μΌμ΄μ
μ
λ°μ΄νΈ λλ λ°μ΄ν° λ³κ²½μΌλ‘ μΈν λ©μμ§λ₯Ό νΈλ¦¬κ±°νλ€. κ·Έλ¦¬κ³ μ΄ν리μΌμ΄μ
μλ²λ 150λ¨κ³μμ μλ² μΈμ¦ μ½λ, λ±λ‘ ID λ° νΈλ¦¬κ±°νκΈ° μν λ°μ΄ν°λ₯Ό ν¬ν¨ν νΈμ μμ²μ νΈμ μλ²λ‘ μ μ‘νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 160λ¨κ³μμ λ±λ‘ IDμ λμλλ μ΄ν리μΌμ΄μ
ID λ° λ°μ΄ν°λ₯Ό ν¬ν¨νλ νΈμ ν΅μ§λ₯Ό λ¨λ§λ‘ μ μ‘νλ€. When the registration response is received from the push server, the terminal transmits a registration confirmation including the registration ID transmitted from the push server to the application server in step 135. The application server receiving this checks the registration ID in
μλλ‘μ΄λμ κ°μ κ°λ°©ν OS(Operating System)μ κ²½μ° λ€μν νΈμ μλ μλΉμ€λ₯Ό μ 곡νλ νΈμ μλ²κ° μ‘΄μ¬νλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ λ€μν νΈμ μλΉμ€μ 곡μλ³λ‘ ꡬμ±λλ€. μλ₯Ό λ€μ΄ μ νμ¬ κ²½μ°, APNS(Apple Push Notification Service)λΌλ λ³λμ νΈμ μλ²λ₯Ό μ 곡νλ€. κ·Έλ¦¬κ³ goolgeμ μλλ‘μ΄λ κ²½μ°, C2DM(Android Cloud To Device Messaging Framework)λΌλ νΈμ μλ²λ₯Ό μ 곡νλ€. λν λ¨λ§μ μλΉμ€λ₯Ό μ 곡νλ μ΄λ ν΅μ μ¬μ μ μλ²λ³λ‘ νΈμ μλ²κ° κ°κ° μ 곡λ μ μλ€.In an open operating system (OS) such as Android, there is a push server that provides various push alarm services. The push server is configured by various push service providers. Apple, for example, offers a separate push server called Apple Push Notification Service (APNS). And in the case of goolge's Android, it provides a push server called C2DM (Android Cloud To Device Messaging Framework). In addition, a push server may be provided for each mobile service provider server providing a service to a terminal.
APSNμ κ²½μ° μ νμ¬μμ μ 곡ν νΉμ λ¨λ§μμ μ¬μ©λλ μ΄ν리μΌμ΄μ λ§ νΈμ μλΉμ€λ₯Ό μ 곡ν μ μλ€. κ·Έλ¦¬κ³ C2DMμ κ²½μ° μ‘μ κ°λ₯ν λ°μ΄ν°κ° μ νλμ΄ μμΌλ©°, μ¬μ© 건μκ° μ νλμ΄ μλ€. νΉμ μ΄λ ν΅μ μ¬μ μ μλ²λ³λ‘ νΈμ μλ²κ° ꡬμ±λλ κ²½μ°, ν΄λΉ μ¬μ μ μλ²μ νμ½ν νΉμ μ΄ν리μΌμ΄μ μλ§ νΈμ μλΉμ€κ° μ 곡λλ€. In the case of APSN, only an application used in a specific terminal provided by Apple can provide a push service. In the case of C2DM, the data that can be transmitted is limited, and the number of uses is limited. When a push server is configured for a specific mobile operator server, the push service is provided only to a specific application that is contracted with the corresponding operator server.
κ° νΈμ μλΉμ€ μ 곡μλ³λ‘ λλ μ΄λ ν΅μ μ¬μ μ λ³λ‘ νΈμ μλ²κ° μ‘΄μ¬ν¨μ λ°λΌ λ¨λ§μ μ 곡λλ νΈμ λ©μμ§λ ν΄λΉ νΈμ μλΉμ€ μ 곡μμ νμ½λ νΉμ μ΄ν리μΌμ΄μ μμλ§ μ μ©λλ€. μ΄μ μ΄ν리μΌμ΄μ μλΉμ€ μ 곡μκ° κ° μ§μλ³ λλ νΈμ μλΉμ€ μ 곡μλ μ΄λ ν΅μ μ¬μ μ λ³λ‘ νΈμ μλ²μ μ°κ²°μ μν λ³λμ μννΈμ¨μ΄ κ°λ°μ΄ νμνλ€. κ·Έλ¦¬κ³ λ¨λ§μ΄ λ±λ‘λ μ΄λ ν΅μ μ¬μ μμμλ§ ν΄λΉ μ΄ν리μΌμ΄μ μ νΈμ μλΉμ€κ° μ 곡λλ€. μ¦ λ¨λ§μ΄ λ€λ₯Έ κ΅κ°λ‘ λ‘λ°λλ κ²½μ°, μ΄ν리μΌμ΄μ μ νΈμ μλΉμ€κ° μ 곡λμ§ μλλ€λ λ¬Έμ μ μ΄ μλ€.As there is a push server for each push service provider or mobile carrier, push messages provided to the terminal are also applied only to a specific application that is contracted with the corresponding push service provider. Therefore, it is necessary to develop a separate software for the application service provider to connect to the push server for each region or for each push service provider or mobile service provider. In addition, the push service of the corresponding application is provided only in the mobile communication provider in which the terminal is registered. That is, when the terminal roams to another country, there is a problem that the push service of the application is not provided.
λ°λΌμ λ³Έ λ°λͺ μμλ μ΄λ ν΅μ μμ€ν λ° κ·Έ μ΄λ ν΅μ μμ€ν μμ μ¬λ¬ νΈμ μλΉμ€ μ 곡μκ° μ‘΄μ¬νλ κ²½μ°μ ν¨μ¨μ μΈ νΈμ μλΉμ€λ₯Ό μ 곡νλ λ°©λ²μ μ μνλ€.Accordingly, the present invention proposes a mobile communication system and a method for providing an efficient push service when there are multiple push service providers in the mobile communication system.
μκΈ°μ κ°μ λ¬Έμ μ μ ν΄κ²°νκΈ° μν΄ λ³Έ λ°λͺ μμ ν΅μ μμ€ν μ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λ¨λ§μ μ΄ν리μΌμ΄μ μ΄ μΈμ€ν¨λλ©΄, νΈμ μλ²λ‘ λ±λ‘μ μμ²νλ κ³Όμ κ³Ό, μκΈ° νΈμ μλ²λ‘λΆν° λ±λ‘ μλ΅μ΄ μμ λλ©΄, μκΈ° λ¨λ§μ μ΄ν리μΌμ΄μ μλ²λ‘ λ±λ‘ νμΈμ μ μ‘νλ κ³Όμ κ³Ό, μκΈ° μ΄ν리μΌμ΄μ μλ²λ μκΈ° νΈμ μλ²λ‘ μλ² λ±λ‘μ μμ²νλ κ³Όμ κ³Ό, μκΈ° νΈμ μλ²λ κ³΅μ© μΈμ¦ μλ²λ‘ μλ² λ±λ‘μ μμ²νκ³ , μκΈ° κ³΅μ© μΈμ¦ μλ²λ‘λΆν° μλ² λ±λ‘ μλ΅μ μμ νλ κ³Όμ κ³Ό, νΈμ μλΉμ€λ₯Ό μν λ©μμ§κ° νΈλ¦¬κ±°λλ©΄, μκΈ° μ΄ν리μΌμ΄μ μλ²λ μκΈ° νΈμ μλ²λ‘ νΈμλ₯Ό μμ²νλ κ³Όμ κ³Ό, μκΈ° νΈμ μλ²λ μκΈ° λ¨λ§λ‘ μκΈ° νΈμ μμ²μ λ°λ₯Έ νΈμ ν΅μ§λ₯Ό μ μ‘νλ κ³Όμ μ ν¬ν¨νλ κ²μ νΉμ§μΌλ‘ νλ€.In order to solve the above problems, in the present invention, a method of providing a push service of a communication system includes a process in which a terminal requests registration with a push server when an application is installed, and a registration response is received from the push server. Transmitting a registration confirmation to a server, the application server requesting a server registration to the push server, the push server requesting a server registration to a public authentication server, and receiving a server registration response from the public authentication server And when a message for a push service is triggered, the application server requesting a push to the push server, and the push server transmitting a push notification according to the push request to the terminal. It features.
κ·Έλ¬κΈ° μν΄ λ³Έ λ°λͺ μμ μκΈ° λ±λ‘ νμΈμ μ μ‘νλ κ³Όμ μ μκΈ° λ¨λ§μ μ¬μ μ μλ²λ‘λΆν° μμ νμ¬ λ―Έλ¦¬ μ μ₯λ νΈμ μλ² μ 보λ₯Ό μ μ‘νλ κ³Όμ μ ν¬ν¨νλ κ²μ νΉμ§μΌλ‘ νλ€. To this end, the process of transmitting the registration confirmation in the present invention is characterized in that it comprises the step of transmitting the push server information stored in advance received from the operator server.
λν λ³Έ λ°λͺ μμ μκΈ° μλ² λ±λ‘μ μμ²νλ κ³Όμ μ μκΈ° μ΄ν리μΌμ΄μ μλ²λ μκΈ° κ³΅μ© μΈμ¦ μλ²λ‘λΆν° 미리 μμ ν μλ² μΈμ¦ μ½λλ₯Ό μ μ‘νλ κ³Όμ μ ν¬ν¨νλ κ²μ νΉμ§μΌλ‘ νλ€.In the present invention, the process of requesting the server registration is characterized in that the application server comprises the step of transmitting a server authentication code received in advance from the public authentication server.
κ·Έλ¦¬κ³ λ³Έ λ°λͺ μμ μκΈ° μλ² λ±λ‘ μλ΅μ μμ νλ κ³Όμ μ μκΈ° νΈμ μλ²λ μκΈ° μ΄ν리μΌμ΄μ μλ²λ‘λΆν° μμ λ μκΈ° μλ² μΈμ¦ μ½λλ₯Ό μκΈ° κ³΅μ© μΈμ¦ μλ²λ‘ μ μ‘νλ κ³Όμ μ ν¬ν¨νλ κ²μ νΉμ§μΌλ‘ νλ€.And in the present invention, the step of receiving the server registration response is characterized in that the push server comprises the step of transmitting the server authentication code received from the application server to the public authentication server.
λν μκΈ°μ κ°μ λ¬Έμ μ μ ν΄κ²°νκΈ° μν΄ λ³Έ λ°λͺ μμ νΈμ μλΉμ€ μ 곡 μμ€ν μ μ΄ν리μΌμ΄μ μ΄ μΈμ€ν¨λλ©΄, νΈμ μλ²λ‘ λ±λ‘μ μμ²νκ³ , μκΈ° νΈμ μλ²λ‘λΆν° λ±λ‘ μλ΅μ΄ μμ λλ©΄, μ΄ν리μΌμ΄μ μλ²λ‘ λ±λ‘ νμΈμ μ μ‘νλ λ¨λ§κ³Ό, μκΈ° λ±λ‘ νμΈμ λ°λΌ μκΈ° νΈμ μλ²λ‘ μλ² λ±λ‘μ μμ²νκ³ , νΈμ μλΉμ€λ₯Ό μν λ©μμ§κ° νΈλ¦¬κ±°λλ©΄, μκΈ° νΈμ μλ²λ‘ νΈμλ₯Ό μμ²νλ μκΈ° μ΄ν리μΌμ΄μ μλ²μ, μκΈ° λ±λ‘ μμ²μ κ³΅μ© μΈμ¦ μλ²λ‘ μ μ‘νκ³ , μκΈ° κ³΅μ© μΈμ¦ μλ²λ‘λΆν° μκΈ° λ±λ‘ μμ²μ λ°λ₯Έ μλ΅μ΄ μμ λλ©΄, μκΈ° μ΄ν리μΌμ΄μ μλ²λ‘λΆν° μμ λλ μκΈ° νΈμ μμ²μ λ°λΌ μκΈ° λ¨λ§λ‘ νΈμ ν΅μ§λ₯Ό μ μ‘νλ μκΈ° νΈμ μλ²μ, μκΈ° μ΄ν리μΌμ΄μ μλ²λ‘ μλ² μΈμ¦ μ½λλ₯Ό μ μ‘νκ³ , μκΈ° νΈμ μλ²λ‘λΆν° μμ λ μλ² λ±λ‘ μμ²μ λ°λ₯Έ μλ΅μ μ μ‘νλ μκΈ° κ³΅μ© μΈμ¦ μλ²λ₯Ό ν¬ν¨νλ κ²μ νΉμ§μΌλ‘ νλ€.In addition, in order to solve the above problems, the push service providing system according to the present invention requests a registration to a push server when an application is installed, and receives a registration response from the push server, and transmits a registration confirmation to an application server. Requesting server registration to the push server according to the registration confirmation, and if a message for a push service is triggered, transmitting the registration request to a public authentication server, the application server requesting push to the push server, and When a response according to the registration request is received from a public authentication server, the push server for transmitting a push notification to the terminal according to the push request received from the application server, and transmits a server authentication code to the application server, On server registration requests received from the push server Transmitting a different response is characterized by including the common authentication server.
κ·Έλ¬κΈ° μν΄ λ³Έ λ°λͺ μμ μκΈ° λ¨λ§μ μ¬μ μ μλ²λ‘λΆν° μμ νμ¬ λ―Έλ¦¬ μ μ₯λ νΈμ μλ² μ 보λ₯Ό μκΈ° μ΄ν리μΌμ΄μ μλ²λ‘ μ μ‘νλ κ²μ νΉμ§μΌλ‘ νλ€. To this end, in the present invention, the terminal is characterized in that it receives from the operator server to transmit previously stored push server information to the application server.
λν λ³Έ λ°λͺ μμ μκΈ° μ΄ν리μΌμ΄μ μλ²λ μλ² λ±λ‘ μμ²μ, μκΈ° μλ² μΈμ¦ μ½λλ₯Ό μκΈ° νΈμ μλ²λ‘ μ μ‘νλ κ²μ νΉμ§μΌλ‘ νλ€.In the present invention, the application server is characterized in that for transmitting the server authentication code to the push server, when the server registration request.
κ·Έλ¦¬κ³ λ³Έ λ°λͺ μμ μκΈ° νΈμ μλ²λ μκΈ° μ΄ν리μΌμ΄μ μλ²λ‘λΆν° μμ λ μκΈ° μλ² μΈμ¦ μ½λλ₯Ό μκΈ° κ³΅μ© μΈμ¦ μλ²λ‘ μ μ‘νλ κ²μ νΉμ§μΌλ‘ νλ€.In the present invention, the push server is characterized in that for transmitting the server authentication code received from the application server to the public authentication server.
λ³Έ λ°λͺ μ λ°λ₯΄λ©΄, λ¨λ§μ μλΉμ€λ₯Ό μ 곡νλ μ΄λ ν΅μ μ¬μ μ μλ²λ³λ‘ νΈμ μλ²κ° ꡬμ±λ μ μλ€. μ΄μ λ°λΌ, λ¨λ§μ΄ λ€λ₯Έ μ΄λν΅μ μ¬μ μλ‘ λ‘λ°μ ν λμμλ νΈμ μλΉμ€λ₯Ό μ 곡 λ°μ μ μλ€. λν μ¬μ μ μλ²μ λ§κ° μ°κ³λ₯Ό ν΅ν΄ νΈλν½ μ€λ²λ‘λ λ°©μ§ λ° λ°μ΄ν° ν΅μ νκ²½μ μ΅μ νν μ μλ€. λν μ΄λ ν΅μ μ¬μ μ λλ νΈμ μλΉμ€ μ¬μ μλ€μ νΈμ μλ²λ₯Ό μ¬μ©νκΈ° μν μ μ°¨λ€μ΄ λμΌν΄μ§λ―λ‘, μ΄ν리μΌμ΄μ κ°λ°μ μ΄λ €μμ ν΄μν μ μλ€. According to the present invention, a push server may be configured for each mobile operator server providing a service to a terminal. Accordingly, the terminal may receive a push service while roaming to another mobile communication provider. In addition, by connecting the operator server and the network, it is possible to prevent traffic overload and optimize the data communication environment. In addition, since the procedures for using a push server of a mobile service provider or a push service provider are the same, it is possible to solve the difficulty of application development.
λ 1μ μ’ λ κΈ°μ μ λ°λΌ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄.1 is a diagram illustrating a push service providing method according to the prior art.
λ 2λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ ν΅μ μμ€ν ꡬμ±μ λμν λλ©΄.2 is a diagram illustrating a communication system configuration according to an embodiment of the present invention.
λ 3μ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλ² μ 보λ₯Ό νλνλ λ°©λ²μ λμν λλ©΄.3 is a diagram illustrating a method for obtaining push server information according to an embodiment of the present invention.
λ 4λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλ² μΈμ¦ λ°©λ²μ λμν λλ©΄.4 is a diagram illustrating a push server authentication method according to an embodiment of the present invention.
λ 5λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄.5 is a diagram illustrating a push service providing method according to an embodiment of the present invention.
λ 6μ λ³Έ λ°λͺ μ λ€λ₯Έ μ€μμμ λ°λ₯Έ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄.6 is a diagram showing a push service providing method according to another embodiment of the present invention.
λ 7μ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ λ¨λ§μμ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄.7 is a diagram illustrating a push service providing method in a terminal according to an embodiment of the present invention.
'νΈμ μλΉμ€'λ μλ²κ° μ¬μ©μκ° μνλ λ°μ΄ν°λ₯Ό μλμ μΌλ‘ μ 곡λλ μλΉμ€λ‘, λ€μν μ 보λ₯Ό κ°μΈμ κ΄μ¬ λΆμΌμ λ°λΌ μκ°λ, μ£Όμ λ³λ‘ μ 곡λλ μλ°©ν₯ ν΅μ μ μΉμΊμ€ν μλΉμ€μ΄λ€.'Push service' is a service in which the server automatically provides the data desired by the user. It is a webcasting service of two-way communication in which various information is provided according to an individual's interests by time zone and subject.
'λ¨λ§'μ μΈλΆλ‘λΆν° μ‘μμ λλ λ°μ΄ν°λ₯Ό μ²λ¦¬ν μ μλ μ 보 μ²λ¦¬ μ₯μΉλ‘, μ»΄ν¨ν°, μ€λ§νΈν°, νλΈλ¦Ώ PC λ±μ΄ ν¬ν¨λλ€.'Terminal' is an information processing apparatus that can process data transmitted and received from the outside, and includes a computer, a smartphone, a tablet PC, and the like.
μ΄ν 첨λΆλ λλ©΄μ μ°Έμ‘°νμ¬ λ³Έ λ°λͺ μ λμ μ리λ₯Ό μμΈν μ€λͺ νλ€. νκΈ°μμ λ³Έ λ°λͺ μ μ€λͺ ν¨μ μμ΄ κ΄λ ¨λ κ³΅μ§ κΈ°λ₯ λλ ꡬμ±μ λν ꡬ체μ μΈ μ€λͺ μ΄ λ³Έ λ°λͺ μ μμ§λ₯Ό λΆνμνκ² ν릴 μ μλ€κ³ νλ¨λλ κ²½μ°μλ κ·Έ μμΈν μ€λͺ μ μλ΅ν κ²μ΄λ€. κ·Έλ¦¬κ³ νμ λλ μ©μ΄λ€μ λ³Έ λ°λͺ μμμ κΈ°λ₯μ κ³ λ €νμ¬ μ μλ μ©μ΄λ€λ‘μ μ΄λ μ¬μ©μ, μ΄μ©μμ μλ λλ κ΄λ‘ λ±μ λ°λΌ λ¬λΌμ§ μ μλ€. κ·Έλ¬λ―λ‘ κ·Έ μ μλ λ³Έ λͺ μΈμ μ λ°μ κ±ΈμΉ λ΄μ©μ ν λλ‘ λ΄λ €μ ΈμΌ ν κ²μ΄λ€.Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.
λ 2λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ ν΅μ μμ€ν ꡬμ±μ λμν λλ©΄μ΄λ€.2 is a diagram illustrating a communication system configuration according to an embodiment of the present invention.
λ 2λ₯Ό μ°Έμ‘°νλ©΄, ν΅μ μμ€ν μ λ¨λ§, νΈμ μλ², μ΄ν리μΌμ΄μ μλ², κ³΅μ© μΈμ¦ μλ²λ‘ ꡬμ±λλ€. λ¨λ§μ μ΄λ ν΅μ μλΉμ€ μ¬μ μ λ±μ΄ μ 곡νλ ν΅μ μλΉμ€ μ¬μ©μ μν λ±λ‘ λ¨κ³ λλ μ±κ³΅μ μΈ λ±λ‘ νμ μ¬μ μκ° μ 곡νλ νΈμ μλ²μ μμΉλ₯Ό λνλ΄λ μ£Όμκ° ν¬ν¨λ νΈμ μλ² μ 보λ₯Ό μμ νλ€.Referring to FIG. 2, the communication system includes a terminal, a push server, an application server, and a public authentication server. The terminal receives the push server information including the address indicating the location of the push server provided by the provider after the registration step or successful registration for use of the communication service provided by the mobile communication service provider.
λ¨λ§μ μ΄ν리μΌμ΄μ μ μΈμ€ν¨νκ³ , μμ λ νΈμ μλ² μ 보λ₯Ό ν΅ν΄ ν΄λΉ νΈμ μλ²λ‘ μΈμ€ν¨ν μ΄ν리μΌμ΄μ λ±λ‘ λ° λ±λ‘ ID λ°κΈμ μμ²νλ€. νΈμ μλ²λ‘λΆν° λ±λ‘ IDκ° λ°κΈλλ©΄, λ¨λ§μ μ΄ν리μΌμ΄μ μλ²λ‘ λ°κΈλ λ±λ‘ IDμ νΈμ μλ² μ 보λ₯Ό μ λ¬νλ€. The terminal installs the application, and requests the application registration and issuance of the registration ID installed in the corresponding push server through the received push server information. When the registration ID is issued from the push server, the terminal delivers the registration ID and the push server information issued to the application server.
νΈμ μλ²λ μ΄ν리μΌμ΄μ μλ²λ‘λΆν° νΈμ λ©μμ§κ° ν¬ν¨λ νΈμ μμ²μ΄ μμ λλ©΄, μ΄λ₯Ό λ¨λ§λ‘ μ λ¬νλ€. νΈμ μλ²λ λ¨λ§λ‘λΆν° λ±λ‘ μμ²μ΄ μμ λλ©΄, λ±λ‘ IDλ₯Ό λ°κΈνλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ μ΄ν리μΌμ΄μ μλ²λ‘λΆν° μλ² μΈμ¦ μ½λκ° ν¬ν¨λ μλ² λ±λ‘ μμ²μ΄ μμ λλ©΄, κ³΅μ© μΈμ¦ μλ²λ‘ μ΄λ₯Ό μ μ‘νμ¬ μ΄ν리μΌμ΄μ μΈμ¦μ νμΈνλ€. μ΄ν리μΌμ΄μ μλ²κ° μΈμ¦λλ©΄, νΈμ μλ²λ μΈμ¦λ μ΄ν리μΌμ΄μ μλ²λ‘λΆν° νΈμ μμ²μ μμ νλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ λ¨λ§λ‘ μ΄λ₯Ό ν΅μ§νλ€.When the push server receives a push request including a push message from the application server, the push server delivers it to the terminal. The push server issues a registration ID when a registration request is received from the terminal. When the push server receives a server registration request including a server authentication code from the application server, the push server transmits it to the public authentication server to confirm application authentication. Once the application server is authenticated, the push server receives the push request from the authenticated application server. The push server notifies the terminal of this.
μ΄ν리μΌμ΄μ μλ²λ μ΄ν리μΌμ΄μ μ μ 곡νλ μ 곡μμ μν΄ κ΄λ¦¬λλ μλ²μ΄λ€. μ΄ν리μΌμ΄μ μλ²λ 미리 κ³΅μ© μΈμ¦ μλ²μ μλ² λ±λ‘μ μμ²νλ€. κ·Έλ¦¬κ³ μ΄ν리μΌμ΄μ μλ²λ κ³΅μ© μΈμ¦ μλ²λ‘λΆν° μλ² λ±λ‘ μλ΅κ³Ό ν¨κ» μμ λλ μλ² μΈμ¦ μ½λλ₯Ό μ μ₯νλ€. κ·Έλ¦¬κ³ μ΄ν리μΌμ΄μ μλ²λ λ¨λ§λ‘λΆν° νΈμ μλ² μ£Όμμ λν νΈμ μλ² μ 보 λ° λ±λ‘ IDκ° μμ λλ©΄, νΈμ μλ²λ‘ μλ² μΈμ¦ μ½λμ ν¨κ» μλ² λ±λ‘μ μμ²νλ€. λ€μμΌλ‘ μ΄ν리μΌμ΄μ μ 곡μκ° μ 곡ν μ΄ν리μΌμ΄μ μ λν νΈμ λ©μμ§κ° νΈλ¦¬κ±°λλ©΄, μ΄ν리μΌμ΄μ μλ²λ νΈμ μλ²λ‘ μ΄λ₯Ό μμ²νλ λ©μμ§λ₯Ό μ μ‘νλ€. An application server is a server managed by a provider that provides an application. The application server requests server registration from the public authentication server in advance. The application server stores the server authentication code received with the server registration response from the public authentication server. When the application server receives the push server information and the registration ID for the push server address from the terminal, the application server requests the server registration with the server authentication code to the push server. Next, when a push message for an application provided by the application provider is triggered, the application server sends a message requesting this to the push server.
κ³΅μ© μΈμ¦ μλ²λ μ΄ν리μΌμ΄μ μ λμλλ νΈμ λ©μμ§λ₯Ό μ μ‘νκΈ° μν μΈμ¦ν€μΈ μλ² μΈμ¦ μ½λλ₯Ό μ΄ν리μΌμ΄μ μλ²λ³λ‘ λ°κΈνλ€. μ¬κΈ°μ κ³΅μ© μΈμ¦ μλ²λ google, Apple, WAC(Wholesale Application Community) λ±κ³Ό κ°μ μ΄ν리μΌμ΄μ λ§μΌ μ΄μ© μλ²λ₯Ό ν΅ν΄ μ΄μ©λ μ μλ€. The common authentication server issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the application, for each application server. Here, the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).
λ¨λ§μ 210λ¨κ³μμ νΈμ μλ²λ‘ μΈμ€ν¨ν μ΄ν리μΌμ΄μ
λ±λ‘μ μμ²νλ€. μ΄λ λ¨λ§μ μ¬μ©μ ID, λ¨λ§μ ν λΉλ ID λ° μΈμ€ν¨ν μ΄ν리μΌμ΄μ
IDλ±μ ν¬ν¨ν λ±λ‘ μμ² λ©μμ§μ ν¨κ» μ μ‘νλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ μ΄μ λν λ±λ‘ IDλ₯Ό λ¨λ§λ‘ λ°κΈνλ€. λ€μμΌλ‘ λ¨λ§μ 220λ¨κ³μμ νΈμ μλ² μ£Όμ λ° λ±λ‘ IDλ₯Ό μ΄ν리μΌμ΄μ
μλ²λ‘ μ μ‘νλ€. μ΄λ νΈμ μλ² μ£Όμλ λ¨λ§μ΄ μ¬μ
μ μλ²λ‘λΆν° μμ ν νΈμ μλ² μ 보λ‘, νΈμ λ©μμ§λ₯Ό μ μ‘νλ νΈμ μλ²μ λν μ 보μ ν¬ν¨λλ€.The terminal requests application registration installed by the push server in step 210. In this case, the terminal transmits a registration request message including a user ID, an ID assigned to the terminal, and an installed application ID. And the push server issues a registration ID for this to the terminal. Next, the terminal transmits the push server address and the registration ID to the application server in
λ€μμΌλ‘ μ΄ν리μΌμ΄μ
μλ²μ νΈμ μλ² κ° λ±λ‘μ 230λ¨κ³μμ μννλ€. μ¦ μ΄ν리μΌμ΄μ
μλ²λ λ¨λ§λ‘λΆν° μμ λ νΈμ μλ² μ£Όμλ₯Ό μ΄μ©νμ¬ νΈμ μλ²μ μλ² λ±λ‘μ μμ²νλ€. μ¬κΈ°μ μ΄ν리μΌμ΄μ
μλ²λ κ³΅μ© μΈμ¦ μλ²λ₯Ό ν΅ν΄ 미리 μμ ν μλ² μΈμ¦ μ½λλ₯Ό ν¨κ» μ μ‘νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 240λ¨κ³μμ μ΄ν리μΌμ΄μ
μλ²λ‘λΆν° μμ ν μλ² μΈμ¦ μ½λλ₯Ό κ³΅μ© μΈμ¦ μλ²λ‘ μ λ¬νλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ κ³΅μ© μΈμ¦ μλ²λ₯Ό ν΅ν΄ λ±λ‘μ μμ²ν μ΄ν리μΌμ΄μ
μλ² μΈμ¦μ νμΈνλ€. Next, the registration between the application server and the push server is performed in step 230. That is, the application server requests a server registration from the push server using the push server address received from the terminal. Here, the application server transmits the server authentication code received in advance through the public authentication server. Then, the push server transmits the server authentication code received from the application server in
λ 3μ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλ² μ 보λ₯Ό νλνλ λ°©λ²μ λμν λλ©΄μ΄λ€.3 is a diagram illustrating a method of obtaining push server information according to an embodiment of the present invention.
λ 3μ μ°Έμ‘°νλ©΄, λ¨λ§μ΄ νΈμ μλ²λ‘ μΈμ€ν¨ν μ΄ν리μΌμ΄μ λ±λ‘μ μμ²νκΈ° μν΄μλ νΈμ μλ²μ μ£Όμλ₯Ό μμμΌ νλ€. κ·Έλ¬κΈ° μν΄ λ¨λ§μ μ¬μ μ μλ²λ‘λΆν° ν΄λΉ νΈμ μλ²μ κ΄λ ¨λ μ 보λ₯Ό μμ νλ€. Referring to FIG. 3, the terminal needs to know the address of the push server in order to request an application registration installed by the push server. To this end, the terminal receives information related to the push server from the operator server.
μ¬μ μ μλ²λ λ¨λ§μ ν΅μ μλΉμ€λ₯Ό μ 곡νλ μ¬μ μκ° κ΄λ¦¬νλ μλ²λ₯Ό μλ―Ένλ€. μ¬κΈ°μ μ¬μ μ μλ²λ νΈμ μλΉμ€λ₯Ό μ 곡νλ νΈμ μλ² μ 보λ₯Ό λ¨λ§μ μ λ¬νλ€. μ¬κΈ°μ νΈμ μλ² μ 보λ νΈμ μλ²μ μ£Όμμ λν μ 보 λ° ν΄λΉ νΈμ μλ²μμ νΈμ λ©μμ§κ° μ 곡λλ μ΄ν리μΌμ΄μ μ λν μ 보λ₯Ό ν¬ν¨νλ€. The operator server refers to a server managed by an operator providing a communication service to a terminal. Here, the operator server delivers the push server information providing the push service to the terminal. In this case, the push server information includes information on an address of a push server and information on an application for which a push message is provided by the corresponding push server.
λ¨λ§μ μ΄λ ν΅μ μ¬μ
μμκ²μμ ν΅μ μλΉμ€ μ¬μ©μ μν λ¨λ§ μΈμ¦ μ μ°¨ ν] 310λ¨κ³μμ μ¬μ
μ μλ²μμ νΈμ μλ² μ 보λ₯Ό μμ νλ€. λ¨λ§μ 320λ¨κ³μμ μ¬μ
μλ‘λΆν° μμ λ νΈμ μλ² μ 보λ₯Ό μ΄μ©νμ¬ ν΄λΉ νΈμ μλ²μ μ£Όμλ₯Ό νμΈνλ€. κ·Έλ¦¬κ³ λ¨λ§μ νμΈλ νΈμ μλ²λ‘ μ΄ν리μΌμ΄μ
μ λμλλ νΈμ λ©μμ§λ₯Ό μμ νκΈ° μν λ±λ‘ λ° λ±λ‘ ID λ°κΈμ μμ²νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ ν΄λΉ λ¨λ§μ λ±λ‘ IDλ₯Ό λ°κΈνμ¬ λ¨λ§λ‘ μ λ¬νλ€. The terminal receives the push server information from the operator server in
λ 4λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλ² μΈμ¦ λ°©λ²μ λμν λλ©΄μ΄λ€.4 is a diagram illustrating a push server authentication method according to an embodiment of the present invention.
λ 4λ₯Ό μ°Έμ‘°νλ©΄, λ³Έ λ°λͺ μμλ νΈμ μλ²μ μ΄ν리μΌμ΄μ μλ²μμ μ΄ν리μΌμ΄μ λ±λ‘ λ° κ·Έμ λν μΈμ¦μ μννλ κ²μ΄ μλλΌ, μ΄ν리μΌμ΄μ μλ²μ κ³΅μ© μΈμ¦ μλ² κ°μ μνλλ€. Referring to FIG. 4, in the present invention, the push server and the application server do not register and authenticate the application, but are performed between the application server and the public authentication server.
κ³΅μ© μΈμ¦ μλ²λ μ΄ν리μΌμ΄μ μ 곡μκ° κ΄λ¦¬νλ μ΄ν리μΌμ΄μ μλ²μμ μ 곡λλ μ΄ν리μΌμ΄μ μ λ±λ‘νκ³ , ν΄λΉ μ΄ν리μΌμ΄μ μ λμλλ νΈμ λ©μμ§λ₯Ό μ μ‘νκΈ° μν μΈμ¦ν€μΈ μλ² μΈμ¦ μ½λλ₯Ό μ΄ν리μΌμ΄μ μλ²λ³λ‘ λ°κΈνλ€. μ¬κΈ°μ κ³΅μ© μΈμ¦ μλ²λ google, Apple, WAC(Wholesale Application Community) λ±κ³Ό κ°μ μ΄ν리μΌμ΄μ λ§μΌ μ΄μ© μλ²λ₯Ό ν΅ν΄ μ΄μ©λ μ μλ€. The common authentication server registers an application provided by an application server managed by an application provider, and issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the corresponding application, for each application server. Here, the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).
μ΄ν리μΌμ΄μ μλ²λ 410λ¨κ³μμ κ³΅μ© μΈμ¦ μλ²λ‘ μμ μ΄ μ 곡νλ μ΄ν리μΌμ΄μ λ±λ‘μ μμ²νλ€. κ·Έλ¬λ©΄ κ³΅μ© μΈμ¦ μλ²λ ν΄λΉ μ΄ν리μΌμ΄μ μ λν μΈμ¦ν€μΈ μλ² μΈμ¦ μ½λλ₯Ό λ°κΈνμ¬ μ΄ν리μΌμ΄μ μλ²λ‘ μ μ‘νλ€. The application server requests the application registration provided by the application server to the public authentication server in step 410. The public authentication server then issues a server authentication code, which is an authentication key for the application, and sends it to the application server.
λ 5λ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄μ΄λ€.5 is a diagram illustrating a push service providing method according to an embodiment of the present invention.
λ 5λ₯Ό μ°Έμ‘°νλ©΄, μ΄ν리μΌμ΄μ μλ²λ 510λ¨κ³μμ κ³΅μ© μΈμ¦ μλ²λ‘ μλ² λ±λ‘μ μμ²νλ€. κ·Έλ¬λ©΄ κ³΅μ© μΈμ¦ μλ²λ 515λ¨κ³μμ μλ² λ±λ‘ μλ΅μ μ΄ν리μΌμ΄μ μλ²λ‘ μ μ‘νλ€. μ΄λ κ³΅μ© μΈμ¦ μλ²λ μ΄ν리μΌμ΄μ μλ²λ₯Ό μΈμ¦νλ©°, νΈμ λ©μμ§λ₯Ό μ μ‘νκΈ° μν μλ² μΈμ¦ μ½λλ₯Ό ν¨κ» μ μ‘νλ€.Referring to FIG. 5, in step 510, the application server requests server registration with a public authentication server. The public authentication server then transmits a server registration response to the application server in step 515. At this time, the public authentication server authenticates the application server and transmits a server authentication code for transmitting a push message.
λ€μμΌλ‘ λ¨λ§μ μ΄ν리μΌμ΄μ μ μΈμ€ν¨νλ€. μ΄λ λ¨λ§μ μ¬μ μ μλ²λ‘λΆν° μ΄ν리μΌμ΄μ μ λν νΈμ λ©μμ§λ₯Ό μ μ‘νλ νΈμ μλ² μ 보λ₯Ό μμ νλ€. μ΄λ νΈμ μλ² μ 보λ νΈμ μλ²μ μ£Όμμ λν μ 보λ₯Ό ν¬ν¨νλ€. Next, the terminal installs the application. At this time, the terminal receives the push server information for transmitting a push message for the application from the operator server. At this time, the push server information includes information on the address of the push server.
λ¨λ§μ 520λ¨κ³μμ μμ λ νΈμ μλ² μ 보λ₯Ό μ μ₯νλ€. κ·Έλ¦¬κ³ λ¨λ§μ 525λ¨κ³μμ μμ λ νΈμ μλ² μ 보λ₯Ό ν΅ν΄ νμΈλ μ£Όμμ νΈμ μλ²μ λ±λ‘μ μμ²νλ€. μ¬κΈ°μ λ¨λ§μ λ¨λ§ ID, μ¬μ©μ ID, μΈμ€ν¨ν μ΄ν리μΌμ΄μ
IDλ₯Ό ν¨κ» νΈμ μλ²λ‘ μ λ¬νλ€. κ·Έλ¦¬κ³ νΈμ μλ²λ 530λ¨κ³μμ μ΄λ₯Ό νμΈνκ³ , λ±λ‘ μλ΅μ λ¨λ§λ‘ μ μ‘νλ€. μ΄λ νΈμ μλ²λ λ±λ‘ IDλ₯Ό λ°κΈνμ¬ λ¨λ§λ‘ ν¨κ» μ λ¬νλ€.The terminal stores the push server information received in
λ±λ‘ μλ΅μ μμ ν λ¨λ§μ 535λ¨κ³μμ μ΄ν리μΌμ΄μ
μλ²λ‘ λ±λ‘ νμΈ λ©μμ§λ₯Ό μ λ¬νλ€. λ±λ‘ νμΈ λ©μμ§λ νΈμ μλ²λ‘λΆν° μμ λ λ±λ‘ ID λ° νΈμ μλ²μ μ£Όμκ° ν¬ν¨λ νΈμ μλ² μ 보λ₯Ό ν¬ν¨νλ€. μ΄λ₯Ό μμ ν μ΄ν리μΌμ΄μ
μλ²λ 540λ¨κ³μμ λ±λ‘μ μλ£νλ€. Upon receiving the registration response, the terminal transmits a registration confirmation message to the application server in step 535. The registration confirmation message includes the push server information including the registration ID received from the push server and the address of the push server. The application server receiving this is registered in
λ€μμΌλ‘ μ΄ν리μΌμ΄μ μλ²λ 545λ¨κ³μμ νΈμ μλ²λ‘ μλ² λ±λ‘μ μμ²νλ€. μ΄λ μ΄ν리μΌμ΄μ μλ²λ κ³΅μ© μΈμ¦ μλ²λ‘λΆν° μμ λ μλ² μΈμ¦ μ½λλ₯Ό ν¨κ» νΈμ μλ²λ‘ μ μ‘νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 550λ¨κ³μμ μ΄ν리μΌμ΄μ μλ²λ‘λΆν° μμ λ μλ² μΈμ¦ μ½λκ° ν¬ν¨λ μλ² λ±λ‘ μμ²μ κ³΅μ© μΈμ¦ μλ²λ‘ μ λ¬νλ€. κ³΅μ© μΈμ¦ μλ²λ 560λ¨κ³μμ νΈμ μλ²λ‘λΆν° μμ λ μλ² μΈμ¦ μ½λλ₯Ό νμΈνκ³ μ΄μ λν μλ΅μ νΈμ μλ²λ‘ μ μ‘νλ€. Next, the application server requests a server registration to the push server in step 545. At this time, the application server transmits the server authentication code received from the public authentication server together to the push server. In operation 550, the push server transmits a server registration request including a server authentication code received from the application server to the public authentication server. The public authentication server checks the server authentication code received from the push server in step 560 and transmits a response to the push server.
μ΄ν리μΌμ΄μ
μλ²λ 565λ¨κ³μμ μ΄ν리μΌμ΄μ
μ
λ°μ΄νΈ λλ λ°μ΄ν° λ³κ²½μ λ°λ₯Έ λ©μμ§λ₯Ό νΈλ¦¬κ±°νλ€. κ·Έλ¦¬κ³ μ΄ν리μΌμ΄μ
μλ²λ 570λ¨κ³μμ νΈμ μλ²λ‘ νΈμ μμ²μ μ μ‘νλ€. μ΄λ μ΄ν리μΌμ΄μ
μλ²λ κ³΅μ© μΈμ¦ μλ²λ‘λΆν° μμ λ μλ² μΈμ¦ μ½λ, λ¨λ§λ‘λΆν° μμ λ λ±λ‘ ID λ° νΈμν λ°μ΄ν°λ₯Ό ν¨κ» μ μ‘νλ€. κ·Έλ¬λ©΄ νΈμ μλ²λ 575λ¨κ³μμ λ±λ‘ IDλ₯Ό νμΈνμ¬ ν΄λΉ λ¨λ§μ νμΈνκ³ , μμ λ νΈμ μμ²μ λ°λΌ νμΈλ λ¨λ§λ‘ μ΄ν리μΌμ΄μ
ID λ° νΈμν λ°μ΄ν°λ₯Ό ν¬ν¨νλ νΈμ λ©μμ§λ₯Ό ν΅μ§νλ€. The application server triggers a message according to the application update or data change in
λ 6μ λ³Έ λ°λͺ μ λ€λ₯Έ μ€μμμ λ°λ₯Έ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄μ΄λ€.6 is a diagram illustrating a push service providing method according to another embodiment of the present invention.
λ 6μ μ°Έμ‘°νλ©΄, λ‘λ° λ±μ ν΅ν΄ νΈμ μλ²κ° λ³κ²½λλ κ²½μ°, μ¬μ μ μλ²λ λ¨λ§λ‘ λ³κ²½λλ νΈμ μλ² μ 보λ₯Ό λ¨λ§λ‘ μ λ¬νλ€. μ¬κΈ°μ νΈμ μλ² 1μ λ‘λ° μ νΈμ λ©μμ§λ₯Ό μ λ¬νλ νΈμ μλ²μ΄κ³ , νΈμ μλ² 2λ λ‘λ°μ μν΄ λ³κ²½λ νΈμ μλ²λ₯Ό λνλΈλ€. Referring to FIG. 6, when the push server is changed through roaming or the like, the operator server transmits the push server information changed to the terminal to the terminal. Here, push server 1 is a push server that delivers a push message before roaming, and push server 2 represents a push server changed by roaming.
λ¨λ§μ 610λ¨κ³μμ μ¬μ
μ μλ²λ‘λΆν° λ³κ²½λ νΈμ μλ² μ 보λ₯Ό μ μ₯νλ€. κ·Έλ¦¬κ³ λ¨λ§μ 615λ¨κ³μμ νΈμ μλ² 1λ‘ λ±λ‘ μμ²νλ€. μ΄λ λ¨λ§μ μ¬μ©μ ID, λ¨λ§ ID λ° μ¬μ
μ μλ²λ‘λΆν° μμ λ νΈμ μλ² μ£Όμκ° ν¬ν¨λ νΈμ μλ² μ 보λ₯Ό ν¨κ» μ μ‘νλ€. κ·Έλ¬λ©΄ νΈμ μλ² 1μ 620λ¨κ³μμ νΈμ μλ² 2λ‘ λ±λ‘ νμΈμ μμ²νλ€. μ¬κΈ°μ νΈμ μλ² 1μ μ¬μ©μ ID λ° μ₯μΉ IDλ₯Ό ν¨κ» μ μ‘νλ€. In
μ΄λ₯Ό μμ ν νΈμ μλ² 2λ 625λ¨κ³μμ νΈμ μλ² 1λ‘ λ±λ‘ νμΈ μλ΅μ μ μ‘νλ€. λ±λ‘ νμΈ μλ΅μ νΈμ μλ² 2κ° μ 곡νλ μ΄ν리μΌμ΄μ λ€μ ID, λ±λ‘ ID λ° νΈμ μλ² 2μ λ±λ‘λ μ΄ν리μΌμ΄μ μλ²μ IDλ₯Ό ν¨κ» μ μ‘νλ€. In response to this, the push server 2 transmits a registration confirmation response to the push server 1 in step 625. The ID of the applications provided by the push server 2, the registration ID, and the ID of the application server registered on the push server 2 are transmitted together in the registration confirmation response.
νΈμ μλ² 1μ 630λ¨κ³μμ νΈμ μλ² 2λ‘λΆν° μμ λ λ±λ‘ μλ΅μ λ¨λ§λ‘ μ μ‘νλ€. μ΄λ νΈμ μλ² 1μ νΈμ μλ² 2λ‘λΆν° μμ λ λ±λ‘ IDλ₯Ό λ¨λ§μ ν¨κ» μ μ‘νλ€. μ΄λ₯Ό μμ ν λ¨λ§μ 635λ¨κ³μμ λ±λ‘ νμΈ λ©μμ§λ₯Ό μ΄ν리μΌμ΄μ μλ²λ‘ μ μ‘νλ€. λ±λ‘ νμΈ λ©μμ§μ νΈμ μλ² 2λ‘λΆν° μ μ‘λ λ±λ‘ ID λ° νΈμ μλ² 2μ μ£Όμμ λν νΈμ μλ² μ λ³΄κ° ν¬ν¨λλ€. The push server 1 transmits a registration response received from the push server 2 to the terminal in step 630. At this time, the push server 1 transmits the registration ID received from the push server 2 to the terminal. In step 635, the terminal receives the registration confirmation message to the application server. The registration confirmation message includes the registration ID sent from push server 2 and the push server information for the address of push server 2.
μ΄ν리μΌμ΄μ
μλ²λ 640λ¨κ³μμ μ΄ν리μΌμ΄μ
λ³κ²½ λλ λ°μ΄ν° μ
λ°μ΄νΈμ λ°λ₯Έ νΈμ λ©μμ§λ₯Ό νΈλ¦¬κ±°νλ€. κ·Έλ¬λ©΄ μ΄ν리μΌμ΄μ
μλ²λ 645λ¨κ³μμ νΈμ μμ²μ νΈμ μλ² 2λ‘ μ μ‘νλ€. μ΄λ μ΄ν리μΌμ΄μ
μλ²λ μλ² μΈμ¦ μ½λ λ° λ±λ‘ ID, νΈμλ λ°μ΄ν°λ₯Ό ν¨κ» μ μ‘νλ€. μ΄λ₯Ό μμ ν νΈμ μλ² 2λ 650λ¨κ³μμ ν΄λΉ μ΄ν리μΌμ΄μ
μ λν νΈμ λ©μμ§λ₯Ό λ¨λ§λ‘ ν΅μ§νλ€. μ¬κΈ°μ νΈμ μλ² 2λ μ΄ν리μΌμ΄μ
ID λ° νΈμλ λ°μ΄ν°λ₯Ό ν¨κ» λ¨λ§λ‘ μ μ‘νλ€. The application server triggers a push message according to the application change or data update in
λ 7μ λ³Έ λ°λͺ μ μ€μμμ λ°λ₯Έ λ¨λ§μμ νΈμ μλΉμ€ μ 곡 λ°©λ²μ λμν λλ©΄μ΄λ€.7 is a diagram illustrating a push service providing method in a terminal according to an embodiment of the present invention.
λ 7μ μ°Έμ‘°νλ©΄, λ¨λ§μ 710λ¨κ³μμ μ΄λ ν΅μ μ¬μ
μμκ² ν΅μ μλΉμ€ μ¬μ©μ μν κ°μ
λ° μΈμ¦μ μμ²νλ€. κ·Έλ¦¬κ³ λ¨λ§μ 720λ¨κ³μμ μ¬μ
μ μλ²λ‘λΆν° νΈμ μλ² μ 보λ₯Ό μμ νμ¬ μ μ₯νλ€. μ΄λ νΈμ μλ² μ 보λ νΈμ μλ²μ μ£Όμλ₯Ό ν¬ν¨νλ©°, μ¬μ
μ μλ²λ κ°κ°μ νΈμ μλ²μ λν μ£Όμλ₯Ό λͺ¨λ μκ³ μλ€. Referring to FIG. 7, in
λ€μμΌλ‘ λ¨λ§μ 730λ¨κ³μμ νΈμ μλ²λ‘ λ±λ‘μ μμ²νλ€. μ΄λ λ¨λ§μ λ¨λ§μ μ¬μ©νλ μ¬μ©μ ID, λ¨λ§μ ν λΉλ ID λ° μ¬μ
μ μλ²λ‘λΆν° μ μ‘λ νΈμ μλ²μ μ£Όμλ₯Ό λ±λ‘ μμ²κ³Ό ν¨κ» μ μ‘νλ€. Next, the terminal requests registration with a push server in
λ¨λ§μ 740λ¨κ³μμ λ±λ‘ IDλ₯Ό νΈμ μλ²λ‘λΆν° μμ νλ€. κ·Έλ¦¬κ³ λ¨λ§μ 750λ¨κ³μμ μ΄ν리μΌμ΄μ
μλ²λ‘ λ±λ‘ IDκ° ν¬ν¨λ λ±λ‘ νμΈμ μ μ‘νλ€. μ΄λ λ¨λ§μ νΈμ μλ²μ μ£Όμλ₯Ό λ±λ‘ νμΈκ³Ό ν¨κ» μ μ‘νλ€. λ€μμΌλ‘ λ¨λ§μ 760λ¨κ³μμ νΈμ μλ²λ‘λΆν° νΈμ λ©μμ§λ₯Ό μμ νλ€. In
μ΄μ κ°μ κ³Όμ λ€μ ν΅ν΄ μ΄ν리μΌμ΄μ μλ²μ νΈμ μλ² κ°μ λ±λ‘μ΄ κ³΅μ© μΈμ¦ μλ²λ₯Ό ν΅ν΄ κ΄λ¦¬λλ―λ‘, νΈμ μλ²λ μ΄ν리μΌμ΄μ μ μ 곡νλ μ΄ν리μΌμ΄μ μλ²λ³λ‘ λ±λ‘ν νμμ±μ΄ μλ€. λν λ¨λ§μ μ΄λμΌλ‘ μ¬μ μ μλ²λ³λ‘ λ‘λ°λμμ λ, μλ‘μ΄ μ΄ν리μΌμ΄μ μ λ€μ΄λ‘λν νμμμ΄, ν΄λΉ μ΄ν리μΌμ΄μ μ λν νΈμ λ©μμ§λ₯Ό ν΅μ§νλ νΈμ μλ²μ μ£Όμλ§μ λ³κ²½νλ©΄ λλ€. Through such processes, registration between the application server and the push server is managed through a common authentication server, so the push server does not need to register for each application server providing the application. In addition, when roaming by the operator server by the movement of the terminal, it is not necessary to download a new application, it is only necessary to change the address of the push server to notify the push message for the application.
ννΈ λ³Έ λ°λͺ μ μμΈν μ€λͺ μμλ ꡬ체μ μΈ μ€μμμ κ΄ν΄ μ€λͺ νμμΌλ, λ³Έ λ°λͺ μ λ²μμμ λ²μ΄λμ§ μλ νλ λ΄μμ μ¬λ¬ κ°μ§ λ³νμ΄ κ°λ₯ν¨μ λ¬Όλ‘ μ΄λ€. κ·Έλ¬λ―λ‘ λ³Έ λ°λͺ μ λ²μλ μ€λͺ λ μ€μμμ κ΅νλμ§ μμΌλ©°, νμ λλ νΉνμ²κ΅¬μ λ²μλΏλ§ μλλΌ μ΄ νΉνμ²κ΅¬μ λ²μμ κ· λ±ν κ²λ€μ μν΄ μ ν΄μ ΈμΌ νλ€. Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.
Claims (12)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR10-2012-0004417 | 2012-01-13 | ||
| KR1020120004417A KR20130083667A (en) | 2012-01-13 | 2012-01-13 | Mobile communication and method for providing push service thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2013105809A1 true WO2013105809A1 (en) | 2013-07-18 |
Family
ID=48781693
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/KR2013/000241 Ceased WO2013105809A1 (en) | 2012-01-13 | 2013-01-11 | Communication system and method for providing push service in said communication system |
Country Status (2)
| Country | Link |
|---|---|
| KR (1) | KR20130083667A (en) |
| WO (1) | WO2013105809A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991412A (en) * | 2015-02-12 | 2016-10-05 | ιΏιε·΄ε·΄ιε’ζ§θ‘ζιε ¬εΈ | Method and device for pushing message |
| CN109299127A (en) * | 2018-08-22 | 2019-02-01 | δΈε½θεη½η»ιδΏ‘ιε’ζιε ¬εΈ | Query method, device and readable storage medium for communication service |
| EP2899945B1 (en) * | 2014-01-23 | 2021-01-13 | Deutsche Telekom AG | Method for an enhanced communication between a first network node and a second network node of a telecommunications network, and telecommunications network |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100788245B1 (en) * | 2006-10-19 | 2007-12-27 | (μ£Ό)μΈνΈλ‘λͺ¨λ°μΌ | Integrated push service system and method |
| US20090158397A1 (en) * | 2007-12-17 | 2009-06-18 | Microsoft Corporation | Secure Push and Status Communication between Client and Server |
| US7673007B2 (en) * | 2001-11-20 | 2010-03-02 | Nokia Corporation | Web services push gateway |
| KR101029921B1 (en) * | 2009-11-27 | 2011-04-18 | μΌμ±μμ€λμμ€ μ£Όμνμ¬ | Content Push System and Method in Wide Area Wireless LAN Environment |
| US20110289172A1 (en) * | 2009-02-25 | 2011-11-24 | Apple Inc. | Managing notification messages |
-
2012
- 2012-01-13 KR KR1020120004417A patent/KR20130083667A/en not_active Withdrawn
-
2013
- 2013-01-11 WO PCT/KR2013/000241 patent/WO2013105809A1/en not_active Ceased
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7673007B2 (en) * | 2001-11-20 | 2010-03-02 | Nokia Corporation | Web services push gateway |
| KR100788245B1 (en) * | 2006-10-19 | 2007-12-27 | (μ£Ό)μΈνΈλ‘λͺ¨λ°μΌ | Integrated push service system and method |
| US20090158397A1 (en) * | 2007-12-17 | 2009-06-18 | Microsoft Corporation | Secure Push and Status Communication between Client and Server |
| US20110289172A1 (en) * | 2009-02-25 | 2011-11-24 | Apple Inc. | Managing notification messages |
| KR101029921B1 (en) * | 2009-11-27 | 2011-04-18 | μΌμ±μμ€λμμ€ μ£Όμνμ¬ | Content Push System and Method in Wide Area Wireless LAN Environment |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2899945B1 (en) * | 2014-01-23 | 2021-01-13 | Deutsche Telekom AG | Method for an enhanced communication between a first network node and a second network node of a telecommunications network, and telecommunications network |
| CN105991412A (en) * | 2015-02-12 | 2016-10-05 | ιΏιε·΄ε·΄ιε’ζ§θ‘ζιε ¬εΈ | Method and device for pushing message |
| KR20170117111A (en) * | 2015-02-12 | 2017-10-20 | μ리λ°λ° κ·Έλ£Ή νλ© λ¦¬λ―Έν°λ | Method and apparatus for pushing messages |
| EP3258653A4 (en) * | 2015-02-12 | 2018-03-14 | Alibaba Group Holding Limited | Message pushing method and device |
| JP2018508072A (en) * | 2015-02-12 | 2018-03-22 | γ’γͺγγ γ°γ«γΌγ γγ¦γ«γγ£γ³γ° γͺγγγγ | Method and apparatus for pushing messages |
| CN105991412B (en) * | 2015-02-12 | 2019-03-19 | ιΏιε·΄ε·΄ιε’ζ§θ‘ζιε ¬εΈ | Information push method and device |
| KR102167613B1 (en) * | 2015-02-12 | 2020-10-20 | μ리λ°λ° κ·Έλ£Ή νλ© λ¦¬λ―Έν°λ | Message push method and device |
| US10812314B2 (en) | 2015-02-12 | 2020-10-20 | Alibaba Group Holding Limited | Methods and apparatuses for pushing a message |
| CN109299127A (en) * | 2018-08-22 | 2019-02-01 | δΈε½θεη½η»ιδΏ‘ιε’ζιε ¬εΈ | Query method, device and readable storage medium for communication service |
| CN109299127B (en) * | 2018-08-22 | 2021-03-30 | δΈε½θεη½η»ιδΏ‘ιε’ζιε ¬εΈ | Communication service query method and device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| KR20130083667A (en) | 2013-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019027061A1 (en) | Connected gateway server system for real-time vehicle control service | |
| WO2011046393A2 (en) | Apparatus and method for establishing a personal network for providing a cpns service | |
| WO2013085316A1 (en) | Method and apparatus for providing firmware over the air service to user equipments | |
| WO2016003142A1 (en) | Method and apparatus for selecting profile of terminal in mobile network | |
| WO2017061800A1 (en) | Method and apparatus for remotely providing profile in communication system | |
| WO2020071888A1 (en) | Method and system for detecting edge server in mobile telecommunication network | |
| WO2019035638A1 (en) | Method for checking change in wireless connection type of terminal in third-party application server | |
| WO2013039278A1 (en) | Method and device for web redirect authentication in wifi roaming based on ac and ap interworking | |
| WO2010041901A2 (en) | System and method for installing smart card applet | |
| CN112565439B (en) | Internet of things communication method and system | |
| WO2011159096A2 (en) | Apparatus and method for registering personal network | |
| WO2012070801A2 (en) | Authentication system and authentication method therefor in a wireless lan environment | |
| WO2011149251A2 (en) | System for authentication management of a sensor node having a subscription processing function, and a method for operating the system | |
| WO2017074034A1 (en) | Method and apparatus for interworking between heterogeneous systems | |
| WO2014163254A1 (en) | P2p connection system and terminal, and p2p connection method using same in mobile environment | |
| WO2015065013A1 (en) | Method and apparatus for multi-users registering home network supporting application based device | |
| WO2016013718A1 (en) | System and method for providing web-based advertisement by using wi-fi network | |
| WO2013039277A1 (en) | Method and device for accounting in wifi roaming based on ac and ap interworking | |
| WO2018070740A1 (en) | Method and device for connecting capability exposure function and network functions | |
| US9781753B2 (en) | Proximity map request method, server and network entity using the same, proximity request validating method, and server and network entity using the same | |
| WO2015002443A1 (en) | Mobile device and method for controlling transmission to web server in mobile device | |
| WO2013112015A1 (en) | Method and apparatus for efficient security management of disaster message in mobile communication system | |
| WO2013147421A1 (en) | Server and method for managing access of terminal to connection blocked resource and terminal | |
| WO2018066870A1 (en) | Initial operation method for roaming terminal accessing network in mobile communication environment | |
| WO2013105809A1 (en) | Communication system and method for providing push service in said communication system |
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: 13736440 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 13736440 Country of ref document: EP Kind code of ref document: A1 |