US20130311618A1

US20130311618A1 - Method and Apparatus for High Performance Low Latency Real Time Notification Delivery

Info

Publication number: US20130311618A1
Application number: US13/877,559
Authority: US
Inventors: Johannes Ruetschi; Rodrigo Pastro
Original assignee: Siemens Enterprise Communications GmbH and Co KG
Current assignee: RingCentral Inc
Priority date: 2012-05-15
Filing date: 2012-05-15
Publication date: 2013-11-21
Also published as: WO2013172819A1; EP2740250B1; CN103548315A; RU2013117418A; US10567483B2; US20180124161A1; EP2740250A1; BR112013010159A2; CN103548315B; US20160088071A1; RU2608469C2

Abstract

A method for real time notification delivery comprises providing to an application server event notifications directed to a plurality of user agents that are at a site remote from an application server and that receive event notifications through a first network device that is capable of receiving aggregated notification messages, aggregating a plurality of event notifications directed to a plurality of user agents to create an aggregated notification message directed to a first network device, and routing an aggregated notification message to a first network device via a communications network.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention
The present invention relates to network communication systems and, more particularly, to a method and device that enables delivery of large scale real time feature notifications such as notifications for call events, presence, feature status, alarm conditions, or other events from a centralized, hosted, or cloud communications system to users at remote sites or branch offices.
2. Description of the Related Art
Traditionally SIP notifications are delivered via a subscription notification scheme as per RFC 3265, which is hereby incorporated by reference in its entirety. Each subscription is associated with a distinct SIP dialog that is maintained by both notifier and subscriber. As a result, when an event occurs in a centralized application the communication system sends each notification in a distinct SIP NOTIFY message on a distinct SIP dialog to the remote user agents.
This approach leads to several problems. If a communication system is sensitive to low bandwidth between the centralized communication system, the remote notification recipient's notifications are queued and sent sequentially over a data link. This results in notification delivery delay (e.g. time from event occurrence to notification delivery) as well as high inter notification latency (e.g. time between first user agent to receive the notification and last user agent to receive the notification). Low bandwidth scenarios can occur if either bandwidth cannot be allocated, or if a link failure occurs and a secondary low bandwidth backup link is used to connect to a remote site.
Additionally, sending distinct messages may cause network latency. Serialization of a large number of notifications over a high latency data link can cause increased delay for delivery of subsequent notifications. This may also causes inefficient usage of network resources since a large number of similar messages are sent from a centralized application to notification recipients at a remote site. In most usage scenarios only SIP dialog information differs between notifications sent to different user agents for the same event occurrence.
There are no known existing SIP deployments or standardization that provides message aggregation for event notifications. Existing mechanisms acting on individual messages such as Transport Layer Security (“TLS”) compression or Signaling Compression (“SIGCOMP”) do not achieve levels of optimization for bandwidth reduction similar to the present invention and do not address latency optimization. Further, existing mechanisms do not provide satisfactory optimization for large numbers of event notifications.
Thus there is a need for method and apparatus that is able to send aggregated event notifications in a communication network from a first location to user agents at a second remote location.

SUMMARY OF THE INVENTION

