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.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
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.
A method for a network control node to handle a device attaching to a heterogeneous network involves receiving an attach request from the device and attempting to authenticate it. If authentication is successful, the control node retrieves the device's original host session ID (for identifying the device) and a locator ID (for routing). The control node then completes the attachment by assigning the device a new locator ID, while keeping the original host session ID the same. Information about the attachment is then sent to the device. If authentication fails, the control node sends an attach reject message to the device.
2. The method of claim 1 further comprising: creating a default bearer for the communications node; and updating information related to the communications node.
The control node method of handling device attachment, as described above, also includes creating a default bearer (a communication channel) for the device after successful authentication. The method further involves updating information related to the device, such as storing the device's IDs and bearer details.
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.
Within the control node attachment method (which includes creating a default bearer for the communications node; and updating information related to the communications node), updating device information involves storing the device's original host session ID and the new locator ID in a subscriber database. This database maintains a record of devices and their current network locations.
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.
In the control node attachment method (which includes creating a default bearer for the communications node; and updating information related to the communications node), updating device information also involves storing the device's original host session ID and the new locator ID at the control node itself. This allows the control node to quickly access the device's information.
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.
As part of the control node's attachment process, after the device successfully attaches to the heterogeneous network (receiving a new locator ID while maintaining its original host session ID), the original host session ID continues to be associated with the device. This ensures consistent identification even as the device moves within the 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.
The control node attachment process, which involves assigning the device a new locator ID while maintaining its original host session ID, includes setting up a context for the device (establishing its network settings) and setting up an access bearer (creating a specific communication channel for the device's traffic).
7. The method of claim 6 , wherein completing the attachment further comprises establishing communications links for the communications node.
The control node attachment process (which includes setting up a context for the communications node; and setting up an access bearer for the communications node) further involves establishing communication links for the device to transmit and receive data.
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.
Establishing communication links for the attaching device involves updating the device's bearer (communication channel) when the control node detects the first data packet sent by the device. The control node sends a downlink data packet to the device after receiving confirmation that device information has been updated on the network.
9. The method of claim 1 , wherein the host session ID comprises an identity for the communications node.
The host session ID used in the control node attachment process represents the unique identity of the communications device within the heterogeneous network.
10. The method of claim 1 , wherein the original host session ID remains assigned to the communications node after completing the attachment.
Even after a communications device attaches to the heterogeneous network and receives a new locator ID, the device's original host session ID remains assigned to it, ensuring consistent identification across different network locations.
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.
A method for a communications device to attach to a heterogeneous network involves transmitting an attach request, which triggers authentication. Upon receiving a response indicating the request was accepted, the device receives its original host session ID and a locator ID. When completing the attachment, the device gets a new locator ID but retains its original host session ID. The device then sends information over a communication link.
12. The method of claim 11 further comprising participating in the authentication and authorization.
The communications device attachment method, which involves requesting attachment to a heterogeneous network and receiving a new locator ID, also includes the device actively participating in the authentication and authorization process.
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.
Completing the attachment to the heterogeneous network, where the device receives a new locator ID while retaining its original host session ID, includes establishing an access bearer (a dedicated communication channel) and sending an "attach complete" message to the network.
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.
The original host session ID and the locator ID assigned to the device during the attachment process are used in a binding for a default bearer, which is a standard communication channel for the device. This binding associates the device's identity and location with the bearer.
15. The method of claim 14 , wherein the binding is stored at a subscriber database.
The binding between the device's original host session ID, locator ID, and default bearer is stored in a subscriber database. This database is used to track the device's network information and manage its communication channels.
16. The method of claim 11 , wherein the original host session ID comprises an identity and a charging record for the communications node.
The original host session ID used in the device attachment process serves as both a unique identifier for the device and a record for tracking its data usage for billing purposes.
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.
When a device switches from one control node to another in a heterogeneous network, the new control node receives a locator update request. The new control node retrieves the device's original host session ID and current locator ID from the old control node. It then authenticates the device. If successful, the new control node receives updated binding information indicating a new locator ID has been assigned, but the original host session ID remains. The new control node then updates its records to associate the original host session ID with the new locator ID, completing the location update. If authentication fails, the new control node sends a locator update reject message to the device.
18. The method of claim 17 further comprising storing the original host session ID and the new locator ID at the control node.
In the control node operation for device handoff (switching from an old control node to a new one), which involves updating a device's locator ID, the new control node also stores the original host session ID and the new locator ID locally. This allows for faster access to the device's information during subsequent operations.
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.
The control node operation for device handoff (switching from an old control node to a new one) also includes updating the subscriber database with the device's original host session ID and the new locator ID. This ensures the database always contains the most up-to-date location information for the device.
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.
During the device handoff process, where the new control node updates the device's location information, the new control node may create a new bearer (communication channel) for the device. The original host session ID continues to be associated with the device even 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.
During the device handoff process, where the new control node updates the device's location information, the new control node may update an existing bearer (communication channel) for the device. The original host session ID continues to be associated with the device even 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.
Throughout the entire device handoff process, from switching from the old control node to the new control node and getting a new locator ID, the original host session ID remains consistently assigned to the device. This ensures continuous identification and tracking of the device within the heterogeneous network.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
December 15, 2009
September 10, 2013
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.