Methods and apparatus to preserve original attestation/signature information for diverted calls

1. A communications method comprising:

receiving, at a first Session Border Controller (SBC), a diverted Session Initiation Protocol (SIP) INVITE message corresponding to a first call, said diverted SIP INVITE message not including an Identity header;

obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a Session Description Protocol (SDP) message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source Internet Protocol (IP) address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

generating an Identity header based on the original Identity header or information from the original Identity header corresponding to the first call obtained using said one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC;

receiving, at a second SBC, a SIP INVITE message corresponding to the first call including the original Identity header prior to receiving at the first SBC the diverted SIP INVITE message; and

storing, by the second SBC prior to receiving at the first SBC the diverted SIP INVITE message, the original Identity header or said information from the original Identity header in a record at the second SBC, a separate storage device, or at both the second SBC and a separate storage device, said separate storage device being accessible to both the second SBC and the first SBC.

2. The communications method of claim 1 , wherein said information included in the diverted SIP INVITE message includes information which identifies a record in which the original Identity header or said information from the original Identity header is stored.

3. The communications method of claim 2 , wherein said information which identifies a record in which the original Identity header or said information from the original Identity header is stored includes one or more of the following: (i) a record identifier and (ii) call identification information.

4. The communications method of claim 2 , wherein said record further includes one or more of the following: (i) a record identifier or (ii) call identification information that identifies the record as including information for the first call.

5. The communications method of claim 4 , wherein said call identification information that identifies the record as including information for the first call includes one or more of the following: (i) a SBC trunk group identifier for an SBC trunk group at the first SBC, (ii) a source IP address transport protocol port of the first SBC, and (iii) a SBC IP address and User Datagram Protocol (UDP) port number of a second SBC.

6. The communications method of claim 1 , wherein said step of obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC includes:

using, by said first SBC, information included in the diverted SIP INVITE message to retrieve the original Identity header or information from the original Identity header from a record stored in a storage device, said information included in the diverted SIP INVITE message including: a record identifier included in a proprietary header, a proprietary header parameter or a proprietary header tag of the diverted SIP INVITE message.

7. The communications method of claim 1 , wherein said step of obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC includes:

using, by said first SBC, information included in the diverted SIP INVITE message to obtain the original Identity header or information from the original Identity header; and

wherein said information included in the diverted SIP INVITE message includes one or more of the following: the original Identity header or an attestation level corresponding to the first call included in a proprietary header, a proprietary header parameter, or a proprietary header tag of the diverted SIP INVITE message.

8. The communications method of claim 3 ,

wherein said call identification information includes: an SBC IP address and User Datagram Protocol (UDP) port number for a media session for the first call; and

wherein said SBC IP address and UDP port number for the media session for the first call is also included in a SDP body of the SDP message included in the diverted SIP INVITE message.

9. The communications method of claim 1 ,

wherein said Identity header, said original Identity header, and said generated Identity header are SIP Identity headers including a Secure Handling of Asserted information using toKENs (SHAKEN) Personal Assertion Token (PASSporT).

10. The communications method of claim 1 ,

wherein said generated Identity header is generated based on information contained in the original Identity header, said information contained in the original Identity header being attestation information.

11. The communications method of claim 1 ,

wherein said original Identity header is a SIP Identity header which includes: calling party information, called party information, and attestation information; and

wherein at least some of the information included in the SIP Identity header has been digitally signed or encrypted.

12. The communications method of claim 1 ,

wherein said original Identity header is a SIP Identity header including:

(i) an originating identity for the first call, and

(ii) an attestation level, said attestation level indicating a specific level of confidence in the correctness of the originating identity of the first call; and

wherein said generated Identity header includes the same originating identity for the first call and the same attestation level which is included in the original Identity header.

13. The communications method of 12 : The communications method of wherein said attestation level included in the original Identity header is full attestation.

14. The communications method of claim 1 ,

wherein said first and said second SBCs are the same SBC.

15. A communications method comprising:

receiving, at a first Session Border Controller (SBC), a diverted Session Initiation Protocol (SIP) INVITE message corresponding to a first call, said diverted SIP INVITE message not including an Identity header;

obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a Session Description Protocol (SDP) message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source Internet Protocol (IP) address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

generating an Identity header based on the original Identity header or information from the original Identity header corresponding to the first call obtained using said one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC;

wherein said step of obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC includes:

said first SBC using information included in the diverted SIP INVITE message to obtain the original Identity header or information from the original Identity header;

wherein said information included in the diverted SIP INVITE message includes one or more of the following: the original Identity header or an attestation level corresponding to the first call included in a proprietary header, a proprietary header parameter, or a proprietary header tag of the diverted SIP INVITE message;

wherein the original Identity header or the attestation level corresponding to the first call is included in a proprietary parameter of a From header included in the diverted SIP INVITE message; and

wherein the original Identity header or the attestation level corresponding to the first call is encrypted using a shared key known to the first SBC.

16. The communications method of claim 15 further comprising:

prior to receiving the diverted SIP INVITE message at the first SBC performing the steps of:

encrypting, at a second SBC, the original Identity header or the attestation level corresponding to the first call; and

placing the encrypted original Identity header or the attestation level corresponding to the first call in a proprietary parameter of a From header of a SIP INVITE message which is communicated to an endpoint device from the second SBC.

17. A communications system comprising:

a first Session Border Controller (SBC) including:

memory;

one or more Input/Output Interfaces; and

a first processor, said first processor controlling the first SBC to perform the following operations:

