Method of monitoring calls in an internet protocol (IP)-based network

• US 6,839,323 B1
• Filed: 05/15/2000
• Issued: 01/04/2005
• Est. Priority Date: 05/15/2000
• Status: Expired due to Fees

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Foti, George
• Primary Examiner(s): Duong, Frank
• Assistant Examiner(s): Jagannathan, Melanie
• Application Number:
  US09/570,997
• Time in Patent Office: 1,695 Days
• Field of Search: 370/235, 370352-356, 370/389, 370/392, 370/401, 370/400, 370/420, 370/466, 370/468, 379/7
• US Class Current: 370/235
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/026 using flow identification
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 63/30 for supporting lawful interception, monitoring or retaining of communications or communication related information circuit switched telephony call monitoring H04M3/2281
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04M 3/2281 Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 74/00 Wireless channel access
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation

Abstract

A method of monitoring a call with a mobile terminal (MT) in an Internet Protocol (IP)-based network having a Gatekeeper that controls the network, a plurality of access routers that provide access to the network, and a Monitoring Station having monitoring facilities and a database of MTs to be monitored. When the MT sends an Admission Request message to the Gatekeeper, the Gatekeeper sends a query to the Monitoring Station asking whether the MT is to be monitored. The Monitoring Station sends a reply to the Gatekeeper indicating that the MT is to be monitored and providing an IP address where monitored packets are to be sent. The Gatekeeper then sends a monitoring request message to the access router associated with the MT. The request identifies the MT to be monitored, instructs the access router to monitor the MT, and provides a unique call identification (Call ID) and the IP address where monitored packets are to be sent. When the access router detects a packet associated with the MT, the router sends all packets associated with the MT to the Monitoring Station. The method also controls monitoring during intra-domain and inter-domain handoffs of the MT.

Claims

1. A method of monitoring a call with an Internet Protocol (IP) client in an IP-based network having a Gatekeeper that controls the network, a plurality of access routers that provide access to the network, and a Monitoring Station having monitoring facilities and a database of IP clients to be monitored, said method comprising:

receiving an access request from the IP client at the Gatekeeper;

sending a query from the Gatekeeper to the Monitoring Station asking whether the IP client is to be monitored;

receiving a reply sent from the Monitoring Station at the Gatekeeper indicating that the IP client is to be monitored and providing an IP address where monitored packets are to be sent; and

sending a monitoring request from the Gatekeeper to an access router associated with the IP client, said request identifying the IP client to be monitored, instructing the access router to monitor the IP client, and providing the IP address where monitored packets are to be sent;

receiving an acknowledgment message from the access router at the Gatekeeper; and

sending an admission confirm message from the Gatekeeper to the IP client when the acknowledgment message has been received from the access router.

2. The method of monitoring a call with an IP client in an IP-based network of claim 1 further comprising, before the step of sending a query from the Gatekeeper to the Monitoring Station asking whether the IP client is to be monitored, the step of performing bandwidth allocation functions by the Gatekeeper to determine whether network access can be granted to the IP client.

3. The method of monitoring a call with an IP client in, an IP-based network of claim 2 further comprising, after the step of receiving a reply from the Monitoring Station at the Gatekeeper indicating that the IP client is to be monitored, the step of setting a flag in the Gatekeeper identifying the IP client as a monitored, IP client.

4. The method of monitoring a call with an IP client in an IP-based network of claim 1, the method further comprising the steps of:

detecting by the access router, a packet associated with the IP client; and

routing by the access router, all packets associated with the IP client to the Monitoring Station.

5. The method of monitoring a call with an IP client in an IP-based network of claim 4 wherein the step of detecting a packet associated with the IP client includes detecting a packet that has an address of the IP client as one address selected from the group of addresses consisting of a source address of the IP client and its a destination address of the IP client.

6. The method of monitoring a call with an IP client in an IP-based network of claim 3 further comprising the steps of:

sending a de-admission request from the IP client to the Gatekeeper;

clearing the flag in the Gatekeeper that identifies the IP client as a monitored IP client;

sending a message from the Gatekeeper to the Monitoring Station to stop the monitoring of the call; and

sending a message from the Gatekeeper to the access router to stop the routing of packets to the Monitoring Station.

7. The method of monitoring a call with an IP client in an IP-based network of claim 1 wherein the IP client is a mobile terminal (MT), and the method further comprises the steps of:

handing off the MT from a first base station to a second base station, each of said base stations being controlled by a single radio network controller (RNC);

sending a monitoring request from the RNC to the second base station, said request identifying the MT to be monitored, instructing the second base station to monitor the MT, and providing a unique call identification (Call ID) and the IP address where monitored packets are to be sent; and

sending a notification from the RNC to the Gatekeeper that the MT is being served by the second base station, said notification including the unique Call ID and a new transport address for the MT.

8. The method of monitoring a call with an IP client in an IP-based network of claim 7 further comprising sending the Call ID and the new transport address from the Gatekeeper to the Monitoring Station.

9. The method of monitoring a call with an IP client in an IP-based network of claim 1 wherein the IP client is a mobile terminal (MI), and the method further comprises the steps of:

handing off the MT from a first base station to a second base station, the first base station being controlled by a first radio network controller (RNC), and the second base station being controlled by a second RNC, and both RNCs being in a single Gatekeeper domain;

sending identifying information regarding the MT being monitored from the first RNC to the second RNC, said information including a unique call identification (Call ID);

sending a monitoring request from the second RNC to the second base station, said request identifying the MT to be monitored, instructing the second base station to monitor the MT, and providing the unique Call ID and the IP address where monitored packets are to be sent;

