NETWORK NODE

Cross-Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Patent Application No.

61/442,736 filed on February 14, 201 1 , entitled "SIPTO at H(e)NB Solution 1 - Using LIPA to Offload Traffic," the contents of which are incorporated by reference herein in its entirety.

Field of the Invention

[0002] The present invention relates generally to Selected IP Traffic Offload (SIPTO) in a wireless communication system, and more particularly, to using Local IP Access (LIPA) services to enable SIPTO at H(e)NB in the 3rd Generation Partnership Project (3GPP) Long- term Evolution (LTE) wireless communication systems.

Background

[0003] As one of the most recent in-building wireless initiatives, a femtocell ecosystem deploys one or more small Universal Mobile Telephone System (UMTS) base stations in homes or small businesses to enhance in-building cellular coverage where the macro cell signal is insufficient, or to provide localized capacity for data hungry customers. Femto-cells provide a number of benefits, such as significant offload of traffic from regular base stations in the macro network, full coverage and high speed transmission at home, better link quality, lower transmit power, higher performance, and so forth.

[0004] In 3 GPP terms, LTE femtocells are called Home Node B's (HNB) for UMTS terrestrial radio access network (UTRAN) and Home eNode B's (HeNB) for evolved UTRAN (E-UTRAN), collectively referred to as H(e)NB. The ability for H(e)NB to offload traffic from the macro network, both in Radio Access Networks (RANs) and in RAN backhaul across a subscriber's broadband internet link, is provided through two services: LIPA and SPITO, as detailed in the 3GPP specification, for example, 3GPP Release 10 or 1 1. In particular, LIPA grants a subscriber, while connected to the mobile operator's core network, simultaneous access to a residential or corporate IP network via the H(e)NB. SIPTO selectively routes different types of traffic to different destinations depending on predefined operator policies, and in doing so, SIPTO allows for traffic offloading from the mobile operator's core network to a defined IP network that is close to a point of attachment to the access point of a wireless device, for example, a User Equipment (UE) in LTE terms.

[0005] With increasing LTE terminal penetration and fixed-mobile convergence, the expected demand for LTE femtocells is likely to provide attractive services and rates in future home environments. Therefore, a need exists to further improve services centered around H(e)NB to achieve quick traffic offload as wells as easy network access.

Summary of the Invention

[0006] The presently disclosed embodiments are directed to solving issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings.

[0007] One embodiment is directed to a method for providing Selected IP Traffic

Offload (SIPTO) at a home network node, wherein the method includes: establishing a first Packet Data Network (PDN) connection for SIPTO in a macro network; establishing a second PDN connection for Local IP Access (LIP A) in a home network in communication with the macro network, the home network comprising the home network node in which SIPTO is enabled; and offloading traffic from the first PDN connection for SIPTO to the second PDN connection for LIPA.

[0008] In another embodiment, the invention provides a device that includes: a transceiver configured to send and receive wireless communication signals; and a processor coupled to the transceiver, the processor configured to receive a NAS message indicating that Selected IP Traffic Offload (SIPTO) is supported at a home network node, and in response to the NAS message, determine whether to accept traffic offloaded from a Packet Data Network (PDN) connection supporting SIPTO in a macro network to the home network node, wherein the device is configured with a Local IP Access (LIPA) connectivity supported by the home network node to have simultaneous access to traffic in the macro network and traffic in a home network centered around the home network node. [0009] In a further embodiment, a non-transitory computer readable storage medium comprising executable instructions that when executed cause a computer to: send a first message that Selected IP Traffic Offload (SIPTO) is supported at or above a Radio Access Network (RAN); establish a Packet Data Network (PDN) connection with SIPTO permission at or above the RAN in response to a request for SIPTO services at a home network node; and send a second message that SIPTO is supported at the home network node if the home network node also supports Local IP Traffic Access (LIPA) with one or more existing LIPA PDN connections.

[0010] Further features and advantages of the present disclosure, as well as the structure and operation of various embodiments of the present disclosure, are described in detail below with reference to the accompanying drawings.

Brief Description of the Drawings

[0011] The present disclosure, in accordance with one or more various embodiments, is described in detail with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict exemplary embodiments of the disclosure. These drawings are provided to facilitate the reader's understanding of the disclosure and should not be considered limiting of the breadth, scope, or applicability of the disclosure. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

