WO2010132826A2 - Femtocell self organization in wimax communications - Google Patents

Femtocell self organization in wimax communications Download PDF

Info

Publication number
WO2010132826A2
WO2010132826A2 PCT/US2010/034991 US2010034991W WO2010132826A2 WO 2010132826 A2 WO2010132826 A2 WO 2010132826A2 US 2010034991 W US2010034991 W US 2010034991W WO 2010132826 A2 WO2010132826 A2 WO 2010132826A2
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
access point
wireless
son
wireless communication
Prior art date
Application number
PCT/US2010/034991
Other languages
French (fr)
Other versions
WO2010132826A3 (en
Inventor
Jianquan Song
Tricci So
Wen Luo
Li Chu
Original Assignee
Zte (Usa) Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zte (Usa) Inc. filed Critical Zte (Usa) Inc.
Publication of WO2010132826A2 publication Critical patent/WO2010132826A2/en
Publication of WO2010132826A3 publication Critical patent/WO2010132826A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/34Reselection control
    • H04W36/38Reselection control by fixed network equipment
    • H04W36/385Reselection control by fixed network equipment of the core network

Definitions

  • This patent document relates to wireless communication systems.
  • Wireless communication systems can include a network of one or more base stations to communicate with one or more wireless devices such as a mobile device, cell phone, wireless air card, mobile station (MS), user equipment (UE), access terminal (AT), or subscriber station (SS).
  • Each base station emits radio signals that carry data such as voice data and other data content to wireless devices.
  • a base station can be referred to as an access point (AP) or access network (AN) or can be included as part of an access network or a base station subsystem (BSS).
  • a base station can transmit a radio signal on a forward link (FL), also called a downlink (DL), to one or more wireless devices.
  • a wireless device can transmit a radio signal on a reverse link (RL), also called an uplink (UL), to one or more base stations.
  • FL forward link
  • DL downlink
  • RL reverse link
  • UL uplink
  • a wireless device can use one or more different wireless technologies for communications.
  • Various examples of wireless technologies include Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA) such as CDMA2000 Ix, High Rate Packet Data (HRPD), evolved HRPD (eHRPD), Universal Mobile Telecommunications System (UMTS), Universal Terrestrial Radio Access
  • WiMAX Worldwide Interoperability for Microwave Access
  • CDMA Code Division Multiple Access
  • HRPD High Rate Packet Data
  • eHRPD evolved HRPD
  • UMTS Universal Mobile Telecommunications System
  • a wireless communication system such as one that uses WiMAX technology that is based on an IEEE 802.16 standard, e.g., IEEE 802.16e, can include one or more Access Service Networks (ASNs) for wireless device communications.
  • ASNs Access Service Networks
  • the system can include one or more base stations configured as a WiMAX Femto Access Point (WFAP).
  • WFAP WiMAX Femto Access Point
  • the system can include one or more gateway units to control base stations.
  • the system can include one or more Connectivity Service Networks (CSNs) to provide services such as policy management, authentication, authorization, and accounting.
  • CSNs Connectivity Service Networks
  • This document describes, among other things, technologies for femtocell self- organization including different network reference models for WiMAX femtocell Self- Organization Network (SON) architectures.
  • SON WiMAX femtocell Self- Organization Network
  • Wireless communication systems can include an access point to provide wireless service to one or more wireless devices, a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices and to provide communications with an external network via the first gateway; and a second gateway to control an interconnection privilege of the access point with the first gateway and provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to SON message traffic associated with the access point.
  • SON message traffic can include one or more wireless communication parameter values.
  • Wireless communication systems can include one or more of the following features.
  • SON message traffic can include message traffic associated with one or more of: auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration.
  • Systems can include a SON server to manage and to assemble wireless communication parameters for multiple access points.
  • a SON server can send one or more wireless communication parameter values to the access point via the second gateway.
  • the access point communicates with the SON server via the secure communication pathway.
  • the second gateway communicates with the access point over a third party wired or wireless broadband infrastructure.
  • the second gateway is configured to prevent unauthorized traffic from being sent to the first gateway.
  • the second gateway is configured to inspect data packets from the access point to verify a source identifier.
  • the second gateway encrypts access point traffic received from the first gateway prior to forwarding the access point traffic to the access point. In some implementations, the second gateway decrypts traffic received from the access point prior to forwarding the decrypted traffic to the first gateway.
  • the first gateway communicates with a server system in a connectivity service network (CSN).
  • the server system provides authentication, authorization, accounting services for wireless devices.
  • a server system can provide a pathway to a network.
  • the access point is a femtocell access point.
  • the second gateway provides authentication, authorization, accounting services that are specific to the femtocell access point.
  • the access point communicates with the one or more wireless devices based on a WiMAX technology.
  • Systems can include a base station to provide wireless service to wireless devices in a geographical wireless service area that is larger than a geographical wireless area associated with the femtocell access point.
  • the first gateway provides control and bearer plane message traffic for the femtocell access point and the base station.
  • Systems can include a gateway that comprises the first gateway and the second gateway.
  • techniques can include causing an access point to provide wireless service to one or more wireless devices, operating a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices to interconnect to an external network via the first gateway, operating a second gateway to control an interconnection privilege of the access point with the first gateway; and operating the second gateway to provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry SON message traffic associated with the access point.
  • FIG. 1 shows an example of a wireless communication system.
  • FIG. 2 shows an example of a radio station architecture.
  • FIGS. 3, 4, 5, 6, 7, and 8 show different wireless communication system architectures.
  • FIG. 9 shows an example of a communication process.
  • This document describes, among other things, techniques, apparatuses, and systems for femtocell self-organization.
  • This document includes descriptions of communication pathways for secure communications between femtocells and network entities such as a communication gateway or a self-organization management server.
  • This document provides descriptions of reference points for communications associated with femtocell access points.
  • FIG. 1 shows an example of a wireless communication system.
  • a wireless communication system can include one or more base stations (BSs) 105, 107, 109 to provide wireless service to wireless devices 110.
  • a base station 105, 107, 109 can transmit a signal to one or more wireless devices 110.
  • a wireless device 110 can transmit a signal to one or more base stations 105, 107, 109.
  • a base station such as a WiMAX Femtocell Access Point (WFAP) 109 can provide wireless service in a smaller geographical coverage area than a macro base station 105, 107.
  • WFAP 109 can provide wireless service in an office building, a home, or a room thereof.
  • WFAP WiMAX Femtocell Access Point
  • a wireless communication system can include one or more Access Service Networks (ASNs) 120, 125.
  • ASNs 120, 125 includes one or more base stations.
  • a wireless communication system can include one or more Connectivity Service Networks (CSNs) 130, 135.
  • the ASNs 120, 125 and the CSNs 130, 135 are networked via one or more networks 140.
  • An ASN 120, 125 can include a gateway to communicate with a CSN 130, 135.
  • an ASN 120 can communicate with a WFAP 109 via a public network such as the Internet.
  • FIG. 2 shows an example of a radio station architecture.
  • a radio station 205 such as a base station or a wireless device can include processor electronics 210 such as a microprocessor that implements one or more techniques presented in this document.
  • a radio station 205 can include transceiver electronics 215 to send and/or receive wireless signals over one or more communication interfaces such as an antenna 220.
  • a radio station 205 can include additional communication interfaces for transmitting and receiving data.
  • a radio station 205 can include one or more memories configured to store information such as data and/or instructions.
  • Entities in a wireless communication system such as a wireless device, ASN and CSN can represent a grouping of functional entities. Such functions can be realized in a single physical functional entity. However, such functions can be distributed over two or more physical functional entities. The grouping and distribution of functions into physical devices within the ASN is an implementation choice.
  • a logical representation of a WiMAX network architecture is based on a Network Reference Model (NRM) that identifies functional entities and reference points over which interoperability is achieved between functional entities.
  • NRM Network Reference Model
  • the intent of the NRM is to allow multiple implementation options for a given functional entity, and yet achieve interoperability among different realizations of functional entities.
  • Interoperability is based on the definition of communication protocols and data plane treatment between functional entities to achieve an overall end-to-end function, for example, security or mobility management.
  • a reference point is a conceptual link that connects two groups of functions that reside in different functional entities of an ASN, CSN, or MS and thus RP is not necessarily a physical interface.
  • a reference point becomes a physical interface when the functional entities on either side of the RP are contained in different physical MSs.
  • the functional entities on either side of RP represent a collection of control and Bearer Plane end-points.
  • interoperability will be verified based on protocols exposed across an RP, which may depend on the end-to-end function or capability realized (e.g., based on the usage scenarios supported by the overall network).
  • a wireless communication system can provide multiple communication interfaces.
  • a system can include one or more of the following Reference Points.
  • Reference Point Rl includes the protocols and procedures between MS and ASN as per the air interface (PHY and MAC) specifications (e.g., IEEE P802.16e-2005, IEEE P802.16-2004 and IEEE 802.16g). Reference point Rl can include additional protocols related to the management plane. Reference Point R2 includes protocols and procedures between the MS and CSN associated with Authentication, Services Authorization and IP Host Configuration management. The authentication part of reference point R2 runs between the MS and the CSN operated by the home NSP, however the ASN and CSN operated by the visited NSP may partially process the aforementioned procedures and mechanisms. Reference Point R2 can support IP Host Configuration Management running between the MS and the CSN (operated by either the home NSP or the visited NSP).
  • PHY and MAC air interface
  • Reference Point R3 includes the set of Control Plane protocols between the ASN and the CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the Bearer Plane methods (e.g., tunneling) to transfer user data between the ASN and the CSN.
  • Reference Point R4 includes a set of Control and Bearer Plane protocols originating/terminating in various functional entities of an ASN that coordinate MS mobility between ASNs and ASN-GWs. R4 is an interoperable RP between similar or heterogeneous ASNs.
  • Reference Point R5 includes the set of Control Plane and Bearer Plane protocols for internetworking between the CSN operated by the home NSP and that operated by a visited NSP.
  • Reference point R6 includes the set of control and Bearer Plane protocols for communication between the BS and the ASN-GW.
  • the Bearer Plane can include an intra-ASN datapath between the BS and ASN gateway.
  • the Control Plane includes protocols for datapath establishment, modification, and release control in accordance with the MS mobility events.
  • Reference Point R8 can include protocols and primitives.
  • a wireless communication system can include multiple systems that are operated by different operators, e.g., a Network Access Provider (NAP), Network Service Provider (NSP), and Femto-NSP.
  • NAP Network Access Provider
  • NSP Network Service Provider
  • Femto-NSP can belong to different operators.
  • the NAP, NSP and the Femto-NSP can belong to the same operator.
  • a NAP can run an ASN.
  • a Single NAP can have two or more types of ASNs, e.g., one that does not support WFAPs and one that does support WFAPs, which can be called a Femto-ASN.
  • a NSP can operate a CSN.
  • a CSN can include an authentication, authorization, accounting (AAA) server and a home agent (HA).
  • a Femto-NSP can operate a CSN for Femto-ASN, which can be called a Femto-CSN.
  • a Femto-CSN is a CSN that supports WFAPs.
  • a Femto-CSN can include a AAA server for WFAPs.
  • a WFAP can be configured to have different access privileges than a macro base station in a wireless communication system.
  • a Femto-AAA can store WFAP specific access privileges.
  • An ASN may communicate with a WFAP over a third party network such as the Internet.
  • a wireless communication system can include a security gateway (SGW, Sec-GW, or Se-GW) to provide secure communication between a WFAP and other network entities.
  • a security gateway is a part of the Femto-NSP system component/function and can belong to the same operator as the WFAP, e.g., the SGW belongs to the Femto-NSP.
  • the secure communication pathway is described by a Rs reference point.
  • the Rs can be used between a WFAP and a security gateway.
  • a security tunnel such as one based on an Internet Protocol Security (IPsec) protocol can be established in Rs between a WFAP and a security gateway to provide backhaul security.
  • IPsec Internet Protocol Security
  • a R3 or R3-F reference point can be used between a security gateway and a AAA server such as a Femto-AAA server.
  • a security gateway is co-located with a Femto-GW.
  • a security gateway is a standalone entity. In a standalone configuration, the security gateway can be located differently than the Femto-GW. Therefore, a wireless communication system can provide an interface, e.g., open interface or closed interface, between a security gateway and a Femto-FW. Such an interface can include an
  • a security gateway can terminate IPsec tunneling for a WFAP.
  • a security gateway can filter out unauthorized traffic on the links between a security gateway and a WFAP.
  • a security gateway can provide access control of WFAP to the Network.
  • a secure communication pathway can provide a pathway for one or more communication pathways such as control plane and bearer plane signaling, e.g., one described by a R6-F reference point, a SON traffic, e.g., one described by a Rson reference point.
  • a security gateway can inspect data packets from a WFAP over R6-F to verify a correct source ID.
  • a security gateway can encrypt the data between a WFAP and a security gateway.
  • the security gateway can provide integrity protection.
  • a wireless communication system can include a gateway such as a Femto-
  • a Femto-GW can reside in an ASN that supports femtocells.
  • a Femto-GW is a separate gateway in the NRM for the support of WFAPs.
  • Femto-GW can have the same set of functionalities which are provided by a macro-GW and additional functionalities which are defined for femtocell-specific operation.
  • R4/R4+ reference point is used between the Femto-GWs.
  • a R4 reference point is used between a Femto-GW and an ASN-GW.
  • a R6 or R6-F reference point is used between a WFAP and a Femto-GW.
  • the R6 and R6-F traffic are transparent from the WFAP to the Femto-GW via a security gateway.
  • a Femto-GW and ASN-GW can be in the same ASN. Some implementations can terminate R6-F starting from the WFAP.
  • a Femto-GW is an ASN-GW with additional functionalities for femtocell access points.
  • a wireless communication system can include a Femto-AAA.
  • a Femto-AAA belonging to the Femto-NSP, can reside in a Femto-CSN which is operated by a Femto-NSP.
  • R5 reference point is used between an AAA for access control at a WFAP and an AAA for the wireless device.
  • a Femto-AAA and an AAA server which is for wireless devices, can be the same device.
  • a femto-AAA can provide authentication and/or authorization of a WFAP.
  • the security gateway can take the responsibility for the WAFP authentication.
  • Reference Point Rl can include protocols and procedures between wireless device and ASN per the air interface (e.g., PHY and MAC) specifications (e.g., IEEE P802.16e-2005, IEEE P802.16-2004).
  • Reference Point R3 can include Control Plane protocols and Bearer Plane protocols to support AAA and also to transfer of user data between the ASN and the CSN.
  • AAA is responsible for subscriber authentication and charging.
  • Reference Point R4 can include Control Plane protocols and Bearer Plane protocols originating/terminating in various functions entities of an ASN that coordinates MS mobility between different ASNs and Femto-GW as well as between Femto-GWs.
  • the Femto-GW can be connected to a macro ASN-GW through R4 if the interoperability with a macro network is required.
  • R4/R4+ reference point is used between the Femto-GWs.
  • a R4 reference point is used between a Femto-GW and an ASN-GW.
  • Reference Point R6-F can include Control Plane and Bearer Plane for communication between a WFAP and a Femto-GW.
  • Reference Point R6-F can support femtocell specific features and the existing features of R6.
  • control and bearer plane traffic over Reference Point R6-F is sent through an IPsec tunnel between a WFAP and a security gateway.
  • Reference Point R3-F can include Control Plane and Management Plane protocols to support the management, authorization and authentication of a WFAP between the WFAP and other entities in a Femto-NSP, such as Femto-AAA and Management system. Additional functions (e.g. SON) can be added in R3-F. In some implementations, communications between the WFAP and the SON are through the Management System. In some implementations, R3-F provides a control panel. In some implementations, R3-F provides a control plane and a management plane.
  • a wireless communication system can include multiple ASN that supports WFAPs. If another ASN also includes a Femto-GW, then this ASN can have a R3-F reference point between itself and a CSN that includes a Femto-
  • Reference Point Rs can include protocols for establishing IPsec tunnel using
  • Reference Point Rs can be used to transmit R6-F control and bearer traffic between a WFAP and a Femto-GW.
  • Reference Point R5 can be used between the Femto-NSP's CSN, which contains a Femto-AAA, and the CSN. Reference Point R5 can be used for communication between the Femto-AAA and the AAA.
  • FIGS. 3, 4, 5, 6, 7, and 8 show different examples of wireless communication system architectures.
  • FIG. 3 shows an example of a wireless communication system architecture.
  • CSN 305 can include a SON server 310, a management system 315, and a AAA server such as a Femto-AAA server 320.
  • a ASN 330 can include a SON controller 340, and one or more gateways such as a Sec-GW 335 and a Femto-GW 345.
  • the WFAP 355 can communicate with a wireless device such as a mobile station 360.
  • the Femto-GW 345 can communicate with one or more CSNs 305, 365 to provide control and bearer plane signaling to the WFAP
  • a Femto-GW 345 communicates with another ASN 370.
  • the Sec-GW 335 can provide a secure communication pathway 350 to an access point such as a WFAP 355.
  • the Sec-GW 335 can communicate control and bearer plane message traffic with the WFAP 355 via the secure communication pathway 350.
  • Sec-GW 335 can communicate SON message traffic with the WFAP 355 via the secure communication pathway 350.
  • SON message traffic includes one or more wireless communication parameter values, such as a radio frequency assignment, transmission power level, and PHY parameter values.
  • the WFAP 355 can produce a wireless communication signal based on the one or more wireless communication parameter values that are received in a SON message.
  • a WFAP 355 takes measurements of a wireless communication environment and reports the measurements to the SON server 310. Based on the measurements, the SON server 310 can determine how to configure a WFAP for wireless communications as to minimize interface with other communication devices within a wireless communication range of a WFAP.
  • a SON server 310 can manage wireless communication parameters for multiple access points such as WFAP 355.
  • the SON server 310 sends wireless communication parameter values to the WFAP 355 via the Femto-GW 345.
  • a SON server 310 causes a SON controller 340 to send and receive SON messages to and from a WFAP 355.
  • the WFAP 355 can run a SON client.
  • a SON client can send a SON message to a SON controller 340 via the secure communication pathway 350.
  • the SON controller 340 can terminate a Rson communication with a SON client on a WFAP 355.
  • the secure communication pathway 330 is layered on top of a transport and network communication stack such as a TCP/IP stack.
  • communications between the WFAP 355 and the Sec-GW 335 are over an public network. Unauthorized sources may attempt to send traffic to the Femto-GW 345. Therefore, in some implementations, the Sec-GW 335 provides access control for communications with the Femto-GW 345.
  • the Sec-GW 335 can be configured to block unauthorized access points from communicating with the Femto-GW 345.
  • a gateway, such as a Sec-GW 335 or a Femto-GW 345, can include one or more processors.
  • FIG. 4 shows another example of a wireless communication system architecture.
  • an ASN 405 includes a SON server 410.
  • the SON server 410 can communicate with a SON agent 420 that resides in a CSN 415.
  • the SON server 410 can communicate with a SON client on an access via a Sec-GW 425.
  • FIG. 5 shows another example of a wireless communication system architecture.
  • an ASN 505 includes a Femto-GW 510 that is configured to provide connectivity with a SON server 520 in a CSN 515.
  • SON message flows between the SON server 520 to a SON client, such as one that resides on a WFAP, via the Femto-GW 510 and a Sec-GW 525.
  • FIG. 6 shows another example of a wireless communication system architecture.
  • a CSN 605 can include a SON server 610, a management system 615, and a AAA server such as a Femto-AAA server 620.
  • An ASN 630 can include a SON controller 640, and one or more gateways such as a Sec-GW 635 and a Femto-GW 645.
  • the WFAP 655 can communicate with one or more wireless devices.
  • the Femto-GW 645 can communicate with one or more CSNs 605 to provide control and bearer plane signaling to the WFAP 655 via the Sec-GW 635.
  • the Femto-GW 645 can communicate with one or more CSNs 605 to provide control and bearer plane signaling to a macro base station 670.
  • the macro base station 670 provides coverage in a larger area than the WFAP 655.
  • the wireless communication system can handoff a wireless device between the WFAP 655 and the macro base station 670.
  • the WFAP 655 can communicate with the Sec-GW 635 via a third party network such as an un-trusted network.
  • the Sec-GW 635 can provide a secure communication pathway 650 between the Sec-GW 635 and the WFAP 655.
  • the Sec-GW 635 can communicate SON message traffic with the WFAP 655 via the secure communication pathway 650.
  • the WFAP 655 can run a SON client configured to perform SON operations such as auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration based on communication with the SON server 610 via a SON controller 640.
  • FIG. 7 shows another example of a wireless communication system architecture.
  • an ASN 705 includes a SON server 710.
  • the SON server 710 can communicate with a SON agent 720 that resides in a CSN 715.
  • the SON server 710 can communicate with a SON client on an access point via a Sec-GW 725.
  • the SON server 710 can communicate with the SON agent 720 via a Femto-GW 730.
  • the Femto-GW 730 can provide communication services for two or more types of base stations, e.g., macro base stations and WFAPs.
  • FIG. 8 shows another example of a wireless communication system architecture.
  • an ASN 805 includes a Femto-GW 810 that is configured to provide connectivity with a SON server 820 in a CSN 815.
  • SON message flows between the SON server 820 to a SON client, such as one that resides on a WFAP, via the Femto-GW 810 and a Sec-GW 825.
  • the Femto-GW 810 can provide communication services for two or more types of base stations, e.g., macro base stations and WFAPs.
  • FIG. 9 shows an example of a communication process.
  • a communication process can include causing an access point to provide wireless service to wireless devices.
  • the process can send a command to control the access point to start providing wireless service.
  • the process can include operating a first gateway to provide control plane and bearer plane signaling associated with the wireless devices to interconnect to an external network, e.g., a CSN, via the first gateway.
  • the process can include operating a second gateway to control an interconnection privilege of the access point with the first gateway.
  • the second gateway can determine whether a specific access point is allowed to communicate with the first gateway.
  • the process can include operating the second gateway to provide a secure communication pathway between the access point and the second gateway to carry information such as control plane and bearer plane signaling and SON message traffic.
  • the process perform encryption and decryption for message traffic in a secure communication pathway.
  • the process includes operating the second gateway to prevent unauthorized traffic from being sent to the first gateway.
  • the process includes operating the second gateway to inspect data packets from the access point to verify a source identifier.
  • the process includes operating the second gateway to encrypt access point traffic received from the first gateway prior to forwarding the access point traffic to the access point.
  • the process includes operating the second gateway to decrypt traffic received from the access point prior to forwarding the decrypted traffic to the first gateway.
  • the process communicates with a gateway such as a combined Femto-GW and Sec-GW gateway.
  • the disclosed and other embodiments and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them.
  • the disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus.
  • the computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them.
  • data processing apparatus encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
  • the apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
  • a propagated signal is an artificially generated signal, e.g., a machine- generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
  • a computer program (also known as a program, software, software application, script, or code) 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 standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • a computer program does not necessarily correspond to a file in a file system.
  • a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code).
  • a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
  • the processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.
  • the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
  • 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.
  • 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 performing 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.
  • mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.
  • a computer need not have such devices.
  • Computer readable media suitable for storing computer program instructions and data include all forms of non volatile memory, media and memory devices, 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.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto optical disks e.g., CD ROM and DVD-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Techniques, apparatuses, and systems can include mechanisms for femtocell self organization. In an implementation a wireless communication system includes a first gateway to communicate with an access point to provide wireless service to one or more wireless devices and to provide control plane and bearer plane signaling associated with the one or more wireless devices to interconnect to an external network via the first gateway. The wireless communication system includes a second gateway to control an interconnection privilege of the access point with the first gateway and provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry self-organizing network (SON) message traffic associated with the access point. The SON message traffic can include one or more wireless communication parameter values.

Description

FEMTOCELL SELF ORGANIZATION IN WIMAX COMMUNICATIONS
PRIORITY CLAIM AND CROSS REFERENCE TO RELATED APPLICATION
[0001] This patent document claims the benefit of the priority of U.S. Provisional
Application Serial No. 61/178,481, filed May 14, 2009, entitled "NETWORK DESIGNS FOR FEMTO BASE STATION SELF ORGANIZATION IN WIMAX COMMUNICATIONS," the entire contents of which are incorporated by reference as part of the disclosure of this document.
BACKGROUND
[0002] This patent document relates to wireless communication systems.
[0003] Wireless communication systems can include a network of one or more base stations to communicate with one or more wireless devices such as a mobile device, cell phone, wireless air card, mobile station (MS), user equipment (UE), access terminal (AT), or subscriber station (SS). Each base station emits radio signals that carry data such as voice data and other data content to wireless devices. A base station can be referred to as an access point (AP) or access network (AN) or can be included as part of an access network or a base station subsystem (BSS). A base station can transmit a radio signal on a forward link (FL), also called a downlink (DL), to one or more wireless devices. A wireless device can transmit a radio signal on a reverse link (RL), also called an uplink (UL), to one or more base stations. [0004] A wireless device can use one or more different wireless technologies for communications. Various examples of wireless technologies include Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA) such as CDMA2000 Ix, High Rate Packet Data (HRPD), evolved HRPD (eHRPD), Universal Mobile Telecommunications System (UMTS), Universal Terrestrial Radio Access
Network (UTRAN), evolved UTRAN (E-UTRAN), and Long-Term Evolution (LTE). [0005] A wireless communication system such as one that uses WiMAX technology that is based on an IEEE 802.16 standard, e.g., IEEE 802.16e, can include one or more Access Service Networks (ASNs) for wireless device communications. The system can include one or more base stations configured as a WiMAX Femto Access Point (WFAP). The system can include one or more gateway units to control base stations. The system can include one or more Connectivity Service Networks (CSNs) to provide services such as policy management, authentication, authorization, and accounting.
SUMMARY
[0006] This document describes, among other things, technologies for femtocell self- organization including different network reference models for WiMAX femtocell Self- Organization Network (SON) architectures.
[0007] Wireless communication systems, based on one of more of the described technologies, can include an access point to provide wireless service to one or more wireless devices, a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices and to provide communications with an external network via the first gateway; and a second gateway to control an interconnection privilege of the access point with the first gateway and provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to SON message traffic associated with the access point. SON message traffic can include one or more wireless communication parameter values. [0008] Wireless communication systems can include one or more of the following features. SON message traffic can include message traffic associated with one or more of: auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration. Systems can include a SON server to manage and to assemble wireless communication parameters for multiple access points. A SON server can send one or more wireless communication parameter values to the access point via the second gateway. In some implementations, the access point communicates with the SON server via the secure communication pathway. [0009] In some implementations, the second gateway communicates with the access point over a third party wired or wireless broadband infrastructure. In some implementations, the second gateway is configured to prevent unauthorized traffic from being sent to the first gateway. In some implementations, the second gateway is configured to inspect data packets from the access point to verify a source identifier. In some implementations, the second gateway encrypts access point traffic received from the first gateway prior to forwarding the access point traffic to the access point. In some implementations, the second gateway decrypts traffic received from the access point prior to forwarding the decrypted traffic to the first gateway.
[0010] In some implementations, the first gateway communicates with a server system in a connectivity service network (CSN). In some implementations, the server system provides authentication, authorization, accounting services for wireless devices. A server system can provide a pathway to a network. In some implementations, the access point is a femtocell access point. In some implementations, the second gateway provides authentication, authorization, accounting services that are specific to the femtocell access point.
[0011] In some implementations, the access point communicates with the one or more wireless devices based on a WiMAX technology. Systems can include a base station to provide wireless service to wireless devices in a geographical wireless service area that is larger than a geographical wireless area associated with the femtocell access point. In some implementations, the first gateway provides control and bearer plane message traffic for the femtocell access point and the base station. Systems can include a gateway that comprises the first gateway and the second gateway. [0012] In another aspect, techniques, based on one of more of the described technologies, can include causing an access point to provide wireless service to one or more wireless devices, operating a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices to interconnect to an external network via the first gateway, operating a second gateway to control an interconnection privilege of the access point with the first gateway; and operating the second gateway to provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry SON message traffic associated with the access point.
[0013] These and other aspects and technical features associated with technologies for femtocell self-organization are set forth in the accompanying drawings, the description, and the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. 1 shows an example of a wireless communication system.
[0015] FIG. 2 shows an example of a radio station architecture.
[0016] FIGS. 3, 4, 5, 6, 7, and 8 show different wireless communication system architectures.
[0017] FIG. 9 shows an example of a communication process.
Like reference symbols in the various drawings indicate like elements.
DETAILED DESCRIPTION
[0018] This document describes, among other things, techniques, apparatuses, and systems for femtocell self-organization. This document includes descriptions of communication pathways for secure communications between femtocells and network entities such as a communication gateway or a self-organization management server. This document provides descriptions of reference points for communications associated with femtocell access points.
[0019] FIG. 1 shows an example of a wireless communication system. A wireless communication system can include one or more base stations (BSs) 105, 107, 109 to provide wireless service to wireless devices 110. A base station 105, 107, 109 can transmit a signal to one or more wireless devices 110. A wireless device 110 can transmit a signal to one or more base stations 105, 107, 109. A base station such as a WiMAX Femtocell Access Point (WFAP) 109 can provide wireless service in a smaller geographical coverage area than a macro base station 105, 107. For example, a WFAP 109 can provide wireless service in an office building, a home, or a room thereof. A wireless communication system can include one or more Access Service Networks (ASNs) 120, 125. In some implementations, an ASNs 120, 125 includes one or more base stations. A wireless communication system can include one or more Connectivity Service Networks (CSNs) 130, 135. The ASNs 120, 125 and the CSNs 130, 135 are networked via one or more networks 140. An ASN 120, 125 can include a gateway to communicate with a CSN 130, 135. In some implementations, an ASN 120 can communicate with a WFAP 109 via a public network such as the Internet. [0020] FIG. 2 shows an example of a radio station architecture. A radio station 205 such as a base station or a wireless device can include processor electronics 210 such as a microprocessor that implements one or more techniques presented in this document. A radio station 205 can include transceiver electronics 215 to send and/or receive wireless signals over one or more communication interfaces such as an antenna 220. A radio station 205 can include additional communication interfaces for transmitting and receiving data. A radio station 205 can include one or more memories configured to store information such as data and/or instructions.
[0021] Entities in a wireless communication system such as a wireless device, ASN and CSN can represent a grouping of functional entities. Such functions can be realized in a single physical functional entity. However, such functions can be distributed over two or more physical functional entities. The grouping and distribution of functions into physical devices within the ASN is an implementation choice. In some implementations, a logical representation of a WiMAX network architecture is based on a Network Reference Model (NRM) that identifies functional entities and reference points over which interoperability is achieved between functional entities. The intent of the NRM is to allow multiple implementation options for a given functional entity, and yet achieve interoperability among different realizations of functional entities. Interoperability is based on the definition of communication protocols and data plane treatment between functional entities to achieve an overall end-to-end function, for example, security or mobility management. A reference point (RP) is a conceptual link that connects two groups of functions that reside in different functional entities of an ASN, CSN, or MS and thus RP is not necessarily a physical interface. A reference point becomes a physical interface when the functional entities on either side of the RP are contained in different physical MSs. The functional entities on either side of RP represent a collection of control and Bearer Plane end-points. In this setting, interoperability will be verified based on protocols exposed across an RP, which may depend on the end-to-end function or capability realized (e.g., based on the usage scenarios supported by the overall network).
[0022] A wireless communication system can provide multiple communication interfaces. For example, a system can include one or more of the following Reference Points.
Reference Point Rl includes the protocols and procedures between MS and ASN as per the air interface (PHY and MAC) specifications (e.g., IEEE P802.16e-2005, IEEE P802.16-2004 and IEEE 802.16g). Reference point Rl can include additional protocols related to the management plane. Reference Point R2 includes protocols and procedures between the MS and CSN associated with Authentication, Services Authorization and IP Host Configuration management. The authentication part of reference point R2 runs between the MS and the CSN operated by the home NSP, however the ASN and CSN operated by the visited NSP may partially process the aforementioned procedures and mechanisms. Reference Point R2 can support IP Host Configuration Management running between the MS and the CSN (operated by either the home NSP or the visited NSP). Reference Point R3 includes the set of Control Plane protocols between the ASN and the CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the Bearer Plane methods (e.g., tunneling) to transfer user data between the ASN and the CSN. Reference Point R4 includes a set of Control and Bearer Plane protocols originating/terminating in various functional entities of an ASN that coordinate MS mobility between ASNs and ASN-GWs. R4 is an interoperable RP between similar or heterogeneous ASNs. Reference Point R5 includes the set of Control Plane and Bearer Plane protocols for internetworking between the CSN operated by the home NSP and that operated by a visited NSP. Reference point R6 includes the set of control and Bearer Plane protocols for communication between the BS and the ASN-GW. The Bearer Plane can include an intra-ASN datapath between the BS and ASN gateway. The Control Plane includes protocols for datapath establishment, modification, and release control in accordance with the MS mobility events. Reference Point R8 can include protocols and primitives.
[0023] A wireless communication system can include multiple systems that are operated by different operators, e.g., a Network Access Provider (NAP), Network Service Provider (NSP), and Femto-NSP. The NAP, NSP and the Femto-NSP can belong to different operators. In some implementations, the NAP, NSP and the Femto-NSP can belong to the same operator. A NAP can run an ASN. A Single NAP can have two or more types of ASNs, e.g., one that does not support WFAPs and one that does support WFAPs, which can be called a Femto-ASN. A NSP can operate a CSN. A CSN can include an authentication, authorization, accounting (AAA) server and a home agent (HA). A Femto-NSP can operate a CSN for Femto-ASN, which can be called a Femto-CSN. A Femto-CSN is a CSN that supports WFAPs. A Femto-CSN can include a AAA server for WFAPs. For example, a WFAP can be configured to have different access privileges than a macro base station in a wireless communication system. A Femto-AAA can store WFAP specific access privileges. [0024] An ASN may communicate with a WFAP over a third party network such as the Internet. Therefore, a wireless communication system can include a security gateway (SGW, Sec-GW, or Se-GW) to provide secure communication between a WFAP and other network entities. In some implementations, a security gateway is a part of the Femto-NSP system component/function and can belong to the same operator as the WFAP, e.g., the SGW belongs to the Femto-NSP.
[0025] This document provides descriptions of a communication pathway for secure communications. The secure communication pathway is described by a Rs reference point. The Rs can be used between a WFAP and a security gateway. A security tunnel such as one based on an Internet Protocol Security (IPsec) protocol can be established in Rs between a WFAP and a security gateway to provide backhaul security. A R3 or R3-F reference point can be used between a security gateway and a AAA server such as a Femto-AAA server. [0026] In some implementations, a security gateway is co-located with a Femto-GW.
In some implementations, a security gateway is a standalone entity. In a standalone configuration, the security gateway can be located differently than the Femto-GW. Therefore, a wireless communication system can provide an interface, e.g., open interface or closed interface, between a security gateway and a Femto-FW. Such an interface can include an
AAA interface based on an AAA protocol such as RADIUS or Diameter. A security gateway can terminate IPsec tunneling for a WFAP. A security gateway can filter out unauthorized traffic on the links between a security gateway and a WFAP. A security gateway can provide access control of WFAP to the Network. A secure communication pathway can provide a pathway for one or more communication pathways such as control plane and bearer plane signaling, e.g., one described by a R6-F reference point, a SON traffic, e.g., one described by a Rson reference point. A security gateway can inspect data packets from a WFAP over R6-F to verify a correct source ID. A security gateway can encrypt the data between a WFAP and a security gateway. The security gateway can provide integrity protection. [0027] A wireless communication system can include a gateway such as a Femto-
GW. A Femto-GW can reside in an ASN that supports femtocells. In some implementations, a Femto-GW is a separate gateway in the NRM for the support of WFAPs. Femto-GW can have the same set of functionalities which are provided by a macro-GW and additional functionalities which are defined for femtocell-specific operation. R4/R4+ reference point is used between the Femto-GWs. A R4 reference point is used between a Femto-GW and an ASN-GW. A R6 or R6-F reference point is used between a WFAP and a Femto-GW. In some implementations, the R6 and R6-F traffic, including control panel and data panel, are transparent from the WFAP to the Femto-GW via a security gateway. In some implementations, a Femto-GW and ASN-GW can be in the same ASN. Some implementations can terminate R6-F starting from the WFAP. In some implementations, a Femto-GW is an ASN-GW with additional functionalities for femtocell access points. [0028] A wireless communication system can include a Femto-AAA. A Femto-AAA, belonging to the Femto-NSP, can reside in a Femto-CSN which is operated by a Femto-NSP. R5 reference point is used between an AAA for access control at a WFAP and an AAA for the wireless device. In some implementations, a Femto-AAA and an AAA server, which is for wireless devices, can be the same device. For example, a femto-AAA can provide authentication and/or authorization of a WFAP. In case the Femto-AAA does not authenticate the WFAP, the security gateway can take the responsibility for the WAFP authentication. [0029] Reference Point Rl can include protocols and procedures between wireless device and ASN per the air interface (e.g., PHY and MAC) specifications (e.g., IEEE P802.16e-2005, IEEE P802.16-2004).
[0030] Reference Point R3 can include Control Plane protocols and Bearer Plane protocols to support AAA and also to transfer of user data between the ASN and the CSN. AAA is responsible for subscriber authentication and charging.
[0031] Reference Point R4 can include Control Plane protocols and Bearer Plane protocols originating/terminating in various functions entities of an ASN that coordinates MS mobility between different ASNs and Femto-GW as well as between Femto-GWs. The Femto-GW can be connected to a macro ASN-GW through R4 if the interoperability with a macro network is required. R4/R4+ reference point is used between the Femto-GWs. A R4 reference point is used between a Femto-GW and an ASN-GW. [0032] Reference Point R6-F can include Control Plane and Bearer Plane for communication between a WFAP and a Femto-GW. Reference Point R6-F can support femtocell specific features and the existing features of R6. In some implementations, control and bearer plane traffic over Reference Point R6-F is sent through an IPsec tunnel between a WFAP and a security gateway.
[0033] Reference Point R3-F can include Control Plane and Management Plane protocols to support the management, authorization and authentication of a WFAP between the WFAP and other entities in a Femto-NSP, such as Femto-AAA and Management system. Additional functions (e.g. SON) can be added in R3-F. In some implementations, communications between the WFAP and the SON are through the Management System. In some implementations, R3-F provides a control panel. In some implementations, R3-F provides a control plane and a management plane. A wireless communication system can include multiple ASN that supports WFAPs. If another ASN also includes a Femto-GW, then this ASN can have a R3-F reference point between itself and a CSN that includes a Femto-
AAA.
[0034] Reference Point Rs can include protocols for establishing IPsec tunnel using
Internet Key Exchange version two (IKEv2) mechanisms between a WFAP and a security gateway. Reference Point Rs can be used to transmit R6-F control and bearer traffic between a WFAP and a Femto-GW.
[0035] Reference Point R5 can be used between the Femto-NSP's CSN, which contains a Femto-AAA, and the CSN. Reference Point R5 can be used for communication between the Femto-AAA and the AAA.
[0036] FIGS. 3, 4, 5, 6, 7, and 8 show different examples of wireless communication system architectures.
[0037] FIG. 3 shows an example of a wireless communication system architecture. A
CSN 305 can include a SON server 310, a management system 315, and a AAA server such as a Femto-AAA server 320. A ASN 330 can include a SON controller 340, and one or more gateways such as a Sec-GW 335 and a Femto-GW 345. The WFAP 355 can communicate with a wireless device such as a mobile station 360. The Femto-GW 345 can communicate with one or more CSNs 305, 365 to provide control and bearer plane signaling to the WFAP
355 via the Sec-GW 335. In some implementations, a Femto-GW 345 communicates with another ASN 370.
[0038] The Sec-GW 335 can provide a secure communication pathway 350 to an access point such as a WFAP 355. The Sec-GW 335 can communicate control and bearer plane message traffic with the WFAP 355 via the secure communication pathway 350. The
Sec-GW 335 can communicate SON message traffic with the WFAP 355 via the secure communication pathway 350. In some implementations, SON message traffic includes one or more wireless communication parameter values, such as a radio frequency assignment, transmission power level, and PHY parameter values. For example, the WFAP 355 can produce a wireless communication signal based on the one or more wireless communication parameter values that are received in a SON message. In some implementations, a WFAP 355 takes measurements of a wireless communication environment and reports the measurements to the SON server 310. Based on the measurements, the SON server 310 can determine how to configure a WFAP for wireless communications as to minimize interface with other communication devices within a wireless communication range of a WFAP. [0039] A SON server 310 can manage wireless communication parameters for multiple access points such as WFAP 355. In some implementations, the SON server 310 sends wireless communication parameter values to the WFAP 355 via the Femto-GW 345. In some implementations, a SON server 310 causes a SON controller 340 to send and receive SON messages to and from a WFAP 355. The WFAP 355 can run a SON client. A SON client can send a SON message to a SON controller 340 via the secure communication pathway 350. In some implementations, the SON controller 340 can terminate a Rson communication with a SON client on a WFAP 355.
[0040] In some implementations, the secure communication pathway 330 is layered on top of a transport and network communication stack such as a TCP/IP stack. In some implementations, communications between the WFAP 355 and the Sec-GW 335 are over an public network. Unauthorized sources may attempt to send traffic to the Femto-GW 345. Therefore, in some implementations, the Sec-GW 335 provides access control for communications with the Femto-GW 345. For example, the Sec-GW 335 can be configured to block unauthorized access points from communicating with the Femto-GW 345. A gateway, such as a Sec-GW 335 or a Femto-GW 345, can include one or more processors. [0041] FIG. 4 shows another example of a wireless communication system architecture. In this example, an ASN 405 includes a SON server 410. The SON server 410 can communicate with a SON agent 420 that resides in a CSN 415. The SON server 410 can communicate with a SON client on an access via a Sec-GW 425. [0042] FIG. 5 shows another example of a wireless communication system architecture. In this example, an ASN 505 includes a Femto-GW 510 that is configured to provide connectivity with a SON server 520 in a CSN 515. SON message flows between the SON server 520 to a SON client, such as one that resides on a WFAP, via the Femto-GW 510 and a Sec-GW 525. The Sec-GW 525 can terminate a Rson communication. The Sec-GW 525 can forward R6-F communication from a Femto-GW 510 to a WFAP. [0043] FIG. 6 shows another example of a wireless communication system architecture. A CSN 605 can include a SON server 610, a management system 615, and a AAA server such as a Femto-AAA server 620. An ASN 630 can include a SON controller 640, and one or more gateways such as a Sec-GW 635 and a Femto-GW 645. The WFAP 655 can communicate with one or more wireless devices. The Femto-GW 645 can communicate with one or more CSNs 605 to provide control and bearer plane signaling to the WFAP 655 via the Sec-GW 635. The Femto-GW 645 can communicate with one or more CSNs 605 to provide control and bearer plane signaling to a macro base station 670. The macro base station 670 provides coverage in a larger area than the WFAP 655. In some cases, the wireless communication system can handoff a wireless device between the WFAP 655 and the macro base station 670.
[0044] The WFAP 655 can communicate with the Sec-GW 635 via a third party network such as an un-trusted network. The Sec-GW 635 can provide a secure communication pathway 650 between the Sec-GW 635 and the WFAP 655. The Sec-GW 635 can communicate SON message traffic with the WFAP 655 via the secure communication pathway 650. The WFAP 655 can run a SON client configured to perform SON operations such as auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration based on communication with the SON server 610 via a SON controller 640. [0045] FIG. 7 shows another example of a wireless communication system architecture. In this example, an ASN 705 includes a SON server 710. The SON server 710 can communicate with a SON agent 720 that resides in a CSN 715. The SON server 710 can communicate with a SON client on an access point via a Sec-GW 725. The SON server 710 can communicate with the SON agent 720 via a Femto-GW 730. The Femto-GW 730 can provide communication services for two or more types of base stations, e.g., macro base stations and WFAPs.
[0046] FIG. 8 shows another example of a wireless communication system architecture. In this example, an ASN 805 includes a Femto-GW 810 that is configured to provide connectivity with a SON server 820 in a CSN 815. SON message flows between the SON server 820 to a SON client, such as one that resides on a WFAP, via the Femto-GW 810 and a Sec-GW 825. The Femto-GW 810 can provide communication services for two or more types of base stations, e.g., macro base stations and WFAPs. [0047] FIG. 9 shows an example of a communication process. At 905, a communication process can include causing an access point to provide wireless service to wireless devices. For example, the process can send a command to control the access point to start providing wireless service. At 910, the process can include operating a first gateway to provide control plane and bearer plane signaling associated with the wireless devices to interconnect to an external network, e.g., a CSN, via the first gateway. At 915, the process can include operating a second gateway to control an interconnection privilege of the access point with the first gateway. For example, the second gateway can determine whether a specific access point is allowed to communicate with the first gateway. At 920, the process can include operating the second gateway to provide a secure communication pathway between the access point and the second gateway to carry information such as control plane and bearer plane signaling and SON message traffic. In some implementations, the process perform encryption and decryption for message traffic in a secure communication pathway. [0048] In some implementations, the process includes operating the second gateway to prevent unauthorized traffic from being sent to the first gateway. In some implementations, the process includes operating the second gateway to inspect data packets from the access point to verify a source identifier. In some implementations, the process includes operating the second gateway to encrypt access point traffic received from the first gateway prior to forwarding the access point traffic to the access point. In some implementations, the process includes operating the second gateway to decrypt traffic received from the access point prior to forwarding the decrypted traffic to the first gateway. In some implementations, the process communicates with a gateway such as a combined Femto-GW and Sec-GW gateway. [0049] The disclosed and other embodiments and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term "data processing apparatus" encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine- generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus. [0050] A computer program (also known as a program, software, software application, script, or code) 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 standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
[0051] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
[0052] 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 performing 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. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non volatile memory, media and memory devices, 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. [0053] While this document contains many specifics, these should not be construed as limitations on the scope of an invention that is claimed or of what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. [0054] Only a few examples and implementations are disclosed. Variations, modifications, and enhancements to the described examples and implementations and other implementations can be made based on what is disclosed.

