WO2012136762A1

WO2012136762A1 - Local network identifier for local internet protocol access

Info

Publication number: WO2012136762A1
Application number: PCT/EP2012/056275
Authority: WO
Inventors: Gyorgy Tamas Wolfner; Seppo Ilmari Vesterinen; Wolfgang Hahn; Robert Zaus
Original assignee: Nokia Siemens Networks Oy
Priority date: 2011-04-06
Filing date: 2012-04-05
Publication date: 2012-10-11

Abstract

A local network identifier can be used to identify a local internet protocol network (for example, residential or Enterprise networks) to which a user can be connected via a local internet protocol access connection. The local network identifier can be used as a criterion for selecting a local gateway and for performing handover when the user moves between home base stations.

Description

DESCRIPTION TITLE:

Local Network Identifier for Local Internet Protocol Access

CROSS-REFERENCE TO RELATED APPLICATION:

[0001] The present application is related to, claims the priority of, and incorporates by reference the entirety of U.S. Provisional Patent Application No. 61/472,433 filed April 6, 201 1.

BACKGROUND:

Field:

[0002] A local network identifier can be used to identify a local internet protocol network (for example, residential or Enterprise networks) to which a user can be connected via a local internet protocol access connection. The local network identifier can be used as a criterion for selecting a local gateway and performing handover when the user moves between home base stations.

Description of the Related Art:

[0003] Third Generation Partnership Project (3GPP) Release 10 (Rel-10) may include local internet protocol (IP) access (LI PA) functionality in universal terrestrial radio access network (UTRAN) and enhanced UTRAN (E-UTRAN) systems. This feature can enable access of local IP networks from femto cells, which are sometimes called Home NodeBs (HNB) and Home eNodeBs (HeNB). More specifically, local IP access can enable IP capable user equipment (for example, laptops, smart phones, and portable devices) connected via a HNB or HeNB to access other IP capable entities in the same residential/enterprise IP network without the user plane traversing the mobile operator's network.

[0004] In Rel-10 the H(e)NB and the Local Gate Way (LGW), which provides the connectivity to the local IP network, are collocated and the local IP access connection is released when the user equipment (UE) leaves the coverage of the femto cell from where the local IP access packet data network (PDN) connection was established.

[0005] In Release 1 1 (Rel-1 1) mobility support may be added. In Rel-11 , the local IP access feature may be enhanced by allowing a standalone local gateway and the local IP access connection to hand over between H(e)NBs connected to the same local network.

[0006] In Rel-10 the network uses the collocated local gateway address, which is sent by the H(e)NB to the MME/SGSN, to discover when the user equipment leaves the original cell. Because in Rel-11 the local gateway can be a standalone device and there can be more than one local gateway in a local network, this method is no longer applicable.

[0007] In 3GPP specifications the Closed Subscriber Group (CSG) identifier is used to identify a group of femto cells providing access to the same group of users. However it is not clear whether a group of femto cells identified by a closed subscriber group identifier is connected to the same local network. Some deployment scenarios can exist in which a group of femto cells identified by a closed subscriber group is not connected to the same local network. An example when the closed subscriber group identifier cannot be used to decide whether H(e)NBs are connected to the same network is a local IP access deployment scenario when cafes belonging to the same brand provide local services (e.g., printing) and Internet access to their users via local IP access. In this case, use of the same closed subscriber group identifier in all shops avoids the need of registrations of a user in a lot of closed subscriber groups when the user becomes a customer of that cafe. On the other hand, the local networks of different cafes may not be connected to each-other, because local services are local to the particular cafe, e.g., there is no need to access printers of other cafes from a given cafe.

SUMMARY:

[0008] In certain embodiments, a method includes receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The method also includes conditionally permitting or rejecting the request based on a local network identifier.

[0009] According to certain embodiments, a method includes receiving a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The method also includes conditionally releasing the connection based on a local network identifier.

[0010] A method, in certain embodiments, includes receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station. The method further includes conditionally establishing the connection based on a local network identifier.

[001 1] An apparatus, according to certain embodiments, includes at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to receive a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The at least one memory and computer program code are also configured to, with the at least one processor, cause the apparatus at least to conditionally permit or reject the request based on a local network identifier.