A method and apparatus embodying the present invention solves the above problems, minimizes latency of delivery, and minimizes bandwidth requirements by providing automatic discovery of branch proxy capabilities and SIP over SIP aggregation of notifications events between application server and branch proxy. The aggregation enables notifications to be delivered in a single message between application server and branch proxy. A method and apparatus embodying the present invention also provides event content compression and message size optimization and maintains a standard compliant interface towards user agents.
A method for real time notification delivery is disclosed herein. The method comprises providing to an application server event notifications directed to a plurality of user agents that are at a site remote from the application server and receiving event notifications through a first network device that is capable of receiving aggregated notification messages and aggregating a plurality of event notifications directed to the plurality of user agents to create an aggregated notification message directed to the first network device. Each of the plurality of event notifications is associated with a user agent of the plurality of user agents. The method further requires routing the aggregated notification message to the first network device via a communications network.
In another preferred embodiment the method comprises parsing the aggregated notification message into the plurality of event notifications for the plurality of user agents and transmitting each event notification to at least one of the plurality of user agents.
In still another preferred embodiment the method comprises aggregating the plurality of event notifications using a first event notification of the plurality of event notifications to aggregate the remaining plurality of event notifications.
In yet another preferred embodiment the method comprises receiving user agent notification subscriptions and generating the plurality of event notifications based on the received notification subscriptions.
In still another preferred embodiment the method comprises receiving user agent notification subscriptions comprising an identifier for a location of the first network.
In a further preferred embodiment of the method, aggregating the plurality of event notifications comprises packaging all of the plurality of event notifications into a body of the aggregated notification message.
In yet a further preferred embodiment of the method, the aggregated notification message comprises an identifier for a location of the first network device.
In yet another preferred embodiment of the method, aggregating a plurality of event notifications comprises using an index for aggregating each event notification, the index comprising information regarding the user agent to which each event notification is directed and wherein the aggregated notification message does not include the index.
In still a further preferred embodiment of the method, the notification aggregated message further comprises information indicating a number of separate event notifications in the notification aggregated message and an index for each event notification, the index comprising information regarding the user agent to which each event notification is directed.
In another preferred embodiment of the method, the body of the aggregated notification message comprises a compressed text format that includes Session Initiation Protocol (“SIP”) information.
In still another preferred embodiment of the method, routing the aggregated notification message comprises a message aggregator sending the aggregated notification message to a transport function and the transport function transmitting the aggregated notification message to the first network device via a communication network.
In yet another preferred embodiment of the method, routing the aggregated notification message comprises routing the aggregated notification message according to Transport Layer Security (“TLS”) transport protocol.
In a further preferred embodiment the method comprises creating a template for each of the plurality of event notifications, the template comprising notification dialog data contained in each of the event notifications and a list of each type of notification dialog data contained in the event notifications.
In yet a further preferred embodiment the method comprises receiving the notification aggregated message at the first network device and the first network device processing the aggregated notification message according to the plurality of event notifications.
In still a further preferred embodiment the method comprises the first network device sending option messages at a predefined interval to the application server and updating a capability attribute associated with the first network device upon receipt of an option message comprising aggregated notification message capability information.
In another preferred embodiment the method comprises determining whether the first network device associated with the user agents is capable of receiving aggregated notification messages.
In still another preferred embodiment of the method, aggregating the plurality of event notifications comprises the application server sending a first plurality of event notifications to a message aggregator, each of the first plurality of event notifications being associated with a user agent of the plurality of user agents, and the message aggregator receiving the first plurality of event notifications and aggregating the first plurality of event notifications based on the first network device, the aggregated first plurality of event notifications comprising the aggregated notification message.
In yet a further preferred embodiment of the method, aggregating the plurality of event notifications further comprises using an identifier for a location of the first network device such that the aggregated notification message includes the identifier for the first network device.
An apparatus for real time notification delivery is also disclosed herein. The apparatus comprises an application server that is capable of receiving event notifications directed to a plurality of user agents. The user agents are at a site remote from the application server and receive event notifications through a first network device that is capable of receiving aggregated notification messages. Further, the application server aggregates a plurality of event notifications directed to the plurality of user agents to create an aggregated notification message directed to the first network device. Each of the plurality of event notifications being associated with a user agent of the plurality of user agents. Additionally, the application server routes the aggregated notification message to the first network device via a communications network.
In another preferred embodiment of the apparatus, the application server aggregates the plurality of event notifications by packaging all of the plurality of event notifications into a body of the aggregated notification message.
In yet another preferred embodiment of the apparatus, the body of the aggregated notification message comprises a compressed text format that includes Session Initiation Protocol (“SIP”) information.
In still another preferred embodiment of the apparatus, the application server receives user agent notification subscription information and aggregates the plurality of event notifications based on the received notification subscriptions.
In a further preferred embodiment of the apparatus, the first network device is an SIP proxy server.
The present invention is applicable to any large scale, hosted or cloud based communication system where real time events services are provided from centralized applications to one or more remote offices locations. Other details, objects, and advantages of the invention will become apparent as the following description of certain present preferred embodiments thereof and certain present preferred methods of practicing the same proceeds