Claims

CLAIMSWhat is claimed is:
1. A system for wireless communication, comprising: an access point to provide wireless service to one or more wireless devices; a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices and to provide communications with an external network via the first gateway; and a second gateway to control an interconnection privilege of the access point with the first gateway and provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry self-organizing network (SON) message traffic associated with the access point, wherein the SON message traffic includes one or more wireless communication parameter values.
2. The system of claim 1 , wherein the SON message traffic includes message traffic associated with one or more of: auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration.
3. The system of claim 1, comprising: a SON server to manage and to assemble wireless communication parameters for multiple access points, wherein the SON server sends the one or more wireless communication parameter values to the access point via the second gateway.
4. The system of claim 2, wherein the access point communicates with the SON server via the secure communication pathway.
5. The system of claim 1 , wherein the second gateway communicates with the access point over a third party wired or wireless broadband infrastructure.
6. The system of claim 1 , wherein the second gateway is configured to prevent unauthorized traffic from being sent to the first gateway.
7. The system of claim 1 , wherein the second gateway is configured to inspect data packets from the access point to verify a source identifier.
8. The system of claim 1, wherein the second gateway encrypts access point traffic received from the first gateway prior to forwarding the access point traffic to the access point.
9. The system of claim 1 , wherein the second gateway decrypts traffic received from the access point prior to forwarding the decrypted traffic to the first gateway.
10. The system of claim 1, wherein the first gateway communicates with a server system in a connectivity service network (CSN), wherein the server system provides authentication, authorization, accounting services for wireless devices, wherein the server system provides a pathway to a network.
11. The system of claim 1 , wherein the access point is a femtocell access point, wherein the second gateway provides authentication, authorization, accounting services that are specific to the femtocell access point.
12. The system of claim 1 , wherein the access point communicates with the one or more wireless devices based on a Worldwide Interoperability for Microwave Access (WiMAX) technology.
13. The system of claim 1, wherein the access point is a femtocell access point.
14. The system of claim 13, further comprising: a base station to provide wireless service to wireless devices in a geographical wireless service area that is larger than a geographical wireless area associated with the femtocell access point, wherein the first gateway provides control and bearer plane message traffic for the femtocell access point and the base station.
15. The system of claim 1 , further comprising: a gateway that comprises the first gateway and the second gateway.
16. A method for wireless communications, comprising: causing an access point to provide wireless service to one or more wireless devices; operating a first gateway to provide control plane and bearer plane signaling associated with the one or more wireless devices to interconnect to an external network via the first gateway; operating a second gateway to control an interconnection privilege of the access point with the first gateway; and operating the second gateway to provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry self-organizing network (SON) message traffic associated with the access point, wherein the SON message traffic includes one or more wireless communication parameter values.
17. The method of claim 16, wherein the SON message traffic includes message traffic associated with one or more of: auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration.
18. The method of claim 16 , comprising : communicating with a SON server that manages and assembles wireless communication parameters for multiple access points, wherein the SON server sends the one or more wireless communication parameter values to the access point via the second gateway.
19. The method of claim 16, wherein the second gateway communicates with the access point over a third party wired or wireless broadband infrastructure.
20. The method of claim 16, comprising: operating the second gateway to prevent unauthorized traffic from being sent to the first gateway.
21. The method of claim 16 , comprising : operating the second gateway to inspect data packets from the access point to verify a source identifier.
22. The method of claim 16, comprising: operating the second gateway to encrypt access point traffic received from the first gateway prior to forwarding the access point traffic to the access point.
23. The method of claim 16, comprising: operating the second gateway to decrypt traffic received from the access point prior to forwarding the decrypted traffic to the first gateway.
24. The method of claim 16, comprising: operating the first gateway to communicate with a server system in a connectivity service network (CSN), wherein the server system provides authentication, authorization, accounting services for wireless devices, wherein the server system provides a pathway to a network.
25. The method of claim 16, wherein the access point is a femtocell access point, the method comprising: operating the second gateway to provide authentication, authorization, accounting services that are specific to the femtocell access point.
26. The method of claim 16, wherein the access point communicates with the one or more wireless devices based on a Worldwide Interoperability for Microwave Access (WiMAX) technology.
27. The method of claim 16, wherein the access point is a femtocell access point.
28. The method of claim 27, further comprising: operating a base station to provide wireless service to wireless devices in a geographical wireless service area that is larger than a geographical wireless area associated with the femtocell access point, wherein operating the first gateway comprises operating the first gateway to provide control and bearer plane message traffic for the femtocell access point and the base station.
29. A system for wireless communication, comprising: a first gateway to (1) communicate with an access point to provide wireless service to one or more wireless devices and (2) provide control plane and bearer plane signaling associated with the one or more wireless devices, and (3) provide communications with an external network via the first gateway; and a second gateway to (1) control an interconnection privilege of the access point with the first gateway and (2) provide a secure communication pathway between the access point and the second gateway to carry the control plane and bearer plane signaling associated with the access point and to carry self-organizing network (SON) message traffic associated with the access point, wherein the SON message traffic includes one or more wireless communication parameter values.
30. The system of claim 29, wherein the SON message traffic includes message traffic associated with one or more of: auto-configuration, auto-provisioning, self-healing, or auto-reconfiguration.
31. The system of claim 29, comprising: a SON server to manage and to assemble wireless communication parameters for multiple access points, wherein the SON server sends the one or more wireless communication parameter values to the access point via the second gateway.
2. The system of claim 31 , wherein the access point communicates with the SON server via the secure communication pathway.
PCT/US2010/034991 2009-05-14 2010-05-14 Femtocell self organization in wimax communications WO2010132826A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17848109P 2009-05-14 2009-05-14
US61/178,481 2009-05-14

