EP3761587B1 - Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk - Google Patents

Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk Download PDF

Info

Publication number
EP3761587B1
EP3761587B1 EP19184398.6A EP19184398A EP3761587B1 EP 3761587 B1 EP3761587 B1 EP 3761587B1 EP 19184398 A EP19184398 A EP 19184398A EP 3761587 B1 EP3761587 B1 EP 3761587B1
Authority
EP
European Patent Office
Prior art keywords
uac
registration
uas
sip
onetime
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP19184398.6A
Other languages
English (en)
French (fr)
Other versions
EP3761587A1 (de
Inventor
Walid Jerbi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Deutsche Telekom AG
Original Assignee
Deutsche Telekom AG
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 Deutsche Telekom AG filed Critical Deutsche Telekom AG
Priority to EP19184398.6A priority Critical patent/EP3761587B1/de
Priority to US16/919,204 priority patent/US11212323B2/en
Publication of EP3761587A1 publication Critical patent/EP3761587A1/de
Application granted granted Critical
Publication of EP3761587B1 publication Critical patent/EP3761587B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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/147—Signalling methods or messages providing extensions to protocols defined by standardisation
    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the invention relates to a method for infinity registration using a Session Initiation Protocol, SIP, based communication in a Session Initiation Protocol based network, and network.
  • Session Initiation Protocol As defined in the standard RFC 3261 (https://tools.ietf.org/html/rfc3261). This protocol is the well-established standard in the IP Multimedia Telephony and is used not only in 3GPP IMS networks but also in Legacy Voice over IP networks or in enterprise networks.
  • a user agent acts a user agent client (UAC) when it requests a service function.
  • a UA acts as a user agent server (UAS) when it responds to a request.
  • a User Agent Client is a Session Initiation Protocol (SIP) or Voice over IP (VoIP) application that works as a communication gateway and generates distributed network service requests.
  • SIP Session Initiation Protocol
  • VoIP Voice over IP
  • the UAC refreshes the contact with the UAS periodically based on an expiry time signaled by the User-Agent-Server (UAS).
  • UAS User-Agent-Server
  • the UAC sends a register message before the timer expires. This process is referred to as a re-register. Otherwise, if the expiry timer expires, the UAC is considered not registered and is deleted from the registered users' database.
  • IMS IP Multimedia Core Network Subsystem
  • the signaling amount involved in this procedure can be very high depending on the re-registration interval, i.e. the periodicity where the UAC sends registration traffic (re-registration). Further, several timers must start here and there to keep the registration alive. This also means that the UAC and the UAS need to keep their respective timers in synchronization. Besides, other application servers in the network who are informed by the registration might also start the timers. In some operator networks this traffic sums up to an 80% of the whole SIP traffic.
  • US 2005/239498 A1 relates to a call set-up for multi-mode communication.
  • the call set up for a call to a multi-mode communication is done by registering and re-registering priorities with a Session Initiation Protocol (SIP) registrar.
  • SIP Session Initiation Protocol
  • US 2006/149847 A1 relates to a method and terminal device for handling a suspended network state, wherein the end of a suspended network state is detected and subscription to a state event package is initiated in response to the detected end of suspension.
  • US 7 610 619 B2 relates to a method for adaptively authenticating a subject based on authentication information, comprising the steps of providing for the receipt of the authentication information; providing for the performance of Java Authentication and Authorization Service (JAAS) authentication of the subject based on the authentication information and wherein successful authentication of the subject results in the association of a principal with the subject; providing for the signing of the principal by determining an authentication code for the principal that is a function of the principal and a key.
  • Java Authentication and Authorization Service Java Authentication and Authorization Service
  • the invention introduces a new means to manage SIP Clients based on the SIP Protocol.
  • a method for infinity registration using a Session Initiation Protocol, SIP, based communication in a Session Initiation Protocol based network, wherein the network comprises at least two or more SIP user agents and wherein each SIP user agent can act as a user agent client, UAC, when requesting a service function and as a user agent server, UAS, when responding to a request service function.
  • SIP Session Initiation Protocol
  • UAC user agent client
  • UAS user agent server
  • the method comprises the steps of: initiating a registration, from the UAC to the UAS, wherein the registration comprises a field for indicating infinity registration capability and a field for indicating management communication capability; sending, from the UAS to the UAC, a registration expiry timer with a value equal to infinity and a management header including a onetime unique token; storing, at the UAC, the onetime unique token in combination with the registered UAC; detecting, at the UAS or UAC, whether loss of a connection between the UAS and the UAC has occurred; if a loss of the connection is detected by the UAC, the UAC initiates a new registration without any indication from the UAS; if a loss of the connection is detected by the UAS, sending, by the UAS to the UAC, a SIP message asking the UAC to initiate a new registration; sending, by the UAS to the UAC, the onetime unique token to refer to the no longer valid registration as indicated during the registration.
  • a Session Initiation Protocol based network comprising at least two or more SIP user agents, wherein each SIP user agent can act as a user agent client, UAC, when requesting a service function and as a user agent server, UAS, when responding to a request service function.
  • the UAC is configured to initiate a registration with the UAS, wherein the registration comprises a field for indicating infinity registration capability and a field for indicating management communication capability.
  • the UAS is configured to send to the UAC, a registration expiry timer with a value equal to infinity and a management header including a onetime unique token.
  • the UAC is configured to store, at the UAC, the onetime unique token in combination with the registered UAC.
  • the UAS and UAC are configured to detect whether loss of a connection between the UAS and the UAC has occurred. If a loss of the connection is detected by the UAC, the UAC is configured to initiate a new registration without any indication from the UAS. If a loss of the connection is detected by the UAS, the UAS is configured to send to the UAC, a SIP message asking the UAC to initiate a new registration.
  • the UAS is configured to send to the UAC, the onetime unique token to refer to the no longer valid registration as announced during the registration.
  • the onetime unique token matches a registration and is sent on a port in which the UAS may contact the UAC, at any time with a SIP message.
  • the expiry timer may be coded as "00".
  • the invention provides a method for infinity registration using Session Initiation Protocol (SIP) based communication in an IP Multimedia Subsystem (IMS) network comprising one or more SIP user agents.
  • SIP Session Initiation Protocol
  • IMS IP Multimedia Subsystem
  • the UAC indicates to the UAS about the capability of infinity registration and/or the capability for management communication.
  • the re-registration procedure to refresh a contact, between a UAC and a UAS, before a registration expiry timer expires is changed, by the UAS, by sending a registration expiry timer with a value equal to infinity (e.g. can be coded as "00", so that it is not to be confused with "0" that typically means deregister).
  • a registration expiry timer with a value equal to infinity (e.g. can be coded as "00", so that it is not to be confused with "0" that typically means deregister).
  • TCP Transmission Control Protocol
  • TLS Transport Layer Security
  • the UAS also sends to the UAC, a management header including a onetime token. This onetime unique token is communicated for the first time during the registration.
  • the Edge proxy(s) is/are the node(s) at the IMS network that communicate with the clients. In other words, the Edge proxy(s) hides all the nodes from the core network so that the client only sees the Edge proxy(s), but nothing else from the network.
  • the UAC shall include a Feature-Caps header field with the "+g.3gpp.infinity-reg" contact field parameter, as specified in the standard RFC 6809. This is illustrated in FIG. 2 which depicts an example of how the registration flow with the infinity registration could look like according to the present invention (simplified to the relevant headers skipping authentication and authorization).
  • the UAC notifies the UAS that it supports infinity registration by sending a message which includes a parameter "+g.3gpp.infinity-reg" in the contact field.
  • the UAC may also notify the UAS that it supports the SIP Management Channel by including the parameter "+g.3gpp.management" in the contact field as shown in FIG. 3 .
  • the UAS changes the re-registration procedure to refresh a contact, by sending a registration expiry timer (see field “Expires” in FIGs. 2 or 3 ) with a value equal to "00" (infinity).
  • the UAS also includes a management header for indicating with a onetime unique token, which registration it wants to address.
  • the onetime unique token is stored in combination with the registered UAC/ contact.
  • the UAS detects the loss of connection, then it deregisters the UAC or contact. Normally, it is up to the operator to implement a way to tell the UAC that it shall try to reregister again.
  • some of these operators have auto-configuration servers - for instance in Fixed Line networks, but not only - that manage UACs and can order a new registration. For such operators the infinity registration as described above is enough, i.e. if these operators manage that these servers react on a trigger from the UAS.
  • the present invention introduces a new option, which involves contacting from the UAS to the SIP Client UAC for instance, to achieve a new registration.
  • the UAC must listen on a well-defined port - for example TCP 5060 or TLS-TCP 5061 - or another port based on operator policy or based on a new header or a parameter on an existing header sent by UAC upon Registration.
  • the unique token specifies which registration it wants to address.
  • the UAS may contact the UAC, at any time on a well-known port (like 5060 or 5061 or a new port to be standardized) or based on operator policy or even based on a new header or as a parameter of an existing header, with a SIP message.
  • the UAS sends the unique token to the UAC to inform the UAC about which registration needs to be restarted (in practice, a UAC may have several running registrations).
  • a UAS can contact the UAC at any time on this port with a SIP Message and ask him to perform a specific action like initiate a new registration. Securing this connection with TLS, Access-lists on IP level and/or with other mechanisms on Layer 2 is out of scope of this invention. If the UAC does not find the unique Token sent by UAS in its database, then it must ignore the message and not execute the action required (i.e. a new registration).
  • the UAC shall include a Feature-Caps header field with the "+g.3gpp.management" contact field parameter, as specified in RFC 6809.
  • This management operation process, started by the UAS, is illustrated in FIG. 3 (simplified to the relevant headers).
  • the UAS contacts and asks the UAC to initiate a new registration.
  • the message includes a management header with the unique token generated as described in FIG.3 .
  • the UAC is configured to store this token in combination with the registered contact or UAC. It is needed to correlate the management action with the registered contact. If the UAC does not find a valid token matching the one sent by the UAS, then it must ignore the message.
  • a major benefit of this approach is also that it reduces the danger of registration storms and gives the operator the possibility to address the devices to reregister in a way that no overload can happen.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Claims (6)

  1. Verfahren zur Infinitätsregistrierung unter Verwendung einer Sitzungseinleitungsprotokoll, SIP, basierten Kommunikation in einem sitzungseinleitungsprotokollbasierten Netzwerk, wobei das Netzwerk mindestens zwei oder mehr SIP-Benutzeragenten aufweist und wobei jeder SIP-Benutzeragent als Benutzeragenten-Client, UAC, agieren kann, wenn er eine Dienstfunktion anfordert, und als Benutzeragenten-Server, UAS, wenn er auf eine angeforderte Dienstfunktion antwortet, wobei das Verfahren die Schritte aufweist:
    Initiieren einer Registrierung vom UAC am UAS, wobei die Registrierung ein Feld zum Anzeigen der Infinitätsregistrierungsfähigkeit und ein Feld zum Anzeigen der Verwaltungskommunikationsfähigkeit aufweist,
    Senden vom UAS an den UAC eines Registrierungsablauf-Timers mit einem Wert gleich unendlich und eines Verwaltungs-Headers, der ein einmalig einzigartiges Token enthält, Speichern des einmalig einzigartigen Tokens im UAC in Kombination mit dem registrierten UAC,
    Erkennen, am UAS oder am UAC, ob ein Verlust einer Verbindung zwischen dem UAS und dem UAC aufgetreten ist,
    wenn ein Verlust der Verbindung durch den UAC erkannt wird, leitet der UAC eine neue Registrierung ein, ohne jede Anzeige vom UAS,
    wenn ein Verlust der Verbindung durch den UAS erkannt wird, Senden durch den UAS an den UAC einer SIP-Nachricht, die den UAC auffordert, eine neue Registrierung einzuleiten,
    Senden durch den UAS an den UAC des einmalig einzigartigen Tokens, um auf die nicht mehr gültige Registrierung zu verweisen, die bei der Registrierung angegeben wurde.
  2. Verfahren nach Anspruch 1, wobei das einmalig einzigartige Token mit einer Registrierung übereinstimmt und auf einem Port gesendet wird, auf dem der UAS den UAC jederzeit mit einer SIP-Nachricht kontaktieren kann.
  3. Verfahren nach Anspruch 1 oder 2, wobei der Ablauf-Timer als "00" codiert ist.
  4. Sitzungseinleitungsprotokoll, SIP, basiertes Netzwerk, das mindestens zwei oder mehr SIP-Benutzeragenten aufweist, wobei jeder SIP-Benutzeragent als Benutzeragenten-Client, UAC, agieren kann, wenn er eine Dienstfunktion anfordert, und als Benutzeragenten-Server, UAS, wenn er auf eine angeforderte Dienstfunktion antwortet, wobei
    der UAC konfiguriert ist, eine Registrierung mit dem UAS zu initiieren, wobei die Registrierung ein Feld zum Anzeigen der Infinitätsregistrierungsfähigkeit und ein Feld zum Anzeigen der Verwaltungskommunikationsfähigkeit aufweist;
    der UAS konfiguriert ist, an die UAC einen Registrierungsablauf-Timer mit einem Wert gleich unendlich und einen Verwaltungs-Header mit einem einmalig einzigartigen Token zu senden;
    der UAC konfiguriert ist, am UAC das einmalig einzigartige Token in Kombination mit dem registrierten UAC zu speichern;
    der UAS und der UAC konfiguriert sind, zu erkennen, ob ein Verlust einer Verbindung zwischen dem UAS und der UAC aufgetreten ist;
    wenn ein Verlust der Verbindung durch den UAC erkannt wird, der UAC konfiguriert ist, eine neue Registrierung ohne jede Anzeige vom UAS einzuleiten,
    wenn ein Verlust der Verbindung durch den UAS erkannt wird, der UAS konfiguriert ist, eine SIP-Nachricht an den UAC zu senden, die den UAC auffordert, eine neue Registrierung zu initiieren;
    der UAS konfiguriert ist, dem UAC das einmalig einzigartige Token zu senden, um auf die nicht mehr gültige Registrierung zu verweisen, die während der Registrierung angekündigt wurde.
  5. Netzwerk nach Anspruch 4, wobei die SIP-Nachricht, die die UAC auffordert, eine neue Registrierung zu initiieren, einen Verwaltungs-Header enthält, um das einmalig einzigartige Token anzuzeigen, das mit einer Registrierung übereinstimmt, und an einem Port gesendet wird, an dem die UAS die UAC jederzeit mit einer SIP-Nachricht kontaktieren kann.
  6. Netzwerk nach Anspruch 4 oder 5, wobei der Ablauf-Timer als "00" codiert ist.
EP19184398.6A 2019-07-04 2019-07-04 Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk Active EP3761587B1 (de)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19184398.6A EP3761587B1 (de) 2019-07-04 2019-07-04 Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk
US16/919,204 US11212323B2 (en) 2019-07-04 2020-07-02 Infinity registration using session initiation protocol-based communication in a session initiation protocol-based network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP19184398.6A EP3761587B1 (de) 2019-07-04 2019-07-04 Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk

Publications (2)

Publication Number Publication Date
EP3761587A1 EP3761587A1 (de) 2021-01-06
EP3761587B1 true EP3761587B1 (de) 2022-11-09

Family

ID=67184794

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19184398.6A Active EP3761587B1 (de) 2019-07-04 2019-07-04 Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk

Country Status (2)

Country Link
US (1) US11212323B2 (de)
EP (1) EP3761587B1 (de)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7610619B2 (en) * 2002-05-22 2009-10-27 Siemens Aktiengesellschaft Method for registering a communication terminal

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9900970D0 (en) * 1999-01-15 1999-03-10 British Telecomm Communications network
US6421674B1 (en) * 2000-02-15 2002-07-16 Nortel Networks Limited Methods and systems for implementing a real-time, distributed, hierarchical database using a proxiable protocol
US20030236860A1 (en) * 2002-06-19 2003-12-25 Yegin Alper E. Link-layer triggers protocol
US20050058068A1 (en) * 2003-07-25 2005-03-17 Racha Ben Ali Refined quality of service mapping for a multimedia session
US7162236B2 (en) * 2004-04-26 2007-01-09 Motorola, Inc. Fast call set-up for multi-mode communication
US7853697B2 (en) * 2005-01-03 2010-12-14 Nokia Corporation Handling suspended network state of a terminal device
US8315247B2 (en) * 2005-07-11 2012-11-20 Cisco Technology Inc. System and method for providing registration-coupled subscriptions in a session initiation protocol (SIP) environment
FR2898003A1 (fr) * 2006-02-28 2007-08-31 France Telecom Procede et systeme de caracterisation de noeuds de communication heterogenes
GB2459841B (en) * 2008-05-02 2012-09-12 Samsung Electronics Co Ltd Reducing occurrence of UE registration expiry during calls
US8159941B2 (en) * 2008-08-28 2012-04-17 Alcatel Lucent In-band DPI media reservation modifications to RFC 3313
US8204228B2 (en) * 2008-12-09 2012-06-19 Cisco Technology, Inc. Group key management re-registration method
WO2010094125A1 (en) * 2009-02-19 2010-08-26 Securekey Technologies Inc. System and methods for online authentication
US8745638B1 (en) * 2010-10-01 2014-06-03 Google Inc. Method and system for distributing object update messages in a distributed network system
US8495186B1 (en) * 2011-01-03 2013-07-23 Sprint Communications Company L.P. Managing termination of point-to-point sessions between electronic devices
US8244244B1 (en) * 2011-08-31 2012-08-14 Renesas Mobile Corporation Method for triggering a user equipment
US9148863B2 (en) * 2012-04-06 2015-09-29 Via Telecom Co., Ltd. Mobile communication devices, service networks, and methods for managing operation of a registration procedure for machine-to-machine (M2M) communications
US9178979B1 (en) * 2014-07-16 2015-11-03 At&T Intellectual Property I, Lp Method and apparatus for initiating communication modes
US9584560B2 (en) * 2014-07-29 2017-02-28 Avaya Inc. Providing external application services with an existing private branch exchange media server
US10523720B2 (en) * 2015-02-27 2019-12-31 Telefonaktiebolaget Lm Ericsson (Publ) P-CSCF recovery and reregistration
US10476978B2 (en) * 2015-09-28 2019-11-12 Facebook, Inc. Providing notifications on online social networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7610619B2 (en) * 2002-05-22 2009-10-27 Siemens Aktiengesellschaft Method for registering a communication terminal

Also Published As

Publication number Publication date
EP3761587A1 (de) 2021-01-06
US11212323B2 (en) 2021-12-28
US20210006602A1 (en) 2021-01-07

Similar Documents

Publication Publication Date Title
Jennings et al. Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Roach SIP-specific event notification
US9143537B2 (en) Device registration in an IMS network
EP1864522B1 (de) Verfahren zur einleitung von ims-basierter kommunikation
EP3142339B1 (de) System und verfahren zur vertrauensbestimmung für sip-nachrichten
US8036659B2 (en) Method for requesting an unregistered UE to perform registration in the IMS
JP5173607B2 (ja) 通信システム
EP2874366B1 (de) Netzübergangseinrichtungsimplementierung einer Instanzenmanagerfunktion
KR100768583B1 (ko) Ｉｍｃ에서의 요청 재지정 처리
EP1902570B1 (de) System und verfahren zum bereitstellen von mit anmeldungen verbundenen subskriptionen in einer umgebung mit sitzungseinleitungsprotokoll
US8625581B2 (en) Methods and apparatus for enhancing the scalability of IMS in VoIP service deployment
US8230074B2 (en) System and method for reducing required memory usage between communication servers
RU2439685C2 (ru) Получение информации из источников информации с помощью запросов refer
US9077722B2 (en) Method and system for controlling the restart traffic in a telecommunication network
EP3761587B1 (de) Verfahren zur infinitätsregistrierung unter verwendung einer sitzungseinleitungsprotokollbasierten kommunikation in einem sitzungseinleitungsprotokollbasierten netzwerk sowie netzwerk
US8630163B1 (en) Server driven endpoint re-homing
EP2202938A1 (de) Schutz gegen Überflutungsangriffe in einem Netzwerk
US8219610B2 (en) Content providing system, monitoring server, and SIP proxy server
Holmberg et al. Push notification with the session initiation protocol (SIP)
Holmberg et al. RFC 8599: Push Notification with the Session Initiation Protocol (SIP)
Roach RFC 6665: SIP-Specific Event Notification
RU2433558C2 (ru) Вычисление критерия начальной фильтрации
Jennings et al. RFC 5626: Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
Notification Internet Engineering Task Force Adam Roach Internet Draft dynamicsoft Category: Standards Track February 2002 Expires August 2002< draft-ietf-sip-events-04. txt

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200330

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210713

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602019021625

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065107300

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 65/1104 20220101ALI20220412BHEP

Ipc: H04L 65/1073 20220101AFI20220412BHEP

INTG Intention to grant announced

Effective date: 20220510

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

RIN1 Information on inventor provided before grant (corrected)

Inventor name: JERBI, WALID

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1531090

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221115

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602019021625

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20221109

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1531090

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230309

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230209

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230309

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230210

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602019021625

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20230810

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230724

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230720

Year of fee payment: 5

Ref country code: DE

Payment date: 20230720

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221109

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230704

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230704

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230731