IP Library Granted Patent US 10,051,014
Granted Patent B2
US 10,051,014 · App. 14/696,138 · Granted Aug 14, 2018

Data processing

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,051,014
App. No.
14/696,138
Granted
Aug 14, 2018
Kind
B2
Abstract

Measures for use in processing data in a telecommunications network. A request message is received in relation to establishment of a communication session involving a given subscriber. Subscriber configuration data is received in relation to the establishment. The subscriber configuration data includes a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber. At least one trigger point from the set of trigger points is encoded into an identifier for the communication session within the request message. The request message including the identifier for the communication session in which the at least one trigger point has been encoded is transmitted.

Claims (80)

1. A method of processing data in a telecommunications network, the method comprising:

at a network routing node, receiving a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receiving subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber;

performing a filtering process on the trigger points in the set to remove one or more trigger points that will not fire;

at the network routing node, evaluating trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the removed one or more trigger points are not involved in the evaluation;

at the network routing node, in response to the evaluation finding at least one trigger point, encoding, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point, wherein the encoding is carried out in response to the evaluation finding the given trigger point; and

at the network routing node, transmitting, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded.

2. The method of claim 1 , wherein the encoding comprises inserting a route header into the transmitted request message.

3. The method of claim 2 , wherein the transmitted request message is routed to an application server at which an application service associated with the at least one trigger point can be invoked in relation to the communication session.

4. The method of claim 2 , wherein the inserted route header comprises a host part set to a network address of a network routing node and a user part comprising the encoded identifier.

5. The method of claim 1 , wherein the encoding comprises inserting a route header into the transmitted request message for each trigger point in the set other than the given trigger point.

6. The method of claim 1 , wherein no route header is inserted in the transmitted request message for the given trigger point.

7. The method of claim 1 , comprising:

in response to transmittal of the request message, receiving a forwarded request message from an application server;

further determining that the received forwarded request message contains an identifier for a communication session in which at least one trigger point has been encoded; and

further evaluating trigger points in the received forwarded request message to further determine whether a further trigger point that fires for the communication session is found.

8. The method of claim 7 , comprising, in response to the further evaluation finding a further trigger point that fires for the communication session, further encoding, into an identifier for the communication session within a further request message, at least one further trigger point from the set of trigger points; and

further transmitting the further request message including the identifier for the communication session in which the at least one further trigger point has been encoded.

9. The method of claim 7 , comprising, in response to the further evaluation finding no further trigger point that fires for the communication session, performing final routing for the received request message.

10. The method of claim 7 , wherein the request message and subscriber configuration data are received at the network routing node, and the encoding and transmitting are performed by the network routing node, the network routing node comprising one of a plurality of network routing nodes responsible for processing routing data relating to communication sessions conducted in the network, and

wherein the forwarded request message is received by a different network routing node in the plurality of network routing nodes and the further determining and the further evaluation are performed by the different network routing node.

11. The method of claim 10 , comprising, in response to the further evaluation finding a further trigger point that fires for the communication session, further encoding, into an identifier for the communication session within a further request message, at least one further trigger point from the set of trigger points; and

further transmitting the further request message including the identifier for the communication session in which the at least one further trigger point has been encoded,

wherein the further encoding and the transmittal of the further request message or the final routing are performed by the different network routing node.

12. The method of claim 1 , comprising,

in response to transmittal of the request message, receiving a forwarded request message from an application server;

determining that the received forwarded request message does not contain an identifier for a communication session in which at least one trigger point has been encoded; and

performing final routing for the received request message.

13. The method of claim 1 , wherein each trigger point in the set has an associated priority, and one or more of the evaluation and the further evaluation are performed on trigger points in order of their associated priorities to determine whether a trigger point that fires for the communication session is found, and/or

wherein the set of trigger points comprises at least one more trigger point other than the given trigger point, and the encoding comprises encoding one or more trigger points in the set other than the given trigger point.

14. The method of claim 1 , wherein the encoding comprises performing a compression encoding, and/or

wherein the set of one or more trigger points comprise initial filter criteria (IFC), and/or

wherein the communication session identifier comprises a SIP dialog identifier, and/or

wherein the communication session identifier comprises an original dialog identifier (ODI) for the communication session.

15. The method of claim 1 , wherein the request message and subscriber configuration data are received at the network routing node, and the encoding and transmitting are performed by the network routing node, the network routing node comprising one of a plurality of network routing nodes responsible for processing routing data relating to communication sessions conducted in the network.

16. The method of claim 1 , wherein the subscriber configuration data is received from a subscriber configuration network node in response to a request transmitted from the network routing node, the subscriber configuration network node comprising a network node responsible for storing subscriber configuration data for a plurality of subscribers.