Publications (2)

Publication Number Publication Date
WO2010132826A2 true WO2010132826A2 (en) 2010-11-18
WO2010132826A3 WO2010132826A3 (en) 2011-01-20

Family

ID=43085610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/034991 WO2010132826A2 (en) 2009-05-14 2010-05-14 Femtocell self organization in wimax communications

Country Status (2)

Country Link
TW (1) TW201134283A (en)
WO (1) WO2010132826A2 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220725A (en) * 2012-01-19 2013-07-24 中兴通讯股份有限公司 Coordination method and system of self-organizing network function
WO2015183618A1 (en) * 2014-05-29 2015-12-03 T-Mobile Usa, Inc. Self-organizing wireless backhaul among cellular access points
US9832797B2 (en) 2015-06-29 2017-11-28 At&T Intellectual Property I, L.P. Mobility network function consolidation
US10305959B2 (en) 2014-12-11 2019-05-28 At&T Intellectual Property I, L.P. Self-organizing network communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080132239A1 (en) * 2006-10-31 2008-06-05 Amit Khetawat Method and apparatus to enable hand-in for femtocells
EP1983771A1 (en) * 2007-04-17 2008-10-22 Alcatel Lucent A method for interfacing a Femto-Cell equipment with a mobile core network
US20090094683A1 (en) * 2007-10-04 2009-04-09 Morgan Todd C Method for authenticating mobile units attached to a femtocell that operates according to code division multiple access

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080132239A1 (en) * 2006-10-31 2008-06-05 Amit Khetawat Method and apparatus to enable hand-in for femtocells
EP1983771A1 (en) * 2007-04-17 2008-10-22 Alcatel Lucent A method for interfacing a Femto-Cell equipment with a mobile core network
US20090094683A1 (en) * 2007-10-04 2009-04-09 Morgan Todd C Method for authenticating mobile units attached to a femtocell that operates according to code division multiple access

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220725A (en) * 2012-01-19 2013-07-24 中兴通讯股份有限公司 Coordination method and system of self-organizing network function
CN103220725B (en) * 2012-01-19 2018-02-16 中兴通讯股份有限公司 A kind of coordination approach and system of self-organizing network function
WO2015183618A1 (en) * 2014-05-29 2015-12-03 T-Mobile Usa, Inc. Self-organizing wireless backhaul among cellular access points
US9591491B2 (en) 2014-05-29 2017-03-07 T-Mobile Usa, Inc. Self-organizing wireless backhaul among cellular access points
US10244404B2 (en) 2014-05-29 2019-03-26 T-Mobile Usa, Inc. Self-organizing wireless backhaul among cellular access points
US10305959B2 (en) 2014-12-11 2019-05-28 At&T Intellectual Property I, L.P. Self-organizing network communication
US10764349B2 (en) 2014-12-11 2020-09-01 At&T Intellectual Property I, L.P. Self-organizing network communication
US9832797B2 (en) 2015-06-29 2017-11-28 At&T Intellectual Property I, L.P. Mobility network function consolidation