[0012] In certain embodiments, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to receive a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The at least one memory and computer program code are also configured to, with the at least one processor, cause the apparatus at least to conditionally release the connection based on a local network identifier.

[0013] According to certain embodiments, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to receive a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station. The at least one memory and computer program code are also configured to, with the at least one processor, cause the apparatus at least to conditionally establish the connection based on a local network identifier.

[0014] An apparatus, according to certain embodiments, includes receiving means for receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The apparatus also includes decision means for conditionally permitting or rejecting the request based on a local network identifier.

[0015] An apparatus, in certain embodiments, includes receiving means for receiving a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The apparatus also includes decision means for conditionally releasing the connection based on a local network identifier.

[0016] According to certain embodiments, an apparatus includes receiving means for receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station. The apparatus also includes decision means for conditionally establishing the connection based on a local network identifier.

[0017] A non-transitory computer-readable medium is, in certain embodiments, encoded with instructions that, when executed in hardware, perform a process. The process includes receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The process also includes conditionally permitting or rejecting the request based on a local network identifier.

[0018] A non-transitory computer-readable medium, according to certain embodiments, is encoded with instructions that, when executed in hardware, perform a process. The process includes receiving a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The process also includes conditionally releasing the connection based on a local network identifier.

[0019] In certain embodiments, a non-transitory computer-readable medium is encoded with instructions that, when executed in hardware, perform a process. The process includes receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station. The process also includes conditionally establishing the connection based on a local network identifier.

BRI EF DESCRIPTION OF THE DRAWI NGS:

[0020] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0021] Figure 1 illustrates an example call flow during establishment of a connection according to certain embodiments of the present invention.

[0022] Figure 2 illustrates an example call flow during a handover procedure according to certain embodiments of the present invention.

[0023] Figure 3 illustrates an architecture in which the local network identifier according to certain embodiments of the present invention can be used.

[0024] Figure 4 illustrates successive handovers of a user equipment according to certain embodiments of the present invention.

[0025] Figure 5 illustrates an example of deactivation due to a user equipment moving out of a local internet protocol access area in accordance with certain embodiments of the present invention.

[0026] Figure 6 illustrates an X2 based handover with the target Home eNodeB admitting local IP access bearer.

[0027] Figure 7 illustrates an X2 based handover with the target Home eNodeB rejecting local IP access bearer.

[0028] Figure 8 illustrates a system according to certain embodiments of the present invention.

[0029] Figure 9 illustrates a method according to certain embodiments of the present invention.

[0030] Figure 10 illustrates another method according to certain embodiments of the present invention.

DETAILED DESCRI PTION:

[0031] A problem in Rel-1 1 is how the 3GPP network can decide at a handover if the target H(e)NB is connected to the same local network as the source and thus the local I P access connection can be kept during the handover. [0032] An identifier of the H(e)NB {e.g., cell identifier) might be applicable in some cases, but the use of such an identifier would require the knowledge of the local network connectivity (e.g., which H(e)NBs are connected to the same local network) by the 3GPP operator. As the local network configuration and deployment is out of the scope of the 3GPP operators, this can be difficult. Moreover in the architecture there is a Home NodeB GateWay (H NBGW) that hides the individual HNBs from the core network, making HNB identification difficult.

[0033] According to certain embodiments, therefore, an identifier that is available in all cases and can be easily used is presented. This new identifier, called a local network identifier, identifies the local network within a closed subscriber group identifier.

[0034] The H(e)NB can receive this local network identifier as a part of its configuration data. The H(e)N B can provide this local network identifier to the 3GPP network either when it is connected or whenever a relevant signaling message is sent to the network (e.g., in the same messages when the local gateway address is sent in Rel-10 specifications).

Providing this local network identifier allows the 3GPP network to decide if the local I P access packet data network connection can hand over (HO) during idle and connected mode mobility procedures.

[0035] As an option, the local network identifier can also be exchanged during X2 handover between HeNBs to decide if the local packet data network connection should be subject to handover.

[0036] In another option the H(e)NB can learn/store the local network identifier from the neighboring H(e)NBs to facilitate a RAN based decision for local I P access packet data network connections maintenance in case of handover.

[0037] The local network identifier can make it both possible and simple for the 3GPP network elements (e.g., for the mobility management entity (MME) and serving general packet radio service (GPRS) support node (SGSN)) to identify the local network to which the user equipment can be connected. This can permit the 3GPP network to decide when the local I P access connection can be kept during a mobility event.

