This patent application relates to an access point in a cellular network for providing a cellular device with network connectivity to a different network.
When connecting to a radio network, an access terminal selects an access point from available radio network access points that are within communication range. Network protocols are used in communicating between an access point and the access terminal.
The 1×RTT protocol has been standardized by the Telecommunication Industry Association (TIA) in the TIA-2000.1 through TIA-2000.6 series of specifications, which are incorporated herein by reference.
The 1×EV-DO protocol has been standardized by the TIA as TIA/EIA/IS-856, “CDMA2000 High Rate Packet Data Air Interface Specification,” 3GPP2 C.S0024-0, Version 4.0, Oct. 25, 2002, which is incorporated herein by reference. Revision A to this specification has been published as TIA/EIA/IS-856A, “CDMA2000 High Rate Packet Data Air Interface Specification,” 3GPP2 C.S0024-A, Version 2.0, July 2005. Revision A is also incorporated herein by reference. Revision B to this specification has been published as TIA/EIA/IS-8560B, 3GPP2 C.S0024-B, version 1.0, April 2006, and is also incorporated herein by reference. Other wireless communication protocols, such as UMTS (Universal Mobile Telecommunications Service), may also be used.
This patent application describes a system for use in wireless communication. The system includes a first device communicating via a first protocol in a first network, a cellular device communicating via a second protocol in a cellular network, the second protocol being incompatible with the first protocol, and an access point in the cellular network, the access point being accessible by the cellular device and being configured to enable communication between the first device and the cellular device.
The system may include one or more of the following features. The first protocol can include a digital living network alliance (DLNA) protocol. The first protocol can include a proprietary protocol. The access point can be configured to provide a cellular-air interface through which the cellular device communicates with the first device. The access point can include a femtocell. The first network and the cellular network an be in a same femtozone. The first network and the cellular network can be in different femtozones. The first device and the cellular device can communicate via a tunnel through one or more other networks.
This patent application also describes a method, used in connection with a first network including a first device that uses a first communication protocol, and a cellular network including a cellular device that uses a second communication protocol incompatible with the first communication protocol. The method includes enabling the cellular device to communicate with the first device by converting messages to the cellular device to the second communication protocol, and by converting the messages to the first device to the first communication protocol.
The method may include one or more of the following features. The enabling can include notifying the first network of presence of the cellular device. The cellular network can further include an access point and the notifying can include generating a message compatible with the first protocol by the access point and delivering the message to the first network. The first protocol can include a DLNA protocol and the message can include a DLNA-compatible message. The first protocol can include a proprietary protocol and generating can include generating a DLNA-compatible message and converting the DLNA-compatible message to a message compatible with the proprietary protocol. The method can further include limiting an amount of communication traffic between devices within the first network from entering the cellular network. The method can further include limiting an amount of communication traffic between devices within the cellular network from entering the first network. The method can further include applying a policy associated with network security to the communication between the cellular device and the first device. The method can further include transcoding a data packet delivered between the cellular device and the first device. The first device and the cellular device can communicate through a cellular-air interface. The first device and the cellular device can communicate through a macro network. The second access point can include a femtocell.
This patent application also describes a system for use in wireless communication. The system includes a first device in a first network, a cellular device in a cellular network, the cellular device comprising applications, an access point in the cellular network, the access point being accessible by the cellular device, and a cellular network connectivity function (CNCF) residing at least partially on the access point and being configured to represent the applications of the cellular device to communicate with the first device when the cellular device and the first device communicate.
The system may include one or more of the following features. The CNCF can include a CNCF server residing on the access point and a CNCF client residing on the cellular device. The CNCF server can communicate with the CNCF client using a protocol having a higher priority level than that of a protocol the cellular device uses to communicate within the cellular network. The cellular device can use a cellular network protocol incompatible with a protocol that the first device uses in the first network. The cellular device can use a protocol compatible with a protocol that the first device uses in the first network.
This application also describes a method, used in connection with a first network including a first device, and a cellular network including a cellular device and an access point accessible by the cellular device. The method includes representing applications of the cellular device using a CNCF to communicate with the access point, and enabling the cellular device to communicate with the first device through the access point based on the representation of the CNCF. The first device can communicate with a protocol incompatible with a protocol that the cellular device uses for communication.
The details of one or more examples are set forth in the accompanying drawings and the description below. Further features, aspects, and advantages will be apparent from the description, drawings, and the claims.
Referring to
RAN 100 uses the 1×EV-DO protocol to transmit data packets between an access terminal, e.g., access terminal 114 and 116, and a macro BTS, e.g., BTSs 108, 110, 112. The BTSs 108 may be connected over a backhaul connection 118 to radio network controller/packet data serving nodes (RNC/PDSN) 120a-b, which may include one or more physical devices at different locations. Although this description uses terminology from EV-DO standards, the same concepts are applicable to other communication standards, including 1×RTT, GSM, UMTS, HSDPA, WiMax, WiBro or WiFi.
The access terminals, such as access terminal 114, may be single-user devices, such as a cellular telephones and PDAs, or multiple-user devices, such as routers 117a that allow single-user devices, such as laptops 117b, to connect to the access terminals through local links (not shown). In some examples, the local links can be wired connections, e.g., Ethernet on a wired LAN, or wireless, e.g., Wi-Fi connections to a wireless local area network (LAN).
Functions of the BTS and the radio network controller (RNC) may be combined into a single device; functions of the PDSN and the radio network control (RNC) may be combined into a single device; and functions of the BTS, the RNC and the PDSN may be combined into the same device.
The implementations described herein are independent of the above combinations and the benefits apply to all combinations. References in this description to a radio access network (RAN) 100 taking action or being acted upon generally refer to a radio network control (RNC) 120a or a radio network control (RNC) 120a in combination with other devices.
Access terminals, such as access terminal 114, may be in communication with a BTS, such as BTS 108, through an air link 124. The air link 124 may include a forward link 124a (also referred to as a downlink), which carries data from a BTS 108 to an access terminal 114, and a reverse link 124b (also referred to as an uplink), which carries data from the access terminal 114 to the BTS 108.
Referring to
A private access point, such as access point 202, may use an available high-speed Internet connection, such as a connection over a digital subscriber line (DSL) modem or a cable modem 204, for connection to the backhaul 218. Such an access point may be in communication with a network 219, such as a remote network or the Internet. Generally, private access points communicate with network 219 through a backhaul connection 218, such as a DSL or a cable connection. Network 219 may include one or more remote network servers, such as servers 201 and 203. A network server database, such as database 209, may be included within at least one of the network servers, such as server 203. Database 209 may be included within the same server 201 as a time server or network server database 209 may include the time server.
In the home 200, the access point 202 is used both by at least one single-user cellular device 206 and at least one multi-user home network access point 230. The access point 202 provides authorized single-user cellular device 206 with connections to a cellular network 207 to establish data connections; and the multi-user home network access point 230 provides devices (or access terminals) such as computers 232, 234, and a printer 236 with connections to a home network 208 to establish data connections. The home network access point 230 can be a WiFi access point or a router, e.g., the router 117a of
The home network 208 can use the DLNA (digital living network alliance) protocol to transmit data packets, e.g., messages or commands, among the access terminals, e.g., the computers 232, 234, the printer 236, and the access point 230. The DLNA protocol includes one or more protocols and technologies, for example, the Universal Plug and Play (UPnP) protocol. The DLNA protocol can be used for data transmission among devices in the home network 208 by, for example, providing functions such as discovering, controlling the devices in the home network 208, presenting data from one device to another, and providing events to the devices. For example, the access point 230 and its access terminals are configured so that when an access terminal, e.g., the computer 232, requests to gain access to the home network 208 by, e.g., turning the computer 232 on, the access terminal delivers a message compatible with the DLNA protocol to the access point 230 to notify the access point 230 of presence of the computer 232. The devices that have accessed the home network 208, such as the computers 232, 234, the printer 236, and the access point 230 are capable of communicating with each other within the home network 208, and with connected external networks, such as the Internet 219. Other proprietary protocols, for example, Tivo or Bonjour, can also be used in the home network 208. Discussion of the function of the communication protocol within a home network 208 is also provided at http://www.dlna.org and http://www.upnp.org, the contents of both are incorporated by reference.
Generally, the home network 208 and the cellular device 206 within the cellular network 207 do not communicate with each other directly. The cellular network protocol, e.g., 1×EV-Do, UMTS, 1×RTT, that the cellular network 207 uses is not compatible with the DLNA protocol or with the proprietary protocols that the home network 208 uses.
Referring to
The CNCF 237 includes a first functional block CNCF client 240 operating on each cellular device 206 and a second functional block CNCF server 242 operating on the access point 202. The CNCF client 240 and the CNCF server 242 communicate with each other using a protocol 238 having a high priority level than that of the cellular network protocol. Accordingly, the CNCF client 240 is enabled to represent the applications of each cellular device 206 to exchange messages between the cellular device 206 and the CNCF server 242, and to provide events received from the CNCF to the applications. In particular, the CNCF client 240 implements a client stack functionality by building an interface between the CNCF server 242 and the cellular stacks so that applications 244 is enabled to communicate with the CNCF server 242. In addition, the CNCF client 240 also provides asynchronous events to the applications 244 when it receives the events from the CNCF server 242. The protocol 238 facilitates achieving various, e.g., all, functionalities of the CNCF client 240 and the CNCF server 242 to enable communication between the home network 208 and the cellular network 207. For example, the protocol 238 provides a way for the CNCF client 240 to send commands and responses to the CNCF server 242, or for the CNCF server 242 to send the asynchronous events to CNCF client 240.
The communications between the CNCF client 240 and CNCF server 242, and between the cellular devices 206 to the home network 208 can be enabled by software programs implemented on the access point 202 and the cellular devices 206. The software programs can be installed into devices and access points by manufacturers prior to commercial sales or can be obtained separately and installed by users. The CNCF can be configured so that a user can activate or deactivate its functionality when desired.
The CNCF provides a bridge for communication between the cellular devices 206 and the home network 208. The bridging process can include notifying each device within the two networks of the presence of any other devices, constructing an extended network 254, and delivering data packets between the devices in the cellular network 207 and those in the home network 208 once the extended network 254 is constructed. The extended network 254 can be constructed automatically when the cellular devices 206 and the network 208 are on, or manually upon the request of a user. The CNCF server 242 gathers presence information from devices in the cellular network 207 and the home network 208, and provides the gathered information to each present device in both networks, based on the subscription level of each device to its corresponding network. In particular, when the bridging is requested (automatically or manually), the applications 244 of each cellular device 206 communicate with the CNCF client 240 through the application programming interface (API) 246. The CNCF client 240, representing the applications 244 delivers a message 250 to the access point using a protocol compatible with the cellular network protocol within the cellular protocol stacks 248, 252 on the cellular device 206 and the access point 202. Upon being notified of the presence of the cellular device 206, the CNCF server 242 of the access point 202 generates a DLNA-compatible message associated with the presence and delivers the message to the access point 230 (
Effectively, the CNCF enables the access point 230 to treat the cellular network 207 as one access terminal within the home network 208. Such an extension allows the devices that are compatible with the DLNA or other protocols, e.g., the computers 232, 234 of
The bridging process the CNCF performs can also be accompanied by a transcoding process to adapt a media format used in the devices within the home network 208 to one that is used in the devices within the cellular network 207, and vice versa. In the example discussed above, the piece of media delivered from the computer 232 can be in a format that is unrecognizable by the cellular device 206, e.g., in a format that facilitates efficient delivery. The CNCF, when bridging the delivery, can transcode the media piece to a format that is supported by the cellular device. In some implementations, the CNCF also transcodes data packets that are delivered between two different cellular devices within the cellular network 207. Different cellular devices can support different media formats and the CNCF adapts a media format of a packet to a specific format of a destination cellular device.
The CNCF can also function as a gateway between the cellular network 207 and the home network 208 to control traffic between the two networks. The CNCF together with the access point 202 keeps the cellular network 207 and the home network 208 relatively independent from each other when the devices within each network are communicating internally. For example, when a data packet is delivered from a device within a first network, access point 202 identifies the destination of a received data packet and blocks the broadcasting of the delivery within a second, different network when the destination is not a device in the second network. When a device in the cellular network 207 delivers a message to another device in the same network, the access point 202 reads and blocks the message from being broadcast to all devices within the home network 208 and effectively routes the message only within the cellular network 207. The CNCF can also limit communication between devices in different networks based on the intention of the device for the communication. For example, the CNCF implements policies on behalf of the cellular devices 206 to process only certain events from the home network 208 so that, for example, only a desired portion of the entire events in the home network 208 are sent to the cellular devices 206. In particular, when the cellular device 206 is only interested in communing with the printer 236 of the home network 208, even though the home network 208 can have other devices, for example, a fax machine (not shown), that advertise their services. In this case, the CNCF will only send printer-related events/presence information to the cellular devices 206. The gateway function of the CNCF server reduces the communication traffic between the devices and within each network, and the amount of broadcasts each device receives. The reduction of traffic can enhance the efficiency and effectiveness of communication within the extended network 254.
In addition, the CNCF can also implement authentication and security policies during communication between the cellular network 207 and the home network 208. For example, the CNCF can control, e.g., restrict, network connections between a device within the cellular network 207 and the operator network of the home network 208, e.g., the network 219 of
The CNCF also authenticates a device requesting network connections to another device external to the non-extended network in which the requesting device is located. The authorization can be done when devices in different networks are broadcasting their presence and constructing the extended network 254 or when a specific network connection is requested to deliver data packets. For example, when a DLNA message is received by the access point 202 indicating that the computer 232 requests to communicate with one of the cellular devices 206, the CNCF server 242 examines the DLNA message to determine whether the computer 232 can be authorized to enter the cellular network 207. In some implementations, the CNCF applies different levels of security and authentication policies based on specific circumstances of the network connectivity. Generally, all devices, including the access point 230, which are connected to the access point 202 have been authenticated when constructing the extended network 254. As a result, less strict authentication is needed when the existing devices are communicating across networks (e.g., between the home network 208 and the cellular network 207). When a new device, e.g., a copier (not shown), is authorized to access the home network 208, the CNCF applies strict authentication rules to the copier to determine whether the copier is allowed to access the cellular network 207. Similarly, when a new cellular device, e.g., a cellular phone of a visitor to the home 200, is authorized to use the cellular network 207, the CNCF strictly authenticates the cellular phone for its access to the home network 208.
The CNCF can also be configured to provide the bridging, gateway, and authentication functions described above to a cellular network located in a first femtozone and a home network located in a second, different femtozone. This is done using a communication tunnel 229. For example, referring back to
The CNCF can also be configured to provide network connections between a cellular network and a home network that uses a proprietary protocol other than the DLNA protocol. Such networks may be in the same femtozone or in different femtozones. In the example shown in
In some implementations, other cellular devices (not shown) that are capable of communicating directly with the home network 208 (e.g., when the cellular devices include protocols compatible with those of the home network 208) to communicate, locally or remotely, with the home network 208 indirectly through the CNCF. The communication protocol 238 between the CNCF client 240 and the CNCF server 242 can have a higher priority level than that of the direct communication protocol between the cellular devices and the home network 208. The CNCF client represents the communication applications of such cellular devices similarly to the representation of those applications 244 of the cellular devices 206; and the CNCF performs similar functions to those described above as to the communication. The indirection communication can allow the use of the access point 202, e.g., a femtocell, to be compatible with different devices for communication between different networks. Such indirect communication can also provide security protection to the home network 208 by preventing unauthorized, direct communication between the cellular devices and the home network 208. For example, the cellular devices can be authenticated by the access point 202 prior to accessing the home network 208.
Following the process 400 of
The extended network can be built by other processes or by executing the process 420 of
According to the process 440 of
According to the process 480 of
The techniques described herein can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The techniques can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device such as a computer-readable storage medium, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Actions associated with the techniques described herein can be performed by one or more programmable processors executing a computer program to perform functions described herein by operating on input data and generating output. Actions associated with the techniques can also be performed by, and apparatus for implementing the techniques can include, e.g., special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Modules can refer to portions of the computer program and/or the processor/special circuitry that implements that functionality.
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact over a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Components of different embodiments described herein may be combined to form other embodiments not specifically set forth above. Any features described herein may be combined with features found in U.S. application Ser. No. 11/958,975, the contents of which are incorporated by reference.
Other embodiments not specifically described herein are also within the scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
6711144 | Kim et al. | Mar 2004 | B1 |
6731618 | Chung et al. | May 2004 | B1 |
6741862 | Chung et al. | May 2004 | B2 |
6781999 | Eyuboglu et al. | Aug 2004 | B2 |
7170871 | Eyuboglu et al. | Jan 2007 | B2 |
7200391 | Chung et al. | Apr 2007 | B2 |
7242958 | Chung et al. | Jul 2007 | B2 |
7277446 | Abi-Nassif et al. | Oct 2007 | B1 |
7299278 | Ch'ng | Nov 2007 | B2 |
7664081 | Luoma et al. | Feb 2010 | B2 |
7764981 | Kalofonos et al. | Jul 2010 | B2 |
8520659 | Humblet | Aug 2013 | B2 |
20020196749 | Eyuboglu et al. | Dec 2002 | A1 |
20030100311 | Chung et al. | May 2003 | A1 |
20050185671 | Hansen et al. | Aug 2005 | A1 |
20050213555 | Eyuboglu et al. | Sep 2005 | A1 |
20050243749 | Mehrabanzad et al. | Nov 2005 | A1 |
20050245279 | Mehrabanzad et al. | Nov 2005 | A1 |
20060025181 | Kalofonos et al. | Feb 2006 | A1 |
20060067422 | Chung | Mar 2006 | A1 |
20060067451 | Pollman et al. | Mar 2006 | A1 |
20060126509 | Abi-Nassif | Jun 2006 | A1 |
20060159045 | Ananthaiyer et al. | Jul 2006 | A1 |
20060240782 | Pollman et al. | Oct 2006 | A1 |
20060291420 | Ng | Dec 2006 | A1 |
20060294241 | Cherian et al. | Dec 2006 | A1 |
20070026884 | Rao | Feb 2007 | A1 |
20070058628 | Rao et al. | Mar 2007 | A1 |
20070077948 | Sharma et al. | Apr 2007 | A1 |
20070097916 | Eyuboglu et al. | May 2007 | A1 |
20070115896 | To et al. | May 2007 | A1 |
20070140172 | Garg et al. | Jun 2007 | A1 |
20070140184 | Garg et al. | Jun 2007 | A1 |
20070140185 | Garg et al. | Jun 2007 | A1 |
20070140218 | Nair et al. | Jun 2007 | A1 |
20070155329 | Mehrabanzad et al. | Jul 2007 | A1 |
20070220573 | Chiussi et al. | Sep 2007 | A1 |
20070230419 | Raman et al. | Oct 2007 | A1 |
20070238442 | Mate et al. | Oct 2007 | A1 |
20070238476 | Raman et al. | Oct 2007 | A1 |
20070242648 | Garg et al. | Oct 2007 | A1 |
20070248042 | Harikumar et al. | Oct 2007 | A1 |
20080003988 | Richardson | Jan 2008 | A1 |
20080013488 | Garg et al. | Jan 2008 | A1 |
20080062925 | Mate et al. | Mar 2008 | A1 |
20080065752 | Ch'ng et al. | Mar 2008 | A1 |
20080069020 | Richardson | Mar 2008 | A1 |
20080069028 | Richardson | Mar 2008 | A1 |
20080076393 | Khetawat et al. | Mar 2008 | A1 |
20080076398 | Mate et al. | Mar 2008 | A1 |
20080117842 | Rao | May 2008 | A1 |
20080119172 | Rao et al. | May 2008 | A1 |
20080120417 | Harikumar et al. | May 2008 | A1 |
20080139203 | Ng et al. | Jun 2008 | A1 |
20080146232 | Knisely | Jun 2008 | A1 |
20080151843 | Valmikam et al. | Jun 2008 | A1 |
20080159236 | Ch'ng et al. | Jul 2008 | A1 |
20080162924 | Chinitz et al. | Jul 2008 | A1 |
20080162926 | Xiong et al. | Jul 2008 | A1 |
20090131049 | Osborn | May 2009 | A1 |
20090156213 | Spinelli et al. | Jun 2009 | A1 |
20100128709 | Liu et al. | May 2010 | A1 |
20100130162 | Yang | May 2010 | A1 |
20100165957 | Hegde et al. | Jul 2010 | A1 |
Entry |
---|
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Packet Data Air Interface Specification”, C.S0024, version 4.0, Oct. 25, 2002 (548 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Packet Data Air Interface Specification”, C.S0024-A, version 1.0, Mar. 2004 (1083 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-A, version 2.0, Jul. 2005 (1227 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-B, version 1.0, Apr. 2006 (1623 pages). |
3rd Generation Partnership Project “3GPP2”, “cdma2000 High Rate Data Air Interface Specification”, C.S0024-B, version 2.0, Mar. 2007 (1627 pages). |
Provisional application with appendix of U.S. Appl. No. 61/117,005, filed Nov. 21, 2008. |
3rd Generation Partnership Project 2 “3GPP2”, “Introduction to cdma2000 Standards for Spread Spectrum Systems”, 3Gpp2 C.S0001-D, Version 2.0, Sep. 6, 2005, Release D (16 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Physical Layer Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0002-D, Version 2.0, Sep. 6, 2005, Revision D (538 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0003-D, Version 2.0, Sep. 2005, Release D (255 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems”, Release D, 3GPP2 C.S0004-D, Version 2.0, Sep. 2005, Revision D. v2.0, (264 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems”, Release D, 3GPP2 C.S0005-D, Version 2.0, Sep. 2005, Release D (2367 pages). |
3rd Generation Partnership Project 2 “3GPP2”, “Analog Signaling Standard for cdma2000 Spread Spectrum Systems”, 3GPP2 C.S0006-D, Version 2.0, Sep. 2005, Release D (95 pages). |
http://www.dlna.org, “The Digital Revolution is Here”, retrieved from Internet on Aug. 25, 2014 (1 page). |
http://upnp.org, “Standardized DCPs & Certification”, retrieved from Internet on Aug. 25, 2014 (1 page). |
Number | Date | Country | |
---|---|---|---|
20100165957 A1 | Jul 2010 | US |