Also Published As

Publication number Publication date
WO2010132826A3 (en) 2011-01-20
TW201134283A (en) 2011-10-01

Similar Documents

Publication Publication Date Title
CN109417709B (en) Method and system for authenticating access in a mobile wireless network system
CN110291803B (en) Privacy protection and extensible authentication protocol authentication and authorization in cellular networks
CN111726804B (en) Unified authentication for integrating small cells and Wi-Fi networks
JP6174617B2 (en) Certificate validation and channel binding
EP2583479B1 (en) Method and apparatus for binding subscriber authentication and device authentication in communication systems
AU2011207450B2 (en) Method and apparatus for securing wireless relay nodes
CN101291464B (en) A method for interfacing a Femto-cell equipment with a mobile core network
EP2845362B1 (en) Secure communications for computing devices utilizing proximity services
CN104854892B (en) Method and apparatus for deriving wlan security context from WWAN security context
ES2894476T3 (en) Techniques for deriving security keys for a cellular network based on performing an Extensible Authentication Protocol (EAP) procedure
JP2019512942A (en) Authentication mechanism for 5G technology
KR20170032305A (en) Associating a device with another device's network subscription
TW201720216A (en) Methods and apparatus for wireless communication using a security model to support multiple connectivity and service contexts
US11523277B2 (en) Method of dynamically provisioning a key for authentication in relay device
CN112887970A (en) Machine-to-machine cellular communication security
KR102205625B1 (en) Security of ciphering and integrity protection
CN101977378B (en) Information transferring method, network side and via node
Fang et al. Security requirement and standards for 4G and 5G wireless systems
WO2010132826A2 (en) Femtocell self organization in wimax communications
CN106797560B (en) Method, server, base station and communication system for configuring security parameters
Namal et al. Secure and multihomed vehicular femtocells
US20240146702A1 (en) Traffic management with asymmetric traffic encryption in 5g networks
CN102625308A (en) Method, apparatus and system for realization of mutual authentication based on LTE-LAN
Santorinaios Privacy Evaluation of 5G Networks
Ergen WiMAX Network Layer

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10775631

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10775631

Country of ref document: EP

Kind code of ref document: A2