WO2010059088A1 - Procédé et agencements dans un réseau de communication - Google Patents

Procédé et agencements dans un réseau de communication Download PDF

Info

Publication number
WO2010059088A1
WO2010059088A1 PCT/SE2008/051338 SE2008051338W WO2010059088A1 WO 2010059088 A1 WO2010059088 A1 WO 2010059088A1 SE 2008051338 W SE2008051338 W SE 2008051338W WO 2010059088 A1 WO2010059088 A1 WO 2010059088A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
server
application
reachability
connectivity
Prior art date
Application number
PCT/SE2008/051338
Other languages
English (en)
Inventor
Johnny Karlsen
Christer Boberg
Anders Eriksson
Per Willars
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to GB1109077.6A priority Critical patent/GB2477889C/en
Priority to PCT/SE2008/051338 priority patent/WO2010059088A1/fr
Priority to US13/130,632 priority patent/US20110231562A1/en
Publication of WO2010059088A1 publication Critical patent/WO2010059088A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/029—Firewall traversal, e.g. tunnelling or, creating pinholes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • 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/14—Session management
    • 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/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to methods and arrangements relating to connectivity or reachability in a communication network.
  • connectivity or reachability When there is connectivity or reachability between a server and a client it is often advantageous if the connectivity or reachability can be maintained, e.g. so that the server can send messages to the client at any time. Such a connectivity or reachability may be established so that the client can be provided with services and applications transmitted to the client by or via the server.
  • FW firewall
  • NAT Network Address Translation
  • the keep-alive message must be sent frequently enough not to let the pinhole open state in the firewall expire.
  • the frequency with which the keep-alive message must be sent depends on the transport protocol used and is also dependent on the settings of the firewall.
  • the protocol User Datagram Protocol (UDP) generally needs a relatively high send-frequency, in the region of multiple times per minute, and the Transmission Control Protocol (TCP) can function with a lower send-frequency, in the region of multiple times per hour.
  • the server can no longer reach the client. There is no guarantee, or is even likely, that the client will in any way be informed that the connectivity or reachability path towards, or with, the server has been terminated. This situation lasts until the client once again initiates a connectivity or reachability path towards, or with, the server.
  • keep-alive messages with a frequency high enough to make sure that potential outages of the connectivity or reachability will be short enough not to adversely affect the perceived Quality of Service (QoS) of the application or service provided to the client.
  • QoS Quality of Service
  • keep-alive messages are sent with an interval of 30 seconds between each message.
  • IMS IP Multimedia Subsystem
  • SIP Session Initiation Protocol
  • TCP Transmission Control Protocol
  • the firewall behaves in an unexpected way is e.g. meant that the configuration of the firewall changes in regards to what is required to keep the pinhole in an open state. Such configuration may e.g.
  • a client as mentioned herein may be present on a terminal, e.g. a mobile terminal. There may be several clients on or in one terminal.
  • the client may comprise at least one platform, e.g. a SIP and/or an IMS platform and at least one application.
  • this server may be called a first server.
  • the deterioration may e.g. be an interruption of the connectivity or reachability.
  • the re- establishment message makes or enables the client to re-establish the connectivity or reachability with the first server.
  • the re-establishment message may be sent from the first server, but it may also be sent from another server, e.g. an additional server monitoring the connectivity or reachability between the client and the first server.
  • the server sending the re-establishment message to the client is provided with, or has access to, address information of the client.
  • the address information of the client may include the MSISDN address of the client or terminal and a port identifier, e.g. a port number, of an available communication port of the terminal.
  • Several clients may be comprised on, or in, a terminal and the MSISDN number relates to the terminal as a whole.
  • a certain communication port of the terminal is or can be related or connected to a certain client and/or a certain application.
  • client communication port means that a communication port of the terminal is related or connected to a certain client and/or a certain application, e.g. while the client has registered itself for listening to this communication port.
  • a first method executed in a server in a communication network The server may handle messages for at least one client and/or application.
  • the first method may comprise to identify a deterioration in a connectivity or reachability between the server and the at least one client and/or application.
  • the first method may further comprise to transmit a re-establishment message to the at least one client and/or application.
  • the re-establishment message is adapted or contains such information so as to make or enable the at least one client and/or application to re-establish the connectivity or reachability.
  • the re-establishment message may also be empty, i.e. contain no information, e.g. contain no information in the body of the re-establishment message.
  • the connectivity or reachability is established via or through a pinhole in a firewall.
  • the deterioration is a termination of an open state of said pinhole.
  • the deterioration is an interruption of said connectivity or reachability.
  • the deterioration is identified by said server.
  • the re-establishment message is transmitted from the server to the at least one client and/or application.
  • the connectivity or reachability is re-established to the state it had before the deterioration.
  • the measure of identifying a deterioration in a connectivity or reachability may be preceded by the step of establishing a connectivity or reachability between the at least one client and/or application, and said server.
  • the measure of identifying a deterioration in a connectivity or reachability may further be preceded by the step of registering, or making available, a terminal address and a client communication port identifier of the at least one client at or for the server.
  • the terminal address is the Mobile Subscriber Integrated Services Digital Network Number (MSISDN) of a terminal of the at least one client
  • the client communication port identifier relates to a client communication port, being e.g. a WAP Push port, of the at least one client and/or application.
  • MSISDN Mobile Subscriber Integrated Services Digital Network Number
  • a server arrangement in a server for handling messages for at least one client and/or application may comprise an identifying element for identifying a deterioration in a connectivity or reachability between the server and the at least one client and/or application.
  • the server arrangement may further comprise a transmitting element for transmitting a re-establishment message to the at least one client and/or application.
  • a transmitting element for transmitting a re-establishment message to the at least one client and/or application.
  • the re-establishment message is adapted to make or enable the at least one client and/or application to re-establish the connectivity or reachability.
  • a server arrangement wherein the connectivity or reachability is established via or through a pinhole in a firewall.
  • a server arrangement wherein said deterioration is a termination of an open state of said pinhole.
  • the identifying element is adapted to identify an interruption in the connectivity or reachability.
  • a server arrangement wherein the transmitting element is adapted to transmit the re-establishment message from the server to the at least one client and/or application.
  • a server arrangement wherein the transmitting element is adapted to transmit a re-establishment message that makes or enables the at least one client and/or application to re-establish the connectivity or reachability to the state it had before the deterioration.
  • a server arrangement may comprise an establishing element that is adapted to establish a connectivity or reachability between the at least one client, and/or application, and the server. Further the server arrangement may comprise a registering element for registering, or making available, a terminal address and a client communication port identifier of the at least one client and/or application at or for the server.
  • a server arrangement wherein the registering element is adapted to retrieve or receive the terminal address and the client communication port identifier from the at least one client and/or from a database.
  • the terminal address is the Mobile Subscriber Integrated Services Digital Network Number of the terminal of the at least one client.
  • the client communication port identifier relates to a client communication port, being e.g. a WAP Push port, of the at least one client and/or application.
  • a second method executed in a client and/or application in a communication network may be adapted to handle connectivity or reachability with or towards at least one server.
  • the second method may comprise the measure of establishing connectivity or reachability between the client, and/or application, and the at least one server.
  • the second method may further comprise the measure of transmitting a registration message to the server.
  • the registration message may comprise a client communication port identifier and optionally a terminal address, of the client and/or application.
  • the connectivity or reachability is established via or through a pinhole in a firewall.
  • the deterioration is a termination of an open state of the pinhole.
  • the second method may comprise the step that the client and/or application receives a re-establishment message enabling or making the client and/or application to re-establish the connectivity or reachability with or towards the at least one server.
  • the second method may comprise the step that the client and/or application receives the re-establishment message from the at least one server or from an additional server.
  • the second method may comprise the step that the client, and/or application, registers itself for listening on or to an available communication port, e.g. a WAP-PUSH port, of the terminal on which said client, and/or application, resides.
  • the step that the client, and/or application, registers itself for listening may be performed before the step of establishing connectivity or reachability.
  • the second method may comprise that the client comprises a platform, e.g. a SIP and/or IMS platform.
  • the platform may be participating in the steps of establishing, transmitting, receiving and registering described above.
  • a client arrangement in a terminal in a communication network may comprise at least one client and may be adapted to handle connectivity or reachability with or towards at least one server.
  • the client arrangement may comprise a client establishing element adapted for establishing connectivity or reachability between a client, and/or application, and the at least one server.
  • the client arrangement may further comprise a client transmitting element adapted for transmitting a registration message to the at least one server.
  • the registration message may comprise a client communication port identifier and optionally a terminal address, of said client and/or application.
  • a client arrangement wherein the connectivity or reachability is established via or through a pinhole in a firewall.
  • a client arrangement wherein the deterioration is a termination of an open state of the pinhole.
  • a client arrangement comprising a client receiving element that is adapted for receiving a re-establishment message.
  • the re-establishment message is adapted for enabling or making the client to re-establish the connectivity or reachability with or towards the at least one server.
  • a client arrangement wherein the client receiving element is adapted to receive the re-establishment message from the at least one server or from an additional server.
  • a client arrangement comprising a client registering element that is adapted so that the client, and/or application, can register itself for listening on or to an available communication port, e.g. a WAP-PUSH port, of the terminal on which the client and/or application resides.
  • a client registering element that is adapted so that the client, and/or application, can register itself for listening on or to an available communication port, e.g. a WAP-PUSH port, of the terminal on which the client and/or application resides.
  • client arrangement wherein at least one of the client elements; client establishing element, client transmitting element, client receiving element and client registering element, is comprised in or on a platform, e.g. a SIP and/or an IMS platform, of or in the client.
  • a platform e.g. a SIP and/or an IMS platform, of or in the client.
  • One advantage of the methods and/or arrangements, in any of its forms or embodiments, is that frequent sending of keep-alive messages is avoided. Further, this is achieved without affecting the perceived QoS of the system, service or application. Yet further may the re-establishment procedure be completely contained, or executed completely, between the client and the first proxy node of the first server. The other end-point of the first server may be completely unaware or uninformed about the re- establishment procedure.
  • a further advantage is that it is enabled a robust operation of a server or system, e.g. an IMS/SIP or SIP server or system, which is located on the outside of a firewall of an access network. It may be that the access network is lacking the infrastructure of the server or system, e.g. a IMS/SIP or SIP infrastructure.
  • - Fig. Ia schematically shows one example of a network topology in which the present methods and arrangements may be used, and elements of said methods and arrangements
  • - Fig. Ib schematically shows another example of a network topology in which the present methods and arrangements may be used, and elements of said methods and arrangements
  • - Fig. 2 schematically shows signalling and messages sent in one embodiment
  • - Fig. 3 schematically shows one embodiment of the server arrangement 300
  • FIG. 4 schematically shows one embodiment of a registration message 400
  • FIG. 5 schematically shows one embodiment of a re-establishment message 500
  • FIG. 6 schematically shows a terminal, a client and one embodiment of the client arrangement 610.
  • S-CSCF Serving Call Session Control Function
  • P-CSCF Proxy Call Session Control Function
  • MSISDN Mobile Subscriber Integrated Services Digital Network Number
  • SIP Session Initiation Protocol
  • IMS IP Multimedia Subsystem
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • One part of the re-establishing is that the server 100 transmits a re-establishment message 500 to the client 108.
  • the re-establishment message 500 enables or makes the client 108 to reestablish the interrupted or deteriorated connectivity or reachability 116.
  • the re- establishment message 500 may be sent using a different type of communication than of the connectivity or reachability 116.
  • the server 100 is provided with address information about the client 108. This address information may be transmitted from the client 108 to the server 100 but may also, at least in part, be provided to the server in some other way, e.g. by storing address information in a database connected to the server 100.
  • the server 100 may include or comprise a proxy node 102 and a serving node 104.
  • the server 100 may be a Call Session Control Function (CSCF) server, the proxy node 102 may be a Proxy- CSCF and the serving node 104 may be a Serving-CSCF.
  • the firewall 106 may comprise a pinhole 124 and Network Address Translation (NAT) functionality.
  • Domain 1 110 may be an IMS domain
  • domain 2 112 may be an operator domain, e.g. the network of a mobile access operator.
  • the client 108 comprises a terminal 109 which may be a mobile terminal, the first network 114 may be the internet, the second network 120 may be a cellular network, e.g. of a mobile access operator.
  • the connectivity or reachability 116 may e.g. be of the TCP or TLS type.
  • the server 100 may comprise an arrangement 300 having among other parts a registering element 306 adapted to retrieve or receive the terminal address 620, e.g. a MSISDN, and/or the client communication port 622 from said client 108.
  • the registering element 306 may as well be adapted to retrieve the terminal address from a database 118, e.g. a user profile database such as an HSS database.
  • the terminal address may e.g. be retrieved from a service profile.
  • the server arrangement 300 may comprise an identifying element 302, a transmitting element 304, a registering element 306, a retrieving element 308 and an establishing element 310.
  • the registration message 400 may comprise address and port information 402 of the client 108 and terminal 109, e.g. msisdn of the terminal/client and a client communication port identifier 624.
  • the communication port identifier 624 may e.g. be a communication port number 624.
  • the communication port may e.g. be a WAP-Push port.
  • a re-establishment message 500 is schematically shown.
  • the re-establishment message 500 may comprise reestablishment information 502. If the re-establishment message 500 is an SMS it could e.g. be suitable that the re- establishment message 500 comprises reestablishment information 502.
  • the terminal 109 may comprise at least one client 108, a terminal address 620 and at least one terminal/client communication port 622 having a communication port number or identifier 624.
  • the client 108 may comprise at least one application 604 and at least one platform 602.
  • the platform 602 may comprise a client arrangement 610 comprising at least one of a client establishing element 612, a client transmitting element 614, a client receiving element 616 and a client registering element 618.
  • the server 100 may e.g. be a SIP server, in case IMS is implemented on the server 100 said server 100 may comprise a P-CSCF node.
  • the first network 114 is a cellular network, e.g. a cellular Internet network, where it is not suitable to send keep-alive messages with a high frequency
  • PUSH is often utilised and can be used for re-establishing the connectivity from the server 100 to the client 108.
  • the first network 114 is a fixed network, e.g. a fixed Internet network, WAP-PUSH is often not present but keep-alive messages may be sent with a high frequency.
  • the client 108 reports to the server the number of the
  • WAP-PUSH port which is currently available at/in the terminal, and also or in parallel starts listening to this port for any server initiated connectivity or reachability.
  • the WAP-PUSH port number may be sent to the server 100 in the SIP REGISTER request in a new header named for example "Reestablish".
  • a new header is chosen to convey this information, but it can also be placed in the body or in an augmented, existing, header, for example using a feature tag.
  • the description in the following is based on using TCP for the transport or connectivity or reachability between the client and the server but this is just one example.
  • Another protocol that may be used is e.g. TLS, this protocol has similar transport characteristics as TCP but the information is encrypted and the terminating point is authenticated to achieve a secure tunnel with a known endpoint.
  • the SIP/IMS platform 602 of the client 108 will register itself for listening on or to a currently available WAP-PUSH port of the terminal, shown at 2:01.
  • the SIP/IMS platform 602 of the client establishes a TCP connection to the proxy node 102, here a P-CSCF, shown at 2:1.
  • the SIP/IMS platform 602 of the client uses the TCP to make a registration, e.g. to send a registration message 400, towards the serving node 104, here an S-CSCF, via the proxy node 102.
  • the registration message 400 contains address information 402 of the client, here in the form of the new header "Reestablish".
  • the format of this header is an MSISDN number and the local WAP-PUSH port number in the form "msidn:port".
  • a first part of the registration towards the serving node 104 is shown at 2:2.
  • the registration message 400 is received by/at the proxy node 102.
  • the new header "Reestablish" is removed from the registration message 400 and the data from this header is stored at the proxy node 102 together with contact information for the client. This is shown at 2:2b.
  • the registration message 400 is passed on to the serving node 104 together with the specific P-CSCF contact information.
  • a response is received from the serving node 104 and passed on to the SIP/IMS platform 602 of the client, shown at 2:4 and 2:5.
  • the proxy node's 102, here P-CSCF, contact information may comprise an internal reference in the P-CSCF used to point at the connection/connectivity of a specific client and may also comprise the P-CSCF identity. These two pieces of information may be used by the serving 104, here an S- CSCF, to address a specific client.
  • the REGISTER response sent at 2:5 is received by the SIP/IMS platform 602 of the client 108.
  • the persistent TCP will have lost its state and can no longer be used by the server 100 to communicate with the client 108. Both endpoints, the client 108, and the proxy node 102 or P-CSCF are unaware of this situation.
  • a message/request comes in from the serving node 104 to the proxy node 102, this is illustrated at 2:7.
  • This message/request is using the specific P-CSCF contact information previously saved at the serving node 104.
  • the proxy node 102 looks up the specific TCP session or connection to be used, and passes on the request to be sent to the client 108.
  • the message/request may e.g. be a pager mode message or a message within an instant messaging (IM) service, e.g. a chat message.
  • IM instant messaging
  • the proxy node 102 is notified in some other way about that the TCP session is no longer functional, e.g through a TCP RST (TCP Reset) message ? or state ?) indicating this.
  • TCP RST TCP Reset
  • the proxy node 102 looks up the WAP-PUSH information for this client or contact and sends a re- establishment message 500 to the client 108 using the WAP-PUSH information, illustrated at 2:9 .
  • the re-establishment message 500 may be sent in the form of an SMS containing the information that is necessary to enable or make the client 108 to re-establish the connectivity or reachability with the server 100.
  • the client 108 and/or terminal 109 receives the re-establishment message 500, e.g. a WAP-PUSH message, which is dispatched to the SIP/IMS platform 602 indicated by the port number. There could be multiple SIP/IMS platform 602s in the client 108/terminal 109 and each will listen to a specific port.
  • the SIP/IMS platform 602 receives the re-establishment message 500, e.g. a WAP-PUSH, and establishes a new connectivity or reachability, e.g. using TCP or TLS, and sends a new registration message 400 in the same way as described in paragraph/heading 1., illustrated at 2:10, 2:11.
  • the proxy node 102 here a P-CSCF
  • the earlier assigned specific contact information will be reassigned to the new connection/connectivity or reachability, illustrated at 2:1 Ib. This re-assignment will only take place if the contact information, source IP address, and call-id are the same as in an already existing registration. If this is not the case, the new registration message 400 will be treated as a new registration.
  • the registration will be passed on to the serving node 104, here a S-CSCF, illustrated at 2:12.
  • the S-CSCF will not see any difference between this registration and a regular re-registration, given that the condition above is fulfilled. Re-using the earlier existing contact information means that a currently pending request is still valid.
  • Transmissions 2:13, 2:14 correspond to transmissions 2:4, 2:5.
  • the proxy node 102 here a P-CSCF, sends out the pending request on the new connectivity or reachability, e.g. of the TCP or TLS type, and receives a response which can be passed on to the S-CSCF 104.
  • These transmissions are illustrated at 2:15a, 2:15b for the pending request and 2:16, 2:17 for the response.