BRIEF DESCRIPTION OF THE FIGURES

Present preferred devices, systems, and apparatuses for High Performance Low Latency Real Time Notification Delivery are shown in the accompanying drawings and certain present preferred methods of practicing the same are also illustrated therein. It should be understood that like reference numbers used in the drawings may identify like components.

FIG. 1 is a block diagram of a first preferred embodiment of a communication system that includes an apparatus of the present invention.

FIG. 2 is a preferred embodiment of a format of an aggregated notification message used by the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring to FIG. 1, an apparatus for real time notification delivery may include an application server 3 located in a data center 1 that is part of a communication network 4. The application server 3 receives event notifications directed to a plurality of user agents 6. Individual agents are represented by boxes A, B, C, and D. Event notifications may include notifications for call events, presence, feature status, alarm conditions, or other events from a centralized, hosted, or cloud communications system. In addition, the event notifications may include an identifier for a remote site, such as a branch office, to which the event notification is directed, a number of notifications to be sent that remote site, and/or an index for each event notification that enables easy aggregation. Further, more than one event notification may be directed to a single user agent 6. In a preferred embodiment, the user agents 6 may be Session Initiation Protocol (“SIP”) user agents, the event notifications are SIP event notifications, and the user agents 6 and the application server 3 are connected via the first network device 5, which is a survivable branch proxy.
The user agents 6 may comprise software applications or hardware applications such as endpoints or terminals. Further, a user agent 6 may be a mobile communication device such as for example; a mobile phone, a computer, a laptop, a personal digital assistant, a netbook, or a tablet computer device or a user agent may be a non-mobile device, for example, a desktop computer or desktop phone. Embodiments of the application server 3 may include, for example, a computer device configured to host a service to a plurality of different client devices by communicating with the devices.
In a preferred embodiment, user agent notification subscriptions may be received by the data center 1, application server 3, or other network device such that the generation of the plurality of event notifications is based on the received and active notification subscriptions. The user agent notification subscriptions may include an identifier for a location of the first network in which the first network device 5 is located. In another preferred embodiment, the application server 3 may be an SIP server or it may include an SIP application 7. In another preferred embodiment, the first network device 5 is a server device. The server device may include a message queue 10 and a message extractor 12. The server device may be a branch or proxy server or it may include for example an SIP proxy function 11.
The application server 3 may generate the event notifications or it may receive the event notifications from another network device such as a server or gateway. The user agents 6 are located at a site 2 that is remote from the application server 3 and are able to receive event notifications through a first network device 5 that is capable of receiving aggregated notification messages. The capability of the first network device may be determined based on option messages sent by the first network device 5. A capability attribute associated with the first network device may be updated upon receipt of an option message that includes information indicating aggregated notification message capability.
In a preferred embodiment, the option messages may be sent at a predefined interval to the application server 3, data center 1, or other device that relays this information to the data center 1. An option message may be an SIP OPTIONS message and an SIP header of the message may include the proxy state of the first network device 5 and the proxy capability to process packaged notifications. Accordingly, the application server may dynamically update a capability attribute that is used for known proxies upon receipt of an OPTIONS message that includes Notification Aggregation capability. Upon the occurrence of an event the application notifications for all active subscription dialogs may be created and the application server or other device may determine which user agents are registered to a network device that supports notification aggregations based on a look-up table, contact information, or other form of registration information of the user agents.
Further, the application server 3 aggregates a plurality of the event notifications directed to the plurality of user agents to create an aggregated notification message that is directed to the first network device 5. Aggregation of the plurality of event notifications may take place using a first event notification of the plurality of event notifications to aggregate the remaining plurality of event notifications. Furthermore, aggregating the plurality of event notifications may comprise packaging all of the plurality of event notifications into a body of the aggregated notification message.
In addition, an identifier of a location of a network or network device may be used in the aggregation process such that the event notifications to be aggregated include the identifier or otherwise, the identifier is included in the aggregated notification message. This mechanism enables the event notifications to be aggregated based on a particular network or network device. In a situation where there are multiple remote sites that each have a network device, event notifications can be aggregated per each remote site and sent to the network device at that remote site.
In a preferred embodiment, the aggregated notification messages include an identifier for a location or address of the first network device 5 along with information that indicates a number of separate event notifications in the notification aggregated message and an index for each event notification. The index may include information regarding the user agent to which that particular event notification is directed. The index may be used to facilitate aggregation of notification events, but may or may not be sent as part of the aggregated notification message. Further, the body of the aggregated notification message may comprise a compressed text format that includes SIP information.
FIG. 2 illustrates a preferred embodiment of an aggregated notification message containing n notifications and associated dialogs. A content-type may be defined for attached compressed SIP messages. This content type could be defined as application/compressed-multipart. Compressed-multipart may be represented as Gzip compressed text. The compressed text is of a type multipart/mixed for which each part is of the type application/SIP. The result provides that a compressed copy of all notifications can be sent in the body of an initial notification from the centralized application to the remote SIP proxy.
In another preferred embodiment, event notifications may be aggregated to provide optimization for dialog processing. Prior to, during, or after the aggregation process, a template for each of the plurality of event notifications may be created, such that the template comprises notification dialog data contained in each of the event notifications along with a list of each type of notification dialog data contained in the event notifications.
The example code below illustrates how event notifications may be combined using an optimization approach. A message aggregator creates a template for the notification data (application/dialog-info-template). The template contains parameters for dialog related fields. The message aggregator also creates a list for all dialogs (application/dialog-list) on which the notifications have to be sent. Additionally, further optimization can be applied by using compression in order to reduce a message size.