[0012] Fig. 1 is a block diagram of an exemplary wireless communication system in which one or more disclosed embodiments may be implemented;

[0013] Fig. 2 is a simplified functional block diagram of exemplary communication networks that may be deployed within the wireless communication system of Fig. 1 ;

[0014] Fig. 3 shows exemplary system architecture of a wireless network configured to support LIPA;

[0015] Fig. 4 shows exemplary system architecture of a wireless network configured to support SIPTO;

[0016] Fig. 5 is a flow diagram of exemplary procedures for enabling SIPTO at a home network node that may be implemented in the wireless communication system of Fig. 1 ; [0017] Fig. 6 is a simplified functional block diagram of an exemplary base station that may be implemented in the wireless communication system of Fig. 1 ; and

[0018] Fig. 7 is a simplified functional block diagram of an exemplary wireless device that may be implemented in the wireless communication system of Fig. 1.

Detailed Description of Exemplary Embodiments

[0019] The following description is presented to enable a person of ordinary skill in the art to make and use the invention. Descriptions of specific devices, techniques, and applications are provided only as examples. Various modifications to the examples described herein will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other examples and applications without departing from the spirit and scope of the invention. Thus, the present invention is not intended to be limited to the examples described herein and shown, but is to be accorded the scope consistent with the claims.

[0020] The word "exemplary" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0021] Reference will now be made in detail to aspects of the subject technology, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.

[0022] It should be understood that the specific order or hierarchy of steps in the processes disclosed herein is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0023] Embodiments disclosed herein are directed to the provision of SIPTO at

H(e)NB by use of existing system architecture and features for both LIPA and SIPTO at or above RAN. More specifically, a method for SIPTO at H(e)NB is provided, which comprises establishing a packet data network (PDN) connection supporting SIPTO at or above RAN, in addition to a LIPA PDN connection, and offloading traffic from the PDN connection with SIPTO permission to the LIPA PDN connection. In one embodiment, NAS messages are exchanged between a user equipment (UE) within or in proximity of the home network centered around the H(e)NB and a mobility management entity (MME) regarding the availability of SIPTO at H(e)NB. In another embodiment, SIPTO at H(e)NB is enabled upon satisfaction of certain conditions, such as existing PDN connections with SIPTO permissions, LGW support at the H(e)NB, UE's LIPA capability and the operator policy allowing for SIPTO at H(e)NB. In yet another embodiment, the UE may accept or decline further traffic offload from the PDN connection with SIPTO permission to a LIPA PDN connection. It should be appreciated that the embodiments described herein are based on 3 GPP LTE specification by referring to the terms and concepts therein (e.g., H(e)NB, SIPTO, LIPA, etc.), the application of these embodiments are not so limited, but can include wireless communication systems using different standards other than LTE.

[0024] Fig. 1 is a block diagram of an exemplary wireless communication system 100 in which one or more disclosed embodiments may be implemented. This communication system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 is configured to enable multiple wireless users to access such content by sharing system resources, such as the wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and the like.

[0025] As shown in Fig. 1 , the wireless communication system 100 includes various communication networks, including a mobile operator's core network 1 10, a Public Switched Telephone Network (PSTN) 120, a Radio Access Network (RAN) 160, the Internet 140, and other networks 130. Particularly, in a residential or enterprise environment, a local IP network 150 may be deployed in communication with a global computer network, e.g., the Internet 140. Operating on these networks are different network equipments and devices, from base stations, such as eNode-B 162 and H(e)NB 152, to wired or wireless devices, such as mobile devices 164 and 154. It should be appreciated that Fig. 1 is for illustration only and the disclosed embodiments contemplate any number of wireless devices, base stations, networks, and/or network elements. [0026] The network devices 154 and 164 can be any type of device configured to transmit and/or receive wireless signals and operate in a wireless environment. For example, these devices may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a tablet computer, a personal computer, a wireless sensor, consumer electronics, and the like. Some of the network devices in the communication system 100 may include multi-mode capabilities, if configured with multiple transceivers for communicating with different wireless networks over different wireless links. For example, the device 154 may be configured to communicate with the H(e)NB 152 using the LTE radio technology, and with the local IP network 150 via an IEEE 802.1 1 radio technology.

