System, method and apparatus for supporting E911 emergency services in a data communications network

• US 7,027,564 B2
• Filed: 09/22/2003
• Issued: 04/11/2006
• Est. Priority Date: 09/22/2003
• Status: Expired due to Term

• Current Assignee: ARRIS Enterprises LLC (CommScope Holding Company, Inc.)
• Original Assignee: Foundry Networks Incorporated (Broadcom, Inc.)
• Inventors: James, Anthony W.
• Primary Examiner(s): Ramakrishnaiah, Melur
• Application Number:
  US10/665,628
• Publication Number:
  US 20050063519A1
• Time in Patent Office: 932 Days
• Field of Search: 379 37- 51, 379/93.25, 379/93.02, 340/531, 340/3.1, 340/506, 340/532, 455/404.2, 455/457, 707200-203, 370/352, 370/93.03
• US Class Current: 379/37
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/42059 Making use of the calling party identifier
• CPC Class Codes: H04M 3/42348 Location-based services which utilize the location information of a target
• CPC Class Codes: H04M 3/4931 Directory assistance systems
• CPC Class Codes: H04M 3/5116 for emergency applications
• 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 2213/13034 A/D conversion, code compression/expansion
• CPC Class Codes: H04Q 2213/1337 Operator, emergency services
• CPC Class Codes: H04Q 2213/13389 LAN, internet
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking
• CPC Class Codes: H04Q 3/72 Finding out and indicating number of calling subscriber

Abstract

A system, method and apparatus for supporting enhanced 911 (E911) emergency services, in a data communications network that includes Voice over Internet Protocol (VoIP) telephones. A network system includes a host network communicatively coupled to an E911 database management system, a network access device, and a VoIP telephone communicatively coupled to an input port of the network access device. The network access device is adapted to assign a physical location identifier to an input port, to authenticate the VoIP telephone, wherein the authentication includes receiving a unique device identifier from the VoIP telephone, and to transmit the location identifier and the unique device identifier to the E911 database management system. The E911 database management system is permitted to store the physical location identifier in association with the unique device identifier.

Claims

1. A method of supporting enhanced 911 (E911) emergency services in a network access device, comprising:

(a) assigning a physical location identifier to an input port of the network access device;

(b) transmitting an automatic report to an E911 database management system (DBMS) when a user device is coupled to said input port;

(c) transmitting a unique device identifier of said user device to said E911 DBMS in response to a first query from said E911 DBMS; and

(d) if said user device is a VoIP telephone, then transmitting said physical location identifier to said E911 DBMS in response to a second query from said E911 DBMS;

whereby said E911 DBMS updates an automatic location identification database with said physical location identifier of said VoIP telephone.

2. The method of claim 1, wherein step (a) includes assigning a physical location identifier to said input port that corresponds to a physical location of a termination point of said input port.

3. The method of claim 1, wherein step (b) includes transmitting a Simple Network Management Protocol (SNMP) trap that has a destination address corresponding to said E911 DBMS when said user devise is coupled to said input port.

4. The method of claim 2, wherein step (b) includes transmitting said SNMP trap via a local Public Service Answering Point (PSAP).

5. The method of claim 1, wherein step (c) includes transmitting a Media Access Control (MAC) address in response to a first SNMP read command from said E911 DBMS, whereby said E911 DBMS determines whether said user device is a VoIP telephone.

6. The method of claim 1, wherein step (d) includes transmitting said physical location identifier in response to a second SNMP read command from said E911 DBMS.

7. A network access device that supports enhanced 911 (E911) emergency services, comprising:

an input port;

a switching fabric for routing data received via said input port to at least one output port; and

control logic adapted to

assign a physical location identifier to said input port,

transmit an automatic report to an E911 database management system (DBMS) when a user device is coupled to said input port,

transmit a unique device identifier to said E911 DBMS in response to a first query from said E911 DBMS, whereby said E911 DBMS determines whether said user device is a VoIP telephone, and

if said user device is a VoIP telephone, transmit said physical location identifier to said E911 DBMS in response to a second query from said E911 DBMS, thereby permitting said E911 database management system to store said physical location identifier in association with said unique device identifier.

8. The device of claim 7, wherein said physical location identifier corresponds to a physical location of a termination point of said input port.

9. The device of claim 7, wherein said automatic report is a Simple Network Management Protocol (SNMP) trap that has a destination address corresponding to said E911 DBMS.

10. The device of claim 9, wherein said SNMP trap is transmitted via a local Public Service Answering Point (PSAP).

11. The device of claim 7, wherein said unique device identifier is a Media Access Control (MAC) address.

12. The device of claim 7, wherein said first and second queries are SNMP read commands from said E911 DBMS.

13. A network system for supporting enhanced 911 (E911) emergency services, comprising:

a host network communicatively coupled to an E911 database management system (DBMS);

a network access device communicatively coupled to said host network; and

a user device communicatively coupled to an input port of said network access device;

wherein said network access device is adapted to assign a physical location identifier to said input port, to automatically transmit a report to said E911 DBMS when said user device is coupled to said input port, to transmit a unique device identifier to said E911 DBMS in response to a first query from said E911 DBMS, and, if said user device is a VoIP telephone, to transmit said physical location identifier to said E911 DBMS in response to a second query from said E911 DBMS;

thereby permitting said E911 database management system to store said physical location identifier in association with said unique device identifier.

14. The system of claim 13, wherein said physical location identifier corresponds to a physical location of a termination point of said input port.

15. The system of claim 13, wherein said automatically transmitted report is a Simple Network Management Protocol (SNMP) trap that has a destination address corresponding to said E911 DBMS.

16. The system of claim 15, wherein said SNMP trap is transmitted via a local Public Service Answering Point (PSAP).

17. The system of claim 13, wherein said unique device identifier is a Media Access Control (MAC) address.

18. The system of claim 13, wherein said first and second queries are SNMP read commands from said E911 DBMS.

19. A method of supporting enhanced 911 (E911) emergency services in a network access device, comprising:

(a) assigning a physical location identifier to an input port of the network access device;

(b) transmitting an automatic report to an E911 database management system (DBMS) when a user device is coupled to said input port;

(c) transmitting a unique device identifier of said user device to said E911 DBMS in response to a first query from said E911 DBMS; and

(d) if said user device is a VoIP telephone, then transmitting said physical location identifier to said E911 DBMS in response to a second query from said E911 DBMS.

20. The method of claim 19, wherein step (a) includes assigning a physical location identifier to said input port that corresponds to a physical location of a termination point of said input port.

21. The method of claim 19, wherein step (b) includes transmitting a Simple Network Management Protocol (SNMP) trap that has a destination address corresponding to said E911 DBMS when said user device is coupled to said input port.

22. The method of claim 21, wherein step (b) includes transmitting said SNMP trap via a local Public Service Answering Point (PSAP).

23. The method of claim 19, wherein step (c) includes transmitting a Media Access Control (MAC) address in response to a first SNMP read command from said E911 DBMS, whereby said E911 DBMS determines whether said user device is a VoIP telephone.

24. The method of claim 19, wherein step (d) includes transmitting said physical location identifier in response to a second SNMP read command from said E911 DBMS.