NOTIFY sip:15615551234@10.161.219.26:5060;transport=udp SIP/2.0
To: 28 <sip:15615551234@10.192.129.54>;tag=e51e42326b
From: <sip:*70@10.192.129.54:5060;transport=udp>;tag=SEC11-
683c00a-783c00a-1-2RFA407AbITY
Call-ID: a578e41905e23570
CSeq: 232 NOTIFY
Route: <sip:10.161.219.18;transport=tcp;r2=on;lr;ftag=e51e42326b>
Route: <sip:10.161.219.18;r2=on;lr;ftag=e51e42326b>
Contact:
<sip:*70@10.192.129.54:5060;transport=tcp;maddr=10.192.129.54>
Via: SIP/2.0/UDP 10.192.129.54:5060;branch=z9hG4bKSEC-683c00a-
783c00a-1-Q71wu37911
Max-Forwards: 70
Event: dialog
Subscription-State: active
Content-Type: multipart/mixed;boundary=“12345abcde”
Content-Length:xxxx
--12345abcde
Content-Type: application/dialog-info-template+xml
<?xml version=“1.0”?>
<dialog-info xmlns=“urn:ietf:params:xml:ns:dialog-info”
version=“231”
state=“full”
entity=“sip:10.192.129.54”>
<dialog id=“%%From-Tag%%” call-id=“%%Call-Id%%”
direction=“initiator”>
<state>early</state>
<local>
<identity display=“John
Smith”>sip:30@10.192.129.54</identity>
</local>
<remote>
<identity>sip:814085554680@
10.192.129.54</identity>
</remote>
</dialog>
</dialog-info>
--12345abcde
Content-Type: application/dialog-list
sip:15615551235@10.161.219.25:5060;transport=udp
To: 26 <sip:15615551235@10.192.129.54>;tag=e4f6478938
From-Tag:SEC11-683c00a-783c00a-1-s4Wf5BOon84D
Call-ID: aa59e6591d5120c0
CSeq: 828
sip:15615551236@10.161.219.128:5060;transport=udp
To: 43 <sip:15615551236@10.192.129.54>;tag=5befde7ce1
From-Tag:SEC11-683c00a-783c00a-1-0J118O5P4SDI
Call-ID: cc3ca556601b5eff
CSeq: 2248
sip:15615551237@10.161.219.22:5060;transport=udp
To: 30 <sip:15615551237@10.192.129.54>;tag=b65cbd3d64
From-Tag:SEC11-683c00a-783c00a-1-zPUJc2zjNZZh
Call-ID: 012487c843ed6444
CSeq: 842
--12345abcde