[0038] There are various possibilities for the local network identifier. For example, the form of this identifier can be a domain name. For example, usually when an I P host is connected to an I P network it receives the local domain as a part of the I P configuration. In another embodiment the local network identifier can be any unique numerical value. For example, the I P address of the default gateway in the network, which is also a part of the I P configuration data, can be used as the local network identifier. The format and the value of the local network identifier can be varied, but it can be unique within a closed subscriber group identifier.

[0039] Certain embodiments of the present invention can be variously implemented. In general, in 3GPP networks (NWs), the mobility management entity typically selects the gateway (GW) by a domain name server (DNS) based approach. The DNS may be a single point of managing the addresses of the different GWs. For local IP access in Rel.10, the HeNB sent the GW address (for the S5 based signaling) to the mobility management entity. There are two reasons why this was done. First, there was no apparent need for a GW selection as the GW was co-located with the HeN B. Second, there was also a simple solution for managing the IP addresses of the local GW: the HeNB could, for example, use its own signaling address received for the S1 interface (after connecting to the security GW in the operators NW). In Rel. 1 1 , however, a local standalone GW is introduced.

[0040] Using a DNS based approach could have the advantages of a unified solution with other (non local) GW selection and benefits for management as well as the flexibility to allow several local GWs in the local network. To achieve such advantages, among other things, a local network identifier can be provided. The local network identifier can be used in the mobility management entity instead of or in connection with the access point name (APN) of the local I P access connection for the DNS query as described below. In 3G, the HNB may enhance the APN in NAS signaling with the local network identifier, as it already encrypted the NAS signaling.

[0041] The local network management system can provision the local network identifier to the HeNBs and local GWs. The local GW can update the operator DNS after a security procedure with the security gateway (SecGW) when it receives its S5 address.

[0042] Figure 1 illustrates an example call flow during establishment of a connection according to certain embodiments of the present invention. The example call flow in Figure 1 demonstrates how a local network identifier can be used during the establishment of a local IP access connection.

[0043] As illustrated in Figure 1 , at S1 a user equipment requests a packet data network connection establishment. Then, at S2, the HeNB sends the packet data network connection establishment request to the mobility management entity, including the closed subscriber group identifier and the local network identifier in the message.

[0044] Subsequently, at S3, the mobility management entity checks whether the user equipment is authorized to use the given closed subscriber group for local IP access services with the given APN, based on the subscription data and received closed subscriber group identifier and APN information. After that, at S4, the mobility management entity selects a local gateway. An option is that a fully qualified domain name (FQDN) is created, for example, in the following way: LocalNetworkld.CSGid.APN.operator_domain. Then this FQDN is used to obtain the IP address of the appropriate local gateway via DNS.

[0045] At S5, the mobility management entity sends the packet data network creation request to the SGW. Next, at S6, the SGW forwards the packet data network creation request to the local gateway. Finally, at S7, the packet data network connection establishment continues as it is specified in 23.401 . [0046] Figure 2 illustrates an example call flow during a handover procedure according to certain embodiments of the present invention. The example call flow in Figure 2 demonstrates how the local network identifier can be used during a handover procedure.

[0047] As illustrated in Figure 2, at S1 , the Source HeNB makes a handover decision. Then, at S2, the Source HeNB sends a Handover Request to the Target HeNB via an X2 interface including the local gateway address and the local network identifier. Next, at S3, the Target HeNB checks if the given local network is supported.

[0048] Subsequently, at S4, the X2-based handover procedure is performed if the outcome of the checking in the previous step is positive. Then, at S5, the Target HeNB sends a Path Switch request to the mobility management entity including the closed subscriber group identifier and the local network identifier. Next, at S6, the mobility management entity may check if the local I P access connection handover was authorized based on the given closed subscriber group identifier and local network identifier. Operators may prefer this type of checking in the core network, as they have limited trust in the HeNBs. Finally, at S7, a path switch procedure is performed.

[0049] It is assumed that a HeNB can reach all local gateways of the same local network identifier. So, for a handover decision of a local I P access connection, the check for support of the same local network identifier is sufficient. Additional identifiers could be provided if this assumption is not correct.

