Caller number identification

• US 10,110,732 B2
• Filed: 10/22/2015
• Issued: 10/23/2018
• Est. Priority Date: 10/22/2015
• Status: Active Grant

• Current Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Original Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Inventors: Hou, Jiongkuan, Mason, Jr., Gerald A., Mozingo, Dale Devert
• Primary Examiner(s): Kamara, Mohamed
• Application Number:
  US14/920,153
• Publication Number:
  US 20170118329A1
• Time in Patent Office: 1,097 Days
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 3/42042 Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42153 by subscriber

Abstract

Methods and apparatus for improving caller identification in telecommunications services based on general-purpose networks are described. A gateway device may process invitation messages sent from a telephone via a private branch exchange, in which the private branch exchange has replaced the number of the telephone with a customized number. The gateway device may determine that the customized number is mapped to an account-related number, and insert that number into a field of the invitation messages that is examined by a telecommunications provider and associated trunking services for account-related purposes.

Claims

1. A method comprising:

receiving a first message indicative of a request to establish a communication session, wherein the first message comprises a first portion comprising a first identifier associated with an identity of an initiator, of the communication session, that is presentable to a recipient of the communication session;

determining, based at least in part on information indicative of a mapping between the first identifier and a second identifier, that the initiator is associated with an account associated with the second identifier;

generating, based on the first message, a second message that comprises the first portion comprising the first identifier and a second portion comprising the second identifier, wherein the second portion is configured to be accessed prior to the first portion in an account identification process; and

transmitting the second message to facilitate establishment of the communication session.

2. The method of claim 1, wherein the first identifier is added to the first message by a private branch exchange.

3. The method of claim 1, wherein the first portion is at least one of a “

p-asserted-identity”

field or a “

from”

field and the second portion is a “

diversion”

field.

4. The method of claim 3, wherein the generating the second message comprises adding the “

diversion”

field to the first message upon determining that the first identifier is mapped to the second identifier.

5. A method comprising:

receiving a first message indicative of a request to establish a communication session, wherein the first message comprises a first identifier;

retrieving a record indicative of the first identifier being mapped to a second identifier;

generating, based on the record, a second message that comprises the first identifier and the second identifier, wherein an account associated with an origin of the request to establish the communication session is identified based on the second identifier; and

transmitting the second message to facilitate establishment of the communication session.

6. The method of claim 5, further comprising:

processing a header manipulation rule comprising instructions to add a “

diversion”

field to the second message based on the record indicative of the first identifier being mapped to the second identifier.

7. The method of claim 5, further comprising:

processing a screening rule comprising instructions to initiate determining that the first identifier is mapped to the second identifier.

8. The method of claim 5, wherein the first message is a session initiation protocol message.

9. The method of claim 5, further comprising:

receiving information indicative of the first identifier being mapped to the second identifier; and

storing, in a memory, the record indicative of the first identifier being mapped to the second identifier.

10. The method of claim 5, wherein the second identifier was replaced with the first identifier in the first message.

11. The method of claim 5, wherein the generating the second message comprises adding a “

diversion”

field to the second message.

12. The method of claim 5, wherein the first identifier is contained in at least one of a “

p-asserted-identity”

field or a “

from”

field.

13. The method of claim 5, wherein a trunking service performs automatic number identification by examining at least one of a “

diversion”

field of the second message, a “

p-asserted-identity”

field of the second message, or a “

from”

field of the second message, wherein the examining in performed in order of the “

diversion”

field, the “

p-asserted-identity”

field, and the “

from”

field.

19. The method of claim 5, wherein, based on the first identifier, an identity, of the origin of the request to establish the communication session, is displayed to a recipient of the communication session.

14. A method comprising:

receiving a message indicative of a request to establish a communication session, the message comprising a first identifier of an origin of the request and a second identifier, wherein the second identifier was added to the message based on a mapping between the first identifier and second identifier;

transmitting, to a device that is a recipient of the communication session, an identity associated with the origin of the request based on the first identifier; and

determining, based on the second identifier, an account associated with the origin of the request.

15. The method of claim 14, wherein the first identifier is contained in one of a “

p-asserted-identity”

field or a “

from”

field of a session initiation protocol message.

16. The method of claim 14, wherein a “

diversion”

field comprises the second identifier.

17. The method of claim 14, further comprising:

transmitting information indicative of the mapping between the first identifier and the second identifier.

18. The method of claim 14, further comprising:

performing automatic number identification by locating the second identifier in a sequence comprising at least one of a “

diversion”

field, a “

p-asserted-identity”

field, or a “

from”

field.

20. The method of claim 14, wherein the identity of the origin of the communication session is displayed to the recipient.