17. The method of claim 1 , wherein removed one or more trigger points are not included in the transmitted request message, and/or

wherein the removed one or more trigger points comprise one or more of:

trigger points relating to a register message,

trigger points where a profile part indicator does not correspond to a current registration state of the given subscriber, and

trigger points where session case conditions determine that the trigger points will not fire.

18. A method of processing data in a telecommunications network, the method comprising:

at a network routing node, receiving a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receiving subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber;

at the network routing node, evaluating trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the set of trigger points does not comprise any more trigger points other than the given trigger point;

at the network routing node, in response to the evaluation finding at least one trigger point, encoding, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point;

further encoding, into the identifier for the communication session, an indication that processing of the set of trigger points is complete for the communication session;

at the network routing node, transmitting, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded; and

performing final routing for the received request message.

19. A system for use in processing data in a telecommunications network, the system comprising at least one memory including computer program code; and

at least one processor in data communication with the at least one memory, wherein the at least one processor is configured to:

at a network routing node, receive a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receive subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber;

at the network routing node, perform a filtering process on the trigger points in the set to remove one or more trigger points that will not fire;

at the network routing node, evaluate trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the removed one or more trigger points are not involved in the evaluation;

at the network routing node, in response to the evaluation finding at least one trigger point, encode, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point, and wherein the encoding is carried out in response to the evaluation finding the given trigger point; and

at the network routing node, transmit, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded.

20. A computer program product comprising a non-transitory computer-readable storage medium having computer readable instructions stored thereon, the computer readable instructions being executable by a computerized device to cause the computerized device to perform a method of processing data in a telecommunications network, the method comprising:

at a network routing node, receiving a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receiving subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber;

at the network routing node, performing a filtering process on the trigger points in the set to remove one or more trigger points that will not fire;

at the network routing node, evaluating trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the removed one or more trigger points are not involved in the evaluation;

at the network routing node, in response to the evaluation finding at least one trigger point, encoding, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point, and wherein the encoding is carried out in response to the evaluation finding the given trigger point; and

at the network routing node, transmitting, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded.

21. A system for use in processing data in a telecommunications network, the system comprising at least one memory including computer program code; and

at least one processor in data communication with the at least one memory, wherein the at least one processor is configured to:

at a network routing node, receive a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receive subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber;

at the network routing node, evaluate trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the set of trigger points does not comprise any more trigger points other than the given trigger point;

at the network routing node, in response to the evaluation finding at least one trigger point, encode, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point;

at the network routing node, further encode, into the identifier for the communication session, an indication that processing of the set of trigger points is complete for the communication session;

at the network routing node, transmit, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded; and

at the network routing node, perform final routing for the received request message.

22. A computer program product comprising a non-transitory computer-readable storage medium having computer readable instructions stored thereon, the computer readable instructions being executable by a computerized device to cause the computerized device to perform a method of processing data in a telecommunications network, the method comprising:

at a network routing node, receiving a request message in relation to establishment of a communication session involving a given subscriber;

at the network routing node, receiving subscriber configuration data in relation to the establishment, the subscriber configuration data comprising a set of one or more trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber; at the network routing node, evaluating trigger points in the set to determine whether a given trigger point that fires for the communication session is found, wherein the set of trigger points does not comprise any more trigger points other than the given trigger point;

at the network routing node, in response to the evaluation finding at least one trigger point, encoding, into an identifier for the communication session within the request message, data defining the at least one trigger point from the set of trigger points at which one or more application services should be invoked in relation to communication sessions for the given subscriber, wherein the encoded data defines at least one triggering condition for the at least one trigger point;

at the network node, further encoding, into the identifier for the communication session, an indication that processing of the set of trigger points is complete for the communication session;

at the network routing node, transmitting, to an application server, the request message including the identifier for the communication session in which the at least one trigger point has been encoded; and

at the network node, performing final routing for the received request message.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: ALIANZA, INC.
Reel/Frame 075645/0892 →
CHANGE OF NAME Recorded May 13, 2026
From: ALIANZA, INC.
To: ALIANZA, LLC
Reel/Frame 075646/0037 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: METASWITCH NETWORKS LTD.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 075578/0155 →
SECURITY INTEREST Recorded May 6, 2025
From: ALIANZA, INC.; METASWITCH NETWORKS LTD
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 071191/0228 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 9, 2015
From: EVANS, MICHAEL JEFFREY
To: METASWITCH NETWORKS LTD
Reel/Frame 036574/0516 →