# US 2010/0142372 A1 · Method And Apparatus For Use In A Communications Network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0142372 A1
- Document ID: US20100142372A1
- Status: Published application
- Kind: A1
- Application number: 12/593,906
- Filed: 2007-03-29
- Published: 2010-06-10
- Earliest claimed: 2007-03-29
- Inventors: Christer Boberg; Anders Lindgren; Hans Lindgren; Jan Holm; Henrik Albertsson
- Web page: https://patentgrep.com/patent/US20100142372A1

## CPC

- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method is disclosed for use in a Universal Mobile Telecommunications System network comprising an IP Multimedia Subsystem. The method comprises receiving node status information relating to a first node of the network which indicates an occurrence of an event associated with the first node, determining the existence of a network association established between the first node and a second node of the network that would be adversely affected by the occurrence of the event, and causing the network association to be terminated, thereby allowing a new network association between the first and second nodes to be established in its place.

## Claims

### Claim 1

A method for use in a Universal Mobile Telecommunications System network comprising an IP Multimedia Subsystem, the method comprising
receiving node status information relating to a first node of the network which indicates an occurrence of an event associated with the first node,
determining the existence of a network association established between the first node and a second node of the network that would be adversely affected by the occurrence of the event, and
causing the network association to be terminated, thereby allowing a new network association between the first and second nodes to be established in its place.

### Claim 2 (depends on 1)

The method as claimed in claim 1, comprising sending a message to the second node which indicates that the association is to be terminated.

### Claim 3 (depends on 1)

The method as claimed in claim 1, wherein the determination is made at least partly by the second node.

### Claim 4 (depends on 3)

The method as claimed in claim 3, comprising:
sending a message to the second node comprising information relating to the first node, and
using the first node information at the second node to determine the existence of a network association between the first and second nodes that would be affected by the occurrence of the event.

### Claim 5 (depends on 4)

The method as claimed in claim 4, wherein the message is a SIP Multicast message, such as a SIP MESSAGE Request, sent to the second and other nodes of the network.

### Claim 6 (depends on 4)

The method as claimed in claim 4, wherein the first node information comprises contact information for the first node.

### Claim 7 (depends on 4)

The method as claimed in claim 4, comprising using a contact header of the message at least in part to make the determination.

### Claim 8 (depends on 4)

The method as claimed in claim 4, wherein the first node information comprises the SIP Uniform Resource Identifier, URI, of the first node.

### Claim 9 (depends on 1)

The method as claimed in claim 1, comprising causing a timing of the re-establishment of the network association between the first and second nodes to be determined at least partly on a random basis, thereby easing system load where a number of network associations relating to other nodes of the network are being reestablished with the first node in view of the event occurrence.

### Claim 10 (depends on 9)

The method as claimed in claim 9, comprising sending a time window to the second node, and causing at least the starting of the re-establishment within the time window.

### Claim 11 (depends on 1)

The method as claimed in claim 1, wherein the event is one that causes at least partial loss of information required to maintain the network association.

### Claim 12 (depends on 1)

The method as claimed in claim 1, wherein the event relates to at least a partial failure of the second node.

### Claim 13 (depends on 1)

The method as claimed in claim 1, wherein the event relates to an at least partial unavailability of the second node.

### Claim 14 (depends on 1)

The method as claimed in claim 1, wherein the event relates to the restarting of the second node.

### Claim 15 (depends on 2)

The method as claimed in claim 2, wherein the network association comprises a communication session between the first and second node.

### Claim 16 (depends on 15)

The method as claimed in claim 15, wherein the message is a SIP BYE message.

### Claim 17 (depends on 2)

The method as claimed in claim 2, wherein the network association comprises a subscription between the first and second node.

### Claim 18 (depends on 17)

The method as claimed in claim 17, wherein the message is a final SIP NOTIFY message.

### Claim 19 (depends on 1)

The method as claimed in claim 1, wherein the network association comprises a Security Association between the first and second node.

### Claim 20 (depends on 1)

The method as claimed in claim 1, wherein the network association comprises a PDP context between the first and second node

### Claim 21 (depends on 1)

The method as claimed in claim 1, comprising making the determination with reference to route information.

### Claim 22 (depends on 1)

The method as claimed in claim 1, comprising making the determination on the basis of information stored locally at the node performing the method.

### Claim 23 (depends on 1)

The method as claimed in claim 1, wherein the first node comprises an Application Server.

### Claim 24 (depends on 1)

The method as claimed in claim 1, wherein the first node comprises a Serving Call Session Control Function.

### Claim 25 (depends on 1)

The method as claimed in claim 1, wherein the method is performed at a Proxy Call Session Control Function.

### Claim 26 (depends on 1)

The method as claimed in claim 1, wherein the first node comprises a Proxy Call Session Control Function.

### Claim 27 (depends on 26)

The method as claimed in claim 26, wherein the method is performed at a Gateway GPRS Support Node.

### Claim 28 (depends on 1)

The method as claimed in claim 1, wherein the method is performed at the second node.

### Claim 29 (depends on 1)

The method as claimed in claim 1, wherein the node status information is received in a Session Initiation Protocol, SIP, Request.

### Claim 30 (depends on 29)

The method as claimed in claim 29, wherein the SIP Request comprises a Request Uniform Resource Identifier, or Request-URI, which identifies the SIP Request as comprising node status information and/or which identifies the intended recipients of the node status information.

### Claim 31 (depends on 30)

The method as claimed in claim 30, comprising determining the intended recipients from the received Request URI.

### Claim 32 (depends on 31)

The method as claimed in claim 31, comprising forwarding the status information to the determined recipients.

### Claim 33 (depends on 31)

The method as claimed in claim 31, comprising using the status information at the receiving node when the receiving node is determined to be one of the intended recipients.

### Claim 34 (depends on 31)

The method as claimed in claim 31, comprising referring to an Initial Filter Criteria associated with the Request URI to determine the intended recipients.

### Claim 35 (depends on 31)

The method as claimed in claim 31, comprising referring to a Dynamic Name Server to determine the intended recipients from the Request URI.

### Claim 36 (depends on 31)

The method as claimed in claim 31, comprising determining the intended recipients in dependence upon a previously-received SIP SUBSCRIBE Request.

### Claim 37 (depends on 29)

The method as claimed in claim 29, wherein the SIP Request is a SIP PUBLISH Request.

### Claim 38 (depends on 37)

The method as claimed in claim 37, comprising using the time to live information from the SIP PUBLISH Request to infer further information about the node status.

### Claim 39 (depends on 29)

The method as claimed in claim 29, wherein the SIP Request is a SIP MESSAGE Request.

### Claim 40 (depends on 29)

The method as claimed in claim 29, comprising storing the node status relating to those nodes identified by the SIP Request URI.

### Claim 41

An apparatus for use in a Universal Mobile Telecommunications System network comprising an IP Multimedia Subsystem, the apparatus comprising
means for receiving node status information relating to a first node of the network which indicates an occurrence of an event associated with the first node,
means for determining the existence of a network association established between the first node and a second node of the network that would be adversely affected by the occurrence of the event, and
means for causing the network association to be terminated, thereby allowing a new network association between the first and second nodes to be established in its place.

### Claim at position 42

42-48. (canceled)