sending a notification from the second RNC to the Gatekeeper that the MT is being served by the second base station, said notification including the unique Call ID and a new transport address for the MT; and

sending the Call ID and the new transport address from the Gatekeeper to the Monitoring Station.

10. The method of monitoring a call with an IP client in an IP-based network of claim 4 wherein the step of detecting a packet associated with the IP client includes detecting a media having the IP client address as either a source address or destination address.

11. The method of monitoring a call with an IP client of claim 10 wherein the step of routing all packets associated with the IP client to the Monitoring Station includes encapsulating each packet associated with the IP client with a new header that includes the router'"'"'s address as a source address, and the Monitoring Station'"'"'s address as a destination address.

12. A method of handing off a monitored mobile terminal (MT) in an Internet Protocol (IP)-based network, said method comprising:

handing off the MT from a first base station to a second base station, the first base station being controlled by a first radio network controller (RNC) in a first Gatekeeper domain, and the second base station being controlled by a second RNC in a second Gatekeeper domain,

sending a notification from the first RNC to the second RNC that the MT is being monitored, said notification including a unique call identification (Call ID) and an IP address of a Monitoring Station where monitored packets are to be sent;

sending a monitoring request from the second RNC to the second base station, said request identifying the MT to be monitored, instructing the base station to monitor the MT, and providing the Call ID and the IP address of the Monitoring Station;

sending by the second base station, media packets having the MT address as a source address or destination address to the Monitoring Station;

sending the unique Call ID and a new transport address for the MT from the second RNC to the second Gatekeeper;

sending the unique Call ID and the new transport address for the MT from the second Gatekeeper to the Monitoring Station;

sending an access request from the MT to the second Gatekeeper; and

allocating bandwidth to the MT by the Gatekeeper.

13. The method of handing off a monitored MT in an IP-based network of claim 12 further comprising, after the step of sending a unique Call ID and a new transport address for the MT from the second RNC to the second Gatekeeper and to the Monitoring Station, the steps of:

setting a flag in the second Gatekeeper indicating that a monitored MT is in the second Gatekeeper'"'"'s area, and that the MT will soon register with the second Gatekeeper; and

starting a registration timer in the second Gatekeeper.

14. The method of handing off a monitored MT in an IP-based network of claim 13 further comprising the steps of:

sending a de-admission request from the monitored MT to the second Gatekeeper, clearing the flag in the second Gatekeeper that identifies the MT as a monitored MT;

sending a message from the second Gatekeeper to the Monitoring Station to stop the monitoring of the call; and

sending a message from the second Gatekeeper to the second base station to stop the routing of packets to the Monitoring Station.

15. The method of handing off a monitored MT in an IP-based network of claim 12 further comprising, after the step of sending an access request from the MT to the second Gatekeeper, the step of stopping the registration timer.

16. The method of handing off a monitored MT in an IP-based network of claim 12 wherein the step of sending media packets having the MT address as a source address or destination address to the Monitoring Station includes encapsulating each packet associated with the MT with a new header that includes the second base station'"'"'s address as a source address, and the Monitoring Station'"'"'s address as a destination address.

17. A method of monitoring a call with a mobile terminal (MT) and routing the monitored call to a Monitoring Station having monitoring facilities and a database of MTs to be monitored, said method being performed within a Gatekeeper in an Internet Protocol (IP)-based network, and comprising the steps of:

receiving in the Gatekeeper, a network access request from the MT;

sending a query from the Gatekeeper to the Monitoring Station asking whether the MT is to be monitored;

receiving in the Gatekeeper, a reply from the Monitoring Station indicating that the MT is to be monitored and providing an IP address where monitored packets are to be sent; and

sending a monitoring request from the Gatekeeper to an access router providing the MT with access to the network, said request identifying the MT to be monitored, instructing the access router to send any packets associated with the MT to the Monitoring Station, and providing a unique call identification (Call ID) and the IP address where monitored packets are to be sent.

18. A Gatekeeper acting to send a query to a Monitoring Station asking whether an IP client is to be monitored in response to a receipt of an access request from the IP client, wherein the Gatekeeper receives a reply from the Monitoring Station indicating that the IP client is to be monitored and providing an Up address where monitored packets are to be sent, the Gatekeeper further acting to send a monitoring request to an access router associated with the IP client, said request identifying the IP client to be monitored, instructing the access router to monitor the IP client, and providing the IP address where monitored packets are to be sent, the Gatekeeper further receives an acknowledgment message from the access router, sends an admission confirm message to the IP client when the acknowledgment message has been received from the access router.

19. The Gatekeeper of claim 18, wherein the Gatekeeper further performs bandwidth allocation functions to determine whether network access can be granted to the IP client.

20. The Gatekeeper of claim 19, wherein the Gatekeeper further sets a flag for identifying the IP client as a monitored IP client.

21. The Gatekeeper of claim 18, wherein the Gatekeeper further detects a packet that has the IP client as its source address.

22. The Gatekeeper of claim 18, wherein the Gatekeeper further detects a packet that has the IP client as its destination address.

23. The Gatekeeper of claim of claim 20, wherein the Gatekeeper further receives a de-admission request from the IP client, clears the flag that identifies the IP client as a monitored IP client, sends a message to the Monitoring Station to stop the monitoring of the call and sends a message to the access router to stop the routing of packets to the Monitoring Station.

24. The Gatekeeper of claim 18, wherein the Gatekeeper further sends a unique call identification (Call ID) and a new transport address to the Monitoring Station.