[0050] Figure 3 illustrates an architecture in which the local network identifier according to certain embodiments of the present invention can be used. As illustrated in Figure 3, a local network identifier may be useful in a network that is divisible into a local or enterprise network and an operator core network. The local/enterprises network may be concealed from the operator by a security gateway (SEC GW), although there may be limited additional interaction via DNS updates, local network identifier, and IP address being provided to a domain name server in the operator core network from the local gateway in the local/enterprise network. As shown in Figure 3, the mobility management entity can query the domain name server with local network identifier. The mobility management entity can receive the local network identifier through the security gateway, which provides secured communication for the signaling traffic on the S1-C and S5 interface between the un-trusted local/Enterprise network and the operator core network. For access to the DNS server, security measures may be in place as well.

[0051] It should be noted that there are different types of handovers, and embodiments of the invention can apply to each of them. For example, in S1 interface based handovers, a Core Network element (Serving mobility management entity) may control local I P access mobility based on a Closed Subscriber Group (CSG) associated to the local I P access subscription. An S1 based handover may imply that the user equipment moves to a macro network, that is, out of closed subscriber group and Local I P Network. [0052] In another example, X2 based handover works autonomously at the E-UTRAN level. That is, an X2 based handover can rely on information exchanged between HeNBs. Even if the handover is made at a Radio Access Network (RAN) level, some kind of criteria can be used to decide whether handover is to be performed or not.

[0053] A Closed Subscriber Group (CSG) identifies a group of subscribers who are permitted to access one or more closed subscriber group cells of the public land mobile network (PLMN) as a member of the closed subscriber group for a HeNB. Local IP access is supported for APNs that are valid only when the user equipment is connected to a specific closed subscriber group. If HeNBs are in "Closed" closed subscriber group mode, then Handover is not allowed.

[0054] A standalone Local Gateway for the local I P access architecture can replace a Local Gateway that is co-located with the HeN B. When a user equipment requests a local I P access bearer, a packet data network connection is established and terminates in the standalone L-GW, where it is assigned an I P address.

[0055] Figure 4 illustrates successive handovers of a user equipment according to certain embodiments of the present invention. As illustrated in Figure 4, a user equipment (UE) moves from left to right and its local I P access bearer is handed over successively from H(e)NB to H(e)NB, as each of the H(e)NBs is associated with the same L-GW.

[0056] In theory, handover to HeNBs which are connected to different standalone L-GWs is possible, but L-GW change would seem to mean break of the local I P access packet data network connection/related bearer service. For example, a user equipment's IP address would seem to need to change in L-GW relocation. Thus, the local I P access packet data network connection would be released in conjunction of the Inter HeNB Handover procedure. However, non-local I P access packet data network connection/related bearer services via P-GW in the EPC could work seamlessly, as the S-GW and P-GW anchor remains unchanged in the core.

[0057] In mobility procedures it may not matter whether the L-GW is standalone or not, as the same procedure can be applied in both cases. The criterion as to whether handover can be performed can be based on whether the target HeNB has I P connectivity over a direct Sxx tunnel to the L-GW (may be co-located in the Source HeNB or a stand-alone L-GW). Thus, to be able to decide whether the local IP access connection can be handed over to a target RAN node (HeNB), there a local network identifier can be used to indicate that the local network and thus the L-GW is reachable from the target RAN-node at the Transport Network (IP) layer, that is that there is I P connectivity between these entities.

[0058] The local I P access subscription can be based on a closed subscriber group identifier but local I P access subscription or other conventional information at the Radio Network layer may not be enough to indicate that the L-GW is reachable from the target RAN-node at the Transport Network layer. [0059] The Closed Subscriber Group (CSG) itself does not provide an alternative either, because there may be for example several local networks behind the same closed subscriber group identifier. If there were a 1 : 1 relation between the closed subscriber group and local network, the closed subscriber group identifier could be used to determine whether handover can be performed. However, this is not always the case because a single closed subscriber group might span several local I P networks, such as in the case of a chain of cafes, as discussed above.

[0060] There may also be a need for the 3GPP mobile operator to keep control of the local IP access mobility decisions. The 3GPP operator may not manage the local networks and consequently may not automatically have information about the local networks of the target HeNB. The use of the local network identifier can permit the 3GPP operator to make the appropriate decisions without having access to the local networks.

