In this digital age, modern telecommunication service providers and device manufacturers are increasingly relying on public and/or private IP networks, including the Internet, as a core part of their technology. For example, many telecommunications service providers now offer a suite of Voice over IP (“VoIP”) services, as well as various data services, that utilize IP networks and/or IP-based wireless access networks (e.g., access networks based on IEEE 802.16 (“WiMAX”), IEEE 802.20 Mobile Broadband Wireless Access (MBWA), Ultra Wideband (UWB), 802.11 wireless fidelity (“Wi-Fi”), Bluetooth, and similar standards) for at least part of their infrastructure. Likewise, device manufacturers are producing a new generation of mobile devices such as wireless handhelds, wireless handsets, mobile phones, personal digital assistants, notebook computers, and similar devices. These devices are enabled to send and receive information using IP-based telecommunications services. In fact, many of today's modern mobile devices are able to function as “dual-mode devices” that take advantage of both cellular network technologies and IP-based technologies.
Unlicensed Mobile Access (UMA) technology has developed as part of this trend to incorporate IP solutions into mobile device telecommunication systems. UMA technology has been accepted into Release 6 of the 3rd Generation Partnership Project (3GPP) and is also referred to as Generic Access Network (GAN) technology. In various implementation schemes, UMA allows wireless service providers to merge cellular networks (such as Global System for Mobile Communications (GSM) networks) and IP-based wireless networks into one seamless service (with one mobile device, one user interface, and a common set of network services for both voice and data). One goal of UMA is to allow subscribers to move transparently between cellular networks and IP-based wireless networks with seamless voice and data session continuity, much like they can transparently move between cells within the cellular network. Seamless in-call handover between the IP-based wireless network and the cellular network ensures that the user's location and mobility do not affect the services delivered to the user.
At an operational level, UMA technology effectively creates a parallel radio access network, the UMA network, which interfaces to the mobile core network using standard mobility-enabled interfaces. For example, UMA can replace a system's GSM radio technology on the lower protocol layers with a wireless LAN, or similar technology. A call or other communication may be tunneled to the Mobile Switching Center (MSC) of a mobile service provider via an access point (e.g., a WiFi access point connected to a modem via the Internet) and gateway (e.g., a UMA network controller). In many cases, the mobile core network remains unchanged, making it much easier to maintain full service and operational transparency and allowing other aspects of the service infrastructure to remain in place. For example, in many systems that utilize UMA, the existing service provider's business support systems (BSS), service delivery systems, content services, regulatory compliance systems, and operation support systems (OSS) can support the UMA network without change. Likewise, service enhancements and technology evolution of the mobile core network apply transparently to both cellular access and UMA.
The following description provides specific details for a thorough understanding of, and enabling description for, various embodiments of the technology. One skilled in the art will understand that the technology may be practiced without these details. In some instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the technology. It is intended that the terminology used in the description presented below be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain embodiments of the technology. Although certain terms may be emphasized below, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
I. Sample Network Configurations
In a communication or set of communications 106, the access point 104 receives IP packets from the telecommunications device 108. These IP packets are then transported through the IP network 114 to a signaling gateway 116, which in the example of
The network system 100 of
Referring to
In general, the described network system 200 accepts registration requests from the mobile device 206. The accepted registration requests can be requests to either the cellular telephone network 202 or to the IP-based network 204. Accordingly, to handle requests to the cellular telephone network 202, the cellular telephone network 202 includes one or more cell towers 208 that are configured to accept cellular communications 210 from the mobile device 206. The cell towers 208 are connected to a base station controller 212 (such as a base station controller/radio network controller (BSC/RNC)) via a private network 214. The private network 214 can include a variety of connections (not shown) such as T1 lines, a wide area network (WAN), a local area network (LAN), various network switches, and other similar components.
The base station controller 212 controls communication traffic to a carrier core network 216, where all communications are managed (including both cellular and IP-based). Components of the carrier core network 216 in this example include a switch (e.g., a mobile switching center or MSC) 218, which is configured to control data/call flows and perform load balancing, as well as other functions. The carrier core network 216 may also include a variety of system databases such as an operation support subsystem (OSS) database 220, a business support system (BSS) database 222, and home location register (HLR) 224 or other central subscriber database that contains details of a carrier's subscribers for billing, call logging, etc.
The sample network system 200 of
When the mobile device 206 attempts to access the IP network 204 (i.e., to initiate an IP-based communication), information (e.g., data, voice, SMS, etc.) is initially formatted in the cellular system's 202 native protocol and then encapsulated into Internet Protocol (IP) packets, which are transmitted to the access point 226 and routed through the IP network 204 to a security gateway 236. In contrast to non-IP communication requests, such transmissions bypass the cellular telephone system's 202 existing network of radio towers. The security gateway 236 controls access to a network controller 238, which communicates with a data store 242 for logging and accessing communications data. Thus, one function of the network controller 238 is to manage access to the carrier network 216 when dealing with an IP-based communication (in a similar manner to that performed by the base station controller 212 for a non-IP-based communication).
In one example, authentication of a request for access by the mobile device 206 over the IP network 204 is handled by the security gateway 236, which communicates with an authentication, access and authorization (AAA) module 240 that is most likely associated with the carrier network 216. Challenges and responses to requests for access by the mobile device 206 are communicated between the HLR 224 and the AAA module 240. When authorization is granted, the security gateway 236 communicates the assignment of an IP address to the mobile device 206 that requested access. Once the security gateway 236 passes the IP address to the mobile device 206, the public IP address assigned to the mobile device 206 is passed to the network controller 238.
In another authorization example, upon receiving an identifier from the mobile device 206, the network controller 238 may query the data store 242 to determine if the mobile device 206 is authorized for accessing the IP network 204. Sample identifiers that may be utilized to determine access include a media access control (MAC) address associated with an access point, a mobile device or subscriber identifier (such as an International Mobile Subscriber Identifier (IMSI)), an Internet Protocol (IP) address (or “Public IP address”) associated with the access point, a fully qualified domain name (FQDN), or other similar types of information. The data store 242 may be a single database, table, or list, or a combination of databases, tables, or lists, such as one for IP addresses 244, one of MAC addresses 246, and one for FQDNs 248. The data store 242 may include “blocked” identifiers as well as “authorized” identifiers. Authorized accesses to the IP-based wireless telecommunications network may be maintained by the network controller 238 in an authorized session table or similar data construct.
In some cases, the signaling portion of a communication (e.g., the portion of the communication that governs various overhead aspects of the communication such as, for example, when the call starts, when the call stops, initiating a telephone ring, etc.) is routed through the network controller 238 to the switch 218, while the voice bearer portion of the communication (e.g., the portion of the communication that contains the actual content (either data or voice information) of the communication) is routed through the network controller 238 to a media gateway 250. In other words, the media gateway 250 controls the content flow between the service provider and the mobile device 206, while the switch 218 controls the signaling flow (or controls overhead-related flow) between the service provider and the mobile device 216.
At step 302, mobile device 206 initiates a call by sending a request to register to the security gateway 236. The security gateway 236 replies with an authentication challenge communicated back to the mobile device 206 at step 304. At step 306, the mobile device 206 responds to the authentication challenge with a response communicated to security gateway 236. Also at step 306, the security gateway 236 communicates a public IP address assigned to the access point 226 to the network controller 238. The mobile device 206 also communicates the IMSI ID and a Cell Global Identifier (CGI) record (CGIREAL) to the security gateway 236. The CGI record is an identifier in a GSM network that uniquely identifies a base station initiating a call through the core network. In a UMA connection, CGIREAL is the CGI record for the nearest base station 208. At step 308, the security gateway 236 transmits the IMSI ID, CGIREAL along with the SSI and MAC address (MACAP) from the access point 226 to the network controller 238. Network controller 238 communicates with database 242 at step 308, which replies with CGIBILLING at step 310. CGIBILLING is used by the UMA network to ensure that the call is billed correctly. At step 312, network controller 238 communicates a registration completion message to the mobile device 206.
Once the registration is completed, mobile device 206 communicates with network controller 238 to request a call at step 314. At step 316, the network controller 238 communicates the IMSI ID and CGIBILLING to switch 218. Switch 218 authorizes the call at step 318 such that the mobile device 206 can communicate over a communication channel established through switch 218 at step 320. At step 322, the call is terminated and switch 218 communicates a call data record (CDR) to the billing system (i.e. the BSS 222).
Although
In some configurations, the access point 226 includes components to provide the connected landline telephone with a simulation of a Plain Old Telephone Service (POTS) network. For example, the access point 226 may act as a POTS end office by providing a dial tone when the user lifts the telephone off the hook if there is a connection to the carrier network. The access point may also provide calling name and number for incoming calls by translating the data from the IP-based telecommunications format to the format used by a POTS caller ID service. It may similarly provide the ability to toggle between calls for call waiting using the standard flash hook by translating the POTS signal into the equivalent UMA format. The access point 226 may also provide a standard POTS stutter dial tone to indicate new voice mail. The access point 226 could do this by periodically querying the carrier network 216 to determine if new voice mail is available and providing the stutter dial tone if the carrier network indicates that there is new voice mail. In addition to the stutter tone, the access point 226 may include an indicator (e.g. a flashing light) to notify the user that new voice mail is available.
II. Selectively Provisioning Connections between the Access Point and the Network
A method and system for reducing network load by selectively provisioning connections between an access point and the carrier network is disclosed. One advantage of providing an IP-based telecommunications connection for a landline telephone is that it allows customers to pay a single bill for all telephone services. In addition, a landline telephone may be easier and more ergonomic for customers to use at home because such telephones do not have to be as compact as a mobile device. Also, customers may prefer to use a landline telephone because they do not have to worry about draining the battery, as they would with a mobile phone. However, a problem that arises when the access point 226 supports connections from a landline telephone is that it is less clear when the connection needs to be provisioned. As discussed above for
The access point also has a connection manager component 516. The connection manager component 516 provisions call connections between the access point 226 and the carrier network 216 when the access point 226 determines that the connection should be set up. The connection manager 516 executes the call setup steps described above for
The telephone connector component 512 is associated with a detection component 518, which determines if a landline telephone is connected to the telephone connector component 512. The detection component 518 may use any method known in the art to detect the landline telephone. For example,
Alternatively,
The connection manager component 516 uses data from these components to selectively provision a connection with the carrier network.
The system may, for example, be configured to loop at a specified interval, such as every 3 seconds, to detect whether a telephone has been plugged in to the telephone connector 512. Alternatively, the detection component 518 may be configured to act as an interrupt by sending a notification signal to the connection manager component automatically when it detects that a telephone is connected. In this example, the connection manager component 516 is configured to provision a connection in response to the interrupt signal. Additionally, the system may be configured to only check for a landline telephone at startup time, in which case the loop terminates after the first check.
As shown in
III. Conclusion
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above detailed description of embodiments of the system is not intended to be exhaustive or to limit the system to the precise form disclosed above. While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges. Those skilled in the art will also appreciate that the actual implementation of a database may take a variety of forms, and the term “database” is used herein in the generic sense to refer to any data structure that allows data to be stored and accessed, such as tables, linked lists, arrays, etc.
The teachings of the methods and system provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the technology can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the technology.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain embodiments of the technology, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the technology disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the technology should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the technology with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the invention under the claims.
While certain aspects of the technology are presented below in certain claim forms, the inventors contemplate the various aspects of the technology in any number of claim forms. For example, while only one aspect of the invention is recited as embodied in a computer-readable medium, other aspects may likewise be embodied in a computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the technology.
Number | Name | Date | Kind |
---|---|---|---|
4998271 | Tortola et al. | Mar 1991 | A |
5513263 | White et al. | Apr 1996 | A |
6493629 | Van Bosch | Dec 2002 | B1 |
6612489 | McCormick et al. | Sep 2003 | B2 |
6615035 | Lucidarme et al. | Sep 2003 | B1 |
6985583 | Brainard et al. | Jan 2006 | B1 |
7110545 | Furuya et al. | Sep 2006 | B2 |
7295556 | Roese et al. | Nov 2007 | B2 |
7376221 | Remy et al. | May 2008 | B1 |
7433673 | Everson et al. | Oct 2008 | B1 |
7577458 | Lin | Aug 2009 | B2 |
7610062 | Beeman et al. | Oct 2009 | B2 |
7701947 | Cunetto et al. | Apr 2010 | B2 |
7773579 | Liu et al. | Aug 2010 | B1 |
7792093 | Myhre et al. | Sep 2010 | B2 |
7843903 | Bakke et al. | Nov 2010 | B2 |
7864673 | Bonner | Jan 2011 | B2 |
8160614 | Shaffer | Apr 2012 | B2 |
8320344 | Hodroj et al. | Nov 2012 | B2 |
20010030235 | Hedemann et al. | Oct 2001 | A1 |
20010052006 | Barker et al. | Dec 2001 | A1 |
20020147926 | Pecen et al. | Oct 2002 | A1 |
20020188581 | Fortin et al. | Dec 2002 | A1 |
20030119480 | Mohammed | Jun 2003 | A1 |
20040078708 | Li et al. | Apr 2004 | A1 |
20040133689 | Vasisht | Jul 2004 | A1 |
20040192299 | Wilson et al. | Sep 2004 | A1 |
20040203815 | Shoemake et al. | Oct 2004 | A1 |
20050026650 | Russell | Feb 2005 | A1 |
20050054342 | Otsuka | Mar 2005 | A1 |
20050063542 | Ryu | Mar 2005 | A1 |
20050078819 | Hsu et al. | Apr 2005 | A1 |
20050083911 | Grabelsky et al. | Apr 2005 | A1 |
20050094592 | Schmidt | May 2005 | A1 |
20050114504 | Marolia et al. | May 2005 | A1 |
20050159149 | Wen et al. | Jul 2005 | A1 |
20050160287 | Mehta et al. | Jul 2005 | A1 |
20050174992 | Files et al. | Aug 2005 | A1 |
20050181805 | Gallagher | Aug 2005 | A1 |
20050243809 | Best et al. | Nov 2005 | A1 |
20060075485 | Funahashi et al. | Apr 2006 | A1 |
20060121941 | Shiflett | Jun 2006 | A1 |
20060198361 | Chen | Sep 2006 | A1 |
20060223498 | Gallagher et al. | Oct 2006 | A1 |
20060256800 | Harrington et al. | Nov 2006 | A1 |
20060293024 | Benco et al. | Dec 2006 | A1 |
20060293038 | Walter et al. | Dec 2006 | A1 |
20060293082 | Neuhaus | Dec 2006 | A1 |
20070008885 | Bonner | Jan 2007 | A1 |
20070026862 | Hicks et al. | Feb 2007 | A1 |
20070049342 | Mayer et al. | Mar 2007 | A1 |
20070079113 | Kulkarni et al. | Apr 2007 | A1 |
20070115900 | Liang et al. | May 2007 | A1 |
20070123231 | Kim | May 2007 | A1 |
20070168553 | Jones et al. | Jul 2007 | A1 |
20070177562 | Castrogiovanni et al. | Aug 2007 | A1 |
20070195803 | Lowery et al. | Aug 2007 | A1 |
20080020773 | Black et al. | Jan 2008 | A1 |
20080046998 | Cromer et al. | Feb 2008 | A1 |
20080095086 | Linkola et al. | Apr 2008 | A1 |
20080151866 | Wu | Jun 2008 | A1 |
20080160914 | McRae et al. | Jul 2008 | A1 |
20080189550 | Roundtree | Aug 2008 | A1 |
20080254833 | Keevill et al. | Oct 2008 | A1 |
20080311917 | Marathe et al. | Dec 2008 | A1 |
20090043876 | Zhang et al. | Feb 2009 | A1 |
20090074187 | Inoue et al. | Mar 2009 | A1 |
20090085760 | Lee | Apr 2009 | A1 |
20090132675 | Horn et al. | May 2009 | A1 |
20090154701 | Kosaraju et al. | Jun 2009 | A1 |
20090163245 | Oozeki | Jun 2009 | A1 |
20090215394 | Dewan | Aug 2009 | A1 |
20090220216 | Marsh et al. | Sep 2009 | A1 |
20100014507 | Linkola et al. | Jan 2010 | A1 |
20100190492 | Jiang | Jul 2010 | A1 |
20100235621 | Winkler et al. | Sep 2010 | A1 |
20100265845 | Lampen | Oct 2010 | A1 |
20110299686 | Saboff et al. | Dec 2011 | A1 |
20120317224 | Caldwell et al. | Dec 2012 | A1 |
20130083785 | Hodroj et al. | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
2666472 | Aug 2010 | CA |
1530321 | May 2005 | EP |
1865656 | Dec 2007 | EP |
WO-2004102941 | Nov 2004 | WO |
WO-2006018047 | Feb 2006 | WO |
WO-2006062907 | Jun 2006 | WO |
WO-2006078430 | Jul 2006 | WO |
WO-2006135285 | Dec 2006 | WO |
WO-2007015075 | Feb 2007 | WO |
WO-2008036938 | Mar 2008 | WO |
WO-2010099229 | Sep 2010 | WO |
Entry |
---|
U.S. Appl. No. 12/446,971, filed Apr. 23, 2009, System and Method for Managing Access Point Functionality and Configuration. |
U.S. Appl. No. 12/401,550, filed Mar. 10, 2009, Method of Securely Pairing Devices With an Access Point for an IP-Based Wireless Network. |
U.S. Appl. No. 12/175,414, filed Jul. 17, 2008, System and Method for Selectively Provisioning Telecommunications Services Between an Access Point and a Telecommunications Network Using a Subscriber Identifier. |
“Vonage and Motorola Announce a Co-Branded Internet Telephone Adaptor with Wireless Router,” PR Newswire (U.S.), Mar. 14, 2007, Copyright 2007 PR Newswire Association LLC, 2 pages. |
Bertolucci, Jeff, “Vonage's flashy V-Portal offers easier VoIP setup,” PC World, Apr. 1, 2008, Copyright 2008 PC World Communications, Inc., 1 page. |
Dontronics, USB to RJ-11 VoIP Phone Adaptor, Apr. 19, 2006, <http://www.dontronics.com/phoneconnector.html>, 7 pages. |
Greene, Tim, “Vonage tailors VoIP for small firms: Flat-fee dialing includes local, long-distance calls,” Network World, Jun. 23, 2003, Copyright 2003 Network World, Inc., 2 pages. |
Honan, Mathew, “I Am Here: One Man's Experience With the Location-Aware Lifestyle,” Wired Magazine: 17.2 (pp. 1-7), <http://www.wired.com/gadgets/wireless/magazine/17-02/Ip—guineapig?currentPage=all> [date accessed Jan. 23, 2009]. |
International Search Report and Written Opinion for PCT/US2009/051072; Applicant: T-Mobile USA, Inc.; Mailing Date: Nov. 6, 2009, 12 pages. |
IVT Corporation, Bluetooth PSTN Voice AP, Apr. 19, 2006, <http://www.ivtcorporation.com/products/ap/index.php>, 3 pages. |
Lazarowitz, Elizabeth, “Easy Call: Phoning Via Web,” New York Daily News, Feb. 5, 2007, Copyright 2007 Daily News, New York, 3 pages. |
Shaw, Keith, “VoIP invades the home network,” Network World, Aug. 30, 2004, Copyright 2004 Network World, Inc., 1 page. |
Telco Systems: A BATM Company, Access200 Product Family Voice over IP Analog Telephone Adapters, Copyright 2005 Telco Systems, 2 pages. |
International Search Report and Written Opinion for PCT/US2010/026715; Filed on Mar. 9, 2010, Applicant: T-Mobile USA, Inc., Mailed on Oct. 18, 2010, 10 pages. |
European Patent Office, Supplementary European Search Report and Opinion, EP Patent Application 07854249, mailed Jun. 4, 2012, 6 pages. |
International Searching Authority, International Search Report, PCT Application PCT/US2010/025271, mailed Dec. 28, 2010, 3 pages. |
International Searching Authority, Written Opinion, PCT Application PCT/US2010/025271, mailed Dec. 28, 2010, 4 pages. |
“AirStation One-Touch Secure System (AOSS),” White paper downloaded from www.buffalo-technology.com on May 27, 2009 bearing a date of Oct. 2004, Buffalo technology (USA), Inc., pp. 1-7. |
“Frequently Asked Questions: Wi-Fi Protected Setup,” Wi-Fi Alliance 2006, pp. 1-4. |
“Wi-Fi Certified™ for Wi-Fi Protected Setup™: Easing the User Experience for Home and Small Office Wi-Fi® Networks,” © 2007, 2008, 2009 Wi-Fi Alliance, 14 pages. |
“Wi-Fi Protected Setup,” Wi-Fi Alliance 2007, http:www.wi-fi.org/wifi-protected-setup/ [Accessed on Sep. 28, 2010], 2 pages. |
Belkin International, Inc., “Belkin N1 Vision Wireless Router User Manual,” Jul. 11, 2007, 117 pages. |
Helander, Johannes et al., “Secure Web Services for Low-Cost Devices,” Proceedings of the Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC'05), May 18-20, 2005, pp. 130-139. |
Houghton, Mike, “Cellular Modems: 3G Access on the Move,” article downloaded from www.enterpriseplanet.com on May 27, 2009 bearing a date of May 25, 2006, Enterprise IT Planet, 4 pages. |
IEEE-SA Standards Board, IEEE Std. 802.11, 1999 Edition, Reaffirmed 2003, 37 pages. |
International Search Report and Written Opinion, International Application No. PCT/US2007/82010, Filed on Oct. 19, 2007, Applicant: T-Mobile USA, Inc., Date of Mailing: Jun. 16, 2008, 10 pages. |
International Search Report and Written Opinion, International Application No. PCT/US2007/82010, Filed on Oct. 19, 2007, Applicant: T-Mobile USA, Inc., Date of Mailing: Jun. 18, 2008, 10 pages. |
International Search Report and Written Opinion, International Application No. PCT/US2007/82285, Filed on Oct. 23, 2007, Applicant: T-Mobile USA, Inc., Date of Mailing: Mar. 10, 2008, 10 pages. |
N1 Wireless Router User Manual, Belkin International, Inc., 2007, 104 pages. |
Number | Date | Country | |
---|---|---|---|
20100014506 A1 | Jan 2010 | US |