# US 2013/0279337 A1 · LOAD-BALANCED NSAPI ALLOCATION FOR iWLAN

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0279337 A1
- Document ID: US20130279337A1
- Status: Published application
- Kind: A1
- Application number: 13/904,925
- Filed: 2013-05-29
- Published: 2013-10-24
- Earliest claimed: 2007-06-22
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Biswaranjan Panda; Kevin D. Shatzkamer; Mark Grayson; Richard Kyle Forster
- Web page: https://patentgrep.com/patent/US20130279337A1

## CPC

- H04L 67/1036: Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1004: Server selection for load balancing
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/101: based on network conditions
- H04L 67/1014: based on the content of a request
- H04W 28/088: among core entities
- H04W 88/16: Gateway arrangements
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

In one embodiment, a load balancer receives a message from a tunnel termination gateway (TTG) associated with a mobile device. The load balancer may receive messages from a plurality of TTGs. A gateway node in a plurality of gateway nodes in which to send the message is determined. The load balancer then assigns a NSAPI for use by the gateway node. For example, the NSAPI may be associated with a tunnel that is generated between the TTG and GGSN. The load balancer ensures that the assigned NSAPI is not currently in use at the gateway node. Thus, no overlapping of NSAPIs may occur even though the load balancer is processing messages from multiple TTGs for multiple gateway nodes.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method, comprising:
receiving a message for a device at a load balancer, wherein the message is to be used to create a tunnel;
determining a first gateway node in a plurality of nodes to which to send the message;
accessing a plurality of mappings between a plurality of network service access point identifiers (NSAPIs) and the plurality of nodes;
determining whether a particular NSAPI of the plurality of NSAPIs is currently in use at the first gateway node; and
assigning, at the load balancer, the particular NSAPI for use by the first gateway node.

### Claim 22 (depends on 21)

The method of claim 21, wherein the message is a packet data protocol (PDP) context create message.

### Claim 23 (depends on 22)

The method of claim 22, wherein the assigning comprises dynamically assigning the particular NSAPI for the PDP context create message.

### Claim 24 (depends on 21)

The method of claim 21, wherein the message is an access request associated with a mobile device.

### Claim 25 (depends on 21)

The method of claim 21, wherein the assigning includes overwriting an existing NSAPI provided in the message with the particular NSAPI.

### Claim 26 (depends on 21)

The method of claim 21, wherein the determining includes employing a load-balancing technique that evaluates available resources for servicing the message.

### Claim 27 (depends on 21)

The method of claim 21, wherein the assigning includes assigning a value that is not active at the first gateway node.

### Claim 28 (depends on 21)

The method of claim 21, wherein the accessing includes identifying one or more mobile devices that are associated with one or more NSAPIs.

### Claim 29 (depends on 21)

The method of claim 21, further comprising:
determining that a particular call involves a mobile device; and
sending a particular message to a same network node that was previously associated with the mobile device.

### Claim 30

A load balancer, comprising:
a processor; and
a non-transitory computer readable media, wherein the apparatus is configured for:
receiving a message for a device, wherein the message is to be used to create a tunnel;
determining a first gateway node in a plurality of nodes to which to send the message;
accessing a plurality of mappings between a plurality of identifiers and the plurality of nodes;
determining whether a particular identifier of the plurality of identifiers is currently in use at the first gateway node; and
assigning the particular identifier for use by the first gateway node.

### Claim 31 (depends on 30)

The load balancer of claim 30, wherein the message is a packet data protocol (PDP) context create message.

### Claim 32 (depends on 31)

The load balancer of claim 31, wherein the assigning comprises dynamically assigning the particular identifier for the PDP context create message.

### Claim 33 (depends on 30)

The load balancer of claim 30, wherein the message is an access request associated with a mobile device.

### Claim 34 (depends on 30)

The load balancer of claim 30, wherein the assigning includes overwriting an existing identifier provided in the message with the particular identifier.

### Claim 35 (depends on 30)

The load balancer of claim 30, wherein the determining includes employing a load-balancing technique that evaluates available resources for servicing the message.

### Claim 36 (depends on 30)

The load balancer of claim 30, wherein the assigning includes assigning a value that is not active at the first gateway node.

### Claim 37 (depends on 30)

The load balancer of claim 30, wherein the accessing includes identifying one or more mobile devices that are associated with one or more identifiers.

### Claim 38 (depends on 30)

The load balancer of claim 30, the load balancer being further configured for:
determining that a particular call involves a mobile device; and
sending a particular message to a same network node that was previously associated with the mobile device.

### Claim 39

An apparatus, comprising:
a processor;
a message receiver element;
a determiner element;
an identifier reviewer element;
an identifier assigner element; and
a non-transitory computer readable media, wherein the apparatus is configured for:
receiving a message for a device, wherein the message is to be used to create a tunnel;
determining a first gateway node in a plurality of nodes to which to send the message;
accessing a plurality of mappings between a plurality of identifiers and the plurality of nodes;
determining whether a particular identifier of the plurality of identifiers is currently in use at the first gateway node; and
assigning the particular identifier for use by the first gateway node.

### Claim 40 (depends on 39)

The apparatus of claim 39, the apparatus being further configured for:
determining that a particular call involves a mobile device; and
sending a particular message to a same network node that was previously associated with the mobile device.
