System and method for communications device and network component operation

• US 8,532,618 B2
• Filed: 12/15/2009
• Issued: 09/10/2013
• Est. Priority Date: 07/03/2009
• Status: Active Grant

• Current Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Inventors: Xiang, Zengjun, Chan, Hinghung Anthony
• Primary Examiner(s): Ly, Nghi H
• Application Number:
  US12/638,639
• Publication Number:
  US 20110003546A1
• Time in Patent Office: 1,365 Days
• Field of Search: 455/411, 455/435.1, 455/436, 455/442, 455/432.1, 455/410
• US Class Current: 455/411
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Abstract

A system and method for communications device and network component operation in an ID/Locator Split Based heterogeneous network is provided. A method for control node operation includes receiving an attach request, and attempting to authenticate/authorize the communications node. The attach request is a request from a communications node to attach to a heterogeneous network. The method also includes if the communications node authenticated/authorized successfully, causing an identification and a location to be assigned for the communications node, completing an attachment for the communications node, and transmitting information to the communications node. The method further includes if the communications node did not authenticate/authorize successfully, sending an attach reject message to the communications node. The identification and the location are separate values.

Claims

1. A method for control node operation, the method comprising:

receiving an attach request, wherein the attach request is a request from a communications node to attach to a heterogeneous network;

attempting to authenticate/authorize the communications node;

if the communications node authenticated/authorized successfully,

retrieving an original host session identifier (ID) and a locator identifier (ID) for the communications node, wherein the original host session ID and locator ID are separate values,

completing an attachment for the communications node, wherein completing the attachment causes the communications node to be assigned a new locator ID without being assigned a new host session ID, and

transmitting information to the communications node; and

if the communications node did not authenticate/authorize successfully, sending an attach reject message to the communications node.

2. The method of claim 1 further comprising:

creating a default bearer for the communications node; and

updating information related to the communications node.

3. The method of claim 2, wherein updating information related to the communications node comprises storing the original host session ID and the new locator ID in a subscriber database.

4. The method of claim 2, wherein updating information related to the communications node further comprises storing the original host session ID and the new locator ID at a control node.

5. The method of claim 4, wherein the original host session ID remains assigned to the communications node after completing the attachment to the heterogeneous network.

6. The method of claim 1, wherein completing the attachment comprises:

setting up a context for the communications node; and

setting up an access bearer for the communications node.

7. The method of claim 6, wherein completing the attachment further comprises establishing communications links for the communications node.

8. The method of claim 7, wherein establishing communications links for the communications node comprises:

updating a bearer for the communications node in response to detecting a first uplink media packet transmitted by the communications node; and

transmitting a first downlink media packet to the communications node after receiving a response from an updating of information related to the communications node.

9. The method of claim 1, wherein the host session ID comprises an identity for the communications node.

10. The method of claim 1, wherein the original host session ID remains assigned to the communications node after completing the attachment.

11. A method for operating a communications node, the method comprising:

transmitting an attach request, wherein the attach request comprises a request to attach to a heterogeneous network, the attach request triggering an authentication and authorization of the communications node;

receiving a response message that indicates the attach request was accepted, wherein the response message includes an original host session identifier (ID) and a locator identifier (ID) that were retrieved during authentication and authorization of the communications node;

completing an attachment to the heterogeneous network, wherein the communications node is assigned a new locator ID without being assigned a new host session ID during the attachment; and

sending information over a communications link.

12. The method of claim 11 further comprising participating in the authentication and authorization.

13. The method of claim 11, wherein completing the attachment to the heterogeneous network comprises:

establishing an access bearer; and

sending an attach complete message.

14. The method of claim 11, wherein the original host session ID and the locator ID assigned to the communications node are used in a binding for a default bearer.

15. The method of claim 14, wherein the binding is stored at a subscriber database.

16. The method of claim 11, wherein the original host session ID comprises an identity and a charging record for the communications node.

17. A method for control node operation, the method comprising:

receiving a locator update request indicating a communications node is switching from an old control node to a new control node, wherein the locator update request is a request from a communications node operating in a heterogeneous network;

retrieving, by the new control node, an original host session identifier (ID) and a locator identifier (ID) assigned to the communications node from the old control node;

attempting to authenticate/authorize the communications node;

if the communications node authenticated/authorized successfully,

receiving updated binding information indicating that a new locator ID was assigned to the communications node without assigning a new host session ID to the communications node,

updating a binding for the communication node by re-associating the original host session ID with the new locator ID, and

completing a location update; and

if the communications node did not authenticate/authorize successfully, sending a locator update reject message to the communications node.

18. The method of claim 17 further comprising storing the original host session ID and the new locator ID at the control node.

19. The method of claim 17, wherein updating the binding comprises storing the original host session ID and the new locator ID at a subscriber database.

20. The method of claim 17 further comprising creating a new bearer for the communications node, wherein the original host session ID remains assigned to the communications node after the new bearer is created.

21. The method of claim 17, further comprising updating an existing bearer associated with the communications node, wherein the original host session ID remains assigned to the communications node after the existing bearer is updated.

22. The method of claim 17, wherein the original host session ID remains assigned to the communications node after the communications node switches from the old control node to the new control node.