[0061] The local network identifier discussed above can be used in various ways. For example, the local network identifier can be used in local IP access connection

establishment and as handover criteria. Thus, for example, the handover can be performed when the local network identifier's match, and/or the Local Gateway is reachable based on User Layer tunnel endpoint parameters towards the L-GW. Additionally, the local network identifier can be used as a criterion for releasing the session.

[0062] Figure 5 illustrates an example of deactivation due to a user equipment moving out of a local internet protocol access area in accordance with certain embodiments of the present invention.

[0063] As illustrated in Figure 5, the HeNB deactivates local I P access E-RAB prior to Handover and sends E-RAB Release Indication to the EPC. Criteria to local I P access E-RAB release could be mismatch in target closed subscriber group identifier, local network identifier etc. that the HeNB knows based on configuration or by learning from its neighbor HeNBs (using X2 interface). The user equipment can delete local I P access EPS Bearer context locally. As local I P access Bearer Related resources are released both in the user equipment and HeNB, there is no need to signal anything from the EPC to the E-UTRAN. If there is need for handover, execution of the handover can start without delay in the HeNB after message 1 c is sent to the mobility management entity.

[0064] The mobility management entity can take care of releasing resources in the EPC nodes and the L-GW. A change in the mobility management entity can be made in order to deactivate whole packet data network connection.

[0065] Figure 6 illustrates an X2 based Inter HeNB handover, target (H)eN B admitting local IP access bearer. Figure 7 illustrates an X2 based Inter HeNB handover, target (H)eNB rejecting local I P access bearer.

[0066] The source HeNB can include local network identifier, uplink (UL) tunnel endpoint parameters towards the target HeNB in the Handover Request message (step 1). Based on the information from the source HeNB, the Target HeNB detects whether L-GW is reachable and local I P access service can be continued

[0067] Note, the source HeNB can already know the closed subscriber group identifier of the Target HeNB based on information exchange in the X2 connection setup, which can happen prior to handover. If local I P access service cannot be continued, the Target (H)eNB does not configure local I P access E-RAB resources. An RRC Handover

Command from the source HeNB can release the local I P access Bearer resources so that the user equipment can delete the related EPS bearer locally, as the Radio Bearer is not in use any more in the target.

[0068] The mobility management entity can detect, from message 5a, that the local I P access E-RAB is released in the target (H)eNB and can initiate local I P access packet data network connection deactivation in the EPC nodes and L-GW. Thus, there is no need to signal anything more from the EPC to the E-UTRAN as the local I P access resources are already released in the E-UTRAN and the user equipment.

[0069] Certain embodiments of the present invention may have various advantages. For example, certain embodiments can enable seamless handover for a local I P access packet data network connection without unnecessary release of the connection, which can lead to a better user experience. Certain embodiments can permit a 3GPP mobile network operator to maintain control of local I P access mobility.

[0070] Figure 8 illustrates a system according to certain embodiments of the present invention. As shown in Figure 8, the system can include a user equipment 810. The user equipment 810 can include various components, such as at least one processor 820 and at least one memory 830. The user equipment 810 can be configured to initially connect to a source home base station 840. Subsequently, the user equipment 810 can be handed over to a target home base station 850. A mobility management entity 860 in a core network can supervise the handover, particularly in terms of path switching.

[0071] As shown in Figure 8, the source home base station 840, target base station 850, and mobility management entity 860, like the user equipment 810, can include various components, such as at least one processor 820 and at least one memory 830.

[0072] Figure 9 illustrates a method according to certain embodiments of the present invention. As illustrated in Figure 9, a method can include, at 910, receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The method can also include conditionally permitting (at 920) or rejecting (at 930) the request based on a local network identifier.

[0073] Figure 10 illustrates a method according to certain embodiments of the present invention. As illustrated in Figure 10, a method can include receiving, at 1010, a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station. The method can also include conditionally releasing the connection based on a local network identifier, namely granting (at 1020) the request when the local network identifier matches or refusing (at 1030) the request when the local network identifier does not match.

[0074] In certain embodiments, a method includes receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station that provides a local network identifier as a basis for local gateway selection.

[0075] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. For a determination of the scope, reference should be made to the appended claims.

Claims

CLAIMS What is claimed is:

1. A method, comprising:

receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

conditionally permitting or rejecting the request based on a local network identifier.

2. The method of claim 1 , wherein permitting the request conditionally occurs when the source home base station and the target home base station have the same local network identifier.

3. The method of claim 1 , wherein rejecting the request conditionally occurs when the source home base station and the target home base station have a different local network identifier.

4. A method, comprising:

receiving a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

conditionally releasing the connection based on a local network identifier.

5. The method of claim 4, wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same local network identifier.

6. The method of claim 4, wherein the releasing is further conditionally based on a closed subscriber group identification.

7. The method of claim 6, wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same closed subscriber group identification.

8. A method, comprising:

receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station; and

conditionally establishing the connection based on a local network identifier.

9. The method of claim 8, further comprising:

selecting a local gateway based on the local network identifier.

10. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to

receive a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

conditionally permit or reject the request based on a local network identifier.

11. The apparatus of claim 10, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to conditionally permit the request when the source home base station and the target home base station have the same local network identifier.

12. The apparatus of claim 10, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to conditionally reject the request when the source home base station and the target home base station have a different local network identifier.

13. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

receive a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

conditionally release the connection based on a local network identifier.

14. The apparatus of claim 13, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to conditionally release the local internet protocol access packet data network connection when the source home base station and the target home base station have the same local network identifier.

15. The apparatus of claim 13, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to further condition the release of the request based on a closed subscriber group

identification.

16. The apparatus of claim 15, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to conditionally release the local internet protocol access packet data network connection when the source home base station and the target home base station have the same closed subscriber group identification.

17. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

receive a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station; and

conditionally establish the connection based on a local network identifier.

18. The apparatus of claim 17, wherein the at least one memory and computer program code are configured to, with the at least one processor, cause the apparatus at least to select a local gateway based on the local network identifier.

19. An apparatus, comprising:

receiving means for receiving a request for handing over of a local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

decision means for conditionally permitting or rejecting the request based on a local network identifier.

20. The apparatus of claim 19, wherein permitting the request conditionally occurs when the source home base station and the target home base station have the same local network identifier.

21. The apparatus of claim 19, wherein rejecting the request conditionally occurs when the source home base station and the target home base station have a different local network identifier.

22. An apparatus, comprising:

receiving means for receiving a request for releasing a local internet protocol access packet data network connection in connection with handing over of the local internet protocol access packet data network connection of a user equipment from a source home base station to a target home base station; and

decision means for conditionally releasing the connection based on a local network identifier.

23. The apparatus of claim 22, wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same local network identifier.

24. The apparatus of claim 22, wherein the releasing is further conditionally based on a closed subscriber group identification.

25. The apparatus of claim 24, wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same closed subscriber group identification.

26. An apparatus, comprising:

receiving means for receiving a request for establishing of a local internet protocol access packet data network connection from a user equipment and home base station; and decision means for conditionally establishing the connection based on a local network identifier.

27. The apparatus of claim 26, further comprising:

selection means for selecting a local gateway based on the local network identifier.

28. A non-transitory computer-readable medium encoded with instructions that, when executed in hardware, perform a process, the process comprising:

29. The non-transitory computer-readable medium of claim 28, wherein permitting the request conditionally occurs when the source home base station and the target home base station have the same local network identifier.

30. The non-transitory computer-readable medium of claim 28, wherein rejecting the request conditionally occurs when the source home base station and the target home base station have a different local network identifier.

31. A non-transitory computer-readable medium encoded with instructions that, when executed in hardware, perform a process, the process comprising:

conditionally releasing the connection based on a local network identifier.

32. The non-transitory computer-readable medium of claim 31 , wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same local network identifier.

33. The non-transitory computer-readable medium of claim 31 , wherein the releasing is further conditionally based on a closed subscriber group identification.

34. The non-transitory computer-readable medium of claim 33, wherein releasing the local internet protocol access packet data network connection conditionally occurs when the source home base station and the target home base station have the same closed subscriber group identification.

35. A non-transitory computer-readable medium encoded with instructions that, when executed in hardware, perform a process, the process comprising:

conditionally establishing the connection based on a local network identifier.

36. The non-transitory computer-readable medium of claim 35, the process further comprising:

selecting a local gateway based on the local network identifier.