In another preferred embodiment, the plurality of event notifications may be aggregated by a message aggregator 8. The message aggregator 8 may be a hardware or software application, which may be a component of the application server 3 or a separate device. Each of the plurality of event notifications is associated with a user agent of the plurality of user agents 6. Aggregating the plurality of event notifications may comprise the application server 3 sending a first plurality of event notifications to a message aggregator 8 such that each of the first plurality of event notifications is associated with a user agent of the plurality of user agents 6. The message aggregator receives the first plurality of event notifications and aggregates the first plurality of event notifications based on the first network device. The aggregated first plurality of event notifications comprises an aggregated notification message.
Further, the application server 3 routes the aggregated notification message to the first network device 5 via the communications network 4. In another preferred embodiment, a message aggregator 8 routes the aggregated notification message by sending the aggregated notification message to a transport function 9 and the transport function 9 transmits the aggregated notification message to the first network device 5 via a communication network 4. The aggregated notification message may preferably be routed through the communication network 4 according to Transport Layer Security (“TLS”) protocol.
The first network device 5 receives the notification aggregated message and processes the aggregated notification message according to the plurality of event notifications. This may include the first network device 5 parsing the aggregated notification message into the plurality of event notifications for the plurality of user agents and initiate transmission of each event notification to at least one of the plurality of user agents.
In another embodiment, the SIP proxy function 11 may process messages from the message queue 10 by reading a notification from the queue that contains aggregated event notifications in its body. The SIP proxy function 11 removes the aggregated notifications from the body and passes them to a message extractor 12. The message extractor 12 receives the packaged notifications and rebuilds the SIP messages either by extracting them directly from the received message body or by rebuilding them based on a dialog list that was produced during aggregation. Once extracted, the notifications are placed in the message queue 10 for normal SIP processing.
The present invention also comprises a method for real time notification delivery. The method may be embodied in a non-transitory computer readable medium. Embodiments of the non-transitory computer readable medium may be, for example, memory of a computer device, such as a communication device or communication terminal, a flash drive, memory of a server, flash memory, a compact disc, an optical disc storage media, or a DVD. The medium may have an application stored thereon that defines instructions that are executable by a processor of a network device. The instructions may define the method that includes the steps of providing to an application server event notifications directed to a plurality of user agents that are at a site remote from the application server and that receive event notifications through a first network device that is capable of receiving aggregated notification messages.
The method further requires aggregating a plurality of event notifications directed to a plurality of user agents to create an aggregated notification message directed to a first network device, each of the event notifications are associated with a user agent of the plurality of user agents, and the method also requires routing an aggregated notification message to a first network device via a communications network.
The present invention optimizes bandwidth usage and latency for the delivery of notifications from a centralized, hosted, or cloud based communication system to recipients at a remote site or branch locations. The present invention minimizes delay of notification delivery caused by data link latency or data link bandwidth restrictions. The present invention also minimizes inter-notification latency and guarantees quasi-simultaneous delivery of notifications to user agents at remote sites even if data links to the remote sites have limited bandwidth or high latency.
While certain present preferred embodiments of apparatuses for High Performance Low Latency Real Time Notification Delivery and methods of making and using the same have been shown and described above, it is to be distinctly understood that the invention is not limited thereto but may be otherwise variously embodied and practiced within the scope of the following claims.

Claims

We claim:

1. A method for real time notification delivery comprising:

providing to an application server event notifications directed to a plurality of user agents, the user agents being at a site remote from the application server and receiving event notifications through a first network device that is capable of receiving aggregated notification messages;