[0027] The base stations 162 and 152 in Fig. 1 can be any type of device configured to wirelessly interface with at least one of the above-listed network devices to facilitate access to one or more communication networks, such as the core network 1 10, the Internet 140, and/or other networks 130. For example, these base stations may include a base transceiver station (BTS), a normal Node-B, an eNodeB, a Home Node B, a controller, an access point (AP), a wireless router, and so forth. Particularly, the base station 152 located on a residential or enterprise premises can be an FINB, which is a customer-premises equipment that connects a 3 GPP UE over UTRAN wireless air interface to a mobile operator's core network using a broadband IP backhaul, or an HeNB, which is a customer- premises equipment that connects a 3 GPP UE over E-UTRAN wireless air interface to a mobile operator's core network using a broadband IP backhaul. While the base stations in Fig. 1 are depicted as a single element, it should be appreciated that they each may include any number of interconnected base stations and/or network elements.

[0028] The base stations 162 and 152 may communicate with one or more of the network devices 164 and 154 over an air interface, such as the air interfaces 166 and 156, which can be any suitable wireless communication link, for example, radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light and so forth. The air interface can be established using any suitable Radio Access Technology (RAT). In one embodiment, the base stations and network devices may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface using Long Term Evolution (LTE) and/or LTE- Advanced (LTE- A). In another embodiment, the base stations and network devices may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0029] Additionally, in one embodiment, the base stations and network devices may implement a radio technology such as IEEE 802.1 1 to establish a wireless local area network (WLAN). In another embodiment, the base stations and network devices may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base stations and network devices may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell, such as the home-based network centered around the H(e)NB 152 in Fig.1.

[0030] As illustrated in Fig. 1, the base station 162 can be part of the RAN 160, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 162 is typically configured to transmit and/or receive wireless signals within a particular geographic region, which is referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 162 may be divided into three sectors. Thus, in one embodiment, the base station 162 may include three transceivers, one for each sector of the cell. In another embodiment, the base station 162 may employ multiple-input multiple output (MIMO) technology and utilize multiple transceivers for each sector of the cell.

[0031] The RAN 160 is configured to be in communication with the mobile operator's core network 110, which can be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to customers. For example, the core network 110 may provide call control, billing services, mobile location- based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in Fig. 1 , it should be appreciated that the RAN 160 and the core network 1 10 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 160 or a different RAT. For example, in addition to being connected to the RAN 160, which may be utilizing an E-UTRA radio technology, the core network 1 10 may also be in communication with another RAN (not shown) employing a GSM radio technology. [0032] The core network 1 10 can serve as a gateway for the network devices to access the PSTN 120, the Internet 140, and/or other networks 130. The PSTN 120 includes circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 140 comprises a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The Internet 140 can also be directly accessed by some of the network devices, such as the device 154 in a home network without going through the core network 1 10. Other networks 130 can be any wired or wireless communications networks owned and/or operated by other service providers. For example, the other networks 130 can be another mobile operator's core network connected to one or more RANs.

[0033] Turning to Fig. 2, provided is a simplified functional block diagram 200 showing exemplary communication networks that may be deployed in the wireless communication system 100. As shown in Fig. 2, the RAN 220 includes eNode-Bs 222a and 222b, although it should be appreciated that the RAN 220 may include any number of eNode- Bs in operation. The eNode-Bs 222a and 222b may each include one or more transceivers for communicating with network devices, such as the device 224. Alternatively, the eNode-Bs 222a and 222b may implement MIMO technology by using multiple antennas to transmit wireless signals to and from network devices. Each eNode-B may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. Also, the eNode-Bs may communicate with one another over an X2 interface.

[0034] The home-based network 230 is centered around the H(e)NB 232, which may communicate with network devices, such as the device 224, using radio access technologies similar to a normal eNode-B. As discussed above, the H(e)NB is typically deployed in a residential or enterprise environment to create a femtocell. In one embodiment, the H(e)NB 232 is configured to communicate with a H(e)NB gateway 218, which becomes part of the H(e)NB subsystem 234. Typically, the H(e)NB 232 is provided by an H(e)NB hosting party that has a contractual relationship with the operator with respect to the provision of access to the operator's core network, while the H(e)NB gateway 218 is provided by the operator and located on the mobile operator's premises, for example, as part of the core network 210. [0035] The core network 210, as shown in Fig. 2, includes a Mobility Management

