HOME NODE-B APPARATUS AND SECURITY PROTOCOLS

• US 20130046980A1
• Filed: 10/24/2012
• Published: 02/21/2013
• Est. Priority Date: 09/24/2008
• Status: Active Grant

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Inventors: Shah, Yogendra C., Schmidt, Andreas U., Cha, Inhyok
• Granted Patent: US 8,826,020 B2
• Time in Patent Office: Days
• US Class Current: 713/168
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 63/162 at the data link layer
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24
• CPC Class Codes: H04W 12/0431 Key distribution or pre-distribution; Key agreement
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/63 Location-dependent; Proximity-dependent
• CPC Class Codes: H04W 88/08 Access point devices

Abstract

A method for authenticating a home nodeB/home evolved node B (H(e)NB) with a network is disclosed. The method includes securely storing H(e)NB location information in a Trusted Environment (TrE); and securely sending the stored H(e)NB location information to the network via the TrE

Claims

1. A method for authenticating a home nodeB/home evolved node B (H(e)NB) with a network, comprising:

securely storing H(e)NB location information in a Trusted Environment (TrE); and

securely sending the stored H(e)NB location information to the network via the TrE.

2. The method as in claim 1, further comprising:

securely storing a last known good location of the H(e)NB in the TrE;

comparing the stored last known good location with a newly acquired location information using the TrE; and

indicating the outcome of the comparison by the TrE to a location server on the network.

3. The method of claim 2, further comprising securely storing the last known good location of the H(e)NB in the TrE after at least one of the expiration of a periodic interval or the occurrence of a pre-defined event.

4. The method as in claim 1, wherein protocols for interacting between the H(e)NB, the TrE and the network include at least one of Internet Key Exchange (IKEv2), Transport Layer Security (TLS), Broadband Forum Technical Requirements (TR) 069, or Open Mobile Alliance (OMA) Device Management (DM).

5. The method of claim 1, further comprising:

receiving cryptographically protected H(e)NB location information from a location information source; and

securely deciphering the cryptographically protected H(e)NB location information to identify the H(e)NB location information.

6. The method of claim 1, wherein the stored H(e)NB location information is cryptographically protected using keys stored securely inside the TrE.

7. The method of claim 1, wherein the sent H(e)NB location information is cryptographically protected.

8. The method of claim 1, wherein the H(e)NB location information is sent to the network via the TrE in a location registration request message.

9. The method of claim 1, further comprising:

receiving a response from the network indicating the results of a decision of whether to grant the H(e)NB access to the network, wherein the decision is based on a comparison between the sent H(e)NB location information and a previous H(e)NB location information,

wherein the H(e)NB location information is sent to the network via the TrE in a location authentication request message.

10. The method of claim 1, wherein the H(e)NB location information comprises an IP address assigned to the H(e)NB.

11. The method of claim 1, further comprising:

scanning for information on macro cells neighboring the H(e)NB,

wherein the location information comprises information on macro cells neighboring the H(e)NB.

12. The method of claim 11, wherein the macro cells neighboring the H(e)NB comprise 2G or 3G cells, wherein the information on macro cells neighboring the H(e)NB comprises location area and cell ID.

13. The method of claim 11, wherein the H(e)NB location information further comprises an IP address assigned to the H(e)NB.

14. The method of claim 1, wherein the H(e)NB has GPS capabilities, wherein the H(e)NB location information comprises GPS location information obtained from the H(e)NB.

15. The method of claim 14, wherein the H(e)NB GPS capabilities comprise a separate security-hardened GPS chip.

16. The method of claim 1, wherein the H(e)NB location information is selected from one or more of:

an IP address assigned to the H(e)NB,

information on macro cells neighboring the H(e)NB, and

GPS location information associated with the H(e)NB;

wherein the H(e)NB location information is selected in accordance with a scenario and policy based pre-configured H(e)NB policy.

17. A H(e)NB, comprising:

a TrE; and

H(e)NB functional building blocks, at least one of the H(e)NB function building blocks;

securely storing H(e)NB location information in a Trusted Environment (TrE); and

securely sending the stored H(e)NB location information to the network via the TrE.

18. The H(e)NB of claim 17, further comprising the at least one of the H(e)NB function building blocks:

securely storing last known good location of the H(e)NB in the TrE;

comparing the stored last known good location with a newly acquired location information using the TrE; and

indicating the outcome of the comparison by the TrE to a location server on the network.

19. The H(e)NB of claim 17, further comprising the at least one of the H(e)NB function building blocks:

receiving a response from the network indicating the results of a decision of whether to grant the H(e)NB access to the network, wherein the decision is based on a comparison between the sent H(e)NB location information and a previous H(e)NB location information,

wherein the H(e)NB location information is sent to the network via the TrE in a location authentication request message.

20. The H(e)NB of claim 17, wherein the H(e)NB location information comprises an IP address assigned to the H(e)NB.

21. The H(e)NB of claim 17, further comprising the at least one of the H(e)NB function building blocks:

scanning for information on macro cells neighboring the H(e)NB,

wherein the location information comprises information on macro cells neighboring the H(e)NB.

22. The H(e)NB of claim 21, wherein the macro cells neighboring the H(e)NB comprise 2G or 3G cells, wherein the information on macro cells neighboring the H(e)NB comprises location area and cell ID.

23. The H(e)NB of claim 17, wherein the H(e)NB has GPS capabilities, wherein the H(e)NB location information comprises GPS location information obtained from the H(e)NB.

24. The H(e)NB of claim 17, wherein the H(e)NB location information is selected from one or more of:

an IP address assigned to the H(e)NB,

information on macro cells neighboring the H(e)NB, and

GPS location information associated with the H(e)NB;

wherein the H(e)NB location information is selected in accordance with a scenario and policy based pre-configured H(e)NB policy.