aggregating a plurality of event notifications directed to the plurality of user agents to create an aggregated notification message directed to the first network device, each of the plurality of event notifications being associated with a user agent of the plurality of user agents; and

routing the aggregated notification message to the first network device via a communications network.

2. The method of claim 1 further comprising parsing the aggregated notification message into the plurality of event notifications for the plurality of user agents and transmitting each event notification to at least one of the plurality of user agents.

3. The method of claim 1 further comprising aggregating the plurality of event notifications using a first event notification of the plurality of event notifications to aggregate the remaining plurality of event notifications.

4. The method of claim 3 wherein aggregating the plurality of event notifications further comprises using an identifier for a location of the first network device such that the aggregated notification message includes the identifier for the first network device.

5. The method of claim 1 further comprising receiving user agent notification subscriptions comprising an identifier for a location of the first network device.

6. The method of claim 1 further comprising receiving user agent notification subscriptions and generating the plurality of event notifications based on the received notification subscriptions.

7. The method of claim 6 wherein the aggregated notification message comprises an identifier for a location of the first network device.

8. The method of claim 7 wherein aggregating a plurality of event notifications comprises using an index for aggregating each event notification, the index comprising information regarding the user agent to which each event notification is directed and wherein the aggregated notification message does not include the index.

9. The method of claim 1 wherein aggregating the plurality of event notifications comprises packaging all of the plurality of event notifications into a body of the aggregated notification message.

10. The method of claim 9 wherein the body of the aggregated notification message comprises a compressed text format that includes Session Initiation Protocol (“SIP”) information.

11. The method of claim 1 wherein routing the aggregated notification message comprises a message aggregator sending the aggregated notification message to a transport function and the transport function transmitting the aggregated notification message to the first network device via a communication network.

12. The method of claim 1 wherein routing the aggregated notification message comprises routing the aggregated notification message according to Transport Layer Security (“TLS”) transport protocol.

13. The method of claim 1 further comprising creating a template for each of the plurality of event notifications, the template comprising notification dialog data contained in each of the event notifications and a list of each type of notification dialog data contained in the event notifications.

14. The method of claim 1 further comprising receiving the notification aggregated message at the first network device and the first network device processing the aggregated notification message according to the plurality of event notifications.

15. The method of claim 1 further comprising the first network device sending option messages at a predefined interval to the application server and updating a capability attribute associated with the first network device upon receipt of an option message comprising aggregated notification message capability information.

16. The method of claim 1 further comprising determining whether the first network device associated with the user agents is capable of receiving aggregated notification messages.

17. The method of claim 1 wherein aggregating the plurality of event notifications comprises the application server sending a first plurality of event notifications to a message aggregator, each of the first plurality of event notifications being associated with a user agent of the plurality of user agents, and the message aggregator receiving the first plurality of event notifications and aggregating the first plurality of event notifications based on the first network device, the aggregated first plurality of event notifications comprising the aggregated notification message.

18. The method of claim 17 wherein aggregating the plurality of event notifications further comprises using an identifier for a location of the first network device such that the aggregated notification message includes the identifier for the first network device.

19. An apparatus for real time notification delivery comprising:

an application server; and

the application server being capable of receiving event notifications directed to a plurality of user agents, the user agents being at a site remote from the application server and receiving event notifications through a first network device that is capable of receiving aggregated notification messages;

the application server aggregating a plurality of event notifications directed to the plurality of user agents to create an aggregated notification message directed to the first network device, each of the plurality of event notifications being associated with a user agent of the plurality of user agents; and

the application server routing the aggregated notification message to the first network device via a communications network.

20. The apparatus of claim 19 wherein the application server aggregates the plurality of event notifications by packaging all of the plurality of event notifications into a body of the aggregated notification message.

21. The apparatus of claim 20 wherein the body of the aggregated notification message comprises a compressed text format that includes Session Initiation Protocol (“SIP”) information.

22. The apparatus of claim 19 wherein the application server receives user agent notification subscription information and aggregates the plurality of event notifications based on the received notification subscriptions.

23. The apparatus of claim 19 wherein the first network device is an SIP proxy server.