# US 8,787,909 B2 · Server for control plane at mobile communication network and method for controlling local IP access service

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

- Number: US 8,787,909 B2
- Document ID: US8787909B2
- Status: Granted
- Kind: B2
- Application number: 12/860,240
- Filed: 2010-08-20
- Published: 2011-02-24
- Granted: 2014-07-22
- Earliest claimed: 2009-08-21
- Assignees: LG Electronics Inc.
- Applicants: Taehyeon Kim; Laeyoung Kim; Hyunsook Kim
- Inventors: Taehyeon Kim; Laeyoung Kim; Hyunsook Kim
- Web page: https://patentgrep.com/patent/US8787909B2

## CPC

- H04W 8/082: {for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents}
- H04W 76/10: Connection setup
- H04W 80/04: Network layer protocols, e.g. mobile IP [Internet Protocol]
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Disclosed is a method of controlling a LIPA (Local IP Access) service in a server taking charge of the control plane within a mobile communication network. The method of controlling a LIPA service may include receiving an initial message from Home (e)NodeB. The initial message may include at least one of LIPA related information and capability information. The LIPA related information may include at least one of APN (Access Point Name) for LIPA and information for a local gateway, and the capability information may include an indicator indicating whether the Home (e)NodeB supports a LIPA function, and the initial message may include an access request message by a terminal. The method of controlling a LIPA service may further include determining whether the terminal can use a LIPA service at the Home (e)NodeB by considering at least one of the LIPA related information within the initial message, the capability information within the initial message, and subscriber information of the terminal, upon receiving the initial message; storing a result of the determination; generating an access accept message including an indicator indicating whether the terminal can use a LIPA service at the Home (e)NodeB; and transmitting an initial setup message including the generated access accept message to the Home (e)NodeB.

## Claims

### Claim 1

A method of controlling a Local IP Access (LIPA) service in a core network entity taking charge of the control plane within a mobile communication network, the method comprising:
receiving an initial message from Home (e)NodeB, wherein the initial message comprises at least one of LIPA related information and capability information, and the LIPA related information comprises at least one of Access Point Name (APN) for LIPA and information for a local gateway, and the capability information comprises a first indicator indicating whether the Home (e)NodeB supports a LIPA function, and the initial message comprises an attachment request message by a terminal;
determining whether the terminal uses a LIPA service at the Home (e)NodeB by considering at least one of the LIPA related information within the initial message, the capability information within the initial message, and subscriber information of the terminal, upon receiving the initial message;
storing a result of the determination;
generating an attachment accept message comprising a second indicator indicating whether the terminal uses a LIPA service at the Home (e)NodeB;
transmitting an initial setup message comprising the generated attachment accept message to the Home (e)NodeB for transmission to the terminal; and
receiving, from the terminal via the Home (e)NodeB, a request related to bearer setup for LIPA only when the second indicator indicates that the terminal uses the LIPA service at the Home (e)NodeB.

### Claim 2 (depends on 1)

The method of claim 1, wherein the initial message is an Initial User Equipment (UE) message, or an UPLINK NAS TRANSPORT message based on S1-AP, and
the access request message is any one of an attach request message, a Tracking Area Update (TAU) request message, a Routing Area Update (RAU) request message, and a handover request message.

### Claim 3 (depends on 1)

The method of claim 1, wherein the access accept message is any one of an Attach Accept message, a Tracking Area Update (TAU) Accept message, and a Routing Area Update (RAU) Accept message, and
the initial setup message is an S1-AP-based message, an Initial context Setup message, or a UE Context Modification message.

### Claim 4 (depends on 1)

The method of claim 1, wherein the initial message further comprises Closed Subscriber Group (CSG) related information.

### Claim 5 (depends on 4)

The method of claim 4, wherein the CSG related information further comprises at least one of a CSG ID and a CSG access mode parameter of the Home (e)NodeB.

### Claim 6 (depends on 1)

The method of claim 1, wherein the indicator indicating whether the Home (e)NodeB supports a LIPA function is LIPA_capability_indicator, and
the indicator indicating whether the terminal can use a LIPA service at the Home (e)NodeB is LIPA_Available_indicator.

### Claim 7 (depends on 1)

The method of claim 1, wherein in the determination step it is further considered whether the terminal is subscribed to a LIPA service based on the subscriber information.

### Claim 8 (depends on 1)

The method of claim 1, wherein in the determination step it is further considered whether the terminal has a Closed Subscriber Group (CSG) membership to the Home (e)NodeB.

### Claim 9 (depends on 1)

The method of claim 1, wherein in the storing step
the result of the determination is stored within a UE context or a Mobility Management/Evolved Packet Core (MM/EPC) Bearer Context.

### Claim 10 (depends on 1)

The method of claim 1, wherein the access accept message further comprises APN for a LIPA service.

### Claim 11

A core network entity of taking charge of a Local IP Access (LIPA) service within a mobile communication network, the core network entity comprising:
a receiver configured to receive an initial message comprising LIPA related information and capability information from Home (e)NodeB, wherein the LIPA related information comprises at least one of Access Point Name (APN) for LIPA and information for a local gateway, and the capability information comprises a first indicator indicating whether the Home (e)NodeB supports a LIPA function, and the initial message comprises an attachment request message by a terminal;
a controller configured to control to determine whether the terminal uses a LIPA service at the Home (e)NodeB by considering at least one of the LIPA related information within the initial message, the capability information within the initial message, and subscriber information of the terminal, in response to the initial message, and store a result of the determination; and
a transmitter configured to encapsulate an attachment accept message comprising a second indicator indicating whether the terminal uses a LIPA service at the Home (e)NodeB in an initial setup message to transmit to the Home (e)NodeB for transmission to the terminal,
wherein the receiver is further configured to receive, from the terminal via the Home (e)NodeB, a request related to bearer setup for LIPA only when the second indicator indicates that the terminal uses the LIPA server at the Home (e)NodeB.

### Claim 12 (depends on 11)

The server of claim 11, wherein the initial message is an Initial User Equipment (UE) message based on S1-AP, and
the access request message is any one of an attach request message, a Tracking Area Update (TAU) request message, a Routing Area Update (RAU) request message, and a handover request message.

### Claim 13 (depends on 11)

The server of claim 11, wherein the initial message further comprises Closed Subscriber Group (CSG) related information, and the CSG related information further comprises at least one of a CSG ID and a CSG access mode parameter of the Home (e)NodeB.

### Claim 14 (depends on 11)

The server of claim 11, wherein the access accept message is any one of an Attach Accept message, a Tracking Area Update (TAU) Accept message, and a Routing Area Update (RAU) Accept message, and
the initial setup message is an Initial context Setup message.

### Claim 15 (depends on 11)

The server of claim 11, wherein the indicator indicating whether the Home (e)NodeB supports a LIPA function is LIPA_capability_indicator, and
the indicator indicating whether the terminal can use a LIPA service at the Home (e)NodeB is LIPA_Available_indicator.

### Claim 16 (depends on 11)

The server of claim 11, wherein the controller performs the determination by further considering whether the terminal a Closed Subscriber Group (CSG) membership to the Home (e)NodeB.