WO2012096438A2 - Procédé de transmission de message de poussée - Google Patents

Procédé de transmission de message de poussée Download PDF

Info

Publication number
WO2012096438A2
WO2012096438A2 PCT/KR2011/008867 KR2011008867W WO2012096438A2 WO 2012096438 A2 WO2012096438 A2 WO 2012096438A2 KR 2011008867 W KR2011008867 W KR 2011008867W WO 2012096438 A2 WO2012096438 A2 WO 2012096438A2
Authority
WO
WIPO (PCT)
Prior art keywords
push
server
terminal
private network
public
Prior art date
Application number
PCT/KR2011/008867
Other languages
English (en)
Korean (ko)
Other versions
WO2012096438A3 (fr
Inventor
김대영
Original Assignee
Kim Dae Young
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 Kim Dae Young filed Critical Kim Dae Young
Publication of WO2012096438A2 publication Critical patent/WO2012096438A2/fr
Publication of WO2012096438A3 publication Critical patent/WO2012096438A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses

Definitions

  • the disclosed technology relates to a push message transmission method, and more particularly, to a push message transmission method capable of flexibly connecting a push server to a private network.
  • terminals With the development of mobile technology, terminals have increased in processing speed and capacity and are able to perform communication through various communication networks. With the development of terminals, various services are provided for terminals, and push services are provided as various service models as one of such services.
  • NAT Network Address Translation
  • the push server is connectable with the application server and at least one terminal.
  • the push server maintains a public network communication module for communicating through a public network, a private network communication module for communicating through a private network, a private network address for a private network and a public network address for a public network, and the private network communication module.
  • a controller for transmitting a push message transmitted from the application server to a corresponding terminal using at least one of the public network communication modules.
  • the controller may allocate a push service ID to the at least one terminal and provide the allocated push service ID to the application server.
  • the push server may be connected to a lookup server through the public network and / or private network.
  • the push server comprises a terminal information database including at least one of a push service ID, a private network address and a public network address of the terminal, and a socket ID of the communication module of the terminal for each terminal of the equator; It may further include.
  • the controller may perform communication with the corresponding terminal via the public network or private network determined according to the service included in the push message.
  • the terminal is connectable to an application server that transmits a push message, a lookup server, and at least one push server.
  • the terminal requests the lookup server for a public network communication module for communicating through a public network, a private network communication module for communicating through a private network, and a network address of the push server, and displays public and private network addresses of the push server.
  • It includes a push client module to determine.
  • the terminal may further comprise a push server database that stores public and private network addresses of the push server.
  • the push client module may perform communication with the private network address stored in the push server database, and if the communication is not made, may request the private network address of the push server from the lookup server.
  • the push client module may perform communication using the private network address, and if communication is not performed, perform communication using the public network address. In one embodiment, the push client module may maintain both the first communication path connected with the push server and the private network address and the second communication path connected with the public network address. In one embodiment, if the terminal is connected to the push server via the public network, the terminal may perform data transmission and reception by performing encryption, otherwise, the terminal may transmit and receive data without performing encryption.
  • the push server comprises a first push server and a second push server, and if the terminal communicated using either the public or private network address of the first push server, the terminal pushes the first push The communication may be performed using the other of the server's public and private network addresses. In one embodiment, the push server includes a first push server and a second push server, and wherein the terminal is connected to the first push server. If communicating using the public network address, the terminal may communicate using the private network address of the first push server.
  • the push message transmission system is connectable with the terminal and the application server.
  • the push message transmission system uses a private network address and a public address for each of the at least one push server and at least one push server for transmitting a push message received from the application server to the terminal using at least one of a private network and a public network.
  • a lookup server that stores a network address and provides the terminal with a private and public network address of the push server.
  • the push server may provide the changed private network address to the lookup server.
  • the public network may be a Wi-Fi network
  • the private network may be a cellular communication network.
  • the push server may select any one of the public network or private network based on the service included in the push message to communicate with the terminal. In one embodiment, if the push server is connected to the terminal through the public network, the push server may perform data transmission and reception by performing encryption, otherwise, the push server may transmit and receive data without performing encryption. In an embodiment, the push server may allocate a push service ID to the terminal and provide the push service ID to the application server.
  • the push message transmission method is performed in a push message transmission system for transmitting a push message received from the application server to the terminal.
  • the push message transmission system includes a lookup server and at least one push server.
  • the method for transmitting push messages may include storing, by the lookup server, a private network address and a public network address of each of the at least one push server, and providing the terminal with the private network address of the corresponding push server. Include.
  • the push message transmission method may further include providing, by the lookup server, a public and / or private network address of the push server to the application server according to a request.
  • the push message transmission method may further include the push server assigning a push service ID to the terminal and providing the allocated push service ID to the application server.
  • the server may be dynamically connected to the terminal capable of performing communication over a public or private network through the public or seo network.
  • the server maintains a public network communication module for communicating through the public network, a private network communication module for communicating through the private network and a private network address for the private network and a public network address for the public network.
  • a controller configured to communicate with the terminal using at least one of a private network communication module and the public network communication module.
  • the server may be a push server for sending push messages.
  • the terminal may be dynamically connected to at least one server capable of communicating through a public network or a private network through the public network or a standing network.
  • the at least one server includes a lookup server that stores public and private network addresses of a particular server.
  • the terminal requests at least one communication module for performing communication over a public or private network, the lookup server for public and / or private network addresses of the specific server, and the public and / or private network according to a current estimation situation.
  • a client module for communicating with the particular server using at least one of the addresses.
  • FIG. 1 is a block diagram of a general push message transmission system.
  • FIG. 2 is a configuration diagram according to an embodiment of a push message system to which the disclosed technology may be applied.
  • FIG. 3 is a configuration diagram according to another embodiment of a push message system to which the disclosed technology may be applied.
  • FIG. 4 is a configuration diagram according to an embodiment of the push server of FIG. 2.
  • FIG. 5 is a diagram illustrating an embodiment of a terminal of FIG. 2.
  • FIG. 6 is a block diagram according to an embodiment of a push message transmission method to which the disclosed technology can be applied.
  • FIG. 7 is a flowchart illustrating a push message transmission method according to FIG. 6.
  • first and second are intended to distinguish one component from another component, and the scope of rights should not be limited by these terms.
  • first component may be named a second component, and similarly, the second component may also be named a first component.
  • first item, second item and / or third item may be given from two or more of the first, second or third items as well as the first, second or third items. Any combination of the possible items.
  • an identification code (e.g., a, b, c, etc.) is used for convenience of description, and the identification code does not describe the order of the steps, and each step is clearly in a specific order. Unless stated otherwise, it may occur out of the stated order. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.
  • FIG. 1 is a block diagram of a general push message transmission system.
  • an application server 110 and a push server 120 are connected to a public network (for example, an internet network), and the terminal 140 is a public network (for example, Wi-Fi network) and private network (for example, cellular network) are connected wirelessly.
  • NAT Network Address Translator, 130
  • NAT Network Address Translator 130
  • the push server 120 transmits the push message received from the application server 110 to the terminal 140 through a public network or a private network. If the terminal is accessible to the public network, the push server 120 may transmit a push message to the public network. If not, the push server 120 transmits a push message through the private network. In order to send the push message over the private network, the push server 120 is connected to the private network via the NAT 130 over the public network.
  • the NAT 130 maintains matching between the public network IP address and the private network IP address for communication between the push server 120 and the terminal 140. As the number of terminals receiving the push service increases, the number of matching that the NAT 130 needs to maintain increases, and high performance is required. That is, the NAT 130 needs to be expanded to provide a smooth push service.
  • the NAT 130 sets a limited port binding time to match the private IP address with the public IP address.
  • the terminal 140 receives the push service through the private network, since the port binding time of the NAT 130 is not infinite, it must transmit a message for maintaining the port binding to the NAT 130 every predetermined time. This message transmission increases the power consumption of the terminal 140.
  • 2 is a configuration diagram according to an embodiment of a push message system to which the disclosed technology may be applied. 2 illustrates the push server 220 and the terminal 240 as one for convenience of description, the push server 220 and the terminal 240 may be configured in plural.
  • the push message system includes a lookup server 230 and a push server 220 and may be connected to an application server 210 and a terminal 240.
  • the lookup server 230 and the application server 210 may also be configured to be connected to both a public network and a private network.
  • the push server 220 receives the push message received from the application server 210 from the public network (eg, Wi). -Fi network) or a private network (for example, a cellular network) using at least one of the transmission to the terminal 240.
  • the push server 220 is directly connected to public and private networks, and has a public network address (for example, a public IP address) for the public network and a private network address (for example, a private IP address) for the private network. have.
  • the push server 220 may allocate a push service ID to the terminal 240 to which communication is performed in order to smoothly provide a push service.
  • the application of the terminal 240 may provide a push service ID assigned to the application server 210 to the application server 210.
  • the application server 210 may display the application of the terminal to be serviced by the push service ID and request the push server 220 to transmit the push message.
  • the push server 220 may establish a connection with the terminal through both a private network and a public network, and set a priority of any one of them. For example, if the priority is set in the public network, the push server 220 may first transmit a push message to the terminal through the public network, and if the communication is not made, may transmit the terminal to the terminal through the private network.
  • the push server 220 may select one of a private network or a public network to communicate with the terminal 240 according to a push service.
  • the push server 220 may know the information about the quality of service (QoS) of the service provided by the push message, and if a large data transmission is required based on the information about the QoS of the service,
  • the terminal 240 may communicate with the terminal 240 through the Wi-Fi network, and may communicate with the terminal 240 through the cellular network when real-time data transmission is required.
  • the push server 220 may connect the communication with the terminal via only the private network or public network. For example, you can always use a public network if you can connect to a public network, and only use a private network if not.
  • push server 220 may consist of multiple servers, and lookup server 230 may include an address for each of the multiple push servers.
  • the lookup server 230 may store an address (first push server) of the first push server. It has a public network address and the private network address of the first push server and the address of the second push server (public network address of the second push server and private network address of the second push server).
  • the lookup server 230 may give an address of the first push server and / or an address of the second push server at the request of the terminal 240.
  • the terminal 240 may receive both the address of the first push server and the address of the second push server. If the terminal 240 uses the public network address of the first push server, the terminal 240 may use the private network address of the first push server and may not use the private network address of the second push server. This is because it may be desirable for the terminal to communicate with the same push server.
  • the terminal when using multiple push servers, the terminal must use the public network address and private network address of the same push server as described above to be connected to the same push server and provide a stable push service.
  • one or more L7 switches may be installed in front of a network of push servers in a push server farm, and the address of the L7 switch may be provided to the terminal as the address of the push server.
  • the L7 switch may interpret the received packet (e.g., there is information identifying the push server in the packet) and may always send the packet to the same push server.
  • the lookup server 230 stores the public network address and the private network address of the push server 220, and provides the public and private network addresses of the corresponding push server 220 according to a request of the terminal. Since the push server 220 may be configured in plurality, the lookup server 230 may establish a database including public and private network addresses for each of the plurality of push servers.
  • the lookup server 230 may communicate with the push server 220 using a pre-stored private network address in order to update the private network address of the push server. If the communication is connected, the lookup server 230 determines that the private network address is valid, and if the communication is not connected, the lookup server 230 may request the changed private network address using the public network address of the corresponding push server. .
  • the push server 220 since the push server 220 itself has a private network address, the push server 220 may communicate using a private network without passing through the NAT 250, and thus, the terminal 240 periodically. As a result, it is not necessary to frequently transmit a message for maintaining port binding, and there is an advantage of reducing power consumption and an advantage of not installing a lot of NAT 250.
  • 3 is a configuration diagram according to another embodiment of a push message system to which the disclosed technology may be applied. 3 illustrates the push server 220 and the terminal 240 as one for convenience of description, the push server 220 and the terminal 240 may be configured in plural.
  • the push server 220 is located in a private network. That is, the push server 220 is directly connected to the private network, but the public network may be connected through the NAT 250.
  • the NAT 250 has a static mapping between the public IP address and the private IP address of the push server 220, and converts the two addresses. Therefore, when a connection attempt is made with the public network address of the push server 220, the packet reaches the NAT 250, and the NAT 250 changes the public IP address of the packet to a private IP address to push the packet. The packet is transmitted to the server 220.
  • Other contents of FIG. 3 correspond to the embodiment of FIG.
  • the server may be dynamically connected through a public network or a private network with a terminal capable of communicating over a public or private network.
  • the server includes a public network communication module, a private network communication module, and a control unit.
  • the public only communication module performs communication through the public network.
  • the private network communication module performs communication through a private network.
  • the control unit maintains a private network address for the private network and a public network address for the public network, and controls to communicate with the terminal using at least one of the private network communication module or the public network communication module according to the current estimation situation of the terminal.
  • the estimation situation may be a communication network (eg, a public network and / or a private network) to which the terminal can be connected, a load situation of the network, which network the terminal is currently connected to the push server, bandwidth required for services, and the like.
  • the terminal 240 may include objective indices of an environment in which the terminal 240 may receive a service.
  • the server may be a push server that sends a push message received from the application server to the terminal.
  • FIG. 4 is a configuration diagram according to an embodiment of the push server of FIG. 2.
  • the push server 220 may include a common network communication module 410, a private network communication module 420, and a controller 430, and further include a terminal information database 440 according to an embodiment. have.
  • the public network communication module 410 may perform communication through the public network
  • the private network communication module 420 may perform communication through the private network.
  • the disclosed push server 220 has a private network communication module 420 because it is directly connected to the private network.
  • the control unit 430 maintains a private and / or public network connection, and transmits a push message to the corresponding terminal 240 through at least one of a private network and a public network. As described above, the push message is transmitted from the application server 210, and the control unit 430 may receive the terminal and identify the target terminal and transmit the push message to the corresponding terminal.
  • the controller 430 may allocate a push service ID for identifying each terminal. For example, a unique push service ID may be allocated to terminals, and the allocated push service ID may be provided to the application server 210.
  • the application server 210 may transmit a push message by designating a target of the service by using the provided push service ID.
  • the push server 220 may be connected to the lookup server 230 through the public network, and the controller 430 may include a lookup notification unit 431.
  • the lookup notification unit 431 may provide the lookup server 230 with at least a private network address (eg, both public and private network addresses).
  • the lookup notification unit 431 may provide the changed private network address to the lookup server 230 whenever the private network address changes.
  • the lookup notification unit 431 may provide the private network address or the public network address to the application server 210.
  • the controller 430 may include a message transmitter 432.
  • the message transmitter 432 may provide a push message to a terminal that is a target of a push service in cooperation with the terminal information database 440.
  • the controller 430 may have already maintained the connection.
  • the push message may be provided to the terminal 240 using a communication network.
  • the controller 430 may select a private network or a public network according to a service provided by a push message and communicate with the corresponding terminal.
  • the control unit 430 may select a private network or a public network based on communication network information required for providing a service, and in order to obtain communication network information for a service, the control unit 430 may request the corresponding information from the application server 210. .
  • the network information may be included in the original push message.
  • the push server 220 may select a communication network capable of real-time communication, that is, a private network (cellular network), to communicate with the terminal in order to provide a service.
  • push server 220 may include a terminal information database 440.
  • the terminal information database 440 may include a push service ID, a private and / or public network address of a corresponding terminal, or a socket ID of a private network communication module and / or a public network communication module capable of sending data toward the corresponding terminal. It may include at least one.
  • the push server 220 may use the terminal information database 440 to communicate by obtaining an address or socket ID of a target terminal.
  • the push server 220 may exchange data without performing encryption when the terminal 240 is connected to the terminal 240 through a private network, and in other cases, that is, when the connection is performed using a public network, encryption (for example, TLS) may be used to exchange data.
  • encryption For example, TLS
  • FIG. 5 is a diagram illustrating an embodiment of a terminal of FIG. 2.
  • the terminal has WiFi and a cellular modem.
  • two or more communication can be easily extended.
  • a case of communicating with a push server toward a public network using a WiFi modem will be described as a connection through a public network communication module, and a case of communicating with a push server through a cellular network using a cellular modem. It is expressed as a connection through.
  • the terminal does not necessarily have a public IP address. For example, it may have a private IP address assigned by a NAT on the WiFi network. Similarly, a private network communication module does not always have a private IP address.
  • a public IP address may be assigned to the cellular modem (ie, a private network communication module) of the terminal.
  • a module for accessing through a WiFi network will be referred to as a common network communication module of a terminal, and a module for accessing via a cellular network will be described as a private network communication module of a terminal.
  • the terminal 240 may be dynamically connected to at least one server capable of communicating through a public or private network through a public or seo network.
  • At least one server may include a lookup server that stores public and private network addresses of a particular server.
  • the terminal 240 requests public and / or private network addresses of a specific server from at least one communication module and a lookup server that communicates through a public network or a private network, and according to a current estimation situation, the public and / or private network. It includes a client module for communicating with a particular server using at least one of the addresses.
  • the estimation situation is an objective for an environment in which the terminal 240 can receive services, such as a communication network to which the terminal 240 can be connected (for example, a public network and / or a private network), a load situation of the network, and bandwidth required for service. May include indicators.
  • a communication network to which the terminal 240 can be connected for example, a public network and / or a private network
  • bandwidth required for service May include indicators.
  • the terminal 240 includes a public network communication module 510, a private network communication module 520, a push client module 530, and an application client module 550.
  • terminal 240 may further include a push server database that stores public and private network addresses of push server 220.
  • the public network communication module 510 communicates through the public network
  • the private network communication module 520 communicates through the private network.
  • the push client module 530 communicates using the public network communication module 510 and / or the private network communication module 520, and receives a push message from the application server 210 transmitted by the push server 220. To the application client module 550.
  • the push client module 530 already knows the public network address of the lookup server 230. For example, when the push client module 530 is generated, it may already have a public network address of the lookup server 230, or may be a DNS (Domain Name Service) query based on the domain name of the lookup server 230. May be obtained. The push client module 530 may request the lookup server 230 to find and communicate with the public and private network addresses of the push server 220.
  • DNS Domain Name Service
  • push client module 530 communicates through private network communication module 520 with the private network address of the push server stored in push server database 540, If communication is not established, the lookup server 230 may request the private network address of the push server 220 again, and perform communication using the received private network address of the push server 220. This is more effective in situations such as when the private network address of push server 220 is changed.
  • the push client module 530 communicates through the private network communication module 520 using the private network address of the push server 220, and if communication is not made, the public of the push server 220 is shared. Communication can be performed using a network address.
  • the push client module 530 performs a communication to the cellular network using the private network address of the push server 220 using the private network communication module 520 (in this case, the push client module is a private IP of the private network communication module).
  • the public network communication module (510 ) To communicate with the public network address of the push server 220 to the Wi-Fi network.
  • the terminal 240 may confirm that the terminal is currently in the private network, and thus, the communication may continue using the private network in subsequent communication.
  • the terminal 240 may include only a private network communication module.
  • the push client module 530 communicates through the private network communication module 520 using the private network address of the push server 220, and if the communication is not made (for example, roaming, etc.) Communication may be performed through the private network communication module 520 using the public network address of 220.
  • the push client module 530 communicates through the private network communication module 520 of the terminal using the private network address of the push server 220, and if the communication is not made (for example, in case of roaming, communication may be performed through the private network communication module 520 using the public network address of the push server 220. If this also fails, communication is performed through the public network communication module 520 using the private network address of the push server 220 (if there is a device such as PDG and the terminal is connected to the WiFi through PDG, communication may be connected. If communication is not performed, communication may be performed through the public network communication module 520 using the public network address of the push server 220.
  • push client module 530 may maintain communication with both push server 220 and private and public networks.
  • the client module 530 may connect cellular communication using the private network address of the push server 220 and Wi-Fi communication using the public network address.
  • the terminal 240 when the terminal 240 receives a push message from the push server 220 through either the public network or the private network, the terminal 240 communicates with the push server 220 through the other of the public network or the private network. Can be.
  • This example may be applied to the case where there are a plurality of push servers 220.
  • the push server includes a first push server and a second push server
  • the terminal 240 if the terminal 240 communicated using either the public or private network address of the first push server, the terminal 240 May perform communication using the other of the public and private network addresses of the first push server. That is, communication can be continuously maintained for the first push server other than the second push server.
  • data when the push server 220 and the terminal 240 are connected through a private network, data may be transmitted and received without performing encryption during data communication. Otherwise, encryption (for example, TLS) may be performed. You can send and receive data by executing.
  • encryption for example, TLS
  • FIG. 6 is a block diagram according to an embodiment of a push message transmission method to which the disclosed technology can be applied
  • FIG. 7 is a flowchart of the push message transmission method according to FIG. 6.
  • the lookup server stores a private network address and a public network address of each of the at least one push server (step S610), and the lookup server stores the private and / or corresponding push servers in the terminal.
  • Providing a public network address step S620).
  • the lookup server 230 may store a private network address and a public network address of each of the at least one push server 220 (step S710).
  • the lookup server 230 may provide the terminal 240 with the public and private network addresses of the push server (step S720). .
  • the lookup server 230 may provide a public and / or private network address of the corresponding push server 220 according to a request of the application server 210 (step S730) (step S740).
  • the push server 220 may allocate a push service ID to the application of the terminal 240 (step S750).
  • the terminal 240 If there are multiple push servers 220 If the terminal 240 previously used the first push server, a change in the network (for example, a change from WiFi network to 3G network) occurs or the terminal is turned off Even when there is a change such as turning on again, it is more efficient to use the first push server. This is because the received push data from the application server is received through the first push server that was used previously. Accordingly, the terminal 240 has information in which a public network address and a private network address of the first push server are configured as a pair, and the addresses of the first push server and the second push server from the lookup server 230. Even if the received all, if you used the private network or public network address of the first push server can continue to use only the address of the first push server to ensure the efficiency of communication.
  • a change in the network for example, a change from WiFi network to 3G network
  • the disclosed technique can have the following effects. However, since a specific embodiment does not mean to include all of the following effects or only the following effects, it should not be understood that the scope of the disclosed technology is limited by this.
  • a push message transmission method and a push server, a terminal, and a push message transmission system may provide a large amount of push services without expanding NAT. This is because the push server is directly connected to the private network, and there is no need to pass through NAT when communicating with the terminal and the private network.
  • the terminal and the push server are directly connected to the private network, the risk of eavesdropping is very small, and thus encryption between the terminal and the push server can be omitted, thereby reducing the load on the push server and the terminal.
  • a push message transmission method and a push server, a terminal, and a push message transmission system for the same may reduce power consumption of the terminal. Because the terminal is directly connected to the push server and the private network, there is no need to send a message to maintain NAT and port binding.
  • a push message transmission method and a push server, a terminal, and a push message transmission system may provide a push service using both a private network and a public network. This is because the push server is directly connected to the private network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système de transmission de message de poussée, selon un mode de réalisation de la technologie décrite, qui peut être connecté à un terminal et à un serveur d'application. Le système de transmission de message de poussée comprend : au moins un serveur de poussée pour envoyer un message de poussée, qui est reçu du serveur d'application, au terminal par un réseau privé et/ou un réseau public ; un serveur de consultation pour stocker une adresse de réseau privé et une adresse de réseau public par rapport à chacun des serveurs de poussée et pour fournir les adresses de réseaux privé et public d'un serveur de poussée correspondant au terminal.
PCT/KR2011/008867 2011-01-14 2011-11-21 Procédé de transmission de message de poussée WO2012096438A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020110003815A KR101190307B1 (ko) 2011-01-14 2011-01-14 푸시 메시지 전송 방법
KR10-2011-0003815 2011-01-14

Publications (2)

Publication Number Publication Date
WO2012096438A2 true WO2012096438A2 (fr) 2012-07-19
WO2012096438A3 WO2012096438A3 (fr) 2012-09-07

Family

ID=46507527

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2011/008867 WO2012096438A2 (fr) 2011-01-14 2011-11-21 Procédé de transmission de message de poussée

Country Status (2)

Country Link
KR (1) KR101190307B1 (fr)
WO (1) WO2012096438A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014035194A1 (fr) * 2012-08-30 2014-03-06 Samsung Electronics Co., Ltd. Système et procédé de service de messages push
CN103856902A (zh) * 2014-03-17 2014-06-11 深圳市中兴移动通信有限公司 信息推送方法和移动终端
CN105208521A (zh) * 2014-05-29 2015-12-30 中国电信股份有限公司 一种信息推送方法和系统
US10148449B2 (en) 2012-08-30 2018-12-04 Samsung Electronics Co., Ltd Push message service system and method
CN114039695A (zh) * 2021-12-24 2022-02-11 浙江中控技术股份有限公司 冗余网络的时间同步方法、冗余网络系统及设备

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101682233B1 (ko) * 2015-01-19 2016-12-05 주식회사 탐생 이동단말기 차단방법, 이동단말기를 이용한 공부데이터 제공방법
KR20160131632A (ko) * 2015-05-08 2016-11-16 주식회사 카우치그램 푸시데이터 송수신 방법 및 시스템
KR101687152B1 (ko) * 2016-08-27 2016-12-15 주식회사 탐생 Vpn을 이용한 이동단말기 차단방법
KR101709454B1 (ko) * 2016-11-28 2017-02-22 주식회사 탐생 이동단말기 차단방법, 이동단말기를 이용한 공부데이터 제공방법
KR101709453B1 (ko) * 2016-11-28 2017-02-22 주식회사 탐생 이동단말기 차단방법, 이동단말기를 이용한 공부데이터 제공방법
KR101709455B1 (ko) * 2016-11-28 2017-02-22 주식회사 탐생 이동단말기 차단방법, 이동단말기를 이용한 공부데이터 제공방법
KR102220994B1 (ko) * 2016-12-26 2021-02-25 주식회사 케이티 기업 전용 네트워크에서의 데이터 푸시 기능 제공 시스템 및 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020138622A1 (en) * 2001-03-21 2002-09-26 Motorola, Inc. Apparatus and method of using long lived addresses in a private network for push messaging to mobile devices
US20050198310A1 (en) * 2004-03-08 2005-09-08 Samsung Electronics Co., Ltd. Method of communicating with server having flexible address
US7328280B2 (en) * 2003-01-15 2008-02-05 Matsushita Electric Industrial Co., Ltd. Peer-to-peer (P2P) connection despite network address translators (NATs) at both ends

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020138622A1 (en) * 2001-03-21 2002-09-26 Motorola, Inc. Apparatus and method of using long lived addresses in a private network for push messaging to mobile devices
US7328280B2 (en) * 2003-01-15 2008-02-05 Matsushita Electric Industrial Co., Ltd. Peer-to-peer (P2P) connection despite network address translators (NATs) at both ends
US20050198310A1 (en) * 2004-03-08 2005-09-08 Samsung Electronics Co., Ltd. Method of communicating with server having flexible address

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014035194A1 (fr) * 2012-08-30 2014-03-06 Samsung Electronics Co., Ltd. Système et procédé de service de messages push
US10148449B2 (en) 2012-08-30 2018-12-04 Samsung Electronics Co., Ltd Push message service system and method
CN103856902A (zh) * 2014-03-17 2014-06-11 深圳市中兴移动通信有限公司 信息推送方法和移动终端
CN105208521A (zh) * 2014-05-29 2015-12-30 中国电信股份有限公司 一种信息推送方法和系统
CN114039695A (zh) * 2021-12-24 2022-02-11 浙江中控技术股份有限公司 冗余网络的时间同步方法、冗余网络系统及设备

Also Published As

Publication number Publication date
KR20120082522A (ko) 2012-07-24
WO2012096438A3 (fr) 2012-09-07
KR101190307B1 (ko) 2012-10-12

Similar Documents

Publication Publication Date Title
WO2012096438A2 (fr) Procédé de transmission de message de poussée
WO2012067382A2 (fr) Procédé permettant d'établir une connexion réseau, procédé permettant une connexion à un réseau et groupe de communication sans fil qui applique ces procédés
AU2009342169B2 (en) Scalable WLAN gateway
US6393488B1 (en) System and method for supporting internet protocol subnets with network address translators
WO2018066907A1 (fr) Procédé de transfert de messages de signalisation de terminal entre fonctions de réseau
WO2015020502A1 (fr) Technique de découverte de service dans un réseau de communication sans fil pour former un groupe p2p
WO2021141348A1 (fr) Procédé et appareil de fourniture d'une pluralité de réseaux virtuels pour une application unique dans un réseau de communication mobile
WO2014163254A1 (fr) Système et terminal de connexion p2p, et procédé de connexion p2p les utilisant dans un environnement mobile
EP2075959A1 (fr) Appareil et procédé d'accès parallèle à plusieurs réseaux sans fil
WO2011159040A2 (fr) Appareil et procédé permettant de configurer un réseau personnel au moyen d'une table de routage pn
US7299287B1 (en) Secure network outlet for supporting IP device address assigning functionality
JP2006352572A (ja) 無線アクセスシステム
WO2023113463A1 (fr) Procédé et appareil de partage de txop déclenché pour une communication poste à poste avec une opération twt
WO2022035010A1 (fr) Optimisation d'intervalle de supervision de nat légère en temps réel pour dispositifs mobiles multi-sim
EP1313294A1 (fr) Procédé pour l' allocation d' un dispositif non-dédié aux données à un VLAN vocal
CN112714202B (zh) 设备配置方法及装置
WO2011027937A1 (fr) Système d'interfonctionnement de réseaux et son procédé
WO2010140739A1 (fr) Système destiné à optimiser des voies de communications entre des stations mobiles dans un réseau à protocole internet mobile mandataire version 6 et procédé associé
WO2019212268A1 (fr) Procédé et dispositif pour gérer un noeud mobile de contrôleur sdn
CN116208551B (zh) 数据传输方法、装置、设备及存储介质
WO2017034055A1 (fr) Procédé de conversion de mode d'un routeur filaire/sans fil
WO2024010388A1 (fr) Découverte et configuration de tdls pour une opération à liaisons multiples
WO2013005982A2 (fr) Dispositif et procédé d'établissement d'une interface dans un réseau local
KR100358440B1 (ko) 데이터망을 이용한 호 시그널링 메시지 전송방법
WO2012026795A2 (fr) Procédé et appareil adaptés pour partager un mémo au moyen d'un système de téléphonie upnp

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

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11855799

Country of ref document: EP

Kind code of ref document: A2