receiving, at the first SBC, a diverted Session Initiation Protocol (SIP) INVITE message corresponding to a first call, said diverted SIP INVITE message not including an Identity header;

obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a Session Description Protocol (SDP) message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source Internet Protocol (IP) address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

generating an Identity header based on the original Identity header or information from the original Identity header corresponding to the first call obtained using said one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC;

a second SBC including:

memory;

one or more Input/Output Interfaces;

a second processor, said second processor controlling the second SBC to perform the following operations:

receiving, at the second SBC, a SIP INVITE message corresponding to the first call including the original Identity header prior to receiving at the first SBC the diverted SIP INVITE message; and

storing, by the second SBC prior to receiving at the first SBC the diverted SIP INVITE message, the original Identity header or said information from the original Identity header in a record at the second SBC, a separate storage device, or at both the second SBC and a separate storage device, said separate storage device being accessible to both the second SBC and the first SBC.

18. The communications system of claim 17 , wherein said information included in the diverted SIP INVITE message includes information which identifies a record in which the original Identity header or said information from the original Identity header is stored.

19. The communications system of claim 18 , wherein said information which identifies a record in which the original Identity header or said information from the original Identity header is stored includes one or more of the following: (i) a record identifier and (ii) call identification information.

20. The communications system of claim 18 , wherein said record further includes one or more of the following: (i) a record identifier or (ii) call identification information that identifies the record as including information for the first call.

21. The communications system of claim 20 , wherein said call identification information that identifies the record as including information for the first call includes one or more of the following: (i) a SBC trunk group identifier for an SBC trunk group at the first SBC, (ii) a source IP address transport protocol port of the first SBC, and (iii) a SBC IP address and UDP port number of a second SBC.

22. The communications system of claim 17 , wherein said operation of obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC includes:

using, by said first SBC, information included in the diverted SIP INVITE message to retrieve the original Identity header or information from the original Identity header from a record stored in a storage device, said information included in the diverted SIP INVITE message including: a record identifier included in a proprietary header, a proprietary header parameter or a proprietary header tag of the diverted SIP INVITE message.

23. The communications system of claim 17 , wherein said operation of obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP Invite message received at the first SBC includes:

using, by the first SBC, information included in the diverted SIP INVITE message to obtain the original Identity header or information from the original Identity header; and

wherein said information included in the diverted SIP INVITE message includes one or more of the following: the original Identity header or an attestation level corresponding to the first call included in a proprietary header, a proprietary header parameter, or a proprietary header tag of the diverted SIP INVITE message.

24. The communications system of claim 17 ,

wherein said first and said second SBCs are the same SBC.

25. The communications system of claim 17 ,

wherein said original Identity header is a SIP Identity header including:

(i) an originating identity for the first call, and

(ii) an attestation level, said attestation level indicating a specific level of confidence in the correctness of the originating identity of the first call; and

wherein said generated Identity header includes the same originating identity for the first call and the same attestation level which is included in the original Identity header; and

wherein said attestation level included in the original Identity header is full attestation.

26. A first non-transitory machine readable medium including processor executable instructions, which when executed by a processor of a first Session Border Controller (SBC) controls the first SBC to:

receive, at the first SBC, a diverted Session Initiation Protocol (SIP) INVITE message corresponding to a first call, said diverted SIP INVITE message not including an Identity header;

obtain an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a Session Description Protocol (SDP) message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source Internet Protocol (IP) address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

generate an Identity header based on the original Identity header or information from the original Identity header corresponding to the first call obtained using said one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

a second non-transitory machine readable medium including processor executable instructions, which when executed by a processor of a second SBC controls the second SBC to:

receive, at the second SBC, a SIP INVITE message corresponding to the first call including the original Identity header prior to receiving at the first SBC the diverted SIP INVITE message; and

store, by the second SBC prior to receiving at the first SBC the diverted SIP INVITE message, the original Identity header or said information from the original Identity header in a record at the second SBC, a separate storage device, or at both the second SBC and a separate storage device, said separate storage device being accessible to both the second SBC and the first SBC.

27. A communications system comprising:

a first Session Border Controller (SBC) including:

memory;

one or more Input/Output Interfaces; and

a first processor, said first processor controlling the first SBC to perform the following operations:

receiving, at the first SBC, a diverted Session Initiation Protocol (SIP) INVITE message corresponding to a first call, said diverted SIP INVITE message not including an Identity header;

obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a Session Description Protocol (SDP) message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source Internet Protocol (IP) address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC; and

generating an Identity header based on the original Identity header or information from the original Identity header corresponding to the first call obtained using said one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC;

wherein said obtaining an original Identity header or information from the original Identity header corresponding to the first call using one or more of the following: (i) information included in the diverted SIP INVITE message, (ii) information included in a SDP message included in the diverted SIP INVITE message, (iii) a SBC trunk group on which the diverted SIP INVITE message was received at the first SBC, or (iv) a source IP address transport protocol port of an IP packet carrying the diverted SIP INVITE message received at the first SBC includes:

said first SBC using information included in the diverted SIP INVITE message to obtain the original Identity header or information from the original Identity header;

wherein said information included in the diverted SIP INVITE message includes one or more of the following: the original Identity header or an attestation level corresponding to the first call included in a proprietary header, a proprietary header parameter, or a proprietary header tag of the diverted SIP INVITE message;

wherein the original Identity header or the attestation level corresponding to the first call is included in a proprietary parameter of a From header included in the diverted SIP INVITE message; and

wherein the original Identity header or the attestation level corresponding to the first call is encrypted using a shared key known to the first SBC.