Entity (MME) 212, a serving gateway 214, a Packet Data Network (PDN) gateway 216, and possibly, as noted above, the H(e)NB gateway 218 in case of providing femtocells. While each of the foregoing elements are depicted as part of the core network 210, it should be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.

[0036] The MME 212 is connected to each of the eNode-Bs 222a and 222b in the

RAN 220, as well as the H(e)NB 232 in the home-based network 230 via an S I interface. The MME 212 usually serves as a controller with various functions. For example, the MME 212 may be responsible for authenticating users of various network devices, bearer activation/deactivation, selecting a particular serving gateway during an initial discovery and acceptance of the network devices, and other related functions. The MME 212 may also provide a control plane function for switching between the RAN 220 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0037] The serving gateway 214 is also connected to each of the eNode-Bs 222a and

222b in the RAN 104 via the SI interface. The serving gateway 214 is configured to route and forward user data packets to/from different network devices. Besides, the serving gateway 214 may also perform functions such as anchoring user planes during inter- handovers, triggering paging when downlink data is available, managing and storing contexts of the network devices, and so forth. Also, the serving gateway 214 is connected to the PDN gateway 216, which provides the network devices with access to packet-switched networks, such as the Internet 1 10, so as to facilitate communications between the network devices, such as the device 224, and other IP-enabled devices.

[0038] The H(e)NB gateway 218 provides functions and configurations specific to the needs of a home base node, such as the H(e)NB 232. In one embodiment, the H(e)NB 232 may directly interface with the MME 212 and serving gateway 214 without the H(e)NB gateway.

[0039] Fig. 3 shows exemplary system architecture of a wireless network configured to support Local IP Access (LIP A). LIPA is a 3GPP initiative that allows a subscriber to access a residential or corporate subnet via a H(e)NB. With LIPA, a terminal, while connected to the mobile operator's core network, will also have simultaneous access to devices on the local IP subnet. As demonstrated in the system architecture 300, the terminal device 324, while being connected to the mobile operator's core network 310 via the H(e)NB 322, may have simultaneous access to the residential or enterprise IP network 320 and the devices thereon, such as the computer 325. In other words, the device 324 is allowed to have access to local IP traffic 326 relating to the local IP subnet 320 at almost the same time as it is accessing IP traffic 328 to and from the core network 310. In operation, the LIPA facility may be advertised by the H(e)NB to the subscribers. Roaming access to LIPA in a visited network is also an option, subject to roaming agreements between different operators. LIPA may require a single or multiple PDN connections for accessing the IP traffic. The 3GPP specification, e.g., 3GPP Release 10 or 1 1, contains detailed service requirements and procedures for LIPA.

[0040] Fig. 4 shows an exemplary wireless system 400 configured to support SIPTO services. SIPTO is an ability to selectively route different types of traffic originating from a terminal to different destinations depending on pre-defined operator policies. More specifically, SIPTO allows for traffic offload from the mobile operator's core network to a defined IP network that is close to a point of attachment to the access point of a wireless device, for example, a User Equipment (UE) in LTE terms. There are two flavors of SIPTO, home network SIPTO for traffic originating from the H(e)NB and macro network SIPTO for traffic originating from the eNode-B. The principle of SIPTO for the eNode-B in a macro network will be described below.

[0041] As shown in Fig. 4, the system 400 includes a user device 410 in communication with an eNode-B 420 that is located in a RAN 425. The eNode-B 420 is also in communication with the serving gateway (S-GW) 430 that is in communication with a local PDN gateway (L-PGW) 435 and a core network (CN) 440. The CN 440 includes an MME 445 and a PDN gateway (P-GW) 450. In operation, the device 410 communicates with the eNode-B 420 over a wireless air interface 455. The eNode-B 420 also communicates with the S-GW 430 over an Sl-U interface 460. The S-GW 430 communicates with the L- PGW 435 over an S5 interface 465, and also with the P-GW 450 over an S5 interface 470 and with the MME 445 over an SI 1 interface 475.