Abstract

L'invention concerne un procédé et un agencement (300, 600) dans un serveur (100) et un client (108) destinés à rétablir la capacité de connexion ou la capacité de portée (116) entre le serveur (100) et le client (108).
PCT/SE2008/051338 2008-11-24 2008-11-24 Procédé et agencements dans un réseau de communication WO2010059088A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
GB1109077.6A GB2477889C (en) 2008-11-24 2008-11-24 Method and arrangements in a communication network
PCT/SE2008/051338 WO2010059088A1 (fr) 2008-11-24 2008-11-24 Procédé et agencements dans un réseau de communication
US13/130,632 US20110231562A1 (en) 2008-11-24 2008-11-24 Method and Arrangements in a Communication Network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2008/051338 WO2010059088A1 (fr) 2008-11-24 2008-11-24 Procédé et agencements dans un réseau de communication

Publications (1)

Publication Number Publication Date
WO2010059088A1 true WO2010059088A1 (fr) 2010-05-27

Family

ID=42198341

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2008/051338 WO2010059088A1 (fr) 2008-11-24 2008-11-24 Procédé et agencements dans un réseau de communication

Country Status (3)

Country Link
US (1) US20110231562A1 (fr)
GB (1) GB2477889C (fr)
WO (1) WO2010059088A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2559192A4 (fr) * 2010-04-15 2017-10-04 Vonage Network LLC Systèmes et procédés pour améliorer la qualité des communications voip
KR20150032018A (ko) * 2013-09-17 2015-03-25 삼성전자주식회사 전자 장치 및 전자 장치의 정보 전송 방법, 정보 전송 시스템
CN104703146B (zh) * 2013-12-09 2019-03-08 腾讯科技（深圳）有限公司 信息推送方法、客户端及系统
US9973305B2 (en) 2014-12-30 2018-05-15 Mediatek Inc. Soft buffer partition for superposition coding
US10064112B2 (en) * 2015-05-29 2018-08-28 Apple Inc. Apparatus, systems and methods for switching between radio access technologies
EP3591928B1 (fr) * 2018-07-05 2021-09-01 Deutsche Telekom AG Procédé de communication améliorée entre une application logicielle client - étant chargée ou installée sur un dispositif informatique client - et un arrière-plan de réseau d'application, dispositif de calcul client et système de communication améliorée entre une application logicielle client et un arrière-plan de réseau d'application, programme et support lisible par ordinateur

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1569404A1 (fr) * 2004-02-25 2005-08-31 Research In Motion Limited Système et méthode pour maintenir une connexion de réseau
US20080162703A1 (en) * 2002-07-23 2008-07-03 International Business Machines Corporation Dynamic client/server session recovery in a heterogenous computer network
US20080159163A1 (en) * 2006-12-29 2008-07-03 Nokia Corporation Communications control

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6018805A (en) * 1997-12-15 2000-01-25 Recipio Transparent recovery of distributed-objects using intelligent proxies
US7925771B1 (en) * 2003-03-03 2011-04-12 Realnetworks, Inc. System and method for uninterrupted streaming
US20050288045A1 (en) * 2004-06-28 2005-12-29 Yang Jianhao M Apparatus, and an associated method, for forming direct data connection between applications of a set of mobile stations
US20060200658A1 (en) * 2005-03-07 2006-09-07 Bitfone Corporation Agent framework for mobile devices
US8620288B2 (en) * 2007-11-16 2013-12-31 Alcatel Lucent Targeted mobile content insertion and/or replacement

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080162703A1 (en) * 2002-07-23 2008-07-03 International Business Machines Corporation Dynamic client/server session recovery in a heterogenous computer network
EP1569404A1 (fr) * 2004-02-25 2005-08-31 Research In Motion Limited Système et méthode pour maintenir une connexion de réseau
US20080159163A1 (en) * 2006-12-29 2008-07-03 Nokia Corporation Communications control

