MANAGING A DATA NETWORK CONNECTION FOR MOBILE COMMUNICATIONS BASED ON USER LOCATION

专利摘要:
managing a data network connection for mobile communications based on user location. provision for selecting sipto in a mobile communication environment is described here. by way of example, sipto traffic can be facilitated through pgws that provide an interface to the internet or a similar data network, in addition to a centralized ggsn. eligibility for sipto may be eu by eu; for example, relying on stored account or subscription information to determine eligibility for sipto may also be based on packet network by packet network, or a combination of the above. this allows flexibility in determining whether sipto can be established for a given eu at a given location and can be based, for example, on eu capacity, subscription status information, data network capacity, tariff rates, and so on, in addition to legal requirements different from government jurisdictions.
公开号:BR112012013309B1
申请号:R112012013309-8
申请日:2010-12-03
公开日:2021-08-10
发明作者:Gavin Bernard Horn；Gerardo Giaretta；Miguel Griot；Osok Song
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

Priority Claim under 35 U.S.C. § 119
[0001] This patent application claims priority from provisional patent application No. 61/266,897 entitled "MANAGING A PDN CONNECTION BASED ON USER LOCATION", and filed on December 4, 2009, assigned to the assignee of this application and expressly incorporated herein by reference. Background Field
[0002] The following description generally refers to wireless communications, and more particularly to the ease of wireless communication for endpoints experiencing significant wireless interference. Background
[0003] Wireless communication systems are widely developed to provide various types of communication content, such as voice content, data content, and so on. Typical wireless communication systems may be multiple access systems capable of supporting communication with multiple users by sharing available system resources (eg bandwidth, transmission power, etc.). Examples of such multiple access systems may include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA) systems, time division multiple access systems. orthogonal frequency division (OFDMA), and the like. Additionally, systems can conform to specifications such as third-generation partnership project (3GPP), long-term evolution 3GPP (LTE), ultra mobile broadband (UMB), or multi-carrier wireless specifications, such as data of optimized evolution (EV-DO), one or more revisions thereof, etc.
[0004] Generally, multiple access communication systems can simultaneously support communication to multiple mobile devices. Each mobile device can communicate with one or more base stations via forward and reverse link transmissions. The forward link (or downlink) refers to the communication link from the base stations to the mobile devices, and the reverse link (or uplink) refers to the communication link from the mobile devices to the base stations. Additionally, communications between mobile devices and base stations can be established through single-entry and single-exit (SISO), multiple-entry and single-exit (MISO), and multiple-entry and multiple-exit (MIMO) systems.
[0005] To supplement conventional mobile phone network base stations, additional base stations can be developed to provide more robust wireless coverage for mobile units. For example, wireless relay stations and low coverage base stations (eg, commonly referred to as access point base stations, home B-nodes, femto access points, or femto cells) can be developed to achieve a user experience. richer and greater capacity growth in addition to indoor coverage. Typically, such low coverage base stations are connected to the Internet and the mobile operator's network through a DSL router or cable modem. Since these other types of base stations can be added to the conventional mobile telephone network (eg a return access channel) differently from conventional base stations (eg macro base stations) there is a need to create techniques for managing these other types of base stations and their associated user equipment.
[0006] One aspect of mobile communications is integrated mobile data services. Recently, many mobile devices and mobile communication service providers have transitioned to incorporating Internet Protocol or similar data networking capabilities. From a user equipment (UE) perspective, user applications in addition to some communication protocols that facilitate communication with a data network have been integrated into the UE hardware/software/firmware. From a network perspective, service provider networks and core networks have been upgraded with infrastructure for establishing packet network connections for UEs. Serving as an intermediary between a radio access network communicatively coupled to these UEs, and the packet connection in the data network (eg Internet), a core network can distribute Internet services to the respective UEs (in addition intranet services, or other wide area network data services). As more users retain subscriptions to data network-based mobile services, these services become more valuable and the focus of future infrastructure improvement on the part of mobile service providers. summary
[0007] The following is a simplified summary of one or more aspects in order to provide a basic understanding of those aspects. This summary is not an extensive overview of all aspects contemplated, nor is it intended to identify key or critical elements of all aspects or delineate the scope of each and every aspect. Its sole purpose is to present some concepts of one or more aspects of this description in a simplified form as an introduction to the more detailed description that will be presented later,
[0008] Various aspects of the present description provide for offloading selected Internet Protocol (SIPTO) traffic to establish data services in a mobile communication environment. In some aspects, SIPTO traffic can be facilitated through a network of local packet access circuits (local P-GWs, also referred to herein as local access circuits or L-GWs) that provide an interface to the Internet or a network similar data. Instead of the few nodes supporting centralized gateway GPRS (GGSN) or packet access circuits (P-GW), local packet access circuits (L-GW) can provide similar functionality as a GGSN or a P-GW centralized, but can be deployed over a radio access network, providing a local alternative to the centralized GGSN or P-GW for packet network access. Additionally, eligibility for SIPTO can be on an EU-by-EU basis; for example, relying on data within a subscriber stored in the UE or account information to determine SIPTO eligibility. In particular aspects, SIPTO eligibility can also be based on packet network by packet network, or a combination thereof. This allows flexibility in determining whether SIPTO can be established for a given UE at a given location, and can be based, for example, on UE capacity, subscription status information, data network capacity, tariff rate, and so on, in addition to different legal requirements of a governmental jurisdiction.
[0009] Other aspects of this description provide mechanisms for maintaining a packet network connection at a local GW. Existing packet connections supported by the local GW can be analyzed and an identifier for the local GW compared to an identifier of a current packet network, or mobile network access point serving a UE. If the identifier does not match a second identifier of a current server packet network gateway, the packet network connection may be terminated. Optionally, a reactivation command can be sent to the UE in case the UE has not terminated the bundled services. Likewise, the UE may request reactivation in other aspects described, based on receiving a reactivation command, ending a transfer, or comparing network gateway identifiers in current and previous packet, or similar. Accordingly, the network resources spent to provide multiple packet connections can be efficiently preserved while mitigating session drops or data loss.
[0010] In other aspects of the present description, a method for wireless communication is provided. The method may comprise receiving a request to establish a data network connection to a UE coupled to a mobile network. Additionally, the method may comprise determining whether a local IP traffic service is allowed for the UE based on a set of stored signature information belonging to the UE. In addition to the above, the method may comprise identifying a local data network gateway associated with a cell or a mobile network access point which the UE serves to establish the data network connection if the IP traffic service location is allowed.
[0011] In other aspects, equipment for wireless communication is provided. The equipment may comprise memory for storing instructions which facilitate the offloading of IP traffic to the network access circuits in local packet and a data processor which executes the modules for implementing the instructions. Particularly, the modules may comprise a receiving module which identifies a request for a connection to an IP network and which retrieves a set of signature information for a UE initiating the request. Additionally, the modules can also comprise an analysis module that analyzes the signature information and determines whether the UE can use the local GW service. Additionally, the modules may further comprise a reference module that identifies a local GW for establishing connection with the IP network, and this is associated with a mobile station providing mobile network service to the UE.
[0012] In another aspect, an equipment for wireless communication is described. The equipment may comprise means for receiving a request to establish a data network connection to a UE coupled to a mobile network. Furthermore, the equipment may comprise means for determining whether a local IP traffic service is allowed for the UE based on a set of stored signature information belonging to the UE. Additionally, the equipment may comprise means for identifying a local data network gateway for establishing the data network connection associated with a cell or a mobile network access point serving the UE, if the service is local IP traffic. is allowed.
[0013] According to one or more additional aspects, at least one processor configured for wireless communication is described. Processors may comprise a first module that receives a request to establish a data network connection to a UE coupled to a mobile network. Additionally, processors may comprise a second module that determines whether a local IP traffic service is allowed for the UE based on a set of stored signature information belonging to the UE. Furthermore, the processors may comprise a third module that identifies a local data network gateway to establish the data network connection that is associated with a cell or a mobile network access point serving the UE, if the traffic service is local IP is allowed,
In at least one aspect, the present description provides a computer program product comprising a computer readable medium. The computer-readable medium may comprise a first set of codes for causing a computer to receive a request to establish a data network connection to a UE coupled to a mobile network. Additionally, the computer-readable medium may comprise a second set of codes for causing the computer to determine whether a local IP traffic service is allowed for the UE based on a set of stored signature information belonging to the UE. Additionally, the computer readable medium may comprise a third set of codes to cause the computer to identify a local data network gateway to establish the data network connection that is associated with a cell or a mobile network access point serving the UE, if local IP traffic service is allowed.
[0015] In addition to the above, particular aspects of the present description provide a wireless communication method. The method may comprise identifying an established data network connection for a UE that receives wireless service from a mobile network base station. Furthermore, the method may comprise referring to a first identifier associated with a data network access point that facilitates data network connection. Additionally, the method may comprise initiating the disabling of the data network connection if the first identifier does not match a second identifier of a data network access point associated with the mobile network base station.
[0016] In other aspects, an equipment configured for wireless communication is described. The equipment may comprise memory comprising instructions configured for managing and removing active data network connections associated with a radio access network (RAN) and a data processor that executes the module for implementing the instructions. Specifically, the modules may comprise a maintenance module that identifies a connection established at a local GW serving the RAN. The modules may further comprise a decommissioning module that initiates a disconnection of the connection if a UE identified with the connection is actively coupled to a wireless node of the RAN that is outside a service area of the local GW.
[0017] According to another additional aspect, an equipment for wireless communication is described. The equipment may comprise means for identifying a packet connection at a local GW that provides data network service to a RAN. Additionally, the equipment may comprise means to terminate the connection if a UE identified with the connection is actively coupled to a wireless node of the RAN that is outside the service area of the local GW, where the service area is defined by at least one among: a data set that correlates the wireless nodes of the RAN with the local GW or set of wireless nodes for which a domain name server lookup comprising a UE identifier or a wireless node identifier returns the Local GW.
[0018] In one or more aspects, at least one processor configured for wireless communication is provided. Processors may comprise a first module that identifies a packet connection at a local GW that provides data network service to a RAN. Additionally, processors may comprise a second module that terminates the connection if a UE identified with the connection is actively coupled to a wireless node of the RAN that is outside a service area of the local GW, where the service area is defined by at least one of: a data set that correlates the wireless nodes of the RAN with the local GW or the set of wireless nodes for which a domain name server lookup comprising a UE identifier or a wireless node identifier wire returns the local GW.
[0019] In at least one other aspect, the present description provides a computer program product comprising a computer readable medium. The computer-readable medium may comprise a first set of codes for causing a computer to identify a packet connection at a local GW that provides data network service to a RAN. Furthermore, the computer-readable medium may comprise a second set of codes to cause the computer to terminate the connection if a UE identified with the connection is actively coupled to a wireless node of the RAN that is outside a service area of the GW local, where the service area is defined by at least one of: a data set that correlates the wireless nodes of the RAN with the local GW or the set of wireless nodes for which a domain name server lookup comprising an identifier of the UE or the wireless node returns the local GW.
[0020] In addition to the above, the present description also provides a wireless communication method. The method may comprise establishing a data network connection over a wireless network and receiving a request to disable the data network connection. Additionally, the method may comprise initiating a request to reactivate the data network connection if a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection.
[0021] According to one or more of the particular aspects, equipment for wireless communication is provided. The equipment may comprise memory for storing instructions configured to maintain packetized network connections in a mobile access environment and a data processor that executes the modules to implement the instructions. In particular, these modules may comprise a connection module that receives a command to disable a data network connection that is established on a SIPTO gateway and a continuation module that initiates a request to re-enable the data network connection if an identifier of cell of a current serving cell is different from a more recent cell identifier associated with the data network connection.
[0022] In another aspect, equipment for wireless communication is provided. The equipment may comprise means for establishing a data network connection over a wireless network and means for receiving a request to disable the data network connection. Additionally, the equipment may comprise means for initiating a request to reactivate the data network connection if a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection.
[0023] According to further described aspects, at least one processor configured for wireless communication is provided. Processors may comprise a first module that establishes a data network connection over a wireless network and a second module that receives a request to disable the data network connection. Additionally, processors may comprise a third module that initiates a request to reactivate the data network connection if a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection.
[0024] In at least one further aspect the present description provides a computer program product comprising a computer readable medium. The computer-readable medium may comprise a first set of codes that cause a computer to establish a data network connection over a wireless network and a second set of codes that cause the computer to decode a request to disable the connection. network data received from a wireless network entity. In addition, the computer-readable medium may comprise a third set of codes that cause the computer to initiate a request to reactivate the data network connection if a cell identifier of a current serving cell is different from a cell identifier plus connection associated with the data network connection.
[0025] To accomplish the above purposes as well as others, the one or more aspects comprise the features hereinafter fully described and particularly highlighted in the claims. The following description and the accompanying drawings present in certain detail illustrative features of one or more aspects. These features are indicative, however, of only a few of the many ways in which the principles of various aspects can be employed, and this description must include all said aspects and their equivalences. Brief Description of Drawings
[0026] Figure 1 illustrates a block diagram of an illustrative equipment that provides SIPTO in some aspects described;
[0027] Figure 2 illustrates a block diagram of an illustrative wireless communication environment providing alternatively local or central IP traffic;
[0028] Figure 3 presents a block diagram of an illustrative wireless environment comprising a development of local packet access circuits according to some aspects;
[0029] Figure 4 illustrates a block diagram of an illustrative equipment for managing local packet connections according to additional aspects of the present description;
[0030] Figure 5 illustrates a block diagram of an illustrative wireless communication equipment for the employment of IP traffic in a SIPTO deployment according to additional aspects;
[0031] Figure 6 presents a block diagram of an illustrative user equipment configured to maintain a packet connection in a P-GW deployment;
[0032] Figure 7 illustrates a flowchart of an illustrative methodology for implementing SIPTO in mobile communications according to one or more aspects;
[0033] Figure 8a and Figure 8b illustrate a flowchart of an illustrative methodology for providing SIPTO based on username or based on access point name;
[0034] Figure 9 illustrates a flowchart of an illustrative methodology for managing data network connections for a local packet gateway development in additional aspects;
[0035] Figure 10 presents a flowchart of an illustrative methodology for using packet connections in a mobile network in additional aspects of this description;
[0036] Figure 11 illustrates a block diagram of an illustrative equipment configured for SIPTO data services for a local GW development in another aspect;
[0037] Figure 12 illustrates a block diagram of an illustrative equipment configured for data connection management for a local GW development;
[0038] Figure 13 illustrates a block diagram of an illustrative equipment for employing data services in mobile communications in other aspects of the present description;
[0039] Figure 14 illustrates a block diagram of an illustrative wireless transmit and receive stream facilitating wireless communication according to some aspects described;
[0040] Figure 15 illustrates a block diagram of an illustrative wireless communication environment to facilitate the various aspects of the present description;
[0041] Figure 16 illustrates an illustrative communication system allowing the development of access point base stations within a network environment. Detailed Description
[0042] Several aspects will now be described with reference to the drawings, in which similar numerical references are used for similar elements. In the following description, for the purpose of explanation, a number of specific details are presented in order to provide an in-depth understanding of one or more aspects. It may be evident, however, that such aspects can be practiced without these specific details. In other cases, well-known structures and devices are illustrated in block diagram form in order to facilitate the description of one or more aspects.
[0043] Additionally, various aspects of the description are described below. It should be apparent that the teachings presented here can be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely representative. Based on the teachings presented herein, those skilled in the art should appreciate that an aspect described herein can be implemented independently of any other aspects and that two or more of those aspects can be combined in various ways. For example, an equipment can be implemented and/or a method practiced using any number of aspects presented here. Additionally, a device may be implemented and/or the method practiced using another structure and/or functionality in addition to or in addition to one or more of the aspects presented here. As an example, many of the methods, devices, systems and equipment described here are described in the context of arbitrating between central and local packet gateway connections for data service in mobile communications, among other things. Those skilled in the art should appreciate that similar techniques can apply to other communication environments.
[0044] As the wireless network infrastructure and features improve over time, and as the processing and user interface capabilities of mobile devices become more sophisticated, users may employ mobile devices to perform functions previously available with personal computers and fixed-line communications. The ability to employ a small portable device for high-quality voice communication, Internet access, multimedia access and playback, and entertainment results in a more desirable consumer product. The data to be consumed by these mobile devices (for example, a UE in a mobile communication equipment) is distributed over the air via a radio access network (RAN). Such RANs may comprise provider-developed infrastructure, such as macro cellular network deployment, subscriber-developed infrastructure, including wireless local area network routers, or a combination thereof, such as conventional macro deployment with subscriber-developed base stations , referred to as domestic Node B (HNB), enhanced HNB (HeNB), femto cells, or the like.
[0045] Wireless communication networks can provide voice services, data services or both. For voice services, traditional cellular core network infrastructure facilitates analog voice communication between remote subscribers. In addition, Voice over Internet Protocol (VoIP) leverages the digital capabilities of packet data networks to provide digital voice communication. VoIP can be instituted within a cellular network by coupling the cellular network to a digital IP network through a packet gateway (P-GW) which contains protocols for propagating data between the respective networks. An example of a conventional P-GW is a gateway GPRS (general packet radio service) support node, or GGSN.
[0046] The GGSN is a relatively centralized gateway that provides an interface between packet networks such as the Internet, or an X.25 network, and mobile communication networks (eg general system for mobile communication (GSM), system universal mobile telecommunications (UMTS), long-term evolution of 3rd generation partnership project (3GPP LTE), broadband code division multiple access (WCDMA), and so on). Particularly in the case of the Internet, relatively few GGSNs exist, yet they are sophisticated entities configured to provide service to very large numbers of subscribers over the GPRS network for a variety of RANs. These GGSNs act as a mobile-to-Internet interface for UEs within a given geographic region (often, for example, for a given state, country, regional union or similar).
[0047] Device mobility during active data services is facilitated with a packet-based data structure stored in the GGSN (eg, packet data protocol context (PDP context), packet data network connection (PDN connection), or similar). An illustrative data structure comprises a PDP context that stores an IP address of a UE, its current server node, and other information related to a particular traffic tunnel or data strings established for the UE. As the UE moves geographically, and is served by different server nodes, the data structure is updated to reflect the current server node, allowing proper data routing to the UE.
[0048] Since conventional GGSNs are relatively large centralized entities, several governments have established rules for law enforcement that track personnel activity based on packet connections in the GGSN. In applicable jurisdictions, therefore, the GGSN is configured to store the movement of the UE (for example, based on server node identifiers) and potentially record information about Internet related traffic, among other functions. Furthermore, GGSN can be configured to deny internet service to selected UEs by a similar mechanism.
[0049] Since a relatively small number of centralized GGSNs handle most if not all packet-related mobile communication traffic for a given geographic region, the GGSN is a very sophisticated and expensive entity. Typical problems can result from this type of centralized development as well. For example, hardware or software failures in the GGSN can affect packet network connectivity for a large number of users across a large region. Simply resetting the software on such a device can be very disruptive too. Additionally, the centralized architecture creates a weakness in the network that can be exploited by data hackers, network hackers, and so on. Additionally, individual service providers have little ability to customize services bundled in the GGSN, requiring support infrastructure for service diversification.
[0050] Recently, proposals for local development of P-GWs have been initiated to reduce some of the inefficiencies of the centralized P-GW architecture. Local GWs can have functionality similar to a conventional P-GW, but comprise less expensive hardware resulting in cost-effective duplication of these entities across a RAN. Additionally, local GWs can be customized even more than conventional P-GWs by service providers. Local GW may connect to the Internet or other bundled networks, and provide bundled services to a set of RAN base stations, including provider-developed eNodeB (or other subscriber-developed RAN base stations), or subscriber-developed HeNB base stations (or similar). The number of base stations served by a local GW, in addition to traffic loading, and a geographic or topological coverage area may vary from entity to entity (referred to here as a local GW coverage umbrella).
[0051] With the coexistence of conventional and local GWs for bundled services in mobile communications, arbitration between P-GWs can be implemented. In one aspect of the present description, this arbitration mechanism is called offloading selected Internet Protocol traffic (SIPTO), and refers to offloading packet traffic from a central P-GW to a local GW. In addition to these aspects, arbitration between central and local GWs can be based or implemented on a UE basis, or on an Access Point Network (APN) basis or a combination thereof. Various criteria can be established to determine whether to offload a particular packet network connection from the central P-GW to a local GW, as described in more detail below. Examples include EU subscription status, government restrictions, APN capabilities, internet tariffs, and so on.
[0052] Referring now to the figures, Figure 1 illustrates a block diagram of an illustrative wireless system 100 for implementing SIPTO for a local GW, or developing local GWs. Particularly, wireless system 100 comprises IP traffic offload selection equipment 102 configured to receive a request 110 for a packet network connection from a mobile communication network. In response to request 110, IP traffic offload selection equipment 102 is configured to determine whether request 110 will be serviced at a central P-GW or can be offloaded to a local GW, where available. Optionally, the IP traffic offload selection equipment 102 may also issue a packet network configuration command 118 to the appropriate P-GW, once the above determination has been made.
[0053] The IP traffic offload selection equipment 102 may comprise memory 104 for storing instructions that facilitate IP traffic offloading to the network access circuits in local packet, and a data processor 106 executing modules for implementing the instructions. In particular, such modules may include a receive module 108 which identifies a request for a connection to a packet network (e.g., an IP network such as the Internet) and which retrieves a set of signature information for a UE initiating the request. 110. Subscription information can be retrieved from a mobile network serving the UE (for example, from a home location record (HLR), visitor location record (VLR), Home Subscriber Server (HSS) ), or similar), retrieved from memory 104 (e.g., where signature information is stored in memory 104 in response to a previous request 110 for packet connection and retrieval of signature information), or the like, or a suitable combination of the same.
[0054] The receiving module 108 sends the UE subscription information pertaining to the request 110 to an analysis module 112 which analyzes the subscription information and determines whether the UE can use the local GW service. This determination may be based at least in part on a set of SIPTO 114 rules stored in memory 104. In one case, the SIPTO 114 rules may specify UE-specific criteria for determining whether the UE can use the local GW service. An example of UE-specific criteria may include whether a UE signature supports SIPTO and a signature status, status of an allowed/prohibited SIPTO indicator stored as part of the UE signature data, or the like. In another case, SIPTO rules 114 may specify APN-specific criteria for determining whether the UE can use the local GW service. Examples of specific APN criteria might include status of an allow/prohibited SIPTO indicator for a given APN that is stored as part of the UE signature data, a quality of service (QoS) capability of an APN identified from the request 110 (for example, see below), and so on. In at least one aspect of the present description, permission may be based on a combination of UE and APN specific criteria.
[0055] If the UE cannot use the local GW service, the IP traffic offload equipment 102 can optionally issue the network configuration command in packet 118 and send it to a conventional P-GW (e.g., a GGSN ). If, on the other hand, the UE can use the local GW service, the data processor 106 can execute a reference module 116 which identifies a local GW to establish the connection with the IP network and this is associated with a base station providing service of mobile network to the UE.
[0056] The reference module 116 can identify the local GW according to one or more of multiple mechanisms. For example, the reference module 116 may employ a data list that associates the respective local GWs of a development of local GWs with respective sets of mobile network base stations, and cross-referencing the base station providing the mobile network service to the UE with a local GW associated with it by the data list. In another aspect, the reference module 116 may send a query (not shown) to the base station, explicitly or implicitly requesting an identifier (e.g., an IP address) of the associated local GW. In other additional aspects, the reference module 116 can perform a domain name server (DNS) lookup in a format that allows a domain server to return a local GW that is geographically or topologically close to the base station. In at least one case, the format may comprise a UE identifier or a base station identifier, for example.
[0057] It should be appreciated that the IP traffic offload selection equipment 102 can be implemented at various physical locations within a communication network. In one case, the IP traffic offload selection equipment 102 can be implemented as part of a server node of a packet core network (for example, as part of a server GPRS support node (SGSN) in a wireless system. GSM/EDGE (Enhanced Data Rate for GSM Evolution), a mobility management entity (MME) in a LTE 3GPP wireless system, or a similar entity in other wireless systems). In another case, the IP traffic offload selection equipment 102 can be implemented in a gateway between the mobile service provider network and the mobile core network. As another example, the IP traffic offload selection equipment 102 can be implemented in a P-GW, whether a local GW or a conventional P-GW such as a GGSN. In at least one aspect of the present description, the IP traffic offload selection equipment 102 may be implemented in a distributed manner across a plurality of locations above or the like.
[0058] By providing arbitration between different P-GWs, the wireless system 100 can facilitate the loading of traffic between conventional P-GWs, and a development of local GWs, for example. This can be important to comply with government regulations that require cell tracking conducted at a central GGSN, for example. In this way, if one UE is subjected to such tracking, the wireless system can establish a packet connection on the GGSN, while other UEs not subject to these requirements can be directed to the local GWs. Additionally, by customizing local GWs, different service providers can provide special bundled network services to differentiate themselves from other service providers; UEs that match the hardware or software requirements of a custom local GW can be routed to it, UEs that don't match the requirements can be routed to another location, and so on. Other benefits and uses can be derived from arbitration between different P-GWs as well, as will be apparent to those skilled in the art. These benefits and uses are considered part of this description.
[0059] Figure 2 illustrates a block diagram of an illustrative network environment 100 suitable for implementing SIPTO for mobile communications in accordance with particular aspects of the present description. The network environment 100 may comprise a UE 202 communicatively coupled with a serving cell 204 via a wireless link. If configured for IP network services, the UE 202 can issue a request 206 for establishing a connection with an IP network, such as the Internet 218. The request 206 is received in the serving cell 204, and sent to a selection equipment download 208. Examples of request 206 may include a PDP context request, a PDN connectivity request, or a similar request suitable for various wireless network systems. In one aspect of the present description, the offload selection equipment 208 may be substantially similar to the IP traffic offload selection equipment 102 of Figure 1 above, although the description is not limited to that aspect.
[0060] The discharge selection equipment 208 may comprise a receiving module 208a for receiving the request 206 and extracting an identifier from the UE 202. Additionally, the receiving module 208a may acquire a set of signature information pertaining to eligibility. from an SIPTO to the UE 202 (e.g., from an HLR associated with the UE 202, a VLR associated with the serving cell 204, or other suitable network entity that stores subscription information for the UE 202). The download selection equipment 208 can then execute an analysis module 208b that analyzes the signature information and determines whether the UE 202 can use the SIPTO service.
[0061] A reference module 208c is employed and identifies a local GW 210 associated with the serving cell 204 to establish the Internet connection 218, if the UE 202 can use the SIPTO service. In one example, reference module 208c performs a domain name server lookup (a DNS lookup) to identify local GW 210. In this example, reference module 208c creates a fully qualified domain name (an FQDN) that allows a domain name server to return the IP address to a local GW 210 that is geographically or topologically closest to the serving cell 204 or UE 202. In at least one aspect of the present description, the FQDN is based at least in part on a UE identifier or a base station identifier. This identifier can allow the domain name server to perform a DNS query to retrieve the geographically or topologically closest local GW, for example.
[0062] In an alternative example, the reference module 208c can store a list of associations between the local GW infrastructure providing access to one or more IP networks, and the base station infrastructure of one or more mobile networks. Upon receipt of the request 206, the reference module 208c extracts an identifier from the serving cell 204 and references the identifier with the stored list. If the serving cell identifier 204 is correlated with the local GW, such local GW 210, reference module 208c retrieves that correlated local GW to establish a packet network connection to the UE 202. reference 208c can obtain a specific P-GW identifier associated with the serving cell 204 from memory. In another case, the reference module 208c may send a request to the server cell 204 to identify one or more local GWs associated with the server cell 204, stored in memory in the server cell 204. Local GW associations stored is not available or does not return a suitable result, the reference module 208c may attempt to obtain the specified P-GW identifier of a base station by sending a request over a packet connection.
[0063] In an illustrative aspect of the present description, the signature information obtained by the receiving module 208a includes a list of local GWs and respective allowed/prohibited indicators associated with the respective local GWs of the list. The allowed/prohibited indicators indicate which local GWs the UE 202 can use, and which local GWs the UE 202 cannot use. In accordance with that aspect, the analysis module 208b extracts a set of local GWs from the signature information that the UE 202 can access. An access module 208d is employed and compares a local GW identifier obtained from the reference module 208c (eg, as a result of a DNS lookup, retrieved from memory, or retrieved from server cell 204) to the set of local GWs obtained from the analysis module 208b to determine whether the UE 202 can use the local GW service in response to the request 206.
[0064] In an alternative aspect, the signature information pertaining to the UE 202 includes a set of IP network access point names (APNs) that are associated with respective data indicators that indicate whether the UE 202 can access or not. the respective IP networks through a local GW (for example, an allowed/not allowed indicator, an allowed/prohibited indicator, or other suitable terminology). In that case, the offload selection equipment 208 determines whether the UE 202 can use SIPTO based on a situation of an allowed/prohibited indicator associated with a particular APN provided by the serving cell 204, returned in response to the DNS lookup, or obtained from from memory. Thus, in a specific implementation, the discharge selection equipment 208 executes the analysis module 208b and determines that the UE 202 can use the local GW service if an APN included in the request 206 is associated with an allowed/prohibited indicator configured to allowed. According to further aspects of the present description, the allowed/prohibited indicators of the respective IP network APNs may be updated by a service provider network (not shown) associated with the UE 202, based on at least one of: status of subscription of the UE 202, government tracking requirements instituted for the UE 202, radio support capabilities of an associated local GW, whether a tariff charged by an operator of the associated local GW, or an amount thereof, or similar, or a appropriate combination of them.
[0065] If the UE 202 is determined to be eligible for access to the local GW, the offload selection equipment sends a network configuration command in packet 210a to the local GW 210. Upon receipt of the configuration command 210a, a GW site 210 establishes a packet context/connection 212 (for example, a PDP context through a PDP context create request, a PDN connection through a session creation request, or similar) to the Internet 218 at the local GW 210 , facilitating Internet communication with the UE 202. Otherwise, if the UE 202 is found to be ineligible for access to the local GE, the download selection equipment sends a network configuration command in packet 214a to the central P-GW 214, which establishes a context/packet connection 216 to the Internet 218 at the central P-GW 214.
[0066] In at least one aspect of the present description, the download selection equipment 208 may further comprise a shutdown module 208e that initiates disabling of context/packet connection 212 or context/packet connection 216 upon expiration of a traffic expiration time, or by moving the UE 202 out of a service band of the local GW 210. Additionally, that service band of the local GW 210 can be determined from the list of base stations, tracking areas, targeting areas, location areas, or radio access controllers, or a similar proxy for a suitable service area for a mobile RAN, which are explicitly or implicitly associated with the local GW 210. Alternatively, the service area can be determined to be the set of cells for which a DNS lookup returns a local GW identifier 210. In any case, when the offload selection equipment 208 determines that the UE 202 has moved out of a service area of the local GW 210, the connection/package context 212 established to the UE 202 is terminated (e.g. a PDP context deactivation request for a PDP context, or a PDP context deactivation request, support for a PDN connection, or other suitable command). This automated shutdown can help provide efficient resource utilization of the local GW 210, improving the load capacities of the local GW 210, reducing excessive power consumption, and so on.
[0067] Figure 3 illustrates a block diagram of an illustrative mobile network environment 300 in accordance with additional aspects of the present description. The mobile network environment 30 may comprise a base station serving area 302 and an associated local GW 304, in addition to another base station serving area 306 with another associated local GW 308. The local GW 304 and the local GW 308 may be part of a common packet gateway deployment (established, for example, by a single mobile network service provider, Internet service provider (ISP), or similar) or associated with independent packet gateway deployments. In any case, the local GWs are associated with the respective base station service areas 302 and 306. The base station service area 302 comprises a planned development of macro base station towers, including macro base station 302a, macro base station 302b, base station macro 302c and base station macro 302d. Base station service area 306, on the other hand, is a semi-planned development comprising a provider-developed macro base station 306a and provider-developed micro base station 306b, in addition to a set of subscriber-developed base stations 306c.
[0068] The local GW 304 and the local GW 308 are part of the mobile core network 310 and are additionally communicatively coupled to one or more IP 312 networks (e.g., Internet or a particular intranet, an X.25 network, or other network packet-based communication method) via the respective IP structures indicated by the dashed lines coupling the Internet 312 with the local GW 304 and local GW 308, respectively. Provider-developed base stations, including base station server area macro base stations 302, and base station server area macro base station 306a and base station server area micro base station 306b 306, are coupled via a back-to-network access channel link mobile core 310, indicated by dotted lines between mobile core network 310 (e.g., a GSM core network, a UMTS core network, an LTE 3GPP core network, and so on) and the respective base stations. Although only a single mobile core network 310 is presented in the mobile network environment 300, it should be appreciated that one or more base stations 302a, 302b, 302c, 302d, 306a or 306b can be coupled to one or more other mobile core networks (via other back-channel links - not shown) in addition to, or instead of. The mobile network environment 300 is not limited to a number or type of mobile core networks, however. Additionally, subscriber-developed base stations 306c are coupled via one or more broadband IP links to one or more IP networks, such as the Internet 312.
[0069] Mobile core network 310 communicatively couples to IP network 312 through GGSN 314. This allows mobile core network 310 to communicate with subscriber-developed base stations 306c, and also allows mobile core network 310 to facilitate IP network 312 access to base station service area 302 and base station service area 306. Additionally, mobile core network 310 can also facilitate access to IP network 312 through local GW 304 and local GW 308, as described here. The selection between GGSN 314 and local GW 304 or local GW 308 can be implemented within the mobile core network 310, in GGSN 314, or in the respective base stations of base station service area 302 or base station service area 306, or another suitable implementation. In at least one aspect, the selection between GGSN 314 and local GW 304 or local GW 308 can be distributed across a plurality of positions above. In any case, the criteria for selecting between GGSN 314 and a local GW can be implemented on a UE basis and on an APN basis.
[0070] According to various aspects of the present description, subscriber data belonging to a UE may indicate whether access to local GW 304 or local GW 308 is allowed. UE and APN permissions can be configured in subscriber data and updated by a mobile service provider to reflect changes in UE or APN permissions. So, for example, where a government agent requires UE tracking for a particular subscriber, APN permissions can be determined to prohibit a UE from being used by the particular subscriber. IP network connections to that subscriber can then be established through GGSN 314 (having mandatory tracking software, for example) rather than through local GW 304 or local GW 308. As another example, if the mobile service provider does not have a tariff agreement with a local GW development owned by an ISP, eg local GWs associated with local GW development (eg local GW 304) can be determined as prohibited for all EUs. Accordingly, a UE operating within the mobile network environment 300 will be directed to a local GW only within the base station service area 306, in this example. In another example, if the particular subscriber maintains the subscription service that authorizes the local GW service for a set of APNs but not for a second set of APNs, the subscription information can be determined as allowed for the local GWs (by example, local GW 308) associated with one set of APNs, and set to prohibited for the local GWs (eg, local GW 304) associated with the second set of APNs, and so on. It will be appreciated that other illustrative implementations known to those of skill in the art, or made known to those of skill in the art through the context provided herein, are considered within the scope of the present description.
[0071] Figure 4 presents a block diagram of an illustrative wireless system 400 in accordance with other aspects of the present description. In particular, wireless system 400 may comprise a mobility entity 402 configured to manage packet connections established at one or more local GWs. Management of packet connections can include monitoring the respective connections for traffic term expirations, termination by expiration or otherwise unused connections, and instigating the reactivation of terminated packet connections that are neither expired nor unused, or that correspond to an appropriate reactivation criterion. The mobility entity 402 therefore can provide a mechanism for promoting efficient use of packet access circuit resources used for mobile network packet services.
[0072] As shown, wireless system 400 may comprise a local GW 404 having a packet connection 406 established to a UE 408 in a mobile cell affiliated with local GW 404 (referred to as an affiliate cell 410). Additionally, wireless system 400 may comprise a second mobile cell that is not affiliated with local GW 404 (outside a service area of the local GW - referred to as unaffiliated cell 422). Affiliated cell 410 and unaffiliated cell 422 are coupled to a mobile core network 430.
[0073] The mobility entity 402 may comprise memory 414 for monitoring instructions configured for managing and removing active data network connections associated with a RAN, and a data processor 416 for executing the modules that implement the instructions. Particularly, the modules may comprise a maintenance module 418 that identifies an established connection, e.g. packet connection 406, at local GW 404 serving the RAN (e.g. comprising affiliate cell 410). Additionally, the mobility entity 402 may comprise a decommissioning module 420 that initiates a disabling of the packet connection 406 if a UE identified with the packet connection (e.g. UE 408) is actively coupled with a wireless node of the RAN that is outside a local GW 410 service area.
[0074] In a particular aspect of the present description, the maintenance module 418 determines, or receives a determination from the mobile core network 430, for example, that the UE 408 has conducted a handover to unaffiliated cell 422, or has accessed the unaffiliated cell. affiliate 422 from inactive state. In that case, the maintenance module 418 digitizes the local GW 404 (and optionally other local GWs - not shown - within a local GW development, associated with a particular APN, associated with a particular mobile network, or similar not shown) to identify whether a packet connection exists for the UE 408. If such a packet connection exists, the maintenance module 418 sends a command to the terminating module 420, which in turn initiates disabling of the packet connection 406 .
[0075] According to another aspect, the maintenance module 418 sends a reactivation command to the UE 408 upon termination of the packet connection 406. The maintenance module 418 can be triggered to send the reactivation command based on a or more criteria. As an example, the maintenance module 418 sends the reset command in response to the reset of the local GW 404, load balancing of the local GW 404 and one or more other P-GWs (which may include local GWs or central P-GWs - not shown), or UE 408 activating a connection outside the service area of the local GW 404, or a suitable combination. The reactivation command can be employed to cause the UE 408 to re-establish the packet connection 406 at the local GW 406 or via the unaffiliated cell 422 as a result of the non-UE termination of the packet connection. This can reduce session disruption, improving the overall reliability of the packet-based services employed by the UE 408.
[0076] In various other aspects, the mobility entity 402 may further comprise a reference module 426 which is configured to determine whether the wireless node (unaffiliated cell 422) is outside the service area of the local GW 404. This may be performed in one or more of several implementations. In one implementation, the reference module 426 performs a DNS lookup for the UE 408, or the wireless node, and retrieves a current local GW associated with the UE 408 or the wireless node. This can be done, for example, based on an FQDN that allows a domain name server to return the current local GW that is geographically or topologically closest to the wireless node. The reference module 426 then compares an identifier of the local GW 404 with a second identifier of the current local GW. Based on the comparison, the reference module 426 determines that the wireless node is within the service area if the identifier and the second identifier are the same. In such a case, the packet connection 406 is not terminated by the mobility entity 402. If the identifier and the second identifier are not the same, the reference module infers that the packet connection 406 is no longer active in the local GW 404, and termination module 420 therefore initiates termination of packet connection 406.
[0077] In an alternative or additional implementation, the reference module 426 acquires a dataset that correlates the wireless nodes within the service area to the local GW 404. In this case, the reference module 426 checks whether the wireless node from the RAN is correlated with the local GW 404. If so, the packet connection 406 is maintained. Otherwise, shutdown module 420 initiates disabling of packet connection 406.
[0078] Figure 5 illustrates a block diagram of an illustrative wireless environment 500 for facilitating IP network services in a mobile operating environment in accordance with additional aspects of the present description. Wireless environment 500 comprises a UE 502 communicatively coupled with a RAN access point 504, such as an eNodeB, a Node B, a home Node B (HNB), a home eNodeB (HeNB), or the like, via an air interface. Additionally, the UE 502 may have a packet network connection maintained by a local GW 506 associated with the RAN access point 504.
[0079] The UE 502 may comprise a packet maintenance equipment 508 employing a connection module 510 that receives a command 522 to disable the packet network connection that is established at a selected SIPTO gateway (e.g., local GW 506 ). Additionally, the UE 502 may execute a continuation module 514 that initiates a request 524 to reactivate the packet network connection if a cell identifier of a current serving cell (e.g., access point RAN 504) is different from an identifier of most recent cell associated with the packet network connection. Thus, where the RAN access point 504 is not an access point that originates the packet network connection, or is not the latest access point server UE 502, the continuation module 514 can automatically initiate the request 524 to reactivate the packet network connection. Additionally, in one aspect of the present description, continuation module 514 may initiate request 524, whereas in other aspects an application 518 operating at UE 502 may initiate an internal request 520 to reactivate the packet network connection, which is sent to access point RAN 504 by continuation module 514. In at least one other aspect, connection module 510 receives an explicit reactivation command from access point RAN 504 or local GW 506 and triggers continuation module 514 to send request 524 in response to the explicit reactivation command.
[0080] In a particular aspect of the present description, the UE 502 may comprise a mobility module 512 that detects a transfer or an active link from the idle state to the RAN access point 504. In that case, the receipt of the command 522 to deactivate results at least in part in the transfer or link up from the down state. Additionally, the continuation module 514 determines if the current serving cell is outside a service range of the SIPTO gateway upon detection of the transfer and issues the request 524 to reactivate the packet network connection if the current serving cell is, in fact, out of service range. As described, packet handling equipment 508 can be configured to reactivate or maintain the packet network connection when the UE 502 conducts a handover to an access point that is outside the service band of the local GW 506. packet hold equipment 508 may be configured to identify a wake command issued by a UE serving mobile network 502, and issues the request 524 to reactivate the packet network connection in response to the wake command. As a result, the UE 502 may be less subject to loss of data services supported by a local GW in case of a handover, reset of the local GW 506, or load balancing packet connection between the local GW and another P- GW (not shown).
[0081] Figure 6 illustrates a block diagram of an illustrative wireless communication system 600 comprising a UE 602 in accordance with one or more additional aspects of the present description. The UE 602 may be configured to communicate wirelessly with one or more base stations 604 (e.g., access points) of a wireless network. Based on such a configuration, the UE 602 can receive wireless signals from base stations 604 on one or more forward link channels and respond with wireless signals on one or more reverse link channels. Additionally, the UE 602 may comprise instructions stored in memory 614 configured to maintain packetized network services in a mobile access environment, and a data processor 612 that runs a packet maintenance equipment 616 that implements these instructions, as described. here (for example, see figure 6, above). Particularly, packet maintenance equipment 616 may initiate a request for reactivation of a packet network connection facilitated by base stations 604 in case the UE 602 conducts a handover from one base station 604 to another, upon request of an operating application in the UE 602, upon premature termination of the packet network connection, or upon receipt of a network command to reactivate the packet network connection.
[0082] UE 602 includes at least one antenna 606 (e.g. comprising one or more input/output interfaces) that receives a signal and receivers 608, which perform typical actions (e.g. filter, amplify, downconvert, etc.) in the received signal. In general, antenna 606 and a transmitter 620 (collectively referred to as a transceiver) can be configured to facilitate wireless data exchange with base stations 604.
[0083] The antenna 606 and receivers 608 may also be coupled with a demodulator 610 that can demodulate received symbols and provide demodulated symbols to data processors 612 for evaluation. It should be appreciated that data processors 612 may control and/or reference one or more components (antenna 606, receiver 608, demodulator 610, memory 614, packet handling equipment 616, modulator 618, transmitter 620) of the UE 602. Additionally, the data processors 612 may run one or more modules, applications, engines or the like that comprise information or controls pertinent to performing the functions of the UE 602. Additionally, the memory 614 of the UE 602 is operatively coupled to the data processors 612. Memory 614 can store data to be transmitted, received, and the like, and instructions suitable for conducting wireless communication with a remote device (e.g., base stations 604).
[0084] The systems mentioned above have been described with respect to the interaction between various components, modules and/or communication interfaces. It should be appreciated that such systems and components/modules/interfaces may include the components/modules or submodules specified herein, some of the specified components/modules or submodules, and/or additional modules. For example, a system may include server cell 102 comprising interference mitigation equipment 604, and UE 702 coupled to RQI equipment 710, or a different combination of these and other entities. Sub-modules can also be implemented as modules communicatively coupled to other modules rather than included in parent modules. Additionally, it should be noted that one or more modules can be combined into a single module providing added functionality. For example, signal allocation module 612 may include transmission module 614, or vice versa, to facilitate instructing one UE to measure interference in a UE-specific pilot of another UE, and transmitting the instruction to the EU, through a single module. The modules may also interact with one or more other modules not specifically described here but known to those skilled in the art.
[0085] Additionally, as will be appreciated, various parts of the systems described above and methods below may include or consist of knowledge of artificial intelligence or rule-based components, subcomponents, processes, means, methodologies, or mechanisms (e.g. support vector, neural networks, expert systems, Bayesian networks, fuzzy logic, data fusion engines, classifiers,...). Such components, among others, and in addition to what has already been described here, can automate certain mechanisms or processes performed to make parts of systems and methods more adaptive as well as efficient and intelligent.
[0086] In view of the illustrative systems described above, the methodologies that can be implemented in accordance with the present matter described will be better appreciated with reference to the flowcharts of figures 7 to 10. While for the sake of simplicity of explanation, the methodologies are illustrated and described as a series of blocks, it should be understood and appreciated that the present claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or simultaneously with other blocks from what was presented and described here. Furthermore, not all the blocks illustrated may be necessary to implement the methodologies described later. Additionally, it should be further appreciated that the methodologies described later and throughout this specification may be stored in an article of manufacture to facilitate transport and transfer of such methodologies to computers. The term article of manufacture, as used, shall encompass a computer program accessible from any computer-readable device, device in conjunction with a carrier, or storage medium.
[0087] Figure 7 illustrates a flowchart of an illustrative methodology 700 in accordance with additional aspects of the present description. At 702, method 700 may comprise receiving a request to establish a data network connection to a UE coupled to a mobile network. Additionally, at 704, method 700 may comprise determining whether a local IP traffic service is allowed for the UE based on a set of stored signature information belonging to the UE. in one case, the local IP traffic service may belong to a SIPTO service to access a packet data network through a local GW instead of a central GGSN or central P-GW. In another case, the local IP traffic service may pertain to the initiation of a local IP access communication (LIPA) between the UE and a local IP network, such as a WiFi network with one or more wireless IP routers, or a network Wide area IP with a wireless wide area network router (eg wireless interoperability for microwave access (WiMAX)).
[0088] Further, at 706, method 700 may comprise identifying a local data network gateway associated with a cell or mobile network access point serving the UE to establish a data network connection if the SIPTO is allowed. By reference to subscription information, SIPTO may be allowed UE by UE, for one or more UEs supported by a mobile service provider. In at least one aspect of the present description, the subscription information is updated on a semi-static basis based on the radio support capabilities of a specified APN with the request, UE subscription status, a tariff rate associated with the network gateway of local data, or an appropriate combination thereof. In these aspects, SIPTO can be activated for the UE based on a status of one or more of the criteria specified above in the signature information. In at least one additional aspect of the present description, determining whether SIPTO is allowed for the UE at least in part comprises determining whether the content tracking requirements associated with the UE, if any, are supported by the network gateway of location data.
[0089] In some described aspects, determining whether SIPTO is allowed for UE may further comprise determining whether SIPTO is allowed for a specified APN with the request and rejecting the request if SIPTO is not allowed for APN. In a particular aspect, determining whether SIPTO is allowed for APN further comprises identifying whether APN matches the QoS requirements of the traffic associated with the request. In another aspect, determining whether SIPTO is allowed for APN comprises determining whether the load requirements associated with the request are supported by the local data network access circuit.
[0090] In other additional aspects of the present description, identifying the local data network gateway further comprises performing a DNS lookup. Performing the DNS lookup may further comprise forming an FQDN comprising an indicator that allows a DNS to retrieve a nearby local data network gateway that is geographically or topologically closer to a mobile network cell serving the UE, and return the near local data network gateway in response to DNS lookup. In a specific aspect, the indicator is based on an identifier of the UE and specifies whether a signature of the UE allows SIPTO, or is based on an identifier of the cell or mobile network access point and implies a capability of the data network gateway support the network connection, or a combination thereof.
[0091] In an alternative aspect, the identification of the local data network gateway further comprises referring to a mobile network cell serving the UE to obtain a data set that associates the mobile network mobile network access points with the local data network access circuits In this aspect, identification of the local data network gateway can be accomplished by combining the mobile network cell with an associated local data network gateway in the data set. According to at least one further aspect, method 700 may further comprise initiating disabling of the data network connection upon expiration of a traffic expiration time, or upon the UE moving out of a network cell band which are served by the local data network gateway. In this last aspect, the resources of the local data network gateway can be preserved by terminating data network connections that are no longer used by the UEs served by the mobile network.
[0092] Figures 8a and 8b illustrate a flowchart of an illustrative methodology 800 in accordance with other additional aspects of the present description. At 802, method 800 may comprise receiving a request for establishing a data context for a mobile network UE. At 804, method 800 may comprise extracting a UE ID or base station ID from the request. Additionally, at 806, method 800 may comprise accessing stored signature data for the UE in response to receipt of the request.
[0093] At 808, method 800 can obtain an APN associated with the request. At 810, method 800 may comprise referring to stored data indicating whether the APN supports SIPTO traffic. At 812, method 800 can determine if SIPTO is available for APN. If not, method 800 proceeds to 814 and requests the data context for the UE at the central P-GW. Method 800 can end after reference number 814. If SIPTO is available for APN, method 800 can proceed to 816, where another determination is made as to whether a dataset is available by correlating the APNs with the points of access from a mobile network serving the UE. Particularly, the dataset may comprise signature information for the UE indicating whether SIPTO is allowed or prohibited for the respective APNs. By reference to the data set, an APN associated with a base station serving the UE can be identified, and based on an allow/prohibited SIPTO indicator associated with the APN, method 800 can determine whether the UE can be downloaded to a Local GW.
[0094] If the data set is available, method 800 can proceed to 822 in figure 8a, otherwise method 800 proceeds to 818 and forms an FQDN based on UE ID or base station ID. The FQDN is used to facilitate the identification of a local GW to serve the UE. Method 800 then proceeds to 820 in Figure 8a.
[0095] At 822, of Figure 8a, method 800 may comprise performing a DNS lookup based on the FQDN formed in reference numeral 820. At 822, method 800 may comprise receiving a geographically or topologically closest local GW of a cell serving the UE. At 826, method 800 may comprise requesting that the data context be established at the local GW. At 828, method 800 may comprise determining whether a traffic expiration period pertaining to the data context has occurred. If that is the case, method 800 proceeds to 830 and disables the data context, terminating method 800; otherwise, method 800 proceeds to a832 and determines whether the UE has moved out of a local GW service area. If the UE has moved out of the service area, method 800 proceeds to 830 and disables the data context; otherwise, method 800 returns to numeric reference 828.
[0096] Figure 9 illustrates a flowchart of an illustrative methodology 900 for managing packet contexts for mobile communication subscribers according to one or more aspects of the present description. At 902, method 900 may comprise identifying an established data network connection for a UE that receives wireless service from a mobile network base station. At 904, method 900 may comprise referring to a first identifier associated with a data network access point that facilitates data network connection. At 906, method 900 may further comprise initiating disabling of the data network connection if the first identifier does not match a second identifier of a data network access point associated with the mobile network base station. In at least one described aspect, the first identifier and the second identifier comprise respective first and second IP addresses and initiation of deactivation is conditioned on the first and second IP addresses not being identical.
[0097] In addition to the above, the combination of the first identifier and the second identifier may comprise performing a DNS lookup for the mobile network base station, or for the UE. Additionally, method 900 may comprise retrieving a hotspot identifier in response to the DNS lookup, and employing the hotspot identifier as the second identifier. In this regard, method 900 compares a data network access point identifier (e.g., a local GW) to a second data network access point identifier returned in response to the DNS lookup. Additionally, performing the DNS lookup may further comprise forming an FQDN which facilitates the identification of a local packet gateway that is geographically or topologically closest to the mobile network base station, where the FQDN is based on an identifier of the UE or an identifier of the mobile network base station. Since the DNS lookup will return an identifier associated with a current mobile access point (e.g., mobile network base station), the second identifier must match a current data network gateway serving the UE. Accordingly, method 900 can effectively compare a data network gateway facilitating, maintaining, establishing, etc. the data network connection to a data network gateway currently serving the UE, and, if they are not identical, start disabling the data network connection.
[0098] In an alternative aspect of the present description, the combination of the first identifier and the second identifier further comprises referring to a list of data network access point identifiers associated with the mobile network base station and determining whether the first identifier is included in the list of data network access point identifiers. According to that aspect, the list of data network access point identifiers comprises respective mobile network tracking areas, mobile network location areas, mobile network targeting areas, base station identifiers or network controller identifiers radio, or the like, or a suitable combination thereof. These data network access point identifiers uniquely or pseudo-singular (singular within a context of access point identifiers for a particular APN, or case) distinguishes one or more data network access points associated with the station mobile network base stations from data network access points associated with other mobile network base stations.
[0099] In a further aspect, initiating deactivation further comprises initiating a deactivation request and sending the deactivation request to the UE if the first identifier does not match the second identifier. In that case the UE may terminate UE-initiated communications relating to the data network connection, or may refrain from trying to reactivate the data network connection, in the absence of a separate application request to establish a second data network connection , for example. In another aspect, initiating deactivation further comprises initiating a deactivation request and sending the deactivation request to a network entity that manages the data network connection, if the first identifier does not match the second identifier. It should be appreciated that the deactivation request can be sent to the UE and the network entity in at least one additional aspect.
[0100] In another alternative aspect, method 900 may comprise determining whether the UE is conducting or has conducted a handover to the mobile network base station. If the UE has conducted a transfer, this can trigger the initiation of deactivation of the data network connection as a result of the transfer. In addition to the above, at 908, method 900 may further comprise sending a reactivation command to the UE which causes the UE to request reactivation of the data network connection at the data network access point associated with the mobile base station. The sending of the reactivation command can be in response to the premature termination of the data network connection, for example. Such an event can be caused by a soft reset at a data network access point facilitating data network connection, powering off at the data network access point, or other suitable shutdown.
[0101] Figure 10 illustrates a flowchart of an illustrative methodology 1000 to facilitate and maintain a data network connection in mobile communications. At 1002, method 1000 may comprise establishing a data network connection over a wireless network. At 1004, method 1000 may comprise receiving a request to disable the data network connection. At 1006, method 1000 may comprise initiating a request to reactivate the data network connection if a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection. In one case, request initiation further comprises determining that the current serving cell is out of service range of a local data network gateway supporting the data network connection. This determination may result from the cell identifier and the latest cell identifier not matching, in one case, or from the determination that a different local packet network gateway serves the current serving cell and the latest cell. In an illustrative aspect, method 1000 may comprise performing a handover to a neighboring cell, where receipt of the deactivation request results at least in part in performing the handover. In another illustrative aspect, method 1000 may comprise receiving a wake command for the data network connection, and comparing the cell identifier with the most recent cell identifier as a result of receiving the wake command. In this way, performing the transfer or receipt of the reactivation command can potentially trigger the initiation of the reactivation request, optionally subject to a difference in the respective identifiers of the current serving cell and most recent cell.
[0102] Figures 11, 12 and 13 illustrate respective illustrative equipment 1100, 1200, 1300 for implementing improved acknowledgment and retransmission protocols for wireless communication in accordance with the aspects of the present description. For example, equipment 1100, 1200, 1300 may reside at least partially within a wireless communication network and/or within a wireless receiver such as a node, base station, access point, user terminal, personal computer coupled to a mobile interface card, or the like. It should be appreciated that devices 1100, 1200, 1300 are represented as including function blocks, which may be function blocks that represent functions implemented by a processor, software, or combination thereof (eg, firmware).
[0103] Equipment 1100 may comprise memory 1102 for storing modules or instructions configured to perform the functions of equipment 1100, including providing SIPTO for UEs operating in a mobile communication environment, and a data processor 1110 for execution of modules implementing these functions. For example, apparatus 1100 may comprise a module 1102 for receiving a request for establishing a data network connection to a UE coupled to a mobile network. Furthermore, apparatus 1100 may comprise a module 1104 for determining whether a local IP traffic service is allowed for the UE based on a stored signature information set belonging to the UE. In one case, the local IP traffic service may belong to a SIPTO service to access a packet data network through a local GW instead of a central GGSN or P-GW. In another case, the local IP traffic service may pertain to initiating a LIPA communication between the UE and a local IP network, such as a WiFi network with one or more wireless IP routers, or a wide area IP network with a wireless wide area network router (eg wireless interoperability for microwave access (WiMAX)).
[0104] Additionally, the equipment 1100 may comprise a module 1106 for identifying a local data network gateway to establish a data network connection associated with a cell or a mobile network access point serving the UE, if the SIPTO is allowed. The module 1106 can perform a DNS lookup based on an FQDN consisting at least in part of a UE identifier or a mobile network access point identifier to retrieve the local data network gateway, in one case, or it can do reference to a data set that explicitly correlates the local data network access circuits with the mobile network access points, using a mobile network access point identifier to identify the local data network gateway. In various aspects of the present description, the dataset may be stored in memory 1102, stored at a mobile network entity (e.g., a VLR, an HLR, or other suitable network entity), or stored at the access point of the mobile network, or similar.
[0105] Equipment 1200 may comprise memory 1202 for storing modules or instructions configured to perform functions of equipment 1200, including managing packet data connections for local packet network access circuits, and a data processor 1208 to run the modules that implement these functions. Particularly, equipment 1200 may comprise a module 1204 for identifying a packet connection at a local GW that provides data network service to a RAN. Additionally, equipment 1200 may comprise a module 1206 to terminate the connection if a UE identified with the connection is actively coupled to a wireless node of the RAN that is outside a service area of the local GW. In particular, the service area is defined by at least one of: the set of wireless nodes for which a DNS lookup comprising a UE identifier or a wireless node identifier returns the local GW, or a data set that correlates the wireless nodes of the RAN with the local GW.
[0106] Equipment 1300 may comprise memory 1302 to store modules or instructions configured to perform the functions of equipment 1300, including facilitating the reactivation of data network connections established for a UE operating in a mobile network environment, and a processor 1310 to run the modules that implement these functions. Particularly, equipment 1300 may comprise a module 1304 for establishing a data network connection via a wireless network. Additionally, apparatus 1300 may comprise a module 1306 for receiving a request to disable the data network connection. In addition to the above, apparatus 1300 may comprise a module 1308 for initiating a request for reactivation of the data network connection if a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data connection. Data Network.
[0107] Figure 14 presents a block diagram of an illustrative system 1400 that can facilitate wireless communication according to some aspects described here. In a DL, at access point 1405, a transmit data processor (TX) 1410 receives, formats, encodes, interleaves and modulates (or symbol maps) traffic data and provides modulation symbols ("data symbols") . A symbol modulator 1415 receives and processes the data symbols and pilot symbols and provides a sequence of symbols. A symbol modulator 1415 multiplexes the data and pilot symbols and supplies them to a transmitter unit (TMTR) 1420. Each transmission symbol can be a data symbol, a pilot symbol, or a signal value of zero. Pilot symbols can be sent continuously in each symbol period. Pilot symbols may be frequency division multiplexed (FDM), orthogonal frequency division multiplexed (OFDM), time division multiplexed (TDM), code division multiplexed (CDM), or a suitable combination of these or of similar modulation and/or transmission techniques.
[0108] TMTR 1420 receives and converts the symbol sequence into one or more analog signals and further conditions (for example, amplifies, filters and upconverts to frequency) the analog signals to generate a DL signal suitable for transmission over the wireless channel . The DL signal is then transmitted through an antenna 1425 to the terminals. At terminal 1430, an antenna 1435 receives the DL signal and provides a received signal to a receiver unit (RCVR) 1440. Receiver unit 1440 conditions (e.g., filters, amplifies, and downconverts to frequency) the received signal and digitizes the signal. conditioned to obtain samples. A symbol demodulator 1445 demodulates and provides received pilot symbols to a processor 1450 for channel estimation. Symbol demodulator 1445 further receives a frequency response estimate for DL from processor 1450, performs data demodulation on the received data symbols to obtain data symbol estimates (which are estimates of transmitted data symbols) and provides the data symbol estimates to a 1455 RX data processor, which demodulates (i.e., demaps the symbol), deinterleaves, and decodes the data symbol estimates to retrieve the transmitted traffic data. The processing performed by symbol demodulator 1445 and RX data processor 1455 is complementary to the processing performed by symbol modulator 1415 and TX data processor 1410, respectively, at access point 1405.
[0109] In UL, a TX 1460 data processor processes traffic data and provides data symbols. A symbol modulator 1465 receives and multiplexes the data symbols with pilot symbols, performs modulation, and provides a sequence of symbols. A transmitter unit 1470 then receives and processes the symbol sequence to generate a UL signal, which is transmitted by antenna 1435 to access point 1405. Specifically, the UL signal may conform to SC-FDMA requirements and may include mechanisms hopping frequency as described here.
[0110] At access point 1405, the UL signal from terminal 1430 is received by antenna 1425 and processed by a receiving unit 1475 to obtain samples. A symbol demodulator 1480 then processes the samples and provides received pilot symbols and data symbol estimates to the UL. An RX data processor 1485 processes the data symbol estimates to retrieve the traffic data transmitted by terminal 1430. A processor 1490 performs channel estimation for each active terminal transmitting in UL. Multiple terminals can transmit the pilot simultaneously in UL on their respective designated sets of pilot subbands, where the sets of pilot subbands can be interleaved.
[0111] Processors 1490 and 1450 direct (eg, control, coordinate, manage, etc.) operation at access point 1405 and terminal 1430, respectively. Respective processors 1490 and 1450 may be associated with memory units (not shown) that store program codes and data. The 1490 and 1450 processors can also perform computations to derive time- and frequency-based impulse response estimates for UL and DL, respectively.
[0112] For a multiple access system (eg SC-FDMA, FDMA, OFDMA, CDMA, TDMA, etc.), multiple terminals can transmit simultaneously in UL. For such a system, pilot subbands can be shared between different terminals. Channel estimation techniques can be used in cases where the pilot subbands for each terminal span the entire operating band (possibly except for the band edges). Such a pilot subband structure would be desirable to obtain frequency diversity for each terminal.
[0113] The techniques described here can be implemented by various means. For example, these techniques can be implemented in hardware, software, or a combination thereof. For a hardware implementation, which can be digital, analog or digital and analog, the processing units used for channel estimation can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors ( DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro controllers, microprocessors, other electronic units designed to perform the functions described here, or a combination of them. With software, implementation can be through modules (for example, procedures, functions, and so on) that perform the functions described here. Software codes can be stored in the memory unit and executed by the 1490 and 1450 processors.
[0114] Figure 15 illustrates a wireless communication system 1500 with multiple base stations (BSs) 1510 (for example, wireless access points, wireless communication equipment) and multiple terminals 1520 (for example, ATs), such as as it can be used in conjunction with one or more aspects. A BS 1510 is usually a fixed station that communicates with the terminals and may also be called an access point, Node B, or some other terminology. Each BS 1510 provides communication coverage for a particular geographic area or coverage area, illustrated as three geographic areas in Figure 15, labeled 1502a, 1502b, 1502c. The term "cell" can refer to a BS or its coverage area depending on the context in which the term is used. To improve system capacity, a geographic area of BS/coverage area can be divided into multiple smaller areas (e.g. three smaller areas according to cell 1502a in figure 15), 1504a, 1504b and 1504c. Each smaller area (1504a, 1504b, 1504c) can be served by a respective base transceiver subsystem (BTS). The term "sector" can refer to a BTS or its coverage area depending on the context in which the term is used. For a sectored cell, the BTSs for all sectors of that cell are typically located within the base station for the cell. The transmission techniques described here can be used for a system with sectorized cells in addition to a system with non-sectorized cells. For the sake of simplicity, in the present description, unless otherwise specified, the term "base station" is used generically for a fixed station that serves a sector in addition to a fixed station that serves a cell.
[0115] The 1520 terminals are typically dispersed throughout the system, and each 1520 terminal can be fixed or mobile. Terminals 1520 may also be referred to as mobile station, user equipment, user device, wireless communication equipment, access terminal, user terminal, or some other terminology. A 1520 terminal can be a wireless device, a cell phone, a personal digital assistant (PDA), a wireless modem card, and so on. Each terminal 1520 can communicate with zero, one or several BSs 1510 downlink (eg FL) and uplink (eg RL) at any given time. Downlink refers to the communication link from the base stations to the terminals, and uplink refers to the communication link from the terminals to the base stations.
[0116] For a centralized architecture, a 1530 system controller couples a 1510 base station and provides coordination and control for BSs 1510. For a distributed architecture, the BSs 1510 can communicate with each other as needed (for example, through of a wired or wireless backhaul channel network communicatively coupling the BSs 1510). Data transmission on the forward link often occurs from an access point to an access terminal at or near the maximum data rate that can be supported by the forward link or the communication system. Additional forward link channels (eg control channel) can be transmitted from multiple access points to an access terminal. Reverse link data communication can take place from an access terminal to one or more access points.
[0117] Figure 16 illustrates an illustrative communication system to allow the development of access point base stations within a network environment. As illustrated in Figure 16, system 1600 includes multiple access point base stations or home Node B units (HNBs) or femto cells, such as, for example, 1610 HNBs, each being installed in a scaled network environment. corresponding small, such as, for example, in one or more user homes 1630, and being configured to serve the associated UE, in addition to 1620 others. Each HNB 1610 is further coupled to the Internet 1640 and a mobile operator core network 1650 through a DSL router (not shown) or, alternatively, a cable modem (not shown).
[0118] Although the modalities described here use 3GPP terminology, it should be understood that the modalities can be applied to 3GPP technology (Rel99, Rel5, Rel6, Rel7), in addition to 3GPP2 technology (1xRTT, 1xEV-DO Rel0, RevA , RevB) and other known and related technologies. In such embodiments described herein, the owner of HNB 1610 subscribes to mobile service, such as, for example, 3G mobile service, offered through mobile operator core network 1650, and the UE 1620 is capable of operating in both macro-cellular and in the small-scale residential network environment. As such, the HNB 1610 is backward compatible with any existing 1620 UE.
[0119] Additionally, in addition to the 1650 mobile operator core network, the 1620 UE can only be served by a predetermined number of 1610 HNBs, that is, 1610 HNBs that reside within the user's home 1630, and cannot be in one soft handover state with the mobile operator core network 1650. The UE 1620 can communicate with the mobile operator core network 1650 via a macro cell access 1655 or with the HNBs 1610, but not both simultaneously. Since the UE 1620 is authorized to communicate with the HNB 1610, within the user's home it is desirable for the UE 1620 to communicate only with the associated HNBs 1610.
[0120] As used in this description, the terms "component", "system", "module" and the like shall refer to a computer-related entity, be it hardware, software, running software, firmware, middleware, microcode and/or any combination thereof. For example, a module can be, but is not limited to, a process running on a processor, a processor, an object, an executable element, an execution sequence, a program, a device and/or a computer. One or more modules can reside within a process or execution sequence; and a module can be located in an electronic device, or distributed between two or more electronic devices. Additionally, these modules can be run from various computer readable media having various data structures stored therein. Modules can communicate through local or remote processes such as according to a signal having one or more data packets (eg data from one component interacting with another component in the local system, distributed system, or over such a network. such as the Internet with other systems via signal). Additionally, the components or modules of the systems described here can be re-arranged, or can be complemented by additional components/modules/systems in order to facilitate the achievement of various aspects, objectives, advantages, etc., described in relation to the same, and they are not limited to the precise configurations presented in a given figure, as will be appreciated by those skilled in the art.
[0121] Additionally, several aspects are described here with respect to a UE. A UE may also be called a system, subscriber unit, subscriber station, mobile station, mobile, mobile communication device, mobile device, remote station, remote terminal, AT, user agent (UA), a user device, or user terminal (UE). A subscriber station may be a cell phone, a cordless telephone, a Session Initiation Protocol (SIP) telephone, a wireless local circuit station (WLL), a personal digital assistant (PDA), a handheld device having wireless capability, or other processing device connected to a wireless modem or similar mechanism facilitating wireless communication with a processing device.
[0122] In one or more illustrative modalities, the functions described can be implemented in hardware, software, firmware, middleware, microcode, or any suitable combination thereof. If implemented in software, the functions can be stored in one or transmitted as one or more instructions or code in a computer-readable medium. Computer readable medium includes both computer storage medium and communication medium including any medium that facilitates the transfer of a computer program from one place to another. A storage medium can be any physical medium that can be accessed by a computer. By way of example, and not limitation, such computer storage medium may comprise RAM, ROM, EEPROM, CD-ROM, other optical disk storage, magnetic disk storage or other magnetic storage devices, smart cards, and devices flash memory (eg card, stick, key drive) or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Floppy disk and disk, as used herein, include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and blu-ray disk, where floppy disks normally reproduce data magnetically, while disks reproduce data optically. with lasers. Combinations of the above should also be included in the scope of computer readable media.
[0123] For a hardware implementation, the various illustrative logics, logic blocks, modules and processing unit circuits described with respect to the aspects described here can be implemented or realized within one or more of ASICs, DSPs, DSPDs, PLDs, FPGAs, discrete gate or transistor logic, discrete hardware components, general purpose processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other suitable configuration. Additionally, at least one processor may comprise one or more modules that operate to perform one or more of the steps and/or actions described herein.
[0124] Furthermore, various aspects or features described here can be implemented as a method, equipment or article of manufacture using standard programming and/or engineering techniques. Additionally, the steps and/or actions of a method or algorithm described with respect to the aspects described here can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. Additionally, in some aspects, the steps or actions of a method or algorithm may reside as at least one or any combination or set of codes or instructions on a machine-readable medium, or a computer-readable medium, which can be incorporated into a computer program product.
[0125] Additionally, the term "illustrative" is used herein to mean serving as an example, case or illustration. Any aspect or design described herein as "illustrative" is not necessarily to be regarded as preferred or advantageous over other features or designs. Instead, the use of the illustrative term must present the concepts in a concrete way. As used in this order, the term "or" shall mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified, or it is clear from the context, "X employs A or B" must mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs A and B, then "X employs A or B" is satisfied under either of the above cases. Additionally, the articles "a", "an" as used in this application and in the appended claims shall generally be taken to mean "one or more" unless otherwise specified or it is clear from the context that the form is used. in the singular.
[0126] Additionally, as used herein, the terms "inferring" or "inference" generally refer to the process of rationalizing about or inferring system, environment, or user states from a set of observations as captured through events, or data. Inference can be used to identify a specific context or action, or it can generate a probability distribution across states, for example. Inference can be probabilistic - that is, computing a probability distribution across the states of interest based on a consideration of data and events. Inference can also refer to techniques employed to compose higher-level events from a set of events or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in temporal proximity, and whether the events and data come from one or multiple sources data and events.
[0127] The foregoing includes examples of aspects of the present claimed subject matter. It is, of course, impossible to describe every possible combination of components or methodologies for purposes of describing the present claimed subject matter, but those skilled in the art can recognize that many additional combinations and permutations of the subject matter described are possible. Accordingly, the present described subject matter shall encompass all said alterations, modifications and variations that are within the spirit and scope of the appended claims. Additionally, to the extent that the terms "includes", "owns" or "possessing" are used in the detailed description or claims, such terms shall be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when used as a transition word in a claim.

权利要求:
Claims (11)
[0001]
1. Wireless communication method, characterized in that it comprises: identifying (902) a data network connection (406) established to a user equipment, UE (408) that receives wireless service from a network base station mobile (422); referencing (904) a first identifier associated with a data network access point (404) that facilitates the data network connection (406); and initiating (906) disabling the data network connection (406) if the first identifier does not match a second identifier of a data network access point associated with the mobile network base station (422), wherein the the first identifier and the second identifier comprise the respective first and second Internet Protocol (IP) addresses and the initiation of deactivation is conditioned on the first and second IP addresses not being identical, wherein the correspondence between the first identifier and the second identifier comprises further referencing a list of data network access point identifiers associated with the mobile network base station and determining whether the first identifier is included in the list of data network access point identifiers.
[0002]
2. Method according to claim 1, characterized in that it further comprises: performing a domain name server (DNS) search for the mobile network base station (422) or for the UE (408); retrieve an access point identifier in response to the DNS lookup; and employing the access point identifier as the second identifier.
[0003]
3. Method according to claim 2, characterized in that it further comprises forming a fully qualified domain name, FQDN, which facilitates the identification of a local packet gateway that is geographically or topologically closer to the network base station mobile, wherein the FQDN is based on at least one of: a UE identifier (408); or a mobile network base station identifier (422).
[0004]
4. Method according to claim 1, characterized in that: the list of data network access point identifiers comprises respective mobile network tracking areas, mobile network location areas, network routing areas mobile network, base station identifiers, or radio network controller identifiers, or a combination thereof, for one or more data network access points associated with the mobile network base station.
[0005]
5. Method according to claim 1, characterized in that it further comprises initiating a deactivation request and sending the deactivation request to the UE (408) if the first identifier does not match the second identifier; and initiating a deactivation request and sending the deactivation request to a network entity that manages the data network connection if the first identifier does not match the second identifier.
[0006]
6. Method according to claim 1, characterized in that it further comprises sending a reactivation command to the UE (408) which causes the UE to request reactivation of the data network connection at the network access point associated with the mobile base station.
[0007]
7. Method according to claim 6, characterized in that it further comprises sending the reactivation command as a result of: resetting a local data network gateway supporting the data network connection; load balance the local data network gateway with associated local data network gateways; or the movement of the UE (408) outside a coverage area of the local data network gateway.
[0008]
8. Wireless communication method, characterized in that it comprises: establishing a data network connection through a wireless network; receive a request to disable the data network connection; receiving at a user equipment (UE) a reactivation command for the data network connection, wherein the reactivation command is received in response to a premature termination of the data network connection; comparing, at the UE, a cell identifier of a current serving cell to a more recent cell identifier associated with the data network connection as a result of receiving the wake command; and initiating, at the UE, a request to reactivate the data network connection when a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection.
[0009]
9. Method according to claim 8, characterized in that it further comprises performing a transfer to a neighboring cell, wherein receipt of the request to deactivate results at least in part in carrying out the transfer.
[0010]
10. Method according to claim 8, characterized in that initiating the request further comprises determining that the current serving cell is out of a service range of a local data network gateway supporting the data network connection.
[0011]
11. Equipment for wireless communication, characterized in that it comprises: means for establishing a data network connection via a wireless network; means for receiving a request to disable the data network connection; means for receiving at a user equipment (UE) a reactivation command for the data network connection, wherein the reactivation command is received in response to premature termination of the data network connection; means for comparing, at the UE, a cell identifier of a current serving cell with a most recent cell identifier associated with the data network connection as a result of receiving the wake command; and means for initiating, at the UE, a request to reactivate the data network connection when a cell identifier of a current serving cell is different from a more recent cell identifier associated with the data network connection.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012013309B1|2021-08-10|MANAGING A DATA NETWORK CONNECTION FOR MOBILE COMMUNICATIONS BASED ON USER LOCATION

---

US11172373B2|2021-11-09|Centralized control of femto cell operation

---

TWI463893B|2014-12-01|Method of handling access network discovery and selection function and related communication device

---

US9480092B2|2016-10-25|Establishing packet data network connectivity for local internet protocol access traffic

---

EP2253179B1|2017-02-08|Methods and apparatus for controlling transmission of a base station

---

CN107432047B|2020-12-11|Method for establishing connection between base stations, storage medium, base station and CPE

---

JP2014514863A|2014-06-19|Switching between radio access technologies in multi-mode access points

---

US20130272219A1|2013-10-17|Methods and apparatus for backhaul sharing by femtocells

---

JP2012531826A|2012-12-10|Manage allowed CSG list and VPLMN autonomous CSG roaming

---

US20140302850A1|2014-10-09|Apparatus and Methods for Device to Device Communications

---

CA2765572A1|2011-02-24|Server for control plane at mobile communication network and method for controlling local ip access service

---

US20160073291A1|2016-03-10|Method for deactivating isr capability for proximity service

---

CN106134281A|2016-11-16|For performing method and the user's set of adjacent service

---

AU2014203142B2|2016-04-21|Method and apparatus for managing a select ip traffic offload for mobile communications based on user location

同族专利:

---

公开号 | 公开日

---

AU2010325803B2|2014-07-31|

---

US9503970B2|2016-11-22|

---

CA2973570C|2020-06-30|

---

KR101416301B1|2014-08-06|

---

MY165558A|2018-04-05|

---

CA2973570A1|2011-06-09|

---

TW201134286A|2011-10-01|

---

EP2685683B1|2021-10-27|

---

ZA201204971B|2018-11-28|

---

EP2685683A1|2014-01-15|

---

JP2015029304A|2015-02-12|

---

EP2508016A2|2012-10-10|

---

JP5882427B2|2016-03-09|

---

CA2781154A1|2011-06-09|

---

CA3018174A1|2011-06-09|

---

KR20120101515A|2012-09-13|

---

WO2011069119A2|2011-06-09|

---

RU2533448C2|2014-11-20|

---

BR112012013309A2|2016-04-12|

---

CA3018174C|2020-09-15|

---

CN102640525A|2012-08-15|

---

AU2010325803A1|2012-06-07|

---

US20110235546A1|2011-09-29|

---

WO2011069119A3|2011-09-09|

---

TWI445425B|2014-07-11|

---

CA2781154C|2017-08-22|

---

RU2012127773A|2014-01-10|

---

JP5985559B2|2016-09-06|

---

JP2013513317A|2013-04-18|

---

JP2015029305A|2015-02-12|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US12026A|1854-12-05|Machibtb for rounding the backs op books |

---

FR2755333B1|1996-10-25|1998-12-04|Quinquis Jean Paul|METHOD FOR REFERRING TOWARDS A SERVER EQUIPMENT OF CELLS TRANSMITTED BY A MODULE ATTACHED TO A LOCAL NETWORK FOR ACCESS TO MOBILE AS WELL AS SUCH A NETWORK FOR IMPLEMENTING SAID METHOD|

---

US6779030B1|1997-10-06|2004-08-17|Worldcom, Inc.|Intelligent network|

---

US8949456B2|1998-05-29|2015-02-03|Blackberry Limited|System and method for redirecting data to a wireless device over a plurality of communication paths|

---

US8073327B2|2000-11-08|2011-12-06|Yaron Mayer|System and method for improving the efficiency of routers on the internet and/or cellular networks and/or other networks and alleviating bottlenecks and overloads on the network|

---

US20020118808A1|2001-02-23|2002-08-29|Kelleher David Wayne|Conference system|

---

US7184415B2|2001-12-07|2007-02-27|Telefonaktiebolaget Lm Ericsson |Service access system and method in a telecommunications network|

---

FI112016B|2001-12-20|2003-10-15|Nokia Corp|Conference Call Events|

---

US7054323B2|2002-03-13|2006-05-30|Motorola, Inc.|Method for packet data protocol context activation|

---

JP3764125B2|2002-04-26|2006-04-05|富士通株式会社|Gateway, communication terminal device, and communication control program|

---

US7602893B2|2002-05-07|2009-10-13|Randeep Bhatia|Method and system for supporting rendezvous based instant group conferencing among mobile users|

---

US7099679B2|2002-07-18|2006-08-29|Intel Corporation|Method of saving power by reducing active reception time in standby mode|

---

US6970694B2|2002-07-30|2005-11-29|Interdigital Technology Corporation|Method and apparatus for mobile based access point name selection|

---

US6714635B1|2002-09-10|2004-03-30|Voyant Technologies, Inc.|Method for reservation-less instant group conferencing|

---

US7477920B2|2002-10-25|2009-01-13|Intel Corporation|System and method for automatically configuring and integrating a radio base station into an existing wireless cellular communication network with full bi-directional roaming and handover capability|

---

US7054621B2|2002-11-08|2006-05-30|Sony Ericsson Mobile Communications Ab|Method, device and system for establishing communications with multiple communication devices|

---

US20050245250A1|2003-02-21|2005-11-03|Gidon Ebenshpanger|Device, system and method for detection of communication disconnection|

---

EP1531645A1|2003-11-12|2005-05-18|Matsushita Electric Industrial Co., Ltd.|Context transfer in a communication network comprising plural heterogeneous access networks|

---

DE502004008001D1|2003-11-14|2008-10-16|Nokia Siemens Networks Gmbh|METHOD FOR TRANSMITTING NOTIFICATIONS RELATING TO A MULTIMEDIA BROADCAST / MULTICAST SERVICE , BASIC STATION, PARTICIPANT STATION AND RADIO COMMUNICATION SYSTEM|

---

EP3886479A1|2004-02-18|2021-09-29|Telefonaktiebolaget LM Ericsson |Method and apparatus for unlicensed-radio access in a mobile radio communications system|

---

KR100928352B1|2004-11-09|2009-11-23|텔레폰악티에볼라겟엘엠에릭슨|Method and apparatus for supporting flexible handling of connections towards dual-mode mobile stations|

---

US20060146781A1|2004-12-30|2006-07-06|Intel Corporation|Acess to cellular services from an internet protocol network|

---

WO2006110016A2|2005-04-14|2006-10-19|Lg Electronics Inc.|A method of reconfiguring an internet protocol address in handover between heterogeneous networks|

---

KR100810207B1|2005-07-22|2008-03-06|삼성전자주식회사|Handover method between core network entities in packet-switched based network and therefor apparatus|

---

EP1753198A1|2005-08-09|2007-02-14|Alcatel|Voice over IP Network Architecture|

---

KR101387475B1|2006-03-22|2014-04-22|엘지전자 주식회사|method of processing data in mobile communication system having a plurality of network entities|

---

WO2007125592A1|2006-04-28|2007-11-08|Panasonic Corporation|Communication apparatus and handover method|

---

US20070268873A1|2006-05-18|2007-11-22|Utstarcom, Inc.|Wireless Communication Session Handover Method and Apparatus for use with Different Wireless Access Technologies|

---

JP4992308B2|2006-06-14|2012-08-08|日本電気株式会社|Communication system, operation control method, location management server, and program|

---

CN101563949A|2006-10-31|2009-10-21|意大利电信股份公司|Management of seamless handover between different communication systems in an IP dual-mode terminal|

---

EP2082546B1|2006-11-16|2015-09-23|Telefonaktiebolaget LM Ericsson |Gateway selection mechanism|

---

FI20075252A0|2007-04-13|2007-04-13|Nokia Corp|Procedure, radio system, mobile terminal and base station|

---

FI20075297A0|2007-04-27|2007-04-27|Nokia Siemens Networks Oy|Method, radio system and base station|

---

EP2147541B1|2007-05-18|2016-08-31|Nokia Technologies Oy|System and method for providing local ip breakout services employing access point names|

---

FI20075631A0|2007-09-10|2007-09-10|Nokia Siemens Networks Oy|Procedure, radio system and base station|

---

US20090086672A1|2007-10-01|2009-04-02|Qualcomm Incorporated|Equivalent home id for mobile communications|

---

ES2370667T3|2007-10-26|2011-12-21|Telefonaktiebolaget Lm Ericsson |METHOD AND APPLIANCE FOR USE IN A COMMUNICATIONS NETWORK.|

---

US7996521B2|2007-11-19|2011-08-09|Experian Marketing Solutions, Inc.|Service for mapping IP addresses to user segments|

---

US8463297B2|2007-12-27|2013-06-11|Trueposition, Inc.|Subscriber selective, area-based service control|

---

JP4952586B2|2008-01-07|2012-06-13|富士通株式会社|Packet data discarding method, radio communication apparatus, and mobile communication system|

---

US20100291943A1|2008-01-23|2010-11-18|Attila Mihaly|Method and Apparatus for Pooling Network Resources|

---

GB2458886A|2008-03-25|2009-10-07|Nec Corp|Inter-network handover request message incorporating identifier of target gateway component|

---

CN102171664B|2008-08-06|2014-12-03|莫维克网络公司|Content caching in the radio access network |

---

US8301744B2|2008-08-08|2012-10-30|Telcordia Technologies, Inc.|Systems and methods for QoS provisioning and assurance for point-to-point SIP sessions in DiffServ-enabled MPLS networks|

---

KR101575223B1|2008-11-25|2015-12-09|삼성전자주식회사|Method and system for requesting local breakout in session home enhanced node b|

---

CN101931928B|2009-06-19|2014-08-13|中兴通讯股份有限公司|Method and system for policy and charging control on single-APN multi-PDN connection under ramble scene|

---

KR101584603B1|2009-11-10|2016-01-14|노키아 솔루션스 앤드 네트웍스 오와이|Network device in a communication network and method for providing communications traffic breakout|

---

US20110116469A1|2009-11-16|2011-05-19|Motorola, Inc.|Local internet protocol access/selected internet protocol traffic offload packet encapsulation to support seamless mobility|EP2443897A1|2009-06-18|2012-04-25|Telefonaktiebolaget L M Ericsson |Method and arrangements in a mobile telecommunications system|

---

GB2472866B|2009-08-21|2013-05-08|Samsung Electronics Co Ltd|Network elements, integrated circuits and methods for routing control|

---

KR101465847B1|2009-09-18|2014-11-26|닛본 덴끼 가부시끼가이샤|Communication system and communication control method|

---

US9015318B1|2009-11-18|2015-04-21|Cisco Technology, Inc.|System and method for inspecting domain name system flows in a network environment|

---

US9009293B2|2009-11-18|2015-04-14|Cisco Technology, Inc.|System and method for reporting packet characteristics in a network environment|

---

US9148380B2|2009-11-23|2015-09-29|Cisco Technology, Inc.|System and method for providing a sequence numbering mechanism in a network environment|

---

US8792495B1|2009-12-19|2014-07-29|Cisco Technology, Inc.|System and method for managing out of order packets in a network environment|

---

CN102118789B|2009-12-31|2013-02-27|华为技术有限公司|Traffic offload method, traffic offload function entities and traffic offload system|

---

US9923995B1|2010-02-27|2018-03-20|Sitting Man, Llc|Methods, systems, and computer program products for sharing information for detecting an idle TCP connection|

---

US8787303B2|2010-10-05|2014-07-22|Cisco Technology, Inc.|Methods and apparatus for data traffic offloading at a router|

---

AU2011340789B2|2010-12-08|2014-03-27|Remasys Pty Ltd|End-user performance monitoring for mobile applications|

---

CN103262503B|2010-12-22|2017-05-31|瑞典爱立信有限公司|Node selecting method and equipment in packet core network|

---

US9003057B2|2011-01-04|2015-04-07|Cisco Technology, Inc.|System and method for exchanging information in a mobile wireless network environment|

---

KR101913253B1|2011-02-11|2018-10-30|엘지전자 주식회사|Server serving for control plane in a mobile communication network and method for controlling service|

---

US8665721B2|2011-02-22|2014-03-04|Genband Us Llc|Systems, methods, and computer readable media for maintaining packet data protocolcontext while performing data offload|

---

US20120254448A1|2011-04-02|2012-10-04|Recursion Software, Inc.|System and method for selection of network transport within a mobile device|

---

EP2696611B1|2011-04-03|2017-08-16|LG Electronics Inc.|Method and apparatus for supporting mobility of selected ip traffic offload, sipto, in a communication network|

---

US8737221B1|2011-06-14|2014-05-27|Cisco Technology, Inc.|Accelerated processing of aggregate data flows in a network environment|

---

US8743690B1|2011-06-14|2014-06-03|Cisco Technology, Inc.|Selective packet sequence acceleration in a network environment|

---

US8792353B1|2011-06-14|2014-07-29|Cisco Technology, Inc.|Preserving sequencing during selective packet acceleration in a network environment|

---

US8948013B1|2011-06-14|2015-02-03|Cisco Technology, Inc.|Selective packet sequence acceleration in a network environment|

---

WO2012177024A1|2011-06-18|2012-12-27|Lg Electronics Inc.|Traffic offload via local network based on apn-specific or non-apn-specific informaiton|

---

US9913213B2|2011-07-07|2018-03-06|Nokia Solutions And Networks Oy|Methods, devices and computer program products providing for RAN based LGW selection|

---

CN102892143B|2011-07-20|2015-11-25|华为技术有限公司|The method of data distribution and subscriber equipment|

---

CN110049431B|2011-09-09|2021-07-23|交互数字专利控股公司|Method and apparatus for direct communication|

---

US9736045B2|2011-09-16|2017-08-15|Qualcomm Incorporated|Systems and methods for network quality estimation, connectivity detection, and load management|

---

US20130250780A1|2011-09-16|2013-09-26|Qualcomm Incorporated|Systems and methods for network quality estimation, connectivity detection, and load management|

---

KR20130038092A|2011-10-07|2013-04-17|주식회사 케이티|Method for provisioning qos policy with offloaded traffic and apparatus thereof|

---

ES2873373T3|2011-10-27|2021-11-03|Ericsson Telefon Ab L M|Caching in wireless communication networks|

---

CN103167558B|2011-12-08|2017-04-19|华为技术有限公司|Access method and system and user equipment and network side equipment|

---

WO2013091236A1|2011-12-23|2013-06-27|Nokia Corporation|Method and apparatus for traffic offloading|

---

JP2015511432A|2012-01-27|2015-04-16|ノキア ソリューションズ アンド ネットワークス オサケユキチュア|Session termination in mobile packet core network|

---

WO2013123644A1|2012-02-21|2013-08-29|Nokia Siemens Networks Oy|Local networks|

---

CN103379542B|2012-04-18|2016-09-07|中兴通讯股份有限公司|It is applied to acquisition methods and the system of the shunting business information of wlan network|

---

JP2014011759A|2012-07-03|2014-01-20|Sharp Corp|Mobile communication system, home base station device, position management device, communication method, and mobile station device|

---

US9167438B2|2012-08-31|2015-10-20|International Business Machines Corporation|Mobility detection for edge applications in wireless communication networks|

---

KR102185568B1|2012-09-14|2020-12-03|인터디지탈 패튼 홀딩스, 인크|System enhancements for enabling non-3gpp offload in 3gpp|

---

EP2898726A4|2012-09-20|2016-04-13|Nec Corp|Communication system and communication control method|

---

EP2717626A3|2012-10-02|2014-07-09|HTC Corporation|Local gateway reselection|

---

US20140119292A1|2012-10-26|2014-05-01|Qualcomm Incorporated|Systems and methods for samog bearer management|

---

US9357430B2|2012-10-26|2016-05-31|Qualcomm Incorporated|Systems and methods for samog bearer management|

---

TWI520634B|2012-12-10|2016-02-01|財團法人工業技術研究院|Method and system for data traffic offload|

---

US10028179B2|2013-05-31|2018-07-17|Qualcomm Incorporated|Reducing signaling during AP to AP handoff in dense networks|

---

US9521077B2|2013-07-22|2016-12-13|Verizon Patent And Licensing Inc.|Network connection via a proxy device using a generic access point name|

---

WO2015018453A1|2013-08-09|2015-02-12|Nokia Solutions And Networks Oy|Offloading traffic of a user equipment communication session from a cellular communication network to a wireless local area network |

---

US9432906B2|2013-09-12|2016-08-30|Cisco Technology, Inc.|Handling connected mode mobility from areas bounding multi-operator core network and non-multi-operator core network shared infrastructure|

---

CN105122888B|2013-10-21|2019-05-24|华为技术有限公司|Method for routing, gateway and base station between base station|

---

US9521539B2|2014-06-05|2016-12-13|Cisco Technology, Inc.|System and method for small cell gateway core network selection in a multi-operator core network environment|

---

US9282465B2|2014-06-16|2016-03-08|Cisco Technology, Inc.|Multi-operator core network shared small cell deployment in a non-multi-operator macro network environment|

---

CN105491557B|2014-09-15|2020-04-21|中兴通讯股份有限公司|System and method for realizing capability opening and capability opening platform|

---

US10313916B2|2014-11-11|2019-06-04|Qualcomm Incorporated|Selected IP flow ultra low latency|

---

TWI568279B|2015-10-27|2017-01-21|財團法人工業技術研究院|Management method for wireless network and network management node|

---

US10425887B2|2015-11-10|2019-09-24|Blackberry Limited|Gateway selection controlled by network|

---

US11006274B2|2015-11-30|2021-05-11|Qualcomm Incorporated|Service-based network selection|

---

CN110138554A|2015-12-10|2019-08-16|深圳市大疆创新科技有限公司|Data connection, transmission, reception, the method and system of interaction and aircraft|

---

WO2017152387A1|2016-03-09|2017-09-14|华为技术有限公司|Voice service processing method and apparatus|

---

RU2630420C1|2016-05-05|2017-09-07|Юрий Алексеевич Громаков|System of cellular communication with channel capacity transfer|

---

WO2018005424A1|2016-06-27|2018-01-04|Spidercloud Wireless, Inc.|System and method for service provider specific remote access via neutral host networks|

---

WO2018022052A1|2016-07-28|2018-02-01|Hewlett-Packard Development Company, L.P.|Regulating assignment of a wireless local area network communication channel|

---

CN108377459B|2016-10-11|2020-09-01|中国移动通信有限公司研究院|Connection management method and device|

---

CN108810872A|2017-05-03|2018-11-13|阿里巴巴集团控股有限公司|Control the methods, devices and systems of data transmission|

---

KR102149263B1|2017-05-09|2020-08-28|후아웨이 테크놀러지 컴퍼니 리미티드|Session management method and session management function network element|

---

US10789179B1|2017-10-06|2020-09-29|EMC IP Holding Company LLC|Decentralized access management in information processing system utilizing persistent memory|

---

US11160014B2|2017-10-16|2021-10-26|Qualcomm Incorporated|Connection gateway selection in a mobile communications device|

---

CN109889406B|2019-02-02|2021-05-14|北京百度网讯科技有限公司|Method, apparatus, device and storage medium for managing network connection|

---

US10880702B1|2019-06-04|2020-12-29|Sprint Communications Company L.P.|Data communications for user applications that are executing in a wireless user device|

---

US11224012B1|2020-06-18|2022-01-11|T-Mobile Usa, Inc.|Simulating continuous millimeter wave band access to a telecommunications network|

---

US20220022025A1|2020-07-14|2022-01-20|Celona, Inc.|Local Traffic Offload Function with Overloaded S5 and SGI Interface|

法律状态:
2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-02-11| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2020-02-18| B15K| Others concerning applications: alteration of classification|Free format text: AS CLASSIFICACOES ANTERIORES ERAM: H04W 8/08 , H04W 36/00 Ipc: H04L 12/66 (2006.01), H04W 48/00 (2009.01), H04W 7 |

---

2021-06-08| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-08-10| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 03/12/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF, QUE DETERMINA A ALTERACAO DO PRAZO DE CONCESSAO. |

优先权:

---

申请号 | 申请日 | 专利标题

---

US26689709P| true| 2009-12-04|2009-12-04|

---

US61/266,897|2009-12-04|

---

US12/893,190|2010-09-29|

---

US12/893,190|US9503970B2|2009-12-04|2010-09-29|Managing a data network connection for mobile communications based on user location|

---

PCT/US2010/058978|WO2011069119A2|2009-12-04|2010-12-03|Managing a data network connection for mobile communications based on user location|

---