METHOD AND APPARATUS FOR INSTANCE IDENTIFIER BASED ON A UNIQUE DEVICE IDENTIFIER

• US 20100009681A1
• Filed: 09/16/2008
• Published: 01/14/2010
• Est. Priority Date: 07/09/2008
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: SCHNEYER, SEAN KENDALL, Lindholm, Fredrik, Heidermark, Alf
• Granted Patent: US 8,135,386 B2
• Time in Patent Office: Days
• US Class Current: 455/435.100
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 2463/061 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key cryptographic mechanisms or cryptographic arrangements for generation of secret information including derivation or calculation of cryptographic keys or passwords H04L9/0861
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/71 Hardware identity

Abstract

A method and apparatus for use in a communications network whereby an Instance Identifier (ID) is created to uniquely identify a device such as a mobile device or User Equipment (UE) in the communications network.

Claims

1. A method for use in a communications network, comprising the step of:

creating an Instance Identifier (ID) to uniquely identify a device such as a mobile device or User Equipment (UE) in the communications network.

2. The method of claim 1, further comprising the step of constructing the Instance ID as a Universally Unique Identifier (UUID) URN using the string representation of a UUID.

3. The method of claim 1, wherein the mobile device is compliant with the 3GPP standards and supports Globally Routable User Agent (GRUU).

4. The method of claim 3, wherein the unique identifier that belongs to the mobile device and is known to the network (DevID) is derived from the International Mobile Equipment Identity (IMEI).

5. The method of claim 4, further comprising the steps of:

creating a DevID by extracting the TAC and SNR from the IMEI;

when using the Type Allocation Code (TAC) and Serial Number (SNR), omitting the spare digit for a total of 14 digits;

placing a name space ID and DevID in network byte order;

concatenating the name space ID and DevID;

computing the hash of the concatenated string using a pre-selected hash algorithm;

setting the UUID fields using the hash and creating a string representation;

placing the string representation in urn form by pre-pending “

urn;

uuid”

to the string.

6. The method of claim 1, wherein the mobile device is compliant with the Third Generation Partnership Project 2 (3GPP2) standards.

7. The method of claim 6, wherein the unique identifier that belongs to the mobile device and is known to the network (DevID) is derived from the Mobile Equipment Identifier (MEID) or Electronic Serial Number (ESN).

8. The method of claim 1, wherein the Instance ID created by the network is identical to an Instance ID created by the device.

9. The method of claim 1, for use in a non-3GPP device, and wherein the DevID is unique to the device and is known by the network.

10. The method of claim 1, further comprising using a private identity to create the Instance ID.

11. The method of claim 10, wherein the private identity is a Network Access Identifier (NAI).

12. The method of claim 1, further comprising the steps of:

constructing, by a User Equipment (UE), an Instance ID derived from an IMEI;

performing a REGISTER request from a UE to a Proxy-Call Session Control Function (P-CSCF);

forwarding, by the P-CSCF, the request to the Interrogating-Call Session Control Function (I-CSCF);

making, by the I-CSCF, a request for information related to the Subscriber registration status by sending the private user identity, public user identity and visited domain name to a Home Subscriber Server (HSS);

returning, by the HSS, the Serving-Call Session Control Function (S-CSCF) required capabilities to the I-CSCF;

using, by the I-CSCF, the S-CSCF required capabilities information to select a suitable S-CSCF;

forwarding, by the I-CSCF, the REGISTER request to the selected S-CSCF;

challenging, by the S-CSCF, the registration request;

forwarding, by the I-CSCF, the response to the P-CSCF;

forwarding, by the P-CSCF, the response to the UE;

resending, by the UE, the REGISTER request with authentication credentials;

forwarding, by the P-CSCF, the request to the I-CSCF;

making, by the I-CSCF, a request for information related to the Subscriber registration status by sending the private user identity, public user identity and visited domain name to an HSS;

returning, by the HSS the S-CSCF required capabilities;

using, by the I-CSCF, the information about the S-CSCF required capabilities to select a suitable S-CSCF;

forwarding, by the I-CSCF, the REGISTER request to the selected S-CSCF;

informing, by the S-CSCF, the HSS that the user has been registered;

including, upon being requested by the S-CSCF, by the HSS the user profile in the response sent to the S-CSCF;

constructing, by the S-CSCF acting as registrar, a Globally Routable User Agent (GRUU) based on the Instance ID;

sending, by the S-CSCF sends a 200 (OK) response, including the GRUU, to the I-CSCF indicating that registration was successful;

forwarding, by the I-CSCF, the 200 (OK) response to the P-CSCF indicating that registration was successful; and

forwarding, by the P-CSCF, the 200 (OK) response to UE indicating that registration was successful.

13. The method of claim 1, for use when the communication network registers on behalf of a device that is using circuit switch (CS) access.

14. The method of claim 13, further comprising the steps of;

circuit switch attaching by a UE to a Mobile Switching Center (MSC);

performing, by a Mobile Switching Center/Visitor Location Register (MSC/VLR) to a Home Location Register/Home Subscriber Server (HLR/HSS) an Authentication and Update Location;

accepting, by the MSC to the UE a CS attach;

evaluating, by the MSC, whether it needs to perform registration with IMS;

deriving, by the MSC, a home network domain name;

creating, by the MSC, an Instance ID derived from the IMEI of UE;

sending, by the MSC to the Interrogating-Call Session Control Function (I-CSCF), a REGISTER request to register a private user identity and a temporary public user identity derived for the subscriber on behalf of the user with a Serving-Call Session Control Function (S-CSCF) in the home network;

routing the request to the I-CSCF in the home network;

requesting, by the I-CSCF, a request for information related to the Subscriber registration status by sending the private user identity, public user identity and visited domain name to an HSS;

returning, by the HSS, the S-CSCF required capabilities;

using, by the I-CSCF the S-CSCF required capabilities to select a suitable S-CSCF;

forwarding, by the I-CSCF, the REGISTER request to the selected S-CSCF;

informing, by the S-CSCF, the HSS that the user has been registered, whereby, upon being requested by the S-CSCF, the HSS will also include the user profile in the response sent to the S-CSCF;

constructing, by the S-CSCF acting as registrar, a GRUU based on the Instance ID;

sending, by the S-CSCF, a 200 (OK) response, including the GRUU, to the I-CSCF indicating that registration was successful; and

forwarding, by the I-CSCF, the 200 (OK) response to the MSC Server indicating that registration was successful.

15. An apparatus for use in a communications network, comprising:

means for creating an Instance Identifier (ID) to uniquely identify a device such as a mobile device or User Equipment (UE) in the communications network.

16. The apparatus of claim 15, further comprising means for constructing the Instance ID as a Universally Unique Identifier (UUID) URN using the string representation of a UUID.

17. The apparatus of claim 15, wherein the mobile device is compliant with the 3GPP standards and supports Globally Routable User Agent (GRUU).

18. The apparatus of claim 17, wherein the unique identifier that belongs to the mobile device and is known to the network (DevID) is derived from the IMEI.

19. The apparatus of claim 15, wherein the mobile device is compliant with the 3GPP2 standards.

20. The apparatus of claim 19, wherein the unique identifier that belongs to the mobile device and is known to the network (DevID) is derived from the MEID or ESN.

21. The apparatus of claim 15, wherein the Instance ID created by the network is identical to an Instance ID created by the device.

22. The apparatus of claim 15, for use in a non-3GPP device, and wherein the DevID is unique to the device and is known by the network.

23. The apparatus of claim 15, further comprising using a private identity to create the Instance ID.

24. The apparatus of claim 23, wherein the private identity is a Network Access Identifier (NAI).

25. The apparatus of claim 15, for use when the communication network registers on behalf of a device that is using circuit switch (CS) access.

26. A computer program for creating an Instance Identifier (ID), said computer program being embodied in a computer readable medium adapted to be executed by a processor, comprising:

computer code for constructing the Instance ID as a Universally Unique Identifier (UUID) URN using the string representation of a UUID.