Also Published As

Publication number Publication date
US20110231562A1 (en) 2011-09-22
GB2477889C (en) 2017-08-16
GB201109077D0 (en) 2011-07-13
GB2477889B (en) 2013-10-09
GB2477889A (en) 2011-08-17

Similar Documents

Publication Publication Date Title
EP1758323B1 (fr) Procede destine a un terminal d'identification de commande de routage d'interaction de capacite pendant que ims et cs sont co-instantanes
US7707286B2 (en) Methods for managing presence information in a real-time communications network
US8150393B2 (en) Method for handling service failures
US8401002B2 (en) Exchange and use of globally unique device identifiers for circuit-switched and packet switched integration
EP2090066B1 (fr) Procedes et appareils de transport d'informations de statut de connectivite de signalisation relatives a la connexion de signalisation entre un terminal et un p-cscf dans un sous-systeme multimedia ip
US9143537B2 (en) Device registration in an IMS network
EP2093970B1 (fr) Gestion de service d'appel dans un système basé sur IMS
US8036659B2 (en) Method for requesting an unregistered UE to perform registration in the IMS
JP5173607B2 (ja) 通信システム
WO2009039894A1 (fr) Récupération de défaut dans un réseau de sous-système multimédia ip
WO2008048753B1 (fr) Procédé et appareil pour des connexions transparentes et une continuité de service dans un système de communication multimédia de protocole IP d'accès agnostique
WO2006064347A1 (fr) Procede et systeme de transfert instantane de fichiers multimedia entre des utilisateurs de radiocommunications mobiles desservis par des services combinatoires
EP2005714A2 (fr) Transfert rapide effectué au moyen de sip
EP2098036B1 (fr) Procédés et appareils pour résilier un service de sous-système multimédia ip lorsque l'adresse ip n'est plus allouée à l'utilisateur
US20110231562A1 (en) Method and Arrangements in a Communication Network
US9420018B2 (en) End-to-end address transfer
KR101453971B1 (ko) 무선 네트워크와 유선 네트워크의 연동을 위한 장치 및방법
KR101602521B1 (ko) 하나의 ｐｕｉｄ를 공유하는 다수의 ｕｅ를 구별하는 방법 및 장치
EP1720365A1 (fr) Procédé destiné à échanger des informations de capacitè entre des utilisateurs d'un réseau UMTS
EP2200254B1 (fr) Système de réseau mobile et procédé de fourniture de message de guidage
KR102273762B1 (ko) VoLTE(Voice over Long Term Evolution) 시스템 및 그 제어방법과 및 이 시스템에 포함되는 PGW(PDN Gateway) 및 CSCF(Call Session Control Function)과 그 제어방법
US20100153559A1 (en) Method and Apparatus for Suspending Network Based Services
EP1879361A1 (fr) Transfert d'appel rapide utilisant SIP
RU2417544C2 (ru) Способы и устройства для передачи информации о состоянии сигнального соединения, относящейся к сигнальному соединению между терминалом и модулем посреднической функции управления сеансом/вызовом (p-cscf) в мультимедийной подсистеме интернет-протокола (ims)
GB2502465A (en) Re-establishing connectivity or reachability between a client and server

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

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 3719/DELNP/2011

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 13130632

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 1109077

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20081124

WWE Wipo information: entry into national phase

Ref document number: 1109077.6

Country of ref document: GB

122 Ep: pct application non-entry in european phase

Ref document number: 08878307

Country of ref document: EP

Kind code of ref document: A1