WO2012005440A2 - Procédé de fourniture d'un service push et système de fourniture d'un service push destiné à sa mise en œuvre - Google Patents

Procédé de fourniture d'un service push et système de fourniture d'un service push destiné à sa mise en œuvre Download PDF

Info

Publication number
WO2012005440A2
WO2012005440A2 PCT/KR2011/003489 KR2011003489W WO2012005440A2 WO 2012005440 A2 WO2012005440 A2 WO 2012005440A2 KR 2011003489 W KR2011003489 W KR 2011003489W WO 2012005440 A2 WO2012005440 A2 WO 2012005440A2
Authority
WO
WIPO (PCT)
Prior art keywords
server
client
push
communication path
mtc
Prior art date
Application number
PCT/KR2011/003489
Other languages
English (en)
Korean (ko)
Other versions
WO2012005440A3 (fr
Inventor
김대영
Original Assignee
주식회사 네이블커뮤니케이션즈
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 네이블커뮤니케이션즈 filed Critical 주식회사 네이블커뮤니케이션즈
Publication of WO2012005440A2 publication Critical patent/WO2012005440A2/fr
Publication of WO2012005440A3 publication Critical patent/WO2012005440A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the disclosed technology relates to a call switching method of a PUSH service and a PUSH service providing system for performing the same, and more particularly, to a call switching method of a PUSH service using a wireless Internet communication network and a cellular communication network, and a PUSH service providing system performing the same.
  • the PUSH service is capable of delivering information on the web to a user terminal by a PUSH server, not by a user request.
  • it may include a function of delivering information to all targets (Broadcast Data Delivery), a function of delivering information to an optional subject (Multicast Data Delivery), and a function of delivering information to a specific target (Unicast Data Delivery). .
  • the call switching method of the PUSH service is performed in a PUSH service providing system including a fixed mobile convergence (FMC) terminal equipped with a PUSH server, a multi-tunnel (MT) server, and an MT client.
  • the MT server and the MT client may be connected by first and / or second communication paths.
  • the MT client is assigned an MTC Internet address (Multi-Tunnel Client IP address) from the MT server.
  • the MTC internet address may be uniquely defined by the MT server.
  • the FMC terminal registers the allocated MTC Internet address with the PUSH server.
  • the MT server determines the MT client based on the MTC internet address and transmits the first or second PUSH message to the MT client. Select a second communication path.
  • the MT client requests the MTC internet address from the MT server, and the MT server selects one of the MTC internet address pools as the MTC internet address of the MT client and sends it to the MT client. Can be.
  • the MT server may further include transmitting the PUSH message to the corresponding MT client through the selected communication path.
  • the PUSH service providing method is performed in a multi-tunnel (MT) server that can be connected to a fixed mobile convergence (FMC) terminal equipped with a PUSH server and an MT client.
  • the MT server and the MT client may be connected by a first and / or a second communication path, and may transmit and receive an IP message through the first communication path.
  • the PUSH message When the PUSH message is received within the set time from the reception time of the uplink packet, the PUSH message is transmitted to the MT client through the second communication path, and the set time has elapsed from the reception time of the uplink packet. When the message is received, the PUSH message is transmitted to the MT client through the first communication path.
  • the PUSH message may include a sender IP address and a receiver IP address corresponding to the selected communication path.
  • the PUSH message transmitted from the PUSH server may be encrypted based on an encryption key, and the encrypted packet may be transmitted to the MT client.
  • the PUSH service providing method is performed in an MT client mounted in a Fixed Mobile Convergence (FMC) terminal that can be connected to a PUSH server and a multi-tunnel (MT) server.
  • the MT server and the MT client may be connected by first and / or second communication paths.
  • the communication path to receive data is selected among the first communication path and the second communication path based on the connection. Inform the MT server that PSUH data is received via the selected communication path.
  • a PUSH message is received through a communication path informed to the MT server.
  • the encapsulated PUSH message may be received from the MT server.
  • the received PUSH message may be restored.
  • the PUSH message may include a sender IP address and a receiver IP address corresponding to the selected communication path.
  • an encrypted PUSH message may be received from the MT server.
  • the encrypted PUSH message may be decrypted.
  • the PUSH service providing system includes an MT server and an MT client.
  • the MT server allocates an MTC Internet address (Multi-Tunnel Client IP address) and transmits it to a MT (Multi-Tunnel) client.
  • MTC Internet address Multi-Tunnel Client IP address
  • the MT server transmits the MTC Internet address.
  • the MT client may be determined based on the first and second communication paths for transmitting the PUSH message to the MT client.
  • the MT client interworks with an application that registers the MTC Internet address allocated from the MT server to the PUSH server.
  • the MTC internet address may be uniquely defined by the MT server.
  • the MT server may select one of the MTC Internet address pools as the MTC Internet address of the MT client and transmit it to the MT client at the request of the MT client.
  • Data transmitted and received between the MT server and the MT client may be converted into an encapsulation process or an encryption process and transmitted, and may be received and restored.
  • the encapsulation process may include Generic Routing Encapsulation (GRE) or Minimal Encapsulation (ME), and the encryption process may include IP-SEC.
  • the PUSH service providing system includes a fixed mobile convergence (FMC) terminal equipped with a PUSH server, a multi-tunnel (MT) server, and an MT client.
  • the MT server and the MT client may be connected by first and / or second communication paths.
  • the MT server includes an IP communication module, a data converter and a communication network selector.
  • the IP communication module receives a PUSH message from the PUSH server.
  • the data converter encapsulates and / or encrypts the received PUSH message.
  • the communication network selecting unit confirms the reception time of the last uplink packet received from the MT client through the second communication path, and when the PUSH message is received within a set time from the reception time of the uplink packet, the second communication. Transmitting the encapsulated and / or encrypted PUSH message to the MT client via a path, and when the set time has elapsed from the reception time of the uplink packet and the PUSH message is received, the MT client through the first communication path And a network selection unit for transmitting the encapsulated and / or encrypted PUSH message.
  • the MT server may further include an IP address pool storage unit for storing the MTC multi-tunnel client IP address pool, the request signal for requesting the MTC Internet address from the MT client is received If one of the MTC Internet address pools stored in the IP address pool storage unit is selected as the MTC Internet address of the corresponding MT client, the MT client may be transmitted to the MT client.
  • the MT server maps the MTC internet address with the internet address of the MT client by the first communication path and the second communication path, and stores the internet address of the MT server by the first communication path and the second communication path. It may further include an IP address storage.
  • the MT server initiates counting by initializing a count value when an uplink packet is received from the MT client through the second communication path, and further provides a counter notifying the communication network selection unit when the count value exceeds a set time. It may include.
  • the PUSH service providing system includes a fixed mobile convergence (FMC) terminal equipped with a PUSH server, a multi-tunnel (MT) server, and an MT client.
  • the MT server and the MT client may be connected by first and / or second communication paths.
  • the MT client includes a communication network confirming unit, a communication network selecting unit, and a data converting unit.
  • the communication network identification unit confirms whether the first communication path and / or the second communication path are connected.
  • the communication network selection unit receives a confirmation result of the communication network identification unit, determines a communication path to receive data, informs the MT server, and receives an encapsulated and / or encrypted PUSH message from the MT server.
  • the data converter restores or decrypts the encapsulated and / or encrypted PUSH message.
  • the MT client maps the MTC Internet address with the MT client's Internet address by the first and second communication paths, and the MT server's Internet address by the first and second communication paths.
  • the apparatus may further include a mapping IP address storage unit configured to map and store the network, and the communication network selector may communicate with the MT server based on the mapping information stored in the mapping IP address storage unit.
  • FIG. 1 is a block diagram illustrating a PUSH service providing system of the disclosed technology.
  • FIG. 2 is a block diagram illustrating the MT server of FIG. 1.
  • FIG. 3 is a flowchart illustrating an operation of the MT server of FIG. 1.
  • FIG. 4 is a block diagram illustrating an FMC terminal of FIG. 1.
  • FIG. 5 is a block diagram illustrating an MT client of FIG. 4.
  • FIG. 6 is a flowchart illustrating an operation of the MT client of FIG. 4.
  • FIG. 7 is a diagram illustrating a packet structure of the disclosed technique.
  • FIG. 8 is a flowchart illustrating a call switching method of a PUSH service of the disclosed technology.
  • step 9 is a view for explaining step "S810" and step “S820" of FIG. 8 in more detail.
  • step "S830" of FIG. 8 is a view for explaining step "S830" of FIG. 8 in more detail.
  • 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, ...) 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 illustrating a PUSH service providing system of the disclosed technology.
  • the PUSH service providing system 100 includes a PUSH server 110, a multi-tunnel (MT) server 120, and an FMC terminal 130.
  • the PUSH server 110 provides a PUSH service to the FMC terminal 130.
  • the PUSH server 110 may communicate with the MT server 120 via a wired or wireless internet network.
  • the PUSH server 110 may include all kinds of servers that provide data of a PUSH method to the terminal.
  • the VoIP service IM (Instant Messaging) service, etc. can send the PUSH method data to the terminal while processing the PULL method data, the subjects that transmit the PUSH method data are all included in the PUSH server 110 can do.
  • a softswitch may transmit data of a PUSH method to a terminal, and thus, the softswitch may be a PUSH server 110.
  • the MT server 120 provides the FMC terminal 130 with the PUSH message transmitted from the PUSH server 110.
  • the MT server 120 communicates with the FMC terminal 130 via a cellular communication network (hereinafter referred to as the first communication path) and / or a wireless Internet communication network (hereinafter referred to as the second communication path).
  • the cellular communication network may include a third generation mobile communication network or a Wibro communication network
  • the wireless internet communication network may include a WiFi communication network.
  • the first communication path may always be connectable and the second communication path may be selectively connectable.
  • the FMC terminal 130 receives the PUSH service from the PUSH server 110.
  • the FMC terminal 130 may be equipped with an MT client that communicates with the MT server 120.
  • the MT client may communicate with the MT server 120 while interworking with an application program executed in the FMC terminal 130.
  • the FMC terminal 130 may include a smartphone or a handset.
  • the FMC terminal 130 may include a terminal capable of accessing an IP communication network in two different communication methods. For example, it may include a terminal having 3G communication and WiFi communication functions. In the disclosed technology, a terminal having both 3G communication and WiFi communication functions is defined and described as the FMC terminal 130. However, according to the needs of those skilled in the art, the terminal may include a terminal capable of accessing an IP communication network using three or more different communication methods. Of course. For example, it may include a terminal having 3G communication, WiMax communication, and WiFi communication functions.
  • the Internet address of the PUSH server 110 is "IP-Push"
  • the address of the MT server 120 based on the first communication path is “IP-Svr-3G”
  • the FMC terminal based on the first communication path ( Address 130) is "IP-3G”
  • address of MT server 120 based on the second communication path is "IP-Svr”
  • address of FMC terminal 130 based on the second communication path is "IP-WiFi”
  • IP-mtc The Internet address managed by the MT client of the FMC terminal 130 may be defined as "IP-mtc.”
  • the address "IP-Svr-3G” and the address "IP-Svr” may be the same.
  • the PUSH server 110 and the application of the FMC terminal 130 may transmit and receive data only by "IP-Push” and "IP-mtc", the data transmission according to the switching of the communication path is MT server ( 120) and MT client only. Accordingly, the PUSH server 110 may be capable of providing an efficient service to the FMC terminal 130.
  • the application of the FMC terminal 130 is an application that does not require the PUSH service
  • the application does not connect to the Internet using the address of "IP-mtc” and the application directly connects "IP-3G" or "IP-WiFi".
  • IP-mtc the address of "IP-mtc”
  • IP-WiFi IP-WiFi
  • a specific application may provide a service using an MT client, and another application may directly receive a service without using an MT client.
  • a specific application and another application may be simultaneously mounted on one FMC terminal 130.
  • FIG. 2 is a block diagram illustrating an MT server of FIG. 1
  • FIG. 3 is a flowchart illustrating an operation of the MT server of FIG. 1.
  • the MT server 120 includes an IP communication module 210, a data converter 220, a communication network selector 230, a 3G communication module 240, a WiFi communication module 250, and an IP address pool.
  • the storage unit 260 may include a mapping IP address storage unit 270 and a counter 280.
  • the IP communication module 210 may receive a PUSH message from the PUSH server 110.
  • the data converter 220 may encapsulate or encrypt the received PUSH message.
  • data may be converted by encapsulation when rapid data transfer is required, data may be converted by encryption when high security is required, and encapsulation and encryption may be performed in parallel.
  • the data converter may convert the data differently according to the path selected by the communication network selector. For example, the encapsulation Internet address and / or destination Internet address can be specified differently depending on the route.
  • the communication network selector 230 may select a communication path to transmit the converted data.
  • the communication path may be selected based on the reception time of the uplink packet received from the MT client via the second communication path (WiFi). For example, when the reception time of the last uplink packet received from the MT client is checked through the second communication path (WiFi), and the PUSH message is received within a set time from the reception time of the last uplink packet, the second communication path Can be selected. If the set time elapses from the reception time of the uplink packet and the PUSH message is received, the first communication path may be selected.
  • the uplink packet may include data sent periodically or response data of the FMC terminal 130 receiving the PUSH message to maintain port binding of WiFi Network Address Traslation (NAT). .
  • NAT WiFi Network Address Traslation
  • the 3G communication module 240 may transmit and receive a packet with the FMC terminal 130 through the first communication path.
  • the MT server 110 may be connected to the FMC terminal 130 through the 3G-based IP communication network using the 3G communication module 240.
  • the FMC terminal 130 may continue to maintain "IP-3G" and the MT server 120 may be 3G. It may always be connected to the FMC terminal 130 through the communication module 240. That is, when the MT server 120 sends data to the address "IP-3G", the FMC terminal 130 may receive this.
  • the WiFi communication module 250 may transmit and receive a packet with the FMC terminal 130 through the second communication path.
  • the MT server 110 may be connected to the FMC terminal 130 through the WiFi-based IP communication network using the WiFi communication module 250.
  • MT server 120 is selectively connected to the FMC terminal 130 through the WiFi communication module 250. Can be.
  • the FMC terminal 130 may operate so as not to receive a WiFi-based wireless communication signal in order to minimize battery consumption.
  • the FMC terminal 130 may maintain port binding only by periodically transmitting a packet due to a network address translation (NAT) existing between the WiFi communication module 250 and in this case. This is because PUSH data may be received only, but packets may not be transmitted to reduce battery consumption.
  • NAT network address translation
  • the FMC terminal 130 may be switched to a state in which reception is not possible even in a region in which a WiFi communication signal is turned off by turning off the WiFi communication network or making a "sleep" mode in order to reduce battery consumption.
  • the IP address pool storage unit 260 may store an MTC multi-tunnel client IP address pool.
  • the communication network selector 230 selects one of the MTC Internet address pool stored in the IP address pool storage unit 260 as the MTC Internet address of the FMC terminal 130 equipped with the MT client to the MT client.
  • Can transmit For example, the MTC internet address may include a public IP address assigned to the MT server 120.
  • the mapping IP address storage unit 270 maps the MTC internet address and the internet address of the MT client by the first communication path and the second communication path, and maps the internet addresses of the MT server by the first communication path and the second communication path. Can be mapped and stored.
  • IP-mtc may be stored mapped to “IP-3G” and “IP-WiFi”
  • IP-3G is mapped to "IP-Svr-3G” and “IP-WiFi” "May be mapped to" IP-Svr "and stored.
  • the counter 280 starts counting when an uplink packet is received from the MT client through the second communication path, and notifies the network selection unit 230 if the count value exceeds the set time (eg, 1 minute). can do. In an embodiment, when the network selector 230 requests confirmation, the network selection unit 230 may inform how long it is. In another embodiment, the counter 280 may perform the same operation for downlink packets over the second communication path. For example, the counter 280 may transmit the count information to the network selector 230 for the uplink and the downlink, respectively, and map the information about the two links (last downlink or uplink packet is on). And time information elapsed from the time point to the present time).
  • the set time eg, 1 minute
  • the reason for using only uplink information without using downlink information is that there is no guarantee that the downlink packet has been sent to the FMC terminal 130 because the downlink packet is sent through the second communication path.
  • the arrival of data to the MT server 120 in an uplink transmission means that the WiFi network coming from the FMC terminal 130 to the MT server 120 is alive and the downlink transmission also supports the WiFi network. This is because the MT server 120 can go to the FMC terminal 130 through.
  • the communication network selecting unit 230 may check the reception time of the previous uplink packet by checking the count value by the counter 280 ( Step S302), if the count value has not passed the set time (step S303), the downlink packet can be transmitted to the MT client via the WiFi communication module 250 (step S304), and if the count value has passed the set time (Step S202)
  • the downlink packet can be transmitted to the MT client via the 3G communication module 240 (step S305).
  • the counter 280 may initialize the count value and start counting again when an uplink packet comes from the MT client during counting.
  • the downlink packet may include data for transmitting the PUSH message.
  • the counter may also monitor for downlink packets.
  • the method of transmitting a counter-based PUSH message may be performed in parallel with the method of transmitting a command-based PUSH message from an MT client described below with reference to FIG. 6.
  • FIG. 4 is a block diagram illustrating an FMC terminal of FIG. 1.
  • the FMC terminal 130 may include a 3G communication module 410, a WiFi communication module 420, an MT client 430, and an application module 440.
  • the 3G communication module 410 may transmit and receive a packet with the MT server 120 through the first communication path.
  • the FMC terminal 130 may be connected to the MT server 110 through the 3G-based IP communication network using the 3G communication module 410.
  • the FMC terminal 130 may continue to maintain "IP-3G" and the 3G communication module 240 Through the MT server 120 can always be connected.
  • the WiFi communication module 420 may transmit and receive a packet with the MT server 120 through the second communication path.
  • the FMC terminal 130 may be connected to the MT server 110 through the WiFi-based IP communication network using the WiFi communication module 420.
  • the FMC terminal 130 if the FMC terminal 130 is located in a region that can receive the WiFi-based wireless communication signal, the FMC terminal 130, the WiFi communication module 420 may be selectively connected to the MT server 120. have.
  • the reason why the FMC terminal 130 and the MT server 120 are selectively connected is the same as that described in the description of FIG. 2.
  • the MT client 430 transmits the PUSH message transmitted from the MT server 120 to the application module 440.
  • encapsulation can include Minimal Encapsulation (ME) or Generic Routing Encapsulation (GRE), and encryption and decryption can include IP-SEC.
  • the MT client 430 may transmit data transmitted from the application module 440 to the MT server 120.
  • the MT client 430 may check whether the second communication path is connected, and transmit data through the WiFi communication module 420 when the second communication path is connected, and the second communication path is not connected. If not, the data may be transmitted through the 3G communication module 410. For example, checking whether the second communication path is connected may correspond to receiving a WiFi-based wireless communication signal.
  • the application module 440 may execute an application executed in the FMC terminal 130.
  • the application module 440 may transmit / receive data with the PUSH server 110 using only “IP-mtc” and “IP-Push”.
  • FIG. 5 is a block diagram illustrating an MT client of FIG. 4
  • FIG. 6 is a flowchart illustrating an operation of the MT client of FIG. 4.
  • the MT client 430 may include a communication network checking unit 510, a communication network selecting unit 510, a data converting unit 530, and a mapping IP address storage unit 530.
  • the communication network checking unit 510 may check whether the second communication path is connected. In one embodiment, the communication network identification unit 510 may simultaneously check whether the first communication path is connected. For example, the connection can be confirmed by detecting the sensitivity of the corresponding communication path. In another embodiment, the 3G communication module 410 and the WiFi communication module 420 may inform the communication network identification unit 510 whether its connection is established.
  • the communication network selecting unit 520 may receive a result of confirming the communication network identifying unit 510, and may select a communication path to transmit an uplink packet based on the received information. In an embodiment, when the second communication path is connected, the second communication path may be selected and communicated. If the second communication path is not connected, the first communication path may be selected and communicated.
  • the network selection unit 520 receives the confirmation result of the network identification unit 510, and finally receives the received information and / or other information (e.g., through the second communication path Received time) may be used to select a communication path to receive the downlink packet and inform the MT server 120 of the selected path. If the situation changes and the communication path to receive the downlink packet is changed, the MT server can be informed of the selected path each time. For example, the MT server 120 may transmit a message to the MT client 430 through a communication path informed by the communication network selector 520.
  • the communication network selection unit 520 may not notify the MT server 120 of the selected path. In this case, the MT server 120 may directly select a communication path for transmitting the downlink packet.
  • the MT server 120 may select the communication network selector 520. ) Can directly select the communication path to which the downlink packet is to be transmitted using both the communication path selected in the ") and the information obtained by the MT server 120 (eg, counter information).
  • the data converter 530 may convert the received PUSH message in the case of a downlink packet. In one embodiment, when the PUSH message is encapsulated or encrypted, the data converter 530 may restore or decrypt the encapsulated or encrypted PUSH message. The data converter 530 encapsulates and / or encrypts the uplink packet according to the communication path selected by the network selector 520.
  • the mapping IP address storage unit 540 maps the MTC Internet address with the MT client's Internet address by the first communication path and the second communication path, and maps the Internet address of the MT server by the first communication path and the second communication path. Can be mapped and stored.
  • IP-mtc may be stored mapped to “IP-3G” and “IP-WiFi”
  • IP-3G is mapped to "IP-Svr-3G” and “IP-WiFi” "May be mapped to" IP-Svr "and stored.
  • the communication network selecting unit 520 may check the state of each communication network according to the result of the confirmation by the communication network confirming unit 510 (step S601), and if there is a communication network that can be connected (step S602), down the corresponding communication network.
  • the link packet may be selected as a communication network to be transmitted and notified to the MT server 120 (step S603), and a downlink packet (PUSH message) may be received from the MT server 120 through the communication network (step S604).
  • FIG. 7 is a diagram illustrating a packet structure of the disclosed technique.
  • the MT server 120 and the MT client 430 may transmit and receive data based on mapping information stored in the mapping IP address storage unit 270 and 540, respectively.
  • the data transmission between the MT server 120 and the MT client 430 may be converted into an encapsulation process and transmitted.
  • the encapsulation process may include ME (Minimal Encapsulation) or GRE, and various encapsulation methods may be applied according to the needs of those skilled in the art.
  • ME Minimum Encapsulation
  • GRE Global System for Mobile Communications
  • the message may include a sender IP address and a receiver IP address, a GRE header and a downlink / uplink packet corresponding to the communication path to be transmitted.
  • the application module 440 receives the IP address of the sender, "IP-mtc", It is possible to generate data including the IP address of the IP address as "IP-push” and transmit the data to the MT client 430, and the MT client 430 is based on the mapping information stored in the mapping IP address storage unit 540.
  • the packet may include an address "IP-3G” and a receiving Internet address as "IP-Svr-3G” and generate a packet encapsulated with GRE, and transmit the packet to the MT server 120.
  • the MT server 120 may perform GRE encapsulation. Solve the sending Internet address "IP-mtc" and the receiving Internet address "IP-push” It can be included to restore the original data to be transmitted to PUSH server 110.
  • FIG. 7 a process of transmitting data (shown as a downlink packet in FIG. 7) from the PUSH server 110 to the application module 440 through the second communication path is described.
  • the Internet network After generating data including the address "IP-push” and the receiving Internet address as “IP-mtc” and transmitting it to the Internet network, the Internet network routes the data by looking at the "IP-mtc" address. It is possible to reach the server 120, MT server 120 is based on the mapping information stored in the mapping IP address storage unit 270, "IP-Svr" for the sending Internet address, "IP-Svr” for the receiving Internet address -WiFi "and the packet encapsulated by GRE can be generated and transmitted to the MT client 430.
  • the MT client 430 decompresses the GRE to send the sender's Internet address" IP-push "and the receiver's Internet address. Restore all original data including "IP-mtc" to It may be transferred to 440.
  • the PUSH server 110 and the application module 440 can perform efficient data transmission only with "IP-push” and "IP-mtc". Therefore, it can be easily applied without changing the existing PUSH server and application.
  • FIG. 8 is a flowchart illustrating a call switching method of a PUSH service of the disclosed technology.
  • the MT client 430 may know the IP address of the MT server 120 in advance (for example, it may be set and stored in advance) or may find the IP address of the MT server 120 through "DNS lookup". .
  • the MT client 430 is assigned an MTC Internet address (Multi-Tunnel Client IP address) from the MT server 120 through the first communication path (step S810).
  • MTC Internet address Multi-Tunnel Client IP address
  • the MT server 120 may automatically recognize “IP-3G” without a separate process. If the communication is performed through a communication path other than the first communication path, a process of notifying the MT server 120 of "IP-3G" may be necessary.
  • the MTC Internet address may be uniquely defined by MT server 120.
  • the application of the FMC terminal 130 registers the allocated MTC Internet address to the PUSH server 110 (step S820).
  • the FMC terminal 130 may include an MT client 430 and an application module 440, the MTC Internet address assigned to the MT client 430 may be sent to the application module 440
  • the application module 440 may register and transmit the unique information of the FMC terminal 130 to the PUSH server 110 together with the MTC internet address.
  • the unique information may include "Tel URL", "SIP URL” and / or "ID" of the application.
  • VoIP it includes a registration step, and at this time, it can be registered in the soft switch using "IP-mtc".
  • the MT server 120 determines the MT client 430 based on the MTC internet address and transmits the PUSH message to the MT client 430. In order to select a first communication path or a second communication path (step S830). In one embodiment, the MT server 120 may transmit data to the MT client 430 via the selected communication path.
  • step 9 is a view for explaining step "S810" and step “S820" of FIG. 8 in more detail.
  • the MT client 430 may transmit a message IP-mtc_Req requesting the MTC Internet address to the MT server 120 through the first communication path (step S901).
  • the MT server 120 may transmit a message (IP-mtc_Res) selected as one of the MTC Internet address pools as the MTC Internet address of the MT client 430 to the MT client 430 (step S902).
  • the MT client 430 may map and store the transmitted MTC internet address and the internet address of the MT client 430 by the first communication path (step S903).
  • the MT client 430 may transmit the MTC Internet address (IP-mtc) to the application module 440 (step S904), and the application module 440 may transmit information of the application including the transmitted MTC internet address (Regi-Info).
  • IP-mtc may be transmitted to the MT client 430 to register with the PUSH server 110 (step S905).
  • the MT client 430 may transmit the information (Regi-Info (IP-mtc)) of the application including the MTC Internet address to the MT server 120 through the first communication path (step S906), and the MT server 120 ) May transmit and register the information (Regi-Info (IP-mtc)) of the application including the MTC Internet address to the PUSH server 110 (step S907).
  • the information (Regi-Info (IP-mtc)) of the application including the MTC Internet address to the MT server 120 through the first communication path (step S906), and the MT server 120 ) May transmit and register the information (Regi-Info (IP-mtc)) of the application including the MTC Internet address to the PUSH server 110 (step S907).
  • the PUSH server may arrive at the MT server 120 once the registration confirmation message (Downlink-pack) is sent to the application module 440 based on the registered information (step S908), and the MT server 120 receives the received registration.
  • the encapsulated packet Uncap_D-Packet may be transmitted to the MT client 430 (step S910).
  • the MT client 430 may transmit a registration confirmation message (Downlink-pack) to the application module 440 (step S912).
  • the MT server 120 and the MT client 430 exchange encryption keys with each other, encrypt them using them, or hash for authentication. can do.
  • step S830 of FIG. 8 may correspond to steps S1008 to S1014 of FIG. 10.
  • the application module 440 transmits data Uplink-Packet to be transmitted to the MT client 430 (step S1001).
  • the MT client 430 selects a communication path to transmit data (step S1002).
  • the selection of the communication path may be based on whether the second communication path is connected.
  • the MT client 430 When the second communication path is selected, the MT client 430 encapsulates the data based on the second communication path (step S1003), and the MT server 120 transmits the data encapsulated through the second communication path (Uncap_U-Packet). If the second communication path is not available, for example, when the first communication path is selected in step "S1002", the MT client 430 transmits data based on the first communication path. Is encapsulated (step S1003 '), and the encapsulated data Uncap_U-Packet may be transmitted to the MT server 120 through the first communication path (step S1005).
  • the MT server 120 may restore the encapsulated data Uncap_U-Packet (step S1006), and then transmit the restored data (Uplink-Packet) to the PUSH server 110 (step S1007).
  • the PUSH server 110 transmits a message (Downlink-Packet) to the address "IP-mtc" and the message may reach the MT server 120 (step S1008).
  • the MT server 120 selects a communication path to transmit the message transmitted from the PUSH server 110 (step S1009). In one embodiment, whether the communication path is connected may be determined based on a reception time of an uplink packet transmitted through the second communication path. In another embodiment, whether the communication path is connected may be confirmed based on the notification of the MT client 430. If the second communication path is selected, the MT server 120 encapsulates the data based on the second communication path (step S1010), and transmits the encapsulated message (Downlink-Packet) to the MT client 430 through the second communication path.
  • Downlink-Packet encapsulated message
  • the MT server 120 encapsulates the data based on the first communication path (step S1010 '), and the message Uncap_D is encapsulated through the first communication path.
  • -Packet can be sent to the MT client 430 (step S1012).
  • the MT client 430 may restore the encapsulated message Uncap_D-Packet (step S1013), and then transmit the restored message (Downlink-Packet) to the application module 440.
  • 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.
  • the PUSH service providing method and the PUSH service providing system performing the same may increase the efficiency of PUSH service transmission. Since there is no need to maintain NAT table by continuously transmitting packets through NAT device in Wifi network, data traffic of WiFi network can be minimized, and sleep time of terminal can be increased, thus minimizing battery consumption of device. can do.
  • the PUSH service providing method and the PUSH service providing system for performing the same may more efficiently manage an IP address of an application mounted on a PUSH server and a terminal. This is because a communication is performed by generating a separate IP address for a communication network selected by the MT server and the MT client, and the PUSH server and the application do not need to register a new IP address for switching the communication network.
  • the PUSH service providing method and the PUSH service providing system performing the same may be easily applied to a conventional PUSH service system. This is because the MT server and the MT client can be added and operated without changing the applications mounted on the PUSH server and the terminal of the conventional PUSH service system.

Landscapes

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

Abstract

L'invention concerne un procédé de réexpédition d'appels dans un service PUSH mis en œuvre dans un système fournisseur de services PUSH qui comprend un serveur PUSH, un serveur MT (MultiTunnel) et un terminal FMC (Fixed Mobile Convergence, Convergence entre fixe et mobile) sur lequel est monté un client MT. Le serveur MT et le client MT peuvent être connectés par l'intermédiaire d'un premier trajet de communication et/ou d'un second trajet de communication. Une adresse internet MTC (MultiTunnel Client IP Address, Adresse IP de client multi-tunnel) est allouée au client MT par le serveur MT. Le terminal FMC enregistre l'adresse internet MTC allouée sur le serveur PUSH. Lorsqu'un message PUSH contenant l'adresse internet MTC est transmise par le serveur PUSH, le serveur MT détermine un client MT correspondant sur la base de l'adresse internet MTC et sélectionne le premier ou le second trajet de communication pour transmettre le message PUSH au client MT correspondant. Conformément à un mode de réalisation, le client MT peut demander au serveur MT de transférer l'adresse internet MTC et le serveur MT peut sélectionner une adresse internet MTC d'un client MT correspondant dans un groupe d'adresses internet MTC et transmettre l'adresse internet MTC sélectionnée au client MT.
PCT/KR2011/003489 2010-07-05 2011-05-12 Procédé de fourniture d'un service push et système de fourniture d'un service push destiné à sa mise en œuvre WO2012005440A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2010-0064252 2010-07-05
KR1020100064252A KR101192389B1 (ko) 2010-07-05 2010-07-05 Ｐｕｓｈ 서비스 제공 방법 및 이를 수행하는 ｐｕｓｈ 서비스 제공 시스템

Publications (2)

Publication Number Publication Date
WO2012005440A2 true WO2012005440A2 (fr) 2012-01-12
WO2012005440A3 WO2012005440A3 (fr) 2012-04-05

Family

ID=45441609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2011/003489 WO2012005440A2 (fr) 2010-07-05 2011-05-12 Procédé de fourniture d'un service push et système de fourniture d'un service push destiné à sa mise en œuvre

Country Status (2)

Country Link
KR (1) KR101192389B1 (fr)
WO (1) WO2012005440A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013189222A1 (fr) * 2012-06-19 2013-12-27 中兴通讯股份有限公司 Procédé d'envoi d'informations de déclenchement, procédé de conversion de protocole et système associé

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101277096B1 (ko) * 2011-08-03 2013-06-21 에스케이텔레콤 주식회사 클라이언트의 접속 방식에 따라 선택적 인증을 수행하는 푸시 서비스 제공 시스템 및 그 제공 방법
KR101671685B1 (ko) * 2016-10-04 2016-11-03 주식회사 케이티 메시지 전송 시스템, 방법 및 컴퓨터 프로그램

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20020042776A (ko) * 2002-04-27 2002-06-07 이환석 네트워크 관리자에 의한 메세지 푸싱방법 및 푸쉬시스템
KR20030006093A (ko) * 2001-07-11 2003-01-23 에스케이 텔레콤주식회사 차세대 이동 통신망에서의 왑 푸시 서비스 방법
KR20060102237A (ko) * 2005-03-23 2006-09-27 하경림 사용자의 멀티미디어 통신환경에 따라 최적의 통신경로를설정하는 멀티미디어 통신 통합시스템 및 이를 이용한통화방법
KR100772498B1 (ko) * 2006-11-08 2007-11-01 주식회사 케이티프리텔 콘텐츠 푸쉬 서비스 제공 방법, 이를 위한 이동통신시스템및 이동 단말

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100764063B1 (ko) 2006-09-30 2007-10-05 광주과학기술원 멀티캐스트 기반 다자간 협업 환경에서의 유디피멀티캐스트 터널링 방법 및 그 시스템

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030006093A (ko) * 2001-07-11 2003-01-23 에스케이 텔레콤주식회사 차세대 이동 통신망에서의 왑 푸시 서비스 방법
KR20020042776A (ko) * 2002-04-27 2002-06-07 이환석 네트워크 관리자에 의한 메세지 푸싱방법 및 푸쉬시스템
KR20060102237A (ko) * 2005-03-23 2006-09-27 하경림 사용자의 멀티미디어 통신환경에 따라 최적의 통신경로를설정하는 멀티미디어 통신 통합시스템 및 이를 이용한통화방법
KR100772498B1 (ko) * 2006-11-08 2007-11-01 주식회사 케이티프리텔 콘텐츠 푸쉬 서비스 제공 방법, 이를 위한 이동통신시스템및 이동 단말

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013189222A1 (fr) * 2012-06-19 2013-12-27 中兴通讯股份有限公司 Procédé d'envoi d'informations de déclenchement, procédé de conversion de protocole et système associé
CN103517230A (zh) * 2012-06-19 2014-01-15 中兴通讯股份有限公司 触发信息发送和协议转换的方法及系统
US9204273B2 (en) 2012-06-19 2015-12-01 Zte Corporation Method and system for trigger information transmission and protocol conversion
CN103517230B (zh) * 2012-06-19 2018-05-08 中兴通讯股份有限公司 触发信息发送和协议转换的方法及系统

Also Published As

Publication number Publication date
KR101192389B1 (ko) 2012-10-17
WO2012005440A3 (fr) 2012-04-05
KR20120003576A (ko) 2012-01-11

Similar Documents

Publication Publication Date Title
US10560265B2 (en) Mobile secret communications method based on quantum key distribution network
EP3007478B1 (fr) Procédé de communications secrètes mobiles basé sur un réseau de distribution de clé quantique
WO2012074198A1 (fr) Terminal et nœud intermédiaire dans un environnement de réseautage orienté contenu et procédé de communication de terminal et de nœud intermédiaire
US7123693B2 (en) Method and apparatus for increasing the reliability of an emergency call communication network
US8874911B2 (en) Terminal device, system, connection management server, and computer readable medium
JP2004530333A (ja) Ｉｐテレフォニにおいてインテリジェントネットワーク制御サービスを提供するための方法およびシステム
WO2015105402A1 (fr) Procédé et système de prise en charge de sécurité pour découverte de service et communication de groupe dans un système de communication mobile
JP5506932B2 (ja) 新たなネットワークとインターネットとの相互通信の実現方法、システム及び通信端
US7873826B2 (en) Routing voice over internet (VoIP) call
US10764341B2 (en) System for routing multicast page/party call audio among voice over internet (VoIP) devices in different local area networks (LANs) via internet
US7333474B2 (en) Extended handset functionality and mobility
WO2010030126A2 (fr) Procédé et appareil pour service de conversion du signal d'appel basé sur la localisation dans un réseau de communication sans fil
CN105657040B (zh) 一种设备间内网通信的方法和系统
WO2012005440A2 (fr) Procédé de fourniture d'un service push et système de fourniture d'un service push destiné à sa mise en œuvre
US9100729B2 (en) Method for handling a telecommunications connection, telecommunications arrangement, switching device and network coupling device
JP2007221481A (ja) 電話システム
WO2013081208A1 (fr) Procédé de transmission de données à partir d'un terminal dans un système de communication sans fil, et dispositif correspondant
JP4911222B2 (ja) 通信システム、通信システムにおける通信方法、及び中継装置
WO2010131432A1 (fr) Dispositif formant relais téléphonique, et procédé et programme de réalisation d'un relais téléphonique
WO2012124891A2 (fr) Système de fourniture de service basé sur une voie de communication multiple
WO2012018190A2 (fr) Système et procédé de communication basés sur le trafic
US20060256777A1 (en) Communication system, exchange apparatus, and communication method
JP4098073B2 (ja) パケット通信システム
WO2012070794A2 (fr) Procédé d'établissement de communication à base de communication fmc, et infrastructure de connexion de communication
JP3751301B2 (ja) 多ノード通信システム

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

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 23/05/2013)

122 Ep: pct application non-entry in european phase

Ref document number: 11803726

Country of ref document: EP

Kind code of ref document: A2