[0042] Also shown in Fig. 4 are two traffic streams: a SIPTO traffic stream 480 that is routed through the S-GW 430 to the L-PGW 435, and a CN traffic stream 485 that is routed through the S-GW 430 to the P-GW 450 in the CN 440. For traffic going through the mobile operator's core network, such as the traffic stream 485, the S-GW 430 user plane functions may be located within the CN 440. Mobility management signaling between the device 410 and the network may also be handled in the CN 440. Session management signaling, such as bearer setup, for SIPTO traffic 480 as well as the CN traffic 485 may terminate in the CN 440. A new offload point that is geographically or topologically close to the device 410 for SIPTO traffic may be re-selected during the device idle mode mobility procedures.

[0043] In order to perform SIPTO transfers from a macro network to a defined IP network, such as a local network or Intranet, a proper PDN connection is required. The device 410 may initiate a request to establish a PDN connection by setting an access point name (APN) to a specific value. The 3GPP specification, e.g., 3GPP Release 10 or 1 1 , contains detailed service requirements and procedures for SIPTO at or above RAN.

[0044] In one embodiment, the eNode-B 420 can be a H(e)NB configured to perform

SIPTO in a user's home network accessible to the device 410. In that case, traffic may be offloaded locally to the user's home network. As shown in Fig. 1 , the home network may be an IP network that is connected to other devices such as a printer, a television, and a personal computer, and all these nodes on the home network may use private addressing. Also, a local gateway, such as the H(e)NB gateway 218 in Fig. 2, can pe deployed in the H(e)NB subsystem to perform IP traffic offload based on the operator's] policy or configurations, for example, based on the IP address designation. In another embodiment, the system 400 may also be configured to provide LIP A for the H(e)NB. In that case, many existing features with regard to SIPTO at or above RAN can be applied to LIPA and SIPTO at the H(e)NB. For example, both SIPTO at or above RAN and LIPA require establishment of appropriate PDN connections, deployment behind network address translation (NAT), and the like.

[0045] The 3GPP specification, e.g., 3GPP Release 10 or 1 1, sets forth a number of service requirement for SIPTO at H(e)NB. For instance, SIPTO at H(e)NB should not traverse the mobile operator's core network, subject to other regulatory requirements. The mobile operator and the H(e)NB hosting party should be able to enable/disable SIPTO per H(e)NB, subject to provisions by the mobile operator. Also, based on mobile operator SIPTO policies, a user should be able to accept/decline offload before the traffic is offloaded. It is possible that the user has a different service experience if the traffic is offloaded via SIPTO for the H(e)NB subsystem. With respect to specific SIPTO policies, the mobile operator should be able to configure the SIPTO policies either statically or dynamically, and these SIPTO policies may be defined per APN, per IP Flow class under any APN, or per IP Flow class under a specific APN. [0046] Fig. 5 provides a flow diagram of exemplary procedures for enabling SIPTO at the H(e)NB by re-using existing system architecture and features associated with LIPA and SIPTO at or above RAN. In one embodiment, the exemplary SIPTO at H(e)NB procedure 500 can start with SIPTO at or above RAN in Step 510, where the MME in the core network or the eNodeB of a RAN may broadcast a message that SIPTO is supported in the macro network. Next, in Step 530, one or more appropriate PDN connections with SIPTO permissions are established at or above RAN. Presumably, the LIPA PDN connections already exist in the home network centered around the H(e)NB. Thus, once SIPTO at or above RAN is established, the MME may send a NAS message to a UE that SIPTO at H(e)NB is supported in Step 550. The NAS message may include such information as existing PDN connections with SIPTO permissions and an identification of the H(e)NB that the UE can access. The identified H(e)NB provides local gateway (LGW) support. The H(e)NB can be identified either by any S 1 NAS transport message or existing LIPA context information. Additional information in the NAS message may include the UE's LIPA subscription and Close Service Group (CSG) subscription information related to LIPA, and/or the operator policy for SIPTO at H(e)NB.

[0047] In an alternative embodiment, the SIPTO at H(e)NB procedure may start with a user's or UE's LIPA connectivity in Step 520, where the H(e)NB advertises to UEs that LIPA is supported in the home network or H(e)NB subsystem by the H(e)NB hosting party. Then, an appropriate PDN connection is established for LIPA in Step 540. With additional PDN connections with SIPTO permissions being established, the MME can send the NAS message to indicate the availability of SIPTO at H(e)NB in Step 550, as discussed above. In fact, once the above-listed requirements in 3 GPP with respect to SIPTO at H(e)NB are satisfied, the SIPTO service at H(e)NB can be triggered anytime upon a change in the established PDN connections.

[0048] The NAS message exchanged between the MME and UE can be one of the existing messages, such as a NAS message during attach or PDN connectivity procedures, or a newly-defined message. Given the service requirement that SIPTO policies be defined per APN, per IP Flow class under any APN or a specific APN, the NAS message can include further information such as APNs to be offloaded, TFTs associated with APNs to be offloaded and LIPA APN to carry the offloaded traffic. The NAS message may also include an alert whether the user wishes to accept or decline offload. This addresses the possibility that a user may wish to decline a network-initiated offloading request and stay with SIPTO at or above RAN. If the user accepts the offload request, the UE can start traffic offload by, for example, establishing a LIPA PDN connection to start diverting traffic.

[0049] Once the CN PDN connections with SIPTO permissions and LIPA PDN connections are established to support SIPTO at H(e)NB, the UE can offload the traffic from a CN PDN connection to a LIPA PDN connection in Step 560. The UE can further decide what traffic to be offloaded based on various information, such as the traffic originally sent on the CN PDN connection, a static local policy dictating the traffic pattern, a semi-static network policy from ANDSF,.or a dynamic policy from the NAS message from MME. In doing so, the UE may be configured with enhanced APN bundling capabilities. In addition, the UE may support traffic re-routing in order to reverse the offloaded traffic back to the CN PDN connection in case that the local network has a strict firewall policy or bad throughput due to a different route, which can be determined by monitoring a traffic timeout and traffic throughput, or from an ICMP destination unreachable message when the traffic is sent on a LIPA PDN connection.

[0050] As seen from the above, the exemplary procedure 500 for SIPTO at H(e)NB uses existing system architecture and features for both LIPA and SIPTO at or above RAN. SIPTO at H(e)NB can start with a PDN connection for SIPTO at or above RAN, followed by a LIPA PDN connection to offload the traffic at H(e)NB, or the other way around. NAS messages are exchanged between the UE and MME regarding the availability of SIPTO at H(e)NB, subject to certain conditions, such as existing PDN connections with SIPTO permissions, LGW support at the H(e)NB, UE's LIPA capability, the operator policy for SIPTO at H(e)NB, and the like. In one embodiment, the user may accept or decline further traffic offload from a CN PDN connection with SIPTO permission to a LIPA PDN connection. The UE's LIPA PDN connectivity can be established in response to a NAS message from MME or out of its self initiative.

[0051] Fig. 6 is a simplified functional block diagram of an exemplary base station that may be implemented in the wireless communication system of Fig. 1. For example, the base station 600 can be the eNode-B or H(e)NB in Fig. 1. It should be noted that certain portions of the base station 600 will be described, while other portions of the base station 600 are omitted for the purposes of brevity and clarity. [0052] As shown in Fig. 6, the base station 600 includes an antenna 602 coupled to an output of a transmitter 610 as well as to an input of a receiver 620. The transmitter 610 is couple to one or more power amplifiers (PA) 612. A downlink signal processor 630 is coupled to the transmitter 610 for downlink transmission from the base station. More specifically, the DL signal processor 630 is typically coupled to an input of one or more multiplexers (not shown) and the active multiplexer path, as determined by a scheduler 660 coupled to the processor 630, is coupled to the transmitter 610 for downlink transmission. The scheduler 660, as a time management unit in the base station, is coupled to a system clock 662. A controller 640 is coupled to the DL signal processor 630. Typically, the controller 640 is configured to control the performance of the base station by coordinating different computing and processing tasks. In one embodiment, the controller 640 is coupled to or configured with a number of service modules 642 including, for example, service requirements or operator policies with respect to LIPA and SIPTO. An Input/Output administrative interface 650 is coupled to the controller 640. It usually serves as an interface between the base station 600 and other network elements.

[0053] Fig. 7 is a simplified functional block diagram of an exemplary wireless network device that may be implemented in the wireless communication system of Fig. 1. For example, the device 700 can be the network device 154 or 164 in Fig. 1. It should be noted that certain portions of the device 700 will be described, while other portions of the device 700 are omitted for the purposes of brevity and clarity.

[0054] As shown in Fig. 7, the device 700 includes a processor 730 coupled to a transceiver 720 that is connected to a transmit/receive element 710. Also coupled to the processor 730 are the following components: an ASIC chipset 731, a power source 732, different peripherals 733, a memory 734, a speaker/microphone 735, a display or touch screen 736 and a keypad or switch or any other physical input mechanism 737. It should be appreciated that the above-listed elements are for illustration only and the device 700 may include any sub-combination of the foregoing elements or additional elements.

[0055] The transmit/receive element 710 is typically configured to transmit signals to, or receive signals from, a base station over the air interface 712. For example, in one embodiment, the transmit/receive element 710 is an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 710 can be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. The transmit/receive element 710 may also be configured to transmit and receive both RF and light signals. It should be appreciated that the transmit/receive element 710 may be configured to transmit and/or receive any combination of wireless signals. In addition, although the transmit/receive element 710 is depicted in Fig. 7 as a single element, the device 700 may include any number of transmit/receive elements. More specifically, the device 700 may employ MIMO technology so that two or more transmit/receive elements 710 (e.g., multiple antennas) are employed for transmitting and receiving wireless signals.

[0056] The transceiver 720 is configured to modulate the signals to be transmitted by the transmit/receive element 710 and to demodulate the signals that are received by the transmit/receive element 710. As noted above, the device 700 may have multi-mode capabilities. Thus, the transceiver 720 may include multiple transceivers for the device 700 to communicate via multiple RATs, such as UTRA and IEEE 802.1 1.

[0057] The processor 730 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 730 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the device 700 to operate in a wireless environment. Although Fig. 7 depicts the processor 730 and the transceiver 720 as separate components, it should be appreciated that they may also be integrated together in an electronic package or chip.

[0058] The processor 730 is coupled to the ASIC chipset 731 providing specific application capabilities. For example, the chipset 731 may provide a GPS function regarding the current location of the device 700.

[0059] The processor 730 is configured to receive power from the power source 732, and further, to distribute and/or control the power to the other components in the device 700. The power source 732 may be any suitable device for powering the device 700. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like. [0060] The processor 730 may also be coupled to other peripherals 733, including one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 733 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth.RTM module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0061] The processor 730 is configured to have access to the memory 734, which can be any type of suitable memory, such as random-access memory (RAM), read-only memory (ROM), a hard disk, a subscriber identity module (SIM) card, a flash memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 730 may also access information from, and store data in, remote memory space that is not physically located on the device 700, such as on a server or a home computer (not shown).

[0062] The processor 730 is further configured to receive user input data from the speaker/microphone 735, the keypad or physical input mechanism 737, and/or the display or touch screen 736, e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit. These components can also be used for the processor 730 to output certain user data in some embodiments.

[0063] While various embodiments of the invention have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or other configuration for the disclosure, which is done to aid in understanding the features and functionality that can be included in the disclosure. The disclosure is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, although the disclosure is described above in terms of various exemplary embodiments and implementations, it should be understood that the various features and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described. They instead can be applied alone or in some combination, to one or more of the other embodiments of the disclosure, whether or not such embodiments are described, and whether or not such features are presented as being a part of a described embodiment. Thus the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. [0064] In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the invention.

[0065] In this document, the terms "computer program product", "computer-readable medium", and the like, may be used generally to refer to media such as, memory storage devices, or storage unit. These, and other forms of computer- readable media, may be involved in storing one or more instructions for use by processor to cause the processor to perform specified operations. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system.

[0066] It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0067] Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term "including" should be read as meaning "including, without limitation" or the like; the term "example" is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; and adjectives such as "conventional," "traditional," "normal," "standard," "known", and terms of similar meaning, should not be construed as limiting the item described to a given time period, or to an item available as of a given time. But instead these terms should be read to encompass conventional, traditional, normal, or standard technologies that may be available, known now, or at any time in the future. Likewise, a group of items linked with the conjunction "and" should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as "and/or" unless expressly stated otherwise. Similarly, a group of items linked with the conjunction "or" should not be read as requiring mutual exclusivity among that group, but rather should also be read as "and/or" unless expressly stated otherwise. Furthermore, although items, elements or components of the disclosure may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated. The presence of broadening words and phrases such as "one or more," "at least," "but not limited to", or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent.

[0068] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the invention. It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0069] Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processing logic element. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined. The inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate.