The present invention relates to a method of and an apparatus for providing access to a communications network and billing for related services. In particular, the present invention relates to a method of and apparatus for generating income for an owner of a network access device used to provide access to a communications network.
A small portion of the radio frequency (RF) spectrum is assigned to each communications carrier. The assigned spectrum, therefore, must be used efficiently in order to allow the maximum number of frequency users to have access to this spectrum. Multiple access modulation techniques have been developed to provide optimum utilization of the RF spectrum. Examples of such modulation techniques include time division multiple access (TDMA), frequency division multiple access (FDMA), and code division multiple access (CDMA).
There is a wide variance in the performance of wireless networks. A conventional wireless cellular network covers a relatively large geographical area, but provides a relatively low bandwidth. Such wireless networks use regulated portions of the radio spectrum and are shared by many users. The infrastructure costs of wireless networks are relatively high due to the size and complexity of the cellular network equipment.
Other wireless networks, such as CDMA2000-EV-DO/DV networks, offer higher bandwidth and enhanced data services, such as web browsing. However, these networks also pack many users into a relatively small portion of the regulated spectrum. Other types of radio networks are adapted to improve spectral efficiency with increased speed and smaller coverage areas. For example, an IEEE 802.11x (or Wi-Fi) network may transmit at speeds up to 11 Mbps using a Direct Sequence Spread Spectrum (DSSS) mode or at speeds up to 54 Mbps using an Orthogonal Frequency Division Multiplexing (OFDM) mode.
An access point conforming to an IEEE 802.11x (e.g., IEEE 802.11b) network may cover an area of a few hundred feet in diameter. Each such access point is connected to a larger network (e.g., Internet). One such example is Wi-Fi VoIP (Wireless Fidelity Voice over Internet Protocol), through which a mobile device user can place a wireless telephone call over the Internet, using the technology specified in IEEE 802.11b at the network access point. VoIP is a method for taking analog audio signals and converting them into digital data that can be transmitted over the Internet. Conventional VoIP telephone communications are enabled by VoIP network carriers, which utilize VoIP networks, e.g. the Internet, to place VoIP based telephone calls. VoIP enabled and compatible networks include VoIP switching for proper routing and billing of VoIP based telephone calls.
In order to cover larger geographical areas, a relatively large number of IEEE 802.11x network access points and relatively large wire-line back haul networks are required. In part, due to the relatively small geographical coverage area of each network access point, the resulting IEEE 802.11x based network may thus be prohibitively expensive to set up. Further, the small coverage areas may lead to many “dead zones” in which mobile device users are unable to place telephone calls using the VoIP network.
Embodiments of the present invention are directed to network access points with embedded switching capabilities. the network access points provide access to a communications network, preferably an IP network. The network access points provide end user devices access to the communications network. These network access points include virtual private network (VPN) and conventional network security technology to provide comprehensive security and privacy. A controller within the network access point utilizes a switching module to track usage of the network access point by wirelessly connected end user devices. Using the switching module, usage associated with each individual end user device is tracked to distinguish each end user device accessing the network access point. The tracked usage information is transmitted from the network access point to a remotely coupled data center. The data center collects usage information from a plurality of different network access points. The collected usage information is in turn transmitted from the data center to an network carrier, such as an IP network carrier or a telephone network carrier. The network carrier uses the received usage information to bill users for accessing the communications network via the network access points and using any services provided by the network access points.
In the preferred embodiment, the network access point tracks VoIP telephone usage by a wireless end user device accessing the network access point for the purpose of utilizing an IP network to make a telephone call. Alternatively, the wireless end user device utilizes the network access point to access an IP network for purposes other than making a telephone call, such as sending and receiving email or broadband content. In this alternative embodiment, the network access point tracks any usage of the network access point by the wireless end user device. The network access point provides additional services associated with accessing the IP network. Using the switching module, the network access point is also able to track usage of these additional services. In yet another alternative embodiment, the carrier network is any conventional communications network, and the network access points provide access to the communications network for end user devices.
In one embodiment, the end user device is configured to perform the necessary conversion of data for transmission over the IP network. For example, when a VoIP telephone call is made using the end user device, the end user device converts the audio signal to IP compatible digital data (e.g. VoIP conversion) and the converted digital data is sent to the network access point, for example using Wi-Fi.
In another embodiment, the network access point is configured to perform the necessary conversion of data for transmission over the IP network. For example, when a VoIP telephone call is made using the end user device, the end user device transmits the audio signal, for example an RF signal, to the network access point where the audio signal is converted to IP compatible digital data.
A network access point of the type described above is utilized as an extension of an existing communications network infrastructure. Entities other than the network carrier can implement the network access point and thereby provide users access to the communications network via their network access point. The network access point, using its embedded switching module, tracks any usage of the network access point by the end user device, and the tracked usage is provided to the network carrier for billing to the user. As compensation for providing this service, the owner of the network access point is remunerated by the network carrier according to an agreed upon schedule. The network carrier benefits by expanding the coverage area accessible to its communications network without having the up-front cost of expanding the network infrastructure itself.
The invention is described relative to the several views of the drawings. Where appropriate and only where identical elements are disclosed and shown in more than one drawing, the same reference numeral will be used to represent such identical elements.
The access point 120 is coupled to a data center 140 via broadband connection 124. The broadband connection 124 can be either a wired or wireless broadband connection. The data center 140 includes a switching and billing server 142 and a network carrier interface server 144. The network carrier maintains the network 130. Usage information collected by the access point 120 is transmitted to the switching and billing server 142 within the data center 140. The switching and billing server 142 collects usage information for each end user device 100 that utilizes the access and services provided by the access point 120. The usage information is associated with a specific end user corresponding to each end user device 100.
The network carrier interface server 144 communicates with a network carrier data terminal 150. The network carrier data terminal 150 is associated with the network carrier that provides usage of the network 130 by the end user devices 100. The network carrier data terminal 150 includes user information associated with the end users of the end user devices 100. This user information is provided by the network carrier data terminal 150 to the network carrier interface server 144. The network carrier interface server 144 provides the user information to the switching and billing server 142. The usage information received from the access point 120 is matched to the user information received from the network carrier interface server 144 to form billing records associated with each end user. The billing records are periodically provided by the data center 140 to the network carrier data terminal 150. The network carrier uses the billing records to bill the corresponding end users for their access and use of the network 130 via the access point 120, and any associated other services provided.
The access point 120 preferably functions as a broadband termination point. As such, the access point 120 is considered an end user broadband network element within the network 110. The network 110 is preferably configured as either a home or enterprise network associated with the access point 120. Examples of a network access point include, but are not limited to, a wireless or wired broadband termination element, a wireless or wired modem, a wireless or wired router, and a Wi-Fi access point.
In an alternative embodiment, a broadband termination point is configured separately from the access point 120, yet within the network 110. In this alternative embodiment, the broadband termination point is coupled to the access point 120 via a broadband connection. The broadband connection can be a wired connection or a wireless connection.
The access point 120 is adapted to transmit signals to and receive signals from the network connections 106. Each of the network connections 106 can be either a wireless connection or a wired connection. Preferably, each of the end user devices 100 is a mobile, or wireless, device and the network connections 106 are wireless connections. Transmissions sent over the wireless connections are preferably transmitted according to Wi-Fi or any other wireless protocol capable of transmitting IP compatible data. Alternatively, the end user devices 100 are wired devices and the network connections 106 are wired connections. As such, the access point 120 can be configured for both wired and wireless network communications.
In one embodiment, the end user device 100 is configured to perform the necessary conversion of data for transmission over the network 130. For example, when a VoIP telephone call is made using the end user device 100, the end user device 100 converts the audio signal to IP compatible digital data (e.g. VoIP conversion) and the converted digital data is sent to the access point 120, for example using a Wi-Fi protocol.
In another embodiment, the access point 120 is configured to perform the necessary conversion of data for transmission over the network 130. For example, when a VoIP telephone call is made using the end user device 100, the end user device 100 transmits the audio signal, for example an RF signal, to the access point 120 where the audio signal is converted to IP compatible digital data.
Each of the end user devices 100 can be wireless, wired, or configured for both wireless and wired. Exemplary end user devices include, but are not limited to, computers, televisions, music players/recorders, PDAs, telephones, or any conventional end user device capable of sending and receiving communications over the network 130. The end user device can also be a mobile communications device configured to automatically switch an existing communication from a wireless cellular network (hereinafter alternatively referred to as cellular network) to a wireless IP network, or to switch an existing communication from an IP network to a cellular network. Such a mobile communication device is described in co-pending and co-owned U.S. patent application Ser. No. 11/031,498, filed Jan. 6, 2005, and entitled “TELEPHONE WITH AUTOMATIC SWITCHING BETWEEN CELLULAR AND VOIP NETWORKS”, which is hereby incorporated by reference.
In the exemplary system 200 shown in
As applied to the system 200, wired connections can be configured according to any conventional wired transmission technologies including, but not limited to, LANs, WANs, and the Internet. Wireless connections included within the system 200 can be configured according to any conventional wireless transmission technologies including, but not limited to, IEEE 802.11a/b/g and Wi-Max.
The switching module 240 provides tracking capabilities, such that when an end user device 100 utilizes the access point 120 to access the network 130, this usage is tracked and associated with the specific end user device 100. The access point 120 provides the end user device 100 with additional services associated with accessing the IP network 130. The switching module 240 enables tracking of these additional services. Tracking performed by the switching module 240 is sent as usage information to the billing and services module 250. The usage information, along with the particular end user device 100 associated with the usage information, is stored in the billing and services module 250. The usage information is transmitted from the billing and services module 250 to the data center 140 (
In operation of the system 200 (
The access point 120 includes a tracking capability that enables tracking of any usage of the access point 120 by a particular end user device 100. For example, if the end user device 100 is within the coverage area of the access point 120 and the end user device 100 utilizes the access point 120 to access the network 130 for the purposes of making a VoIP telephone call, the access point 120 tracks the duration of the VoIP telephone call over the network 130. This tracking information, also referred to as usage information, is collected by the access point 120 and associated with the particular end used device 100. The usage information is transmitted from the access point 120 to the data center 140, where the usage information is matched to user information received from the network carrier data terminal 150 to form a billing record. The network carrier data terminal 150 is associated with the network carrier that provides the communication over the network 130. The billing records are stored in the data center 140 and are periodically transmitted to the network carrier, via the network carrier data terminal 150.
At the step 304, once the end user device is provided access to the access point, the access point provides a connection to the network, thereby providing a communication link between the end user device and the network. The communication link can be used for a VoIP telephone call, transmission of broadband content to the end user device, or other data transmission applications. At the step 306, the end user device utilizes one or more services associated with the network. Preferably, the access point enables use of these services. At a minimum, one service utilized by the end user device is using the access point to access the network. In this case, the duration of time that a particular end user device is connected to the network via the access point is tracked and associated with the particular end user device. If content data is accessed by the end user device via the access point, then the type of content data can be tracked. In general, any utilization of the one or more services can be tracked.
At the step 308, services used by the end user device are tracked by the access point. Usage information corresponding to services used by a particular end user device is associated with the particular end user device. The usage information, including its associated end user device, is collected and stored by the access point. At the step 310, the usage information is first transmitted from the access point to a data center. The data center includes a switching and billing server that receives the usage information from the access point. The data center also includes an network carrier interface server that receives user information from the network carrier associated with the network. The switching and billing server receives the user information from the network carrier interface server and matches the user information to the usage information received from the access point to form billing records. The billing records are then transmitted to the network carrier. At the step 312, the network carrier uses the billing records to bill the user of the end user device that utilized the network via the access point. At the step 314, income is provided to the third party owner of the access point. The income provided is determined by a payment schedule previously agreed to by the network carrier and the third party owner.
The network access point is preferably owned by a third party independent of the network carrier. A portion of the revenue collected from end users for accessing the communications network via the network access point is distributed to the third party owner. The communications network is essentially expanded by the network access points without the network carrier paying the capital expenditures required in building out the carrier network. Instead, the capital expenditure burden is assumed by the third party owner of the network access point, and in exchange, the third party owner shares in any revenue collected by the network carrier from end users accessing the carrier network via the network access point. Alternatively, the third party owner is compensated based upon previously agreed upon parameters, such as a per minute fee, independent of the billing charges or revenue collected between the end user and the network carrier. It is understood that an end user device can also be a third party owner.
In some embodiments, only a specific entity (e.g., company) is able to earn revenue from an access point (secured, unsecured, trusted, untrusted, mobile, fixed, other). In some embodiments, (cellular) base stations (e.g., LTE, 4G, 5G, and others) are access points. In some embodiments, the revenue earned is direct revenue such as fees for access points and corresponding provisions of broadband/WiFi/“hotspots” (e.g., fixed, mobile, secured, unsecured, trusted, untrusted, other). In some embodiments, the revenue earned is indirect revenue such as content from an access point and/or corresponding broadband/WiFi. For example, the content is able to be multimedia/video content, data, telephone calls, video calls, VoIP multimedia calls, video streaming, data streaming, multi-media sessions, web conferences, and/or advertisements/commercials. The content is able to be secured or unsecured. For secured content, billing is able to be done at the client or on a backend content provider server. The content is able to be pushed, pulled or streamed, and billing is able to be per usage or per usage for a given media type, and/or for what application, page or media it is. Software and/or hardware are able to be installed/used on any devices of a system (e.g., user devices, source devices, access points, proxy devices, others) to collect information to be used with billing. The presence of specific hardware (e.g., a proxy) may be checked/verified as a condition for using a network or accessing content. In some embodiments, peer-to-peer communication is able to be billed by a user device, on an access point or other device in the network and/or at the source of content. In some embodiments, the access points are deployed by the specific entity or are approved by the specific entity. In some embodiments, if another entity deploys an access point without approval by the specific entity, then no revenue is made by the other entity. In some embodiments, if another entity does earn revenue for an access point, then that revenue then goes to the specific entity (not the other entity). In other words, regardless of who implements an access point, the revenue from that access point goes to a specific entity, not other entities (even the implementing entity, unless the implementing entity is the specific entity). In some embodiments, a content provider is able to earn revenue for content only on access points belonging (e.g., owned and/or operated by) to a specific entity, or access points approved by the specific entity, and the content provider is not able to earn revenue for content on access points that do not belong to the specific entity, or are not approved by the specific entity.
In some embodiments, in addition to or instead of earning revenue from an access point, other components of a network are able to provide revenue such as a client/user device, a controller device (e.g., any devices in a network system), a sensor device (e.g., a device configured for sensing items such as network traffic, QoS, and/or any other contexts), and/or any other devices. By receiving revenue based on other devices, an entity does not have to own/control an access point to earn revenue (e.g., earn revenue when another company/user uses an entity's controller). By receiving revenue based on other devices, an entity is able to receive revenue when there is encrypted content. As a session is done with a client code and a continuity server, the entity is able to generate billing events.
In some embodiments, instead of or in addition to sending/determining charging events and billing, a mechanism is implemented to enforce policy/Service Level Agreements (SLAs) on traffic. Enforcing a policy is able to include different processing of media, different routing implementations, and/or different SLAs instead of or in addition to billing aspects. The mechanism is able to be implemented on any device in a network (e.g., client, sensors, controller, access point). Different traffic is able to be processed differently and therefore, transmitted differently.
The system 200 (
Other than providing access to the network 130, an exemplary service provided by the access point 120 is to manage and selectively process broadband content transmitted to the end user devices 100 from a content provider. The access point 120 is preferably configured to perform such management and selective processing of the broadband content according to the co-owned, co-pending U.S. patent application Ser. No. 11/261,153, filed on Oct. 27, 2005, and entitled “APPARATUS FOR CONTROLLING BROADBAND ACCESS AND DISTRIBUTION OF CONTENT AND COMMUNICATIONS THROUGH AN ACCESS POINT”, and co-owned, co-pending U.S. patent application Ser. No. 11/262,156, filed on Oct. 27, 2005, and entitled “METHOD OF PROVIDING BROADBAND CONTENT TO AN END USER DEVICE”, which are hereby incorporated by reference.
As described above in relation to the system 200 in
Although the data center 140 is shown in
The above embodiments of the present invention are illustrative and not limiting. Various alternatives and equivalents are possible. It is understood that the functionality associated with any blocks described above may be centralized or distributed, whether locally or remotely. It is also understood that one or more blocks of each mobile communication device may be performed by hardware, firmware or software, or some combinations thereof. The present invention is not limited by the network. The network access point can be configured to provide access to any conventional communications network. The present invention is not limited by the Wi-Fi signals, such as those defined by IEEE 802.11x, where x may be a, b, g, or Wi-MAX used to carry VoIP communication. The present invention is not limited by the type of integrated circuit(s) in which the present invention may be disposed. Nor is the present invention limited to any specific type of process technology, e.g., CMOS, Bipolar, or BICMOS that may be used to manufacture the present invention.
Although VoIP communications/calls are described throughout, the present invention applies to any content communication such as video, data, and/or telephone calls.
The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of the principles of construction and operation of the invention. As such, references herein to specific embodiments and details thereof are not intended to limit the scope of the claims appended hereto. It will be apparent to those skilled in the art that modifications can be made to the embodiments chosen for illustration without departing from the spirit and scope of the invention.
This patent Application is a continuation-in-part application of U.S. patent application Ser. No. 15/380,958, filed on Dec. 15, 2016, and entitled, “ACCESS POINT WITH CONTROLLER FOR BILLING AND GENERATING INCOME FOR ACCESS POINT OWNER,” which is a continuation application of co-pending U.S. patent application Ser. No. 14/869,520, filed on Sep. 29, 2015, and entitled “ACCESS POINT WITH CONTROLLER FOR BILLING AND GENERATING INCOME FOR ACCESS POINT OWNER,” which is a continuation of U.S. patent application Ser. No. 14/539,907, filed on Nov. 12, 2014, and entitled “ACCESS POINT WITH CONTROLLER FOR BILLING AND GENERATING INCOME FOR ACCESS POINT OWNER,” which is a continuation application of U.S. patent application Ser. No. 11/262,078, filed on Oct. 27, 2005, and entitled “ACCESS POINT WITH CONTROLLER FOR BILLING AND GENERATING INCOME FOR ACCESS POINT OWNER,” which claims priority of U.S. provisional application Ser. No. 60/652,258, filed Feb. 11, 2005, and entitled “METHOD OF AND APPARATUS FOR CONTROLLING BROADBAND ACCESS AND DISTRIBUTION OF CONTENT AND COMMUNICATIONS THROUGH AN ACCESS POINT,” by the same inventors, which are all incorporated by reference. This application incorporates U.S. provisional application Ser. No. 60/652,258 in its entirety by reference. U.S. patent application Ser. No. 11/262,078, filed on Oct. 27, 2005, and entitled “ACCESS POINT WITH CONTROLLER FOR BILLING AND GENERATING INCOME FOR ACCESS POINT OWNER,” is also a continuation-in-part of U.S. patent application Ser. No. 11/031,498, filed Jan. 6, 2005, and entitled “TELEPHONE WITH AUTOMATIC SWITCHING BETWEEN CELLULAR AND VOIP NETWORKS”, which is hereby incorporated by reference. U.S. patent application Ser. No. 11/031,498 claims priority of U.S. provisional application Ser. No. 60/534,466, filed Jan. 6, 2004, and entitled “RADIOTELEPHONE WITH AUTOMATIC SWITCHING BETWEEN CELLULAR AND WI-FI NETWORKS USING WI-FI SIGNAL STRENGTH VALUES”, the content of which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6009328 | Muszynski | Dec 1999 | A |
6175737 | Kao | Jan 2001 | B1 |
6195543 | Granberg | Feb 2001 | B1 |
6473413 | Chiou et al. | Oct 2002 | B1 |
6515983 | Utas | Feb 2003 | B1 |
6553022 | Hartmaier | Apr 2003 | B2 |
6584087 | Czaja et al. | Jun 2003 | B1 |
6754833 | Black et al. | Jun 2004 | B1 |
6795700 | Karaoguz et al. | Sep 2004 | B2 |
6862444 | Karaoguz et al. | Mar 2005 | B2 |
6996107 | Janoska | Feb 2006 | B2 |
7127232 | O'Neil et al. | Oct 2006 | B2 |
7142847 | Umeda et al. | Nov 2006 | B2 |
7254119 | Jiang et al. | Aug 2007 | B2 |
7382763 | Ludwig et al. | Jun 2008 | B2 |
7398088 | Belkin et al. | Jul 2008 | B2 |
7483984 | Jpnker et al. | Jan 2009 | B1 |
7512796 | Haverinen et al. | Mar 2009 | B2 |
8041360 | Ibe et al. | Oct 2011 | B2 |
8514867 | Ganesan | Aug 2013 | B2 |
8520605 | Ganesan | Aug 2013 | B2 |
8958434 | Ganesan | Feb 2015 | B2 |
20010049790 | Faccin et al. | Dec 2001 | A1 |
20020073226 | Sridhar | Jun 2002 | A1 |
20020078174 | Sim et al. | Jun 2002 | A1 |
20020085516 | Bridgelall | Jul 2002 | A1 |
20020114305 | Oyama et al. | Aug 2002 | A1 |
20020147008 | Kallio | Oct 2002 | A1 |
20020150228 | Umeda et al. | Oct 2002 | A1 |
20020152305 | Jackson et al. | Oct 2002 | A1 |
20020183038 | Comstock et al. | Dec 2002 | A1 |
20030009580 | Chen | Jan 2003 | A1 |
20030012350 | Wong et al. | Jan 2003 | A1 |
20030053632 | Bousis | Mar 2003 | A1 |
20030058876 | Conor | Mar 2003 | A1 |
20030061206 | Qian | Mar 2003 | A1 |
20030083079 | Clark et al. | May 2003 | A1 |
20030086366 | Branlund et al. | May 2003 | A1 |
20030087629 | Juitt et al. | May 2003 | A1 |
20030112766 | Riedel | Jun 2003 | A1 |
20030133421 | Sundar | Jul 2003 | A1 |
20030157899 | Trossen et al. | Aug 2003 | A1 |
20030163697 | Pabla | Aug 2003 | A1 |
20030177196 | Bhasin et al. | Sep 2003 | A1 |
20030185172 | Rue | Oct 2003 | A1 |
20030217007 | Fukushima et al. | Nov 2003 | A1 |
20030217091 | Echigo | Nov 2003 | A1 |
20030224792 | Verma et al. | Dec 2003 | A1 |
20030232615 | Kim | Dec 2003 | A1 |
20040005878 | Olin et al. | Jan 2004 | A1 |
20040030791 | Dorenbosch | Feb 2004 | A1 |
20040052223 | Karaoguz | Mar 2004 | A1 |
20040053599 | Karaoguz | Mar 2004 | A1 |
20040076144 | Ishidoshiro | Apr 2004 | A1 |
20040083360 | Walsh | Apr 2004 | A1 |
20040085959 | Ohkawa | May 2004 | A1 |
20040087307 | Ibe et al. | May 2004 | A1 |
20040095916 | Maki | May 2004 | A1 |
20040105424 | Skoczkowski et al. | Jun 2004 | A1 |
20040114559 | Wang | Jun 2004 | A1 |
20040127208 | Nair et al. | Jul 2004 | A1 |
20040132427 | Lee et al. | Jul 2004 | A1 |
20040137902 | Chaskar et al. | Jul 2004 | A1 |
20040141484 | Rogalski et al. | Jul 2004 | A1 |
20040153676 | Krantz | Aug 2004 | A1 |
20040170173 | Pan | Sep 2004 | A1 |
20040174880 | White et al. | Sep 2004 | A1 |
20040176128 | Grabelsky et al. | Sep 2004 | A1 |
20040181811 | Rakib | Sep 2004 | A1 |
20040192294 | Pan et al. | Sep 2004 | A1 |
20040203666 | Foster et al. | Oct 2004 | A1 |
20040203788 | Fors et al. | Oct 2004 | A1 |
20040203802 | McCormick et al. | Oct 2004 | A1 |
20040204097 | Scheinert et al. | Oct 2004 | A1 |
20040205158 | Hsu | Oct 2004 | A1 |
20040218575 | Ibe et al. | Nov 2004 | A1 |
20040229618 | Adatrao et al. | Nov 2004 | A1 |
20040246990 | Krishnamurthi et al. | Dec 2004 | A1 |
20040267880 | Patiejunas | Dec 2004 | A1 |
20050044138 | Albert et al. | Feb 2005 | A1 |
20050059400 | Jagadeesan et al. | Mar 2005 | A1 |
20050090259 | Jain et al. | Apr 2005 | A1 |
20050135286 | Nurminen | Jun 2005 | A1 |
20050147049 | Ganesan | Jul 2005 | A1 |
20050149740 | Kotzin et al. | Jul 2005 | A1 |
20050259958 | Johansson | Nov 2005 | A1 |
20060003796 | Vireday | Jan 2006 | A1 |
20060040711 | Whistler | Feb 2006 | A1 |
20060050663 | Ganesan | Mar 2006 | A1 |
20060050687 | Ganesan | Mar 2006 | A1 |
20060050721 | Ganesan | Mar 2006 | A1 |
20060080423 | Brewer et al. | Apr 2006 | A1 |
20060092901 | Parantainen | May 2006 | A1 |
20060098643 | Pfeffer | May 2006 | A1 |
20060141984 | Taglienti | Jun 2006 | A1 |
20060146767 | Moganti | Jul 2006 | A1 |
20060234678 | Juitt et al. | Oct 2006 | A1 |
20060291455 | Katz et al. | Dec 2006 | A1 |
20070026862 | Hicks, III | Feb 2007 | A1 |
20070076665 | Nair et al. | Apr 2007 | A1 |
20070112948 | Uhlik | May 2007 | A1 |
20070124490 | Kalavade et al. | May 2007 | A1 |
20070249390 | Purkayastha et al. | Oct 2007 | A1 |
20090070489 | Lu et al. | Mar 2009 | A1 |
20090191864 | Mousseau | Jul 2009 | A1 |
20100074228 | Hicks et al. | Mar 2010 | A1 |
20110010282 | Olin | Jan 2011 | A1 |
20110044310 | Uhlik | Feb 2011 | A1 |
Number | Date | Country |
---|---|---|
1723719 | Jan 2006 | CN |
200310113 UI | Jan 2004 | DE |
0936777 | Aug 1999 | EP |
1471665 | Oct 2004 | EP |
2287858 | Sep 1995 | GB |
200226994 | Jan 2002 | JP |
2004320473 | Nov 2004 | JP |
03056719 | Jul 2003 | WO |
2004013998 | Feb 2004 | WO |
2003061177 | Jul 2004 | WO |
2004057903 | Jul 2004 | WO |
Entry |
---|
3GPP Organization Project,“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Service aspects; Handover requirements between UTRAN and GERAN or other radio systems(Release 8)”, Mar. 2006, pp. 1-20. |
3GPP Organization Project,3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Service aspects; Service principles(Release 8), Mar. 2006, pp. 1-45. |
3GPP Organization Project,3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service Requirements for the All-IP Network (AIPN);V8.0.0, Stage 1, (Release 8), p. 1-24. |
“Unlicensed Mobile Access (UMA); Protocols (Stage 3)”, R1.0.4, May 2, 2005, pp. 1-162. |
Office Action from Chinese Patent Application No. 201510039302.4, dated Feb. 8, 2018. |
Number | Date | Country | |
---|---|---|---|
20180077291 A1 | Mar 2018 | US |
Number | Date | Country | |
---|---|---|---|
60652258 | Feb 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14869520 | Sep 2015 | US |
Child | 15380958 | US | |
Parent | 14539907 | Nov 2014 | US |
Child | 14869520 | US | |
Parent | 11262078 | Oct 2005 | US |
Child | 14539907 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15380958 | Dec 2016 | US |
Child | 15815534 | US |