Forwarding a terminal identity between core network nodes

• US 20040258019A1
• Filed: 04/12/2004
• Published: 12/23/2004
• Est. Priority Date: 10/19/2001
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Hurtta, Tuija, Haumont, Serge
• Granted Patent: US 7,792,078 B2
• Time in Patent Office: Days
• US Class Current: 370/331
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/72 Subscriber identity
• CPC Class Codes: H04W 12/75 Temporary identity
• CPC Class Codes: H04W 60/04 using triggered events
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 88/10 adapted for operation in multiple networks, e.g. multi-mode access points

Abstract

A method, system and network element for forwards a terminal identity from a first core network node to a second core network node via a common radio access network. The common radio access network is arranged to incorporate a derived terminal identity received from the first core network node into a signaling message transmitted to the second core network node. The second core network node may then use this terminal identity to address the concerned terminal device.

Claims

1. A method for forwarding a terminal identity from a first core network node to a second core network node, said method comprising the steps of:

a) deriving said terminal identity at a first core network node;

b) transmitting said derived terminal identity to a radio access network shared by said first and second core network nodes;

c) adding said terminal identity to a signaling message generated at said shared radio access network; and

d) transmitting said signaling message to said second core network node.

2. A method according to claim 1, wherein said signaling message is a signaling message used to establish a connection to said second core network node.

3. A method according to claim 1, wherein said signaling message is a RANAP Initial UE Message.

4. A method according to claims 1, wherein said terminal identity is an IMSI, PTMSI or a TMSI.

5. A method according to claim 1, further comprising the step of transmitting security parameters together with said terminal identity from said first core network node via said shared access network to said second core network node.

6. A method according to claim 1, fuirther comprising the steps of evaluating said terminal identity at said first core network node and performing said transmitting step (b) if the result of said evaluation indicates that said terminal device is to be served by another core network node.

7. A method according to claim 6, wherein said transmitting step (b) comprises transmitting a re-direction request from said first core network node to said radio access network.

8. A method according to claims 1, wherein said transmitting step (b) is performed during a Common ID procedure.

9. A method according to claim 1, further comprising the step of performing a security mode procedure directly between said first core network node and said radio access network.

10. A method according to claim 1, further comprising the steps of deciding on a need to redirect a registered terminal from said first core network node to said second core network node (CNT), and confirming said redirection in response to a successful reallocation of said terminal identity.

12. A method according to claim 10, wherein said transmission step (b) is performed by transmitting a redirect message to a radio network controller (30) of said radio access network, and wherein said signaling message is a redirect forward message used by said radio network controller 3 to establish a new lu connection for routing signaling messages to said second core network node (CN2).

13. A method according to claim 12, wherein said redirect forward message contains context information, and wherein said context information is marked as unconfirmed at said second core network node.

14. A method according to ay one of claims 13, wherein said context information is confirmed after a successful, routing area update or reallocation of said terminal identity has been signaled to said second core network node.

11. A method according to claim I0, wherein said decision step is performed in response to a network command, an overload risk, or a request for a non-supported feature.

15. A system for forwarding a terminal identity between core network nodes, said system comprising:

a) a first core network node, arranged to derive said terminal identity from a signaling message received from a concerned terminal device; and

b) a radio access network shared by said first core network node and a second core network node and arranged to receive said derived terminal identity from said first core network node, and to add said received terminal identity to an initial signaling message;

c) wherein said second core network node is arranged to receive said initial signaling message and to use said added terminal identity for addressing said terminal device.

16. A system according to claim 15, wherein said radio access network is a UTRAN.

17. A system according to claim 15, wherein said first core network node is arranged to evaluate said terminal identity as to whether said terminal device is to be served by another core network node.

18. A system according to claim 17, wherein said first core network node is arranged to transmit a request for re-direction of said signaling message, if said evaluation leads to the result that said terminal device is to be served by a second core network node.

19. A system according to claim 15, wherein said first core network node is an SGSN, and said second core network node is an MSCNLR.

20. A system according to claim 15, wherein said first core network node is an MSCNLR, and said second core network node is an SGSN.

21. A network element of a radio access network, said network element being arranged to receive a derived terminal identity from a first core network node, to add said terminal identify if available to a signaling message, and to transmit said signaling message to another core network node.

22. A network according to claim 21, wherein said network element is further arranged to derive security parameters associated with said terminal identity, to add said security parameters together with said terminal identity to an signaling message, and to transmit said signaling message to said other core network node.

23. A network element according to claim 21, wherein said network element is an RNC.

24. A network element of a core network, said network element being arranged to extract a terminal identity of a terminal device from a signaling message generated at a radio access network, and to use said terminal identity for an initial access to said terminal device.

25. A network element according to claim 24, further arranged to check if security parameters are associated with the terminal identity, and to use these security parameters for the connection with the terminal if they are present, or to perform an authentication procedure toward the terminal if they are not present.

26. A network element according to claim 24, wherein said network element is an MSC/VLR or an SGSN.

27. A network element according to claim 24, fturther arranged to decide on a need to redirect said terminal device, and to confirm said redirection in response to a successfuil redirection.

28. A network element of a core network, said network element being arranged to derive a terminal identity from a signaling message received from a terminal device, to evaluate said terminal identity as to whether said terminal device is to be served by said core network, and to transmit said derived terminal identity together with a request for re-direction to a radio access network if said evaluation indicates that said terminal device is to be served by another core network.

29. A network element according to claim 28, wherein said network element is an MSC/VLR or an SGSN.