US20100167718A1 - Femto personal proxy application client - Google Patents
Femto personal proxy application client Download PDFInfo
- Publication number
- US20100167718A1 US20100167718A1 US12/347,201 US34720108A US2010167718A1 US 20100167718 A1 US20100167718 A1 US 20100167718A1 US 34720108 A US34720108 A US 34720108A US 2010167718 A1 US2010167718 A1 US 2010167718A1
- Authority
- US
- United States
- Prior art keywords
- identifier
- access point
- applications
- application
- fap
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
Definitions
- This description relates to access terminal authorization at private access points in wireless networks.
- Cellular wireless communications systems are designed to serve multiple wireless-enabled devices distributed over a large geographic area by dividing the area into regions called “cells” or “cell areas”.
- a network-side access device e.g., an access point or base station
- client devices located in the cell area and is commonly referred to as an “access terminal”.
- access terminals include wireless-enabled devices such as cellular telephones, laptops, personal digital assistants (PDAs), and/or other user equipment (e.g., mobile devices).
- An access terminal generally establishes a call, also referred to as a “communication session,” with an access point to communicate with other entities (e.g., servers) in the network.
- an access point detects a presence of a first device having a device identifier in a femtozone associated with the access point.
- the access point matches the device identifier with an identifier associated with corresponding applications and activates a set of applications associated with the device identifier.
- the access point may deactivate the set of applications when the presence of the first device is not detected.
- Implementations may include one or more of the following.
- the first device may include a handset.
- Matching may include looking up the device identifier in a database that is accessible to the access point.
- Activating an application in the set of applications may include changing a value of a usage flag associated with the application from “off” to “on”, and deactivating an application in the set of applications may include changing a value of a usage flag associated with the application from “on” to “off”.
- At least one application in the set of activated applications associated with the device identifier may run on one or more devices chosen from a group comprising the access point, the first device, a second device attached to a home network attached to the access point, and a network server communicating with the access point.
- a method comprises steps as outlined above.
- a computer program product tangibly embodied in a computer readable storage medium, is operable to cause a data processing apparatus to perform operations comprising the steps of the method above.
- an apparatus can be configured to perform the steps outlined above.
- an access point detects a presence of a first device having a device identifier in a femtozone associated with the access point.
- the access point matches the device identifier with an identifier associated with an auxiliary application and activates the auxiliary application associated with the identifier that interacts with one or more device applications.
- the access point creates a data connection between the auxiliary application and the first device.
- the access point may deactivate the auxiliary application and terminate the data connection between the auxiliary application and the first device when the presence of the device is not detected by the detector.
- Implementations may include the following.
- the auxiliary application associated with the device identifier may run on a device chosen from a group comprising the access point and a second device attached to a home network associated with the access point.
- a method comprises steps as outlined above.
- a computer program product tangibly embodied in a computer readable medium, is operable to cause a data processing apparatus to perform operations comprising the steps of the method above.
- an apparatus can be configured to perform the steps outlined above.
- FIG. 1 is a diagram illustrating a wireless network.
- FIG. 2 is a diagram illustrating a wireless network with a home networking deployment.
- FIG. 3 is a diagram illustrating a personal proxy application client for a femtocell.
- FIG. 4 is a diagram illustrating an auxiliary application for a personal proxy application client for a femtocell.
- geographic areas served by access points may vary in size, may include smaller service areas, and/or may be located within larger service areas. Larger geographic areas that include one or more smaller service areas are referred to as “macrocell areas,” and an access point that serves a macrocell area is referred to as a “macrocell.” Within a macrocell area, one or more access points may be located to serve smaller geographic areas, referred to as “femtocell areas”, or “femtozones.” An access point that serves a femtozone is referred to as a “femtocell access point.” A macrocell, for example, may provide coverage to an area of a few blocks, while a femtocell access point may provide coverage to an area spanning a floor of a building, a house, or an office space.
- GSM/WCDMA Global System for Mobile communications/Wideband Code Division Multiple Access
- 2G/3G macro networks have been implemented and are in operation globally.
- one motivation for providing “femtocell access points” in such 2G/3G macro networks is that the coverage of those macro networks is often poor indoors, which may cause, e.g., service disruption (e.g., a dropped telephone call) to users of devices at home and inside buildings.
- Femtocell access points also known as, e.g., “home” base stations, private access points, or simply “femtocells”, provide complementary indoor coverage to 2G/3G macro networks for service continuity.
- Femtocell access point (FAP) implementations may also serve as a new service platform to enable mobile wireless broadband applications and home entertainment.
- a private access point may include, for example, a femtocell access point or a picocell access point.
- a private access point may be installed anywhere, for example, a home, an office, a public space, or a restaurant.
- private access points will be described hereinafter as femtocell access points or FAPs.
- a radio access network (RAN) 100 includes multiple macro access points or “macrocells” 108 , 110 , and 112 located in macrocell areas 102 , 104 , and 106 , respectively.
- the macrocell areas 102 , 104 , and 106 can include one or more femtocell access points (FAPs).
- FAPs femtocell access points
- the macrocells 108 , 110 , and 112 are each configured to communicate with a device over an airlink.
- macrocell 108 communicates with device 116 over an airlink 109 .
- Macrocells 108 , 110 , and 112 are connected over a backhaul connection (e.g., backhaul connection 118 a or 118 b ) to a radio network controller (RNC) which in turn communicates with the service provider's core network 122 , e.g., via RNC 120 a or 120 b , which may be one or more physical devices at different locations.
- RNC radio network controller
- the RAN 100 is configured to support various mobile wireless access technologies, examples of which include Universal Mobile Telecommunications System (UMTS) and Code Division Multiple Access (CDMA) 2000.
- UMTS Universal Mobile Telecommunications System
- CDMA Code Division Multiple Access
- the 1xEV-DO protocol has been standardized by the Telecommunication Industry Association (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.S 0024-A, Version 2.0, July 2005. Revision A is also incorporated herein by reference.
- FIG. 2 shows a femtocell deployment in the macrocell service area 102 of the RAN 100 of FIG. 1 .
- the service area 102 of macrocell 108 includes femtocell areas 240 a , 240 b , and 240 c served by femtocell access points (FAPs) 242 a , 242 b , and 242 c , respectively.
- FAPs femtocell access points
- the femtocell access points 242 a , 242 b , and 242 c are referred to as “FAPs 242 a , 242 b , and 242 c .”
- FAPs 242 a , 242 b , and 242 c are referred to as “FAPs 242 a , 242 b , and 242 c .”
- a macrocell area can include many more FAPs.
- a macrocell area could include hundreds, thousands, or hundreds
- a femtocell server 244 is in communication with one or more of the FAPs 242 a - c .
- the femtocell server 244 maintains active associations between devices such as devices 116 a, 116 b , and 116 c and the FAPs 242 a - c so that a hand-in request from the macrocell 108 (or other components of the mobile core network) can be directed to the correct FAP.
- One or more of the FAPs 242 a - c and the femtocell server 244 may be combined as a single device.
- the femtocell server 244 may present a similar, conventional system interface as that of RNC 120 to the existing core network infrastructure 122 .
- References to the core network 122 may in some cases be a shorthand for a reference to the femtocell server 244 , and in some implementations, certain functions of the core network 122 may be included in the femtocell server 244 and vice versa. For example, when reference is made to a FAP accessing stored information from the core network 122 , all or part of the information might be stored on the core network 122 and/or the femtocell server 244 .
- Femtocell access point systems typically perform some type of closed access control. Closed access control means, e.g., that access to each femtocell access point is limited in some fashion, i.e., not every device may “camp” on the femtocell and/or utilize the services of the femtocell. For example, an owner of a FAP may like to control which devices are allowed to camp on and register with the core network 122 via the FAP to use normal service (e.g., non-emergency service).
- normal service e.g., non-emergency service
- Each FAP of the FAPs 242 a - c may include an authorization list, or “access control list”, which may be stored in memory on the FAP. See, e.g., access control lists (ACLs) stored on respective FAPs 242 a , 242 b , 242 c in FIG. 2 .
- the access control list for a particular FAP includes identities of devices that are authorized on that FAP. Devices that are not identified on the access control list of a particular FAP are not authorized on that FAP. A particular device may be authorized on one FAP and unauthorized on another FAP.
- a device is either an authorized device or an unauthorized device.
- a FAP is either an authorized FAP (e.g., a “home” FAP that the device is authorized on), or an unauthorized FAP (e.g., a “foreign” FAP that the device is not authorized on).
- a “home” FAP need not be located in a user's home and may, e.g., be located in an office building, or a public place.
- a “foreign” FAP may be located, e.g., in close physical proximity to a user's “home” FAP but still be “foreign” from the perspective of the device.
- Access control lists may be updated periodically and/or built dynamically and loaded to the FAP by, e.g., an administrator or operator of the core network, e.g., the core network 122 .
- each access point is assigned an access point identifier such as a Location Area Identifier.
- Location Area Identifiers are explained in more detail in, e.g., 3GPP Technical Specification 23.003, section 4.4.4.6.
- the Location Area Identifier (LAI) of the access point is broadcast to devices. When camping on an access point, the device issues a Location Area Update Request message that contains the LAI assigned to that access point.
- LAI Location Area Identifier
- That Location Area Update Request message is forwarded by the access point to the core network and the core network returns a message to the device that, e.g., allows that device to camp on the access point to use normal service (e.g., non-emergency service) or that rejects the device's Location Area Update Request to disable normal service (e.g., unless the device is trying to make an emergency call from the FAP).
- the device Once camped on an access point with a particular LAI, the device can move into the coverage area of another access point with the same LAI without issuing a new Location Area Update Request.
- the device issues a new Location Area Update Request message when the device moves into the coverage area of an access point with a different LAI.
- the device may also issue the Location Area Update Request periodically to inform an access point that the device is still in the vicinity of the access point.
- a LAI is an example of an access point identifier.
- an access point identifier other than a LAI may be used in, e.g., access control.
- the device When a device moves into the coverage area of a FAP, the device will generally issue a Location Area Update Request message containing the LAI assigned to that FAP. Thus, even a device that is unauthorized on a particular FAP but that is in range of or in the coverage area of the FAP will generally attempt to camp on the FAP and perform Location Area registration with the core network (e.g., core network 122 ) using the Location Area Update Request message. In order to support a form of closed access control, Location Area Update Request messages from unauthorized devices should be rejected to prevent the unauthorized devices from camping on the FAP to use normal service.
- the core network e.g., core network 122
- Location Area Update requests from unauthorized devices are not rejected by the FAP in some fashion, then unauthorized devices that remain in range of the FAP will generally keep retrying the Location Area Update Requests, which drains the battery and shortens the battery life of the devices.
- Other issues may arise when Location Area Update requests from unauthorized devices are not properly rejected. In a situation in which a FAP is surrounded by unauthorized devices, for example in a crowded area, the FAP may become overloaded in handling Location Area Update requests. If the FAP passes messages from devices to the core network without first confirming that the devices originating the messages are authorized on the FAP, then, due to the potential volume of requests from unauthorized devices, excessive messaging traffic between the FAP and the core network may become an issue.
- a FAP 242 is configured to detect the presence of devices 320 a and 320 b , for example, handsets, that enter femtozone 240 . Based on a device identifier associated with a device, say 320 a , FAP 242 , upon detection of and verification that the device 320 a may camp on the FAP 242 , may make available a set of applications to run on the device 320 a . The set of applications are particular to that device through personal proxy client 340 a . FAP 242 may also detect and verify permission to camp for device 320 b and make available a set of applications for device 320 b through personal proxy client 320 b.
- a device 320 has associated with it a unique device identifier with which the FAP 242 is able to identify the device.
- Examples of device identifiers that may be used in an access control list on a particular FAP may include the International Mobile Subscriber Identity (IMSI) of the device. While the device may also use a temporary identifier such as a Temporary Mobile Subscriber Identity (TMSI) in initial communications with a FAP, access control lists may generally include the unique IMSI of the device rather than the TMSI.
- IMSI International Mobile Subscriber Identity
- TMSI Temporary Mobile Subscriber Identity
- Detection of the device begins when the device enters the femtozone associated with FAP 242 and broadcasts its device identifier via a signal.
- the FAP 242 then receives the signal containing the device identifier with a built-in receiver. Once the device identifier is retrieved from the signal using a processor in the FAP 242 , the device is considered detected by the FAP 242 .
- the detected device has its device identifier located on the access control list as described above. Assuming the device is authorized to camp on the FAP 242 , the device identifier is then matched with an identifier in the personal proxy client (“PPC identifier”) in order to identify applications that are to be run on the device 320 , the FAP 242 , a device attached to the home network 360 , or on a server attached to the Internet 370 and associated with the device identifier.
- PPC identifier personal proxy client
- a database of PPC identifiers and pointers to applications corresponding to each PPC identifier may be kept in a location accessible to the FAP 242 . Such a database may be separate from the access control list, but it may be incorporated into the access control list and therefore stored in memory in the FAP as well.
- Matching the device identifier with a PPC identifier may be accomplished, for example, through looking up the PPC identifier in a database. Such a looking up may be done using a standard pattern-matching algorithm.
- a PPC identifier is associated with pointers to applications that may be run on the device 320 , the FAP 242 , a device attached to the home network 360 , or on a server attached to the Internet 370 .
- the device identifier is associated with the pointers to the applications.
- the pointers may comprise, e.g., IP addresses denoting locations where the corresponding applications are stored. The locations may be directly accessible by the FAP 242 .
- the FAP 242 may access the applications now associated with the device identifier via the associated pointers.
- Typical applications may include a single sign-on application, a personal automated teller application, and an automatic network backup application.
- the applications may be run on the FAP 242 , on the device 320 or on other devices connected to the FAP 242 , e.g., a device attached to the home network 360 , or on a server attached to the Internet 370 .
- a pointer contains the IP address of a storage location of an application, then a message may be sent from the FAP 242 to the storage location to download the application to the device 320 via the FAP 242 .
- An application may also be stored on, for example, the FAP 242 , or a femto server 244 . At least some of the applications may already be present on device 320 ; in that case, such applications need not be loaded onto the device. An application may also be loaded to a device attached to the home network 360 or a server attached to the Internet 370 .
- Each application may have a usage flag associated with device 320 .
- a usage flag has two states: “on” and “off”. An application may be activated on the device if its usage flag associated with the device is in the “on” state. By default, a usage flag is in the “off” state. If the device 320 has been detected and authorized, and an associated application has been loaded by the FAP 242 , then the usage flag for that application is switched to the “on” state. Typically, the usage flag stays in the “on” state while the device 320 is camped on FAP 242 .
- the applications loaded onto the device 320 , FAP 242 , a device attached to the home network 360 , or to a server attached to the Internet 370 may be deactivated.
- the deactivation may occur by a switching of the usage flags of the applications loaded onto device 320 , FAP 242 , the device attached to home network 360 , or the server attached to the Internet 370 , from “on” to “off”.
- FRBAC Femto Robot Buddy Application Client
- FRBAC 440 may reside on FAP 242 , or on a device closely integrated with FAP 242 , such as femto server 244 or a device attached to the home network 360 .
- a specific device 320 a enters the femtozone 240 associated with FAP 242 , a data connection is automatically created and terminated at the FRBAC 440 a.
- FRBAC 440 a initiates the data connection with device 320 a .
- the FRBAC 440 a may be connected with corresponding Application Client 340 a running on FAP 242 or on an external device, such as femto server 244 , a device attached to the home network 360 , or a device directly connected with the FAP 242 .
- FRBAC 440 a provides a communication link between Application Client 340 a and device 320 a .
- the communication link operates in most cases at the Application Layer in the Open Systems Interconnection (OSI) model, and is locally managed by the FAP 242 and corresponding device 320 a . Because the communication link exists at the Application Layer, the communication link may be implemented in a specific, proprietary way independent of standards of other devices involved in the data connection. Further, a “keep alive” mechanism can be implemented using the automatically created data connection on the communication link.
- OSI Open Systems Interconnection
- FRBAC 440 a may have a usage flag having two states: “on” and “off”. The FRBAC 440 a may be activated if its usage flag is in the “on” state. By default, a usage flag is in the “off” state. If the device 320 a has been detected and authorized, and FRBAC 440 a has been loaded by the FAP 242 , then the usage flag for the FRBAC 440 a is switched to the “on” state.
- FRBAC 440 a associated with device 320 a may be deactivated. The deactivation may occur by a switching of the usage flag of FRBAC 440 a from “on” to “off”. As soon as the FRBAC 440 a is deactivated, the corresponding connection with device 320 a is terminated.
- the techniques described above employ the UMTS air interface standard, the techniques are also applicable to other CDMA and non-CDMA air interface technologies in which, e.g., messages can be passed between access terminals and other network components.
- the processes described herein and their various modifications are not limited to the hardware and software described above. All or part of the processes can be implemented, at least in part, via a computer program product, e.g., a computer program tangibly embodied in an information carrier, such as one or more machine-readable storage media or in a propagated signal, for execution by, or to control the operation of, one or more data processing apparatus, e.g., a programmable processor, a computer, multiple computers, and/or programmable logic components.
- a computer program product e.g., a computer program tangibly embodied in an information carrier, such as one or more machine-readable storage media or in a propagated signal, for execution by, or to control the operation of, one or more data processing apparatus, e.g., a programmable processor, a computer, multiple computers, and/or programmable logic components.
- 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 network.
- Actions associated with implementing all or part of the processes can be performed by one or more programmable processing devices executing one or more computer programs to perform the functions of the processes. All or part of the processes can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit).
- special purpose logic circuitry e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit).
- Processing devices 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 processing device will receive instructions and data from a read-only memory or a random access memory or both.
- the components of a computer include one or more processing devices for executing instructions and one or more memory devices for storing instructions and data.
- 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 techniques described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer (e.g., interact with a user interface element, for example, by clicking a button on such a pointing device).
- a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
- a keyboard and a pointing device e.g., a mouse or a trackball
- feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- the techniques described herein can be implemented in a distributed computing system that includes a back-end component, e.g., as a data server, and/or a middleware component, e.g., an application server, and/or a front-end component, e.g., a client computer having a graphical user interface and/or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet, and include both wired and wireless networks.
- LAN local area network
- WAN wide area network
- 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.
- Actions associated with the processes can be rearranged and/or one or more such actions can be omitted to achieve the same, or similar, results to those described herein.
Abstract
Description
- This patent application relates to U.S. application Ser. No. ______, entitled “Femto Personal Policy Server” and filed concurrently herewith (attorney docket no. 12144-092001). The contents of U.S. application Ser. No. ______, entitled “Femto Personal Policy Server” are hereby incorporated by reference into this application as if set forth herein in full, and may be combined with any of the features described herein.
- This description relates to access terminal authorization at private access points in wireless networks.
- Cellular wireless communications systems, for example, are designed to serve multiple wireless-enabled devices distributed over a large geographic area by dividing the area into regions called “cells” or “cell areas”. At or near the center of each cell area, a network-side access device (e.g., an access point or base station) is located to serve client devices located in the cell area and is commonly referred to as an “access terminal”. Examples of access terminals include wireless-enabled devices such as cellular telephones, laptops, personal digital assistants (PDAs), and/or other user equipment (e.g., mobile devices). An access terminal generally establishes a call, also referred to as a “communication session,” with an access point to communicate with other entities (e.g., servers) in the network.
- In an aspect, an access point detects a presence of a first device having a device identifier in a femtozone associated with the access point. The access point matches the device identifier with an identifier associated with corresponding applications and activates a set of applications associated with the device identifier.
- The access point may deactivate the set of applications when the presence of the first device is not detected.
- Implementations may include one or more of the following.
- The first device may include a handset.
- Matching may include looking up the device identifier in a database that is accessible to the access point.
- Activating an application in the set of applications may include changing a value of a usage flag associated with the application from “off” to “on”, and deactivating an application in the set of applications may include changing a value of a usage flag associated with the application from “on” to “off”.
- At least one application in the set of activated applications associated with the device identifier may run on one or more devices chosen from a group comprising the access point, the first device, a second device attached to a home network attached to the access point, and a network server communicating with the access point.
- In an aspect, a method comprises steps as outlined above.
- In another aspect, a computer program product, tangibly embodied in a computer readable storage medium, is operable to cause a data processing apparatus to perform operations comprising the steps of the method above.
- In yet another aspect, an apparatus can be configured to perform the steps outlined above.
- In another aspect, an access point detects a presence of a first device having a device identifier in a femtozone associated with the access point. The access point matches the device identifier with an identifier associated with an auxiliary application and activates the auxiliary application associated with the identifier that interacts with one or more device applications. The access point creates a data connection between the auxiliary application and the first device.
- The access point may deactivate the auxiliary application and terminate the data connection between the auxiliary application and the first device when the presence of the device is not detected by the detector.
- Implementations may include the following.
- The auxiliary application associated with the device identifier may run on a device chosen from a group comprising the access point and a second device attached to a home network associated with the access point.
- In an aspect, a method comprises steps as outlined above.
- In another aspect, a computer program product, tangibly embodied in a computer readable medium, is operable to cause a data processing apparatus to perform operations comprising the steps of the method above.
- In yet another aspect, an apparatus can be configured to perform the steps outlined above.
-
FIG. 1 is a diagram illustrating a wireless network. -
FIG. 2 is a diagram illustrating a wireless network with a home networking deployment. -
FIG. 3 is a diagram illustrating a personal proxy application client for a femtocell. -
FIG. 4 is a diagram illustrating an auxiliary application for a personal proxy application client for a femtocell. - Like reference symbols in the various drawings indicate like elements.
- In wireless communication networks generally, geographic areas served by access points, also referred to as “service areas,” may vary in size, may include smaller service areas, and/or may be located within larger service areas. Larger geographic areas that include one or more smaller service areas are referred to as “macrocell areas,” and an access point that serves a macrocell area is referred to as a “macrocell.” Within a macrocell area, one or more access points may be located to serve smaller geographic areas, referred to as “femtocell areas”, or “femtozones.” An access point that serves a femtozone is referred to as a “femtocell access point.” A macrocell, for example, may provide coverage to an area of a few blocks, while a femtocell access point may provide coverage to an area spanning a floor of a building, a house, or an office space.
- Global System for Mobile communications/Wideband Code Division Multiple Access (GSM/WCDMA) wireless communication networks (e.g., 2G/3G macro networks) have been implemented and are in operation globally. However, one motivation for providing “femtocell access points” in such 2G/3G macro networks is that the coverage of those macro networks is often poor indoors, which may cause, e.g., service disruption (e.g., a dropped telephone call) to users of devices at home and inside buildings. Femtocell access points, also known as, e.g., “home” base stations, private access points, or simply “femtocells”, provide complementary indoor coverage to 2G/3G macro networks for service continuity. Femtocell access point (FAP) implementations may also serve as a new service platform to enable mobile wireless broadband applications and home entertainment.
- A private access point may include, for example, a femtocell access point or a picocell access point. A private access point may be installed anywhere, for example, a home, an office, a public space, or a restaurant. For ease of description, private access points will be described hereinafter as femtocell access points or FAPs.
- Referring to
FIG. 1 , a radio access network (RAN) 100 includes multiple macro access points or “macrocells” 108, 110, and 112 located inmacrocell areas macrocell areas macrocells macrocell 108 communicates withdevice 116 over anairlink 109. Macrocells 108, 110, and 112 are connected over a backhaul connection (e.g.,backhaul connection core network 122, e.g., viaRNC - The RAN 100 is configured to support various mobile wireless access technologies, examples of which include Universal Mobile Telecommunications System (UMTS) and Code Division Multiple Access (CDMA) 2000. The 1xEV-DO protocol has been standardized by the Telecommunication Industry Association (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.S 0024-A, Version 2.0, July 2005. Revision A is also incorporated herein by reference. Revision B to this specification has been published as TLA/EIA/IS-856-B, 3GPP2 C.S0024-B and is also incorporated herein by reference. Other wireless communication standards may also be used. Although this description uses terminology from the 3GPP's UMTS standards, the same concepts are applicable to other wireless communication standards, including CDMA 1x EV-DO, CDMA2000, WiMax, WiBro, WiFi, and the like.
- The following sections of the 3GPP Standard are hereby incorporated by reference in their entirety:
- 3GPP Technical Specification 25.331 version 8.3.0 Release 8, July 2008, Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification;
- 3GPP Technical Specification 25.304 version 7.6.0 Release 7, July 2008, Universal Mobile Telecommunications System (UMTS); User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode;
- 3GPP Technical Specification 25.133 version 8.3.0 Release 8, June 2006, Universal Mobile Telecommunications System (UMTS); Requirements for support of radio resource management (FDD);
- 3GPP Technical Specification 24.008 version 7.9.0 Release 7, October 2007, Digital cellular telecommunications system (
Phase 2+); Universal Mobile Telecommunications System (UMTS); Mobile radio interface Layer 3 specification; Core network protocols; Stage 3; and - 3GPP Technical Specification 23.122 version 7.9.0 Release 7, June 2007, Digital cellular telecommunications system (
Phase 2+); Universal Mobile Telecommunications System (UMTS); Non-Access-Stratus (NAS) functions related to Mobile Station (MS) in idle mode. -
FIG. 2 shows a femtocell deployment in themacrocell service area 102 of theRAN 100 ofFIG. 1 . Theservice area 102 ofmacrocell 108 includesfemtocell areas femtocell access points FAPs FIG. 2 , in practice a macrocell area can include many more FAPs. For example, a macrocell area could include hundreds, thousands, or hundreds of thousands of FAPs. - A
femtocell server 244 is in communication with one or more of theFAPs 242 a-c. Thefemtocell server 244 maintains active associations between devices such asdevices 116a, 116 b, and 116 c and theFAPs 242 a-c so that a hand-in request from the macrocell 108 (or other components of the mobile core network) can be directed to the correct FAP. One or more of theFAPs 242 a-c and thefemtocell server 244 may be combined as a single device. In early deployment, thefemtocell server 244 may present a similar, conventional system interface as that ofRNC 120 to the existingcore network infrastructure 122. References to thecore network 122 may in some cases be a shorthand for a reference to thefemtocell server 244, and in some implementations, certain functions of thecore network 122 may be included in thefemtocell server 244 and vice versa. For example, when reference is made to a FAP accessing stored information from thecore network 122, all or part of the information might be stored on thecore network 122 and/or thefemtocell server 244. - Femtocell access point systems typically perform some type of closed access control. Closed access control means, e.g., that access to each femtocell access point is limited in some fashion, i.e., not every device may “camp” on the femtocell and/or utilize the services of the femtocell. For example, an owner of a FAP may like to control which devices are allowed to camp on and register with the
core network 122 via the FAP to use normal service (e.g., non-emergency service). - Devices may be “authorized” or “not authorized” (“unauthorized”) to camp on and/or use services of a FAP. Each FAP of the
FAPs 242 a-c may include an authorization list, or “access control list”, which may be stored in memory on the FAP. See, e.g., access control lists (ACLs) stored onrespective FAPs FIG. 2 . The access control list for a particular FAP includes identities of devices that are authorized on that FAP. Devices that are not identified on the access control list of a particular FAP are not authorized on that FAP. A particular device may be authorized on one FAP and unauthorized on another FAP. From the perspective of a FAP, a device is either an authorized device or an unauthorized device. From the perspective of a device, a FAP is either an authorized FAP (e.g., a “home” FAP that the device is authorized on), or an unauthorized FAP (e.g., a “foreign” FAP that the device is not authorized on). A “home” FAP need not be located in a user's home and may, e.g., be located in an office building, or a public place. Likewise, a “foreign” FAP may be located, e.g., in close physical proximity to a user's “home” FAP but still be “foreign” from the perspective of the device. Just as a FAP may identify more than one authorized device in its access control list, a device may be authorized on more than one FAP (and thus may have more than one authorized FAP or “home” FAP). Hereafter, for ease of description, a home FAP for an access terminal will be referred to as though it is the only home FAP for the access terminal. Access control lists may be updated periodically and/or built dynamically and loaded to the FAP by, e.g., an administrator or operator of the core network, e.g., thecore network 122. - In, e.g., a wireless network such as a UMTS network, each access point is assigned an access point identifier such as a Location Area Identifier. Location Area Identifiers are explained in more detail in, e.g., 3GPP Technical Specification 23.003, section 4.4.4.6. The Location Area Identifier (LAI) of the access point is broadcast to devices. When camping on an access point, the device issues a Location Area Update Request message that contains the LAI assigned to that access point. That Location Area Update Request message is forwarded by the access point to the core network and the core network returns a message to the device that, e.g., allows that device to camp on the access point to use normal service (e.g., non-emergency service) or that rejects the device's Location Area Update Request to disable normal service (e.g., unless the device is trying to make an emergency call from the FAP). Once camped on an access point with a particular LAI, the device can move into the coverage area of another access point with the same LAI without issuing a new Location Area Update Request. The device issues a new Location Area Update Request message when the device moves into the coverage area of an access point with a different LAI. The device may also issue the Location Area Update Request periodically to inform an access point that the device is still in the vicinity of the access point.
- A LAI is an example of an access point identifier. In wireless networks that use other air interface standards, an access point identifier other than a LAI may be used in, e.g., access control.
- When a device moves into the coverage area of a FAP, the device will generally issue a Location Area Update Request message containing the LAI assigned to that FAP. Thus, even a device that is unauthorized on a particular FAP but that is in range of or in the coverage area of the FAP will generally attempt to camp on the FAP and perform Location Area registration with the core network (e.g., core network 122) using the Location Area Update Request message. In order to support a form of closed access control, Location Area Update Request messages from unauthorized devices should be rejected to prevent the unauthorized devices from camping on the FAP to use normal service. If Location Area Update requests from unauthorized devices are not rejected by the FAP in some fashion, then unauthorized devices that remain in range of the FAP will generally keep retrying the Location Area Update Requests, which drains the battery and shortens the battery life of the devices. Other issues may arise when Location Area Update requests from unauthorized devices are not properly rejected. In a situation in which a FAP is surrounded by unauthorized devices, for example in a crowded area, the FAP may become overloaded in handling Location Area Update requests. If the FAP passes messages from devices to the core network without first confirming that the devices originating the messages are authorized on the FAP, then, due to the potential volume of requests from unauthorized devices, excessive messaging traffic between the FAP and the core network may become an issue. On the other hand, it is possible for a FAP to reject an unauthorized device completely, or effectively completely. However, since some core network operators consider it desirable for any device, even an unauthorized device, to make emergency calls using a FAP, such rejection methods that block unauthorized devices from making even emergency calls may be undesirable.
- Referring to
FIG. 3 , aFAP 242 is configured to detect the presence ofdevices femtozone 240. Based on a device identifier associated with a device, say 320 a,FAP 242, upon detection of and verification that thedevice 320 a may camp on theFAP 242, may make available a set of applications to run on thedevice 320 a. The set of applications are particular to that device throughpersonal proxy client 340 a.FAP 242 may also detect and verify permission to camp fordevice 320 b and make available a set of applications fordevice 320 b throughpersonal proxy client 320 b. - A device 320 has associated with it a unique device identifier with which the
FAP 242 is able to identify the device. Examples of device identifiers that may be used in an access control list on a particular FAP may include the International Mobile Subscriber Identity (IMSI) of the device. While the device may also use a temporary identifier such as a Temporary Mobile Subscriber Identity (TMSI) in initial communications with a FAP, access control lists may generally include the unique IMSI of the device rather than the TMSI. - Detection of the device begins when the device enters the femtozone associated with
FAP 242 and broadcasts its device identifier via a signal. TheFAP 242 then receives the signal containing the device identifier with a built-in receiver. Once the device identifier is retrieved from the signal using a processor in theFAP 242, the device is considered detected by theFAP 242. - The detected device has its device identifier located on the access control list as described above. Assuming the device is authorized to camp on the
FAP 242, the device identifier is then matched with an identifier in the personal proxy client (“PPC identifier”) in order to identify applications that are to be run on the device 320, theFAP 242, a device attached to thehome network 360, or on a server attached to theInternet 370 and associated with the device identifier. A database of PPC identifiers and pointers to applications corresponding to each PPC identifier may be kept in a location accessible to theFAP 242. Such a database may be separate from the access control list, but it may be incorporated into the access control list and therefore stored in memory in the FAP as well. - Matching the device identifier with a PPC identifier may be accomplished, for example, through looking up the PPC identifier in a database. Such a looking up may be done using a standard pattern-matching algorithm.
- As stated above, a PPC identifier is associated with pointers to applications that may be run on the device 320, the
FAP 242, a device attached to thehome network 360, or on a server attached to theInternet 370. Once the device identifier is matched with a PPC identifier, the device identifier is associated with the pointers to the applications. The pointers may comprise, e.g., IP addresses denoting locations where the corresponding applications are stored. The locations may be directly accessible by theFAP 242. - The
FAP 242 may access the applications now associated with the device identifier via the associated pointers. Typical applications may include a single sign-on application, a personal automated teller application, and an automatic network backup application. The applications may be run on theFAP 242, on the device 320 or on other devices connected to theFAP 242, e.g., a device attached to thehome network 360, or on a server attached to theInternet 370. For example, if a pointer contains the IP address of a storage location of an application, then a message may be sent from theFAP 242 to the storage location to download the application to the device 320 via theFAP 242. An application may also be stored on, for example, theFAP 242, or afemto server 244. At least some of the applications may already be present on device 320; in that case, such applications need not be loaded onto the device. An application may also be loaded to a device attached to thehome network 360 or a server attached to theInternet 370. - Once the applications are loaded onto device 320,
FAP 242, a device attached tohome network 360, or to a server attached to theInternet 370, they are activated by theFAP 242. Each application may have a usage flag associated with device 320. A usage flag has two states: “on” and “off”. An application may be activated on the device if its usage flag associated with the device is in the “on” state. By default, a usage flag is in the “off” state. If the device 320 has been detected and authorized, and an associated application has been loaded by theFAP 242, then the usage flag for that application is switched to the “on” state. Typically, the usage flag stays in the “on” state while the device 320 is camped onFAP 242. - If the device 320 departs from the femtozone associated with
FAP 242 or is no longer detected by theFAP 242, then the applications loaded onto the device 320,FAP 242, a device attached to thehome network 360, or to a server attached to theInternet 370, may be deactivated. The deactivation may occur by a switching of the usage flags of the applications loaded onto device 320, FAP242, the device attached tohome network 360, or the server attached to theInternet 370, from “on” to “off”. - There may be instances which would necessitate an auxiliary application that may interface with a personal proxy client 340. Such an auxiliary application, which may be transparent to a user 410 of device 320, is illustrated in
FIG. 4 as a “Femto Robot Buddy Application Client” (FRBAC) 440. FRBAC 440 may reside onFAP 242, or on a device closely integrated withFAP 242, such asfemto server 244 or a device attached to thehome network 360. When aspecific device 320 a enters thefemtozone 240 associated withFAP 242, a data connection is automatically created and terminated at the FRBAC 440 a. - When the
device 320 a is detected by and camps onFAP 242,FRBAC 440 a initiates the data connection withdevice 320 a. In turn, the FRBAC 440 a may be connected withcorresponding Application Client 340 a running onFAP 242 or on an external device, such asfemto server 244, a device attached to thehome network 360, or a device directly connected with theFAP 242.FRBAC 440 a provides a communication link betweenApplication Client 340 a anddevice 320 a. The communication link operates in most cases at the Application Layer in the Open Systems Interconnection (OSI) model, and is locally managed by theFAP 242 andcorresponding device 320 a. Because the communication link exists at the Application Layer, the communication link may be implemented in a specific, proprietary way independent of standards of other devices involved in the data connection. Further, a “keep alive” mechanism can be implemented using the automatically created data connection on the communication link. -
FRBAC 440 a may have a usage flag having two states: “on” and “off”. TheFRBAC 440 a may be activated if its usage flag is in the “on” state. By default, a usage flag is in the “off” state. If thedevice 320 a has been detected and authorized, and FRBAC 440 a has been loaded by theFAP 242, then the usage flag for the FRBAC 440 a is switched to the “on” state. - If the
device 320 a departs from the femtozone associated withFAP 242 or is no longer detected by theFAP 242, then FRBAC 440 a associated withdevice 320 a may be deactivated. The deactivation may occur by a switching of the usage flag of FRBAC 440 a from “on” to “off”. As soon as the FRBAC 440 a is deactivated, the corresponding connection withdevice 320 a is terminated. - Although the techniques described above employ the UMTS air interface standard, the techniques are also applicable to other CDMA and non-CDMA air interface technologies in which, e.g., messages can be passed between access terminals and other network components.
- The processes described herein are not limited to use with any particular hardware, software, or programming language; they may find applicability in any computing or processing environment and with any type of machine that is capable of running machine-readable instructions. All or part of the processes can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations thereof.
- The processes described herein and their various modifications (hereinafter “the processes”), are not limited to the hardware and software described above. All or part of the processes can be implemented, at least in part, via a computer program product, e.g., a computer program tangibly embodied in an information carrier, such as one or more machine-readable storage media or in a propagated signal, for execution by, or to control the operation of, one or more data processing apparatus, e.g., a programmable processor, a computer, multiple computers, and/or programmable logic components.
- 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 network.
- Actions associated with implementing all or part of the processes can be performed by one or more programmable processing devices executing one or more computer programs to perform the functions of the processes. All or part of the processes can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) and/or an ASIC (application-specific integrated circuit).
- Processing devices 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 processing device will receive instructions and data from a read-only memory or a random access memory or both. The components of a computer include one or more processing devices 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.
- To provide for interaction with a user, the techniques described herein can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer (e.g., interact with a user interface element, for example, by clicking a button on such a pointing device). Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- The techniques described herein can be implemented in a distributed computing system that includes a back-end component, e.g., as a data server, and/or a middleware component, e.g., an application server, and/or a front-end component, e.g., a client computer having a graphical user interface and/or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet, and include both wired and wireless networks.
- 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.
- Actions associated with the processes can be rearranged and/or one or more such actions can be omitted to achieve the same, or similar, results to those described herein.
- Components of different implementations may be combined to form implementations not specifically set forth above. Other implementations not specifically described are also within the scope of the following claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/347,201 US9210569B2 (en) | 2008-12-31 | 2008-12-31 | Femto personal proxy application client |
PCT/US2009/069734 WO2010078364A1 (en) | 2008-12-31 | 2009-12-29 | Femto personal proxy application client |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/347,201 US9210569B2 (en) | 2008-12-31 | 2008-12-31 | Femto personal proxy application client |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100167718A1 true US20100167718A1 (en) | 2010-07-01 |
US9210569B2 US9210569B2 (en) | 2015-12-08 |
Family
ID=41728063
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/347,201 Active 2030-10-20 US9210569B2 (en) | 2008-12-31 | 2008-12-31 | Femto personal proxy application client |
Country Status (2)
Country | Link |
---|---|
US (1) | US9210569B2 (en) |
WO (1) | WO2010078364A1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100167694A1 (en) * | 2008-12-31 | 2010-07-01 | Chiussi Fabio M | Femto personal policy server |
US20110065464A1 (en) * | 2001-10-12 | 2011-03-17 | Sae-Young Chung | Boosting a signal-to-interference ratio of a mobile station |
US7926098B2 (en) | 2006-12-29 | 2011-04-12 | Airvana, Corp. | Handoff of a secure connection among gateways |
US20110190000A1 (en) * | 2010-02-01 | 2011-08-04 | Samsung Electronics Co. Ltd. | Method and apparatus for allocating identifier of base station in communication system |
US20120317252A1 (en) * | 2011-06-09 | 2012-12-13 | Freescale Semiconductor, Inc | Method and system for address conflict resolution |
US8615238B2 (en) | 2001-06-25 | 2013-12-24 | Ericsson Evdo Inc. | Radio network control |
US8886249B2 (en) | 2004-07-30 | 2014-11-11 | Airvana Lp | Method and system of setting transmitter power levels |
US9210569B2 (en) | 2008-12-31 | 2015-12-08 | Commscope Technologies Llc | Femto personal proxy application client |
US9237492B2 (en) | 2012-05-31 | 2016-01-12 | Commscope Technologies Llc | Providing circuit switched service |
US9380466B2 (en) | 2013-02-07 | 2016-06-28 | Commscope Technologies Llc | Radio access networks |
US9414399B2 (en) | 2013-02-07 | 2016-08-09 | Commscope Technologies Llc | Radio access networks |
US9936470B2 (en) | 2013-02-07 | 2018-04-03 | Commscope Technologies Llc | Radio access networks |
US10057916B2 (en) | 2014-06-09 | 2018-08-21 | Commscope Technologies Llc | Radio access networks in which mobile devices in the same communication cell can be scheduled to use the same airlink resource |
US10785791B1 (en) | 2015-12-07 | 2020-09-22 | Commscope Technologies Llc | Controlling data transmission in radio access networks |
US10798667B2 (en) | 2018-06-08 | 2020-10-06 | Commscope Technologies Llc | Automatic transmit power control for radio points of a centralized radio access network that primarily provide wireless service to users located in an event area of a venue |
US11304213B2 (en) | 2018-05-16 | 2022-04-12 | Commscope Technologies Llc | Dynamic uplink reuse in a C-RAN |
US11395259B2 (en) | 2018-05-16 | 2022-07-19 | Commscope Technologies Llc | Downlink multicast for efficient front-haul utilization in a C-RAN |
US11627497B2 (en) | 2018-09-04 | 2023-04-11 | Commscope Technologies Llc | Front-haul rate reduction for use in a centralized radio access network |
US11678358B2 (en) | 2017-10-03 | 2023-06-13 | Commscope Technologies Llc | Dynamic downlink reuse in a C-RAN |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9521621B2 (en) | 2010-06-02 | 2016-12-13 | Qualcomm Incorporated | Application-proxy support over a wireless link |
ES2942750T3 (en) | 2016-12-12 | 2023-06-06 | Commscope Technologies Llc | LTE-WIFI aggregation (LWA) support in a cloud-run system |
WO2019152717A1 (en) | 2018-02-01 | 2019-08-08 | Commscope Technologies Llc | Licensed-assisted access (laa) in a c-ran |
Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030045275A1 (en) * | 2000-04-27 | 2003-03-06 | Mcdonagh Brendan | Communication method and apparatus |
US20040043763A1 (en) * | 2002-08-30 | 2004-03-04 | Brian Minear | System and method for application and application metadata filtering based on wireless device capabilities |
US6940321B2 (en) * | 2003-01-23 | 2005-09-06 | Samsung Electronics Co., Ltd. | Circuit for generating a data strobe signal used in a double data rate synchronous semiconductor device |
US6941148B2 (en) * | 2000-06-03 | 2005-09-06 | International Business Machines Corporation | Device registry for automatic connection and data exchange between pervasive devices and backend systems |
US20070001852A1 (en) * | 2005-06-30 | 2007-01-04 | Nokia Corporation | Wireless rights management |
US20070054668A1 (en) * | 2002-10-25 | 2007-03-08 | Ibis Telecom, Inc. | Private base station with exclusivity |
US20070183427A1 (en) * | 2005-10-04 | 2007-08-09 | Tomas Nylander | Access control in radio access network having pico base stations |
US20070208937A1 (en) * | 2006-03-02 | 2007-09-06 | Cisco Technology, Inc. | System and method for wireless network profile provisioning |
US20070220573A1 (en) * | 2006-03-20 | 2007-09-20 | Chiussi Fabio M | Unicasting and multicasting multimedia services |
US7280417B2 (en) * | 2005-04-26 | 2007-10-09 | Micron Technology, Inc. | System and method for capturing data signals using a data strobe signal |
US7319744B1 (en) * | 2001-01-31 | 2008-01-15 | Palmsource, Inc. | Unified messaging/call routing configuration using palmtop computer |
US20080043689A1 (en) * | 2004-07-13 | 2008-02-21 | Sbc Knowledge Ventures, Lp | System and method for location based policy management |
US20080076412A1 (en) * | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for registering an access point |
US20080207182A1 (en) * | 2006-12-13 | 2008-08-28 | Quickplay Media Inc. | Encoding and Transcoding for Mobile Media |
US20080214161A1 (en) * | 2005-05-26 | 2008-09-04 | Symb | Location Based Push Presence and Profile on a Wireless Communications Device |
US20090011738A1 (en) * | 2006-03-10 | 2009-01-08 | Akihiro Sasakura | Mobile communication apparatus |
US20090221278A1 (en) * | 2005-12-30 | 2009-09-03 | Telecom Italia S.P.A. | Method for Customizing the Operation of a Telephonic Terminal |
US20090288152A1 (en) * | 2008-05-13 | 2009-11-19 | At&T Mobility Ii Llc | Automatic population of an access control list to manage femto cell coverage |
US20090298470A1 (en) * | 2008-05-13 | 2009-12-03 | At&T Mobility Ii Llc | Administration of access lists for femtocell service |
US20100167694A1 (en) * | 2008-12-31 | 2010-07-01 | Chiussi Fabio M | Femto personal policy server |
US20110009113A1 (en) * | 2008-06-10 | 2011-01-13 | Telefonaktiebolaget L M Ericsson (Publ) | Access control using temporary identities in a mobile communication system including femto base stations |
US20130115916A1 (en) * | 2008-11-13 | 2013-05-09 | Apple Inc. | Location Specific Content |
Family Cites Families (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6553375B1 (en) | 1998-11-25 | 2003-04-22 | International Business Machines Corporation | Method and apparatus for server based handheld application and database management |
US6711144B1 (en) | 2000-09-15 | 2004-03-23 | Airvana, Inc. | Multi-user communication of voice and data |
US6731618B1 (en) | 2000-10-20 | 2004-05-04 | Airvana, Inc. | Coding for multi-user communication |
US7277446B1 (en) | 2000-11-02 | 2007-10-02 | Airvana, Inc. | Communication of digital data over a wireless transmission medium |
US6741862B2 (en) | 2001-02-07 | 2004-05-25 | Airvana, Inc. | Enhanced reverse-link rate control in wireless communication |
US8160020B2 (en) | 2001-06-25 | 2012-04-17 | Airvana Network Solutions, Inc. | Radio network control |
US8195187B2 (en) | 2001-06-25 | 2012-06-05 | Airvana Network Solutions, Inc. | Radio network control |
US6781999B2 (en) | 2001-07-23 | 2004-08-24 | Airvana, Inc. | Broadcasting and multicasting in wireless communication |
US7603127B2 (en) | 2001-10-12 | 2009-10-13 | Airvana, Inc. | Boosting a signal-to-interference ratio of a mobile station |
US7299278B2 (en) | 2002-01-16 | 2007-11-20 | Airvana, Inc. | Managing network faults |
US7072672B1 (en) | 2002-11-01 | 2006-07-04 | Nokia Corporation | Disposable mini-applications |
US7200391B2 (en) | 2002-12-06 | 2007-04-03 | Airvana, Inc. | Capacity enhancement schemes for forward and reverse links of distributed cellular base stations |
US7843892B2 (en) | 2004-04-28 | 2010-11-30 | Airvana Network Solutions, Inc. | Reverse link power control |
US7983708B2 (en) | 2004-04-28 | 2011-07-19 | Airvana Network Solutions, Inc. | Reverse link power control |
US9876670B2 (en) | 2004-07-30 | 2018-01-23 | Commscope Technologies Llc | Local network node |
EP1779543B1 (en) | 2004-07-30 | 2012-04-25 | Andrew Richardson | Signal transmission method from a local network node |
WO2006010958A2 (en) | 2004-07-30 | 2006-02-02 | Andrew Richardson | Power control in a local network node (lnn) |
US7558356B2 (en) | 2004-09-30 | 2009-07-07 | Airvana, Inc. | Providing global positioning system (GPS) timing signals to remote cellular base stations |
US7515643B2 (en) | 2004-09-30 | 2009-04-07 | Airvana, Inc. | Modulation for broadcasting from multiple transmitters |
US7626926B2 (en) | 2004-12-09 | 2009-12-01 | Airvana, Inc. | Traffic management in a wireless data network |
US7729243B2 (en) | 2005-01-18 | 2010-06-01 | Airvana, Inc. | Reverse link rate and stability control |
US7831257B2 (en) | 2005-04-26 | 2010-11-09 | Airvana, Inc. | Measuring interference in radio networks |
US8099504B2 (en) | 2005-06-24 | 2012-01-17 | Airvana Network Solutions, Inc. | Preserving sessions in a wireless network |
US20060291420A1 (en) | 2005-06-27 | 2006-12-28 | Dennis Ng | Network-initiated dormant handoffs |
US8111253B2 (en) | 2005-07-28 | 2012-02-07 | Airvana Network Solutions, Inc. | Controlling usage capacity in a radio access network |
US8295818B2 (en) | 2005-09-15 | 2012-10-23 | Airvana Network Solutions, Inc. | Broadcasting in wireless systems |
US7751835B2 (en) | 2005-10-04 | 2010-07-06 | Airvana, Inc. | Non-circular paging areas |
US7558588B2 (en) | 2005-11-18 | 2009-07-07 | Airvana, Inc. | Resource allocation in a radio access network |
US8094630B2 (en) | 2005-12-16 | 2012-01-10 | Airvana Network Solutions, Inc. | Radio frequency dragging prevention |
US20070140218A1 (en) | 2005-12-16 | 2007-06-21 | Nair Girish R | Managing backhaul connections in radio access networks |
US8145221B2 (en) | 2005-12-16 | 2012-03-27 | Airvana Network Solutions, Inc. | Radio network communication |
US8619702B2 (en) | 2005-12-16 | 2013-12-31 | Ericsson Evdo Inc. | Radio network control |
US7801487B2 (en) | 2005-12-29 | 2010-09-21 | Airvana, Inc. | Detection of radio frequency interference in wireless communication systems |
US7672682B2 (en) | 2006-03-28 | 2010-03-02 | Airvana, Inc. | Managing page cycle periods of access terminals |
US8346220B2 (en) | 2006-03-31 | 2013-01-01 | Airvana Network Solutions, Inc. | Signaling for push-to-talk |
US20070230419A1 (en) | 2006-03-31 | 2007-10-04 | Sundar Raman | QoS signaling to support fairness |
US20070242648A1 (en) | 2006-04-12 | 2007-10-18 | Deepak Garg | Managing dormant handoffs in radio access networks |
US7953040B2 (en) | 2006-04-19 | 2011-05-31 | Airvana Network Solutions, Inc. | Channel assignment in wireless communication |
US8085696B2 (en) | 2006-07-14 | 2011-12-27 | Airvana Networks Solutions, Inc. | Dynamic modification of route update protocols |
US8688809B2 (en) | 2006-09-07 | 2014-04-01 | Airvana Lp | Provisioning private access points for wireless networking |
US8160629B2 (en) | 2006-09-07 | 2012-04-17 | Airvana, Corp. | Controlling reverse link interference in private access points for wireless networking |
US8078165B2 (en) | 2006-09-07 | 2011-12-13 | Airvana, Corp. | Configuring preferred user zone lists for private access points for wireless networking |
US8023439B2 (en) | 2006-11-20 | 2011-09-20 | Airvana Network Solutions, Inc. | Multicast flow distribution |
US8130686B2 (en) | 2006-11-20 | 2012-03-06 | Airvana Network Solutions, Inc. | Multicasting push-to-media content |
US7730189B2 (en) | 2006-11-22 | 2010-06-01 | Airvana, Inc. | Network-initiated session recovery |
US8639247B2 (en) | 2006-12-12 | 2014-01-28 | Ericsson Evdo Inc. | Access terminal session authentication |
US8532658B2 (en) | 2006-12-19 | 2013-09-10 | Airvana Network Solutions, Inc. | Neighbor list provision in a communication network |
US8457084B2 (en) | 2006-12-20 | 2013-06-04 | Airvana Llc | Communication group configuration in a network |
US8176327B2 (en) | 2006-12-27 | 2012-05-08 | Airvana, Corp. | Authentication protocol |
US8229498B2 (en) | 2006-12-28 | 2012-07-24 | Airvana, Corp. | Assigning code space to portable base stations |
US7926098B2 (en) | 2006-12-29 | 2011-04-12 | Airvana, Corp. | Handoff of a secure connection among gateways |
US9210569B2 (en) | 2008-12-31 | 2015-12-08 | Commscope Technologies Llc | Femto personal proxy application client |
-
2008
- 2008-12-31 US US12/347,201 patent/US9210569B2/en active Active
-
2009
- 2009-12-29 WO PCT/US2009/069734 patent/WO2010078364A1/en active Application Filing
Patent Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030045275A1 (en) * | 2000-04-27 | 2003-03-06 | Mcdonagh Brendan | Communication method and apparatus |
US6941148B2 (en) * | 2000-06-03 | 2005-09-06 | International Business Machines Corporation | Device registry for automatic connection and data exchange between pervasive devices and backend systems |
US7319744B1 (en) * | 2001-01-31 | 2008-01-15 | Palmsource, Inc. | Unified messaging/call routing configuration using palmtop computer |
US20040043763A1 (en) * | 2002-08-30 | 2004-03-04 | Brian Minear | System and method for application and application metadata filtering based on wireless device capabilities |
US20070054668A1 (en) * | 2002-10-25 | 2007-03-08 | Ibis Telecom, Inc. | Private base station with exclusivity |
US6940321B2 (en) * | 2003-01-23 | 2005-09-06 | Samsung Electronics Co., Ltd. | Circuit for generating a data strobe signal used in a double data rate synchronous semiconductor device |
US20080043689A1 (en) * | 2004-07-13 | 2008-02-21 | Sbc Knowledge Ventures, Lp | System and method for location based policy management |
US7280417B2 (en) * | 2005-04-26 | 2007-10-09 | Micron Technology, Inc. | System and method for capturing data signals using a data strobe signal |
US20080214161A1 (en) * | 2005-05-26 | 2008-09-04 | Symb | Location Based Push Presence and Profile on a Wireless Communications Device |
US20070001852A1 (en) * | 2005-06-30 | 2007-01-04 | Nokia Corporation | Wireless rights management |
US20070183427A1 (en) * | 2005-10-04 | 2007-08-09 | Tomas Nylander | Access control in radio access network having pico base stations |
US20090221278A1 (en) * | 2005-12-30 | 2009-09-03 | Telecom Italia S.P.A. | Method for Customizing the Operation of a Telephonic Terminal |
US20070208937A1 (en) * | 2006-03-02 | 2007-09-06 | Cisco Technology, Inc. | System and method for wireless network profile provisioning |
US20090011738A1 (en) * | 2006-03-10 | 2009-01-08 | Akihiro Sasakura | Mobile communication apparatus |
US20070220573A1 (en) * | 2006-03-20 | 2007-09-20 | Chiussi Fabio M | Unicasting and multicasting multimedia services |
US20080076412A1 (en) * | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for registering an access point |
US20080207182A1 (en) * | 2006-12-13 | 2008-08-28 | Quickplay Media Inc. | Encoding and Transcoding for Mobile Media |
US20090288152A1 (en) * | 2008-05-13 | 2009-11-19 | At&T Mobility Ii Llc | Automatic population of an access control list to manage femto cell coverage |
US20090298470A1 (en) * | 2008-05-13 | 2009-12-03 | At&T Mobility Ii Llc | Administration of access lists for femtocell service |
US20110009113A1 (en) * | 2008-06-10 | 2011-01-13 | Telefonaktiebolaget L M Ericsson (Publ) | Access control using temporary identities in a mobile communication system including femto base stations |
US20130115916A1 (en) * | 2008-11-13 | 2013-05-09 | Apple Inc. | Location Specific Content |
US20100167694A1 (en) * | 2008-12-31 | 2010-07-01 | Chiussi Fabio M | Femto personal policy server |
Cited By (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8615238B2 (en) | 2001-06-25 | 2013-12-24 | Ericsson Evdo Inc. | Radio network control |
US8140091B2 (en) | 2001-10-12 | 2012-03-20 | Airvana Network Solutions, Inc. | Boosting a signal-to-interference ratio of a mobile station |
US20110065464A1 (en) * | 2001-10-12 | 2011-03-17 | Sae-Young Chung | Boosting a signal-to-interference ratio of a mobile station |
US8886249B2 (en) | 2004-07-30 | 2014-11-11 | Airvana Lp | Method and system of setting transmitter power levels |
US7926098B2 (en) | 2006-12-29 | 2011-04-12 | Airvana, Corp. | Handoff of a secure connection among gateways |
US8693987B2 (en) | 2008-12-31 | 2014-04-08 | Airvana Lp | Femto personal policy server |
US20100167694A1 (en) * | 2008-12-31 | 2010-07-01 | Chiussi Fabio M | Femto personal policy server |
US9210569B2 (en) | 2008-12-31 | 2015-12-08 | Commscope Technologies Llc | Femto personal proxy application client |
US20110190000A1 (en) * | 2010-02-01 | 2011-08-04 | Samsung Electronics Co. Ltd. | Method and apparatus for allocating identifier of base station in communication system |
US9107182B2 (en) * | 2010-02-01 | 2015-08-11 | Samsung Electronics Co., Ltd. | Method and apparatus for allocating identifier of base station in communication system |
US20120317252A1 (en) * | 2011-06-09 | 2012-12-13 | Freescale Semiconductor, Inc | Method and system for address conflict resolution |
US8805977B2 (en) * | 2011-06-09 | 2014-08-12 | Freescale Semiconductor, Inc. | Method and system for address conflict resolution |
US9237492B2 (en) | 2012-05-31 | 2016-01-12 | Commscope Technologies Llc | Providing circuit switched service |
US10142858B2 (en) | 2013-02-07 | 2018-11-27 | Commscope Technologies Llc | Radio access networks |
US10764846B2 (en) | 2013-02-07 | 2020-09-01 | Commscope Technologies Llc | Radio access networks |
US9936470B2 (en) | 2013-02-07 | 2018-04-03 | Commscope Technologies Llc | Radio access networks |
US11700602B2 (en) | 2013-02-07 | 2023-07-11 | Commscope Technologies Llc | Radio access networks |
US10064072B2 (en) | 2013-02-07 | 2018-08-28 | Commscope Technologies Llc | Radio access networks |
US9380466B2 (en) | 2013-02-07 | 2016-06-28 | Commscope Technologies Llc | Radio access networks |
US10292175B2 (en) | 2013-02-07 | 2019-05-14 | Commscope Technologies Llc | Radio access networks |
US10455597B2 (en) | 2013-02-07 | 2019-10-22 | Commscope Technologies Llc | Radio access networks |
US11445455B2 (en) | 2013-02-07 | 2022-09-13 | Commscope Technologies Llc | Radio access networks |
US9414399B2 (en) | 2013-02-07 | 2016-08-09 | Commscope Technologies Llc | Radio access networks |
US11706640B2 (en) | 2013-02-07 | 2023-07-18 | Commscope Technologies Llc | Radio access networks |
US11729758B2 (en) | 2013-02-07 | 2023-08-15 | Commscope Technologies Llc | Radio access networks |
US11122447B2 (en) | 2013-02-07 | 2021-09-14 | Commscope Technologies Llc | Radio access networks |
US11102663B2 (en) | 2013-02-07 | 2021-08-24 | Commscope Technologies Llc | Radio access networks |
US11082997B2 (en) | 2014-06-09 | 2021-08-03 | Commscope Technologies Llc | Radio access networks in which mobile devices can be scheduled to use the same time-frequency resource |
US10536959B2 (en) | 2014-06-09 | 2020-01-14 | Commscope Technologies Llc | Radio access networks in which remote units are configured to perform at least some baseband processing |
US10057916B2 (en) | 2014-06-09 | 2018-08-21 | Commscope Technologies Llc | Radio access networks in which mobile devices in the same communication cell can be scheduled to use the same airlink resource |
US10785791B1 (en) | 2015-12-07 | 2020-09-22 | Commscope Technologies Llc | Controlling data transmission in radio access networks |
US11678358B2 (en) | 2017-10-03 | 2023-06-13 | Commscope Technologies Llc | Dynamic downlink reuse in a C-RAN |
US11395259B2 (en) | 2018-05-16 | 2022-07-19 | Commscope Technologies Llc | Downlink multicast for efficient front-haul utilization in a C-RAN |
US11304213B2 (en) | 2018-05-16 | 2022-04-12 | Commscope Technologies Llc | Dynamic uplink reuse in a C-RAN |
US10798667B2 (en) | 2018-06-08 | 2020-10-06 | Commscope Technologies Llc | Automatic transmit power control for radio points of a centralized radio access network that primarily provide wireless service to users located in an event area of a venue |
US11627497B2 (en) | 2018-09-04 | 2023-04-11 | Commscope Technologies Llc | Front-haul rate reduction for use in a centralized radio access network |
Also Published As
Publication number | Publication date |
---|---|
WO2010078364A1 (en) | 2010-07-08 |
US9210569B2 (en) | 2015-12-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9210569B2 (en) | Femto personal proxy application client | |
US8693987B2 (en) | Femto personal policy server | |
US8542707B2 (en) | Multi-carrier system selection | |
US8229397B2 (en) | Access terminal authorization at private access points in wireless networks | |
US10080097B2 (en) | System and method for managing interference in a network environment based on user presence | |
EP1932385B1 (en) | Access control in radio access network having pico base stations | |
EP3488635B1 (en) | Mobility in a multi-network wireless system | |
RU2521615C2 (en) | Communication device and method of providing services to communication devices in communication system including private cell | |
EP2343927B1 (en) | Devices for supporting emergency services in home cells and method thereof | |
US8078165B2 (en) | Configuring preferred user zone lists for private access points for wireless networking | |
EP2213121B1 (en) | Methods for access control in femto systems | |
US9554317B2 (en) | System and method for supporting emergency services in home cells | |
US20110171924A1 (en) | Selective Support and Establishment of Emergency Services in Home Cells | |
EP2863680B1 (en) | Handling connected mode mobility from areas bounding multi-operator core network and non-multi-operator core network shared infrastructure | |
TW201306544A (en) | Method and apparatus for Selected Internet Protocol (IP) Traffic Offload (SIPTO) and Local IP Access (LIPA) mobility | |
WO2021159307A1 (en) | Network slice aware cell selection | |
US20120172082A1 (en) | Mobility detection and reporting system and method for detecting and reporting cell changes of a mobile terminal in a mobile telecommunication network | |
US8479269B1 (en) | Method and system for redirecting unauthorized wireless communication devices away from a femtocell | |
US20230309059A1 (en) | User alert for change in network coverage | |
US8868033B1 (en) | Method and system for avoiding unauthorized wireless communication devices at a femtocell |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AIRVANA, INC.,MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHIUSSI, FABIO M.;HEGDE, PARAMESHWAR;PANDIT, MAYURESH;SIGNING DATES FROM 20090428 TO 20090429;REEL/FRAME:022609/0682 Owner name: AIRVANA, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHIUSSI, FABIO M.;HEGDE, PARAMESHWAR;PANDIT, MAYURESH;SIGNING DATES FROM 20090428 TO 20090429;REEL/FRAME:022609/0682 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST FSB,NEW YORK Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AIRVANA, INC.;REEL/FRAME:024213/0355 Effective date: 20100409 Owner name: WILMINGTON TRUST FSB, NEW YORK Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AIRVANA, INC.;REEL/FRAME:024213/0355 Effective date: 20100409 |
|
AS | Assignment |
Owner name: AIRVANA NETWORK SOLUTIONS, INC., MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:AIRVANA, INC.;REEL/FRAME:024804/0404 Effective date: 20100716 |
|
AS | Assignment |
Owner name: AIRVANA CORP., MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:AIRVANA NETWORK SOLUTIONS, INC.;REEL/FRAME:024822/0680 Effective date: 20100719 |
|
AS | Assignment |
Owner name: AIRVANA, CORP., MASSACHUSETTS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE BRIEF DESCRIPTION AND EXECUTION DATE OF ASSIGNOR PREVIOUSLY RECORDED ON REEL 024822 FRAME 0680. ASSIGNOR(S) HEREBY CONFIRMS THE BRIEF: ASSIGNMENT OF ASSIGNOR'S INTEREST AND THE DOC DATE: 07/23/2010;ASSIGNOR:AIRVANA NETWORK SOLUTIONS, INC.;REEL/FRAME:024841/0287 Effective date: 20100723 |
|
AS | Assignment |
Owner name: AIRVANA, INC., MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WILMINGTON TRUST FSB, AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT;REEL/FRAME:024892/0924 Effective date: 20100827 |
|
AS | Assignment |
Owner name: AIRVANA LLC, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:AIRVANA CORP.;REEL/FRAME:030802/0191 Effective date: 20110502 |
|
AS | Assignment |
Owner name: AIRVANA LP, MASSACHUSETTS Free format text: CONVERSION;ASSIGNOR:AIRVANA LLC;REEL/FRAME:031814/0063 Effective date: 20130828 |
|
AS | Assignment |
Owner name: AIRVANA LP, MASSACHUSETTS Free format text: CONVERSION;ASSIGNOR:AIRVANA LLC;REEL/FRAME:032263/0796 Effective date: 20130828 |
|
AS | Assignment |
Owner name: COMMSCOPE TECHNOLOGIES LLC, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AIRVANA LP;REEL/FRAME:036927/0544 Effective date: 20151001 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., ILLINOIS Free format text: PATENT SECURITY AGREEMENT (ABL);ASSIGNOR:COMMSCOPE TECHNOLOGIES LLC;REEL/FRAME:037268/0524 Effective date: 20151110 Owner name: JPMORGAN CHASE BANK, N.A., ILLINOIS Free format text: PATENT SECURITY AGREEMENT (TERM);ASSIGNOR:COMMSCOPE TECHNOLOGIES LLC;REEL/FRAME:037268/0488 Effective date: 20151110 |
|
AS | Assignment |
Owner name: COMMSCOPE, INC. OF NORTH CAROLINA, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:048840/0001 Effective date: 20190404 Owner name: ALLEN TELECOM LLC, ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:048840/0001 Effective date: 20190404 Owner name: COMMSCOPE TECHNOLOGIES LLC, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:048840/0001 Effective date: 20190404 Owner name: REDWOOD SYSTEMS, INC., NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:048840/0001 Effective date: 20190404 Owner name: ANDREW LLC, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:048840/0001 Effective date: 20190404 Owner name: COMMSCOPE TECHNOLOGIES LLC, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:049260/0001 Effective date: 20190404 Owner name: REDWOOD SYSTEMS, INC., NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:049260/0001 Effective date: 20190404 Owner name: ANDREW LLC, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:049260/0001 Effective date: 20190404 Owner name: ALLEN TELECOM LLC, ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:049260/0001 Effective date: 20190404 Owner name: COMMSCOPE, INC. OF NORTH CAROLINA, NORTH CAROLINA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:049260/0001 Effective date: 20190404 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: ABL SECURITY AGREEMENT;ASSIGNORS:COMMSCOPE, INC. OF NORTH CAROLINA;COMMSCOPE TECHNOLOGIES LLC;ARRIS ENTERPRISES LLC;AND OTHERS;REEL/FRAME:049892/0396 Effective date: 20190404 Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: TERM LOAN SECURITY AGREEMENT;ASSIGNORS:COMMSCOPE, INC. OF NORTH CAROLINA;COMMSCOPE TECHNOLOGIES LLC;ARRIS ENTERPRISES LLC;AND OTHERS;REEL/FRAME:049905/0504 Effective date: 20190404 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATE Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:COMMSCOPE TECHNOLOGIES LLC;REEL/FRAME:049892/0051 Effective date: 20190404 Owner name: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CONNECTICUT Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:COMMSCOPE TECHNOLOGIES LLC;REEL/FRAME:049892/0051 Effective date: 20190404 |
|
AS | Assignment |
Owner name: WILMINGTON TRUST, DELAWARE Free format text: SECURITY INTEREST;ASSIGNORS:ARRIS SOLUTIONS, INC.;ARRIS ENTERPRISES LLC;COMMSCOPE TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:060752/0001 Effective date: 20211115 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |