U.S. patent application number 12/252222 was filed with the patent office on 2009-05-21 for system, method, and computer-readable medium for access restriction of user equipment devices in an ip-femtocell system.
This patent application is currently assigned to AirWalk Communications, Inc.. Invention is credited to Christopher Martin Edward Osborn.
Application Number | 20090131017 12/252222 |
Document ID | / |
Family ID | 40639066 |
Filed Date | 2009-05-21 |
United States Patent
Application |
20090131017 |
Kind Code |
A1 |
Osborn; Christopher Martin
Edward |
May 21, 2009 |
SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR ACCESS RESTRICTION
OF USER EQUIPMENT DEVICES IN AN IP-FEMTOCELL SYSTEM
Abstract
A system, method, and computer readable medium for screening
services in a network system is provided. A list of electronic
serial numbers of handsets in a user subscription may be compiled
by a base station manager and transmitted to a femtocell system in
a configuration download. The femtocell system may then screen
electronic serial numbers of user equipments that attempt to
register with the femtocell system. In an embodiment, the femtocell
system may allow calls to be placed through the femtocell system on
an emergency basis regardless of whether the user equipment has an
electronic serial number that is authorized for access by the
femtocell system. In non-emergency scenarios, only user equipments
having an electronic serial number that matches an electronic
serial number in the femtocell system's electronic serial number
list are allowed to place calls or register with the femtocell
system.
Inventors: |
Osborn; Christopher Martin
Edward; (Allen, TX) |
Correspondence
Address: |
RG & ASSOCIATES
1103 TWIN CREEKS, STE. 120
ALLEN
TX
75013
US
|
Assignee: |
AirWalk Communications,
Inc.
Richardson
TX
|
Family ID: |
40639066 |
Appl. No.: |
12/252222 |
Filed: |
October 15, 2008 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61003151 |
Nov 15, 2007 |
|
|
|
Current U.S.
Class: |
455/411 ;
370/389 |
Current CPC
Class: |
H04M 7/009 20130101;
H04W 72/0406 20130101; H04W 4/14 20130101; H04W 72/0426 20130101;
H04M 3/42314 20130101; H04W 36/30 20130101; H04W 40/20 20130101;
H04L 65/1073 20130101; H04L 65/1016 20130101; H04W 76/12 20180201;
H04W 36/00 20130101; H04W 36/08 20130101; H04W 40/02 20130101; H04L
5/0055 20130101; H04L 65/103 20130101; H04W 88/085 20130101; H04L
65/1006 20130101; H04L 63/12 20130101; H04L 65/1069 20130101; H04L
63/08 20130101; H04W 76/10 20180201; H04L 65/104 20130101; H04M
3/44 20130101; H04W 36/0058 20180801; H04L 61/3085 20130101; H04W
36/0085 20180801; H04W 24/10 20130101; H04W 36/0088 20130101; H04W
84/045 20130101; H04W 12/06 20130101; H04W 36/0083 20130101; Y02D
30/70 20200801 |
Class at
Publication: |
455/411 ;
370/389 |
International
Class: |
H04M 1/66 20060101
H04M001/66; H04L 12/56 20060101 H04L012/56 |
Claims
1. A method of service screening in a network system, comprising:
provisioning a femtocell system with a list of at least one
electronic serial number of at least one user equipment authorized
to access the femtocell system; receiving, by the femtocell system,
a service request from a user equipment; determining an electronic
serial number of the user equipment; and comparing the electronic
serial number with the list of at least one electronic serial
number.
2. The method of claim 1, where receiving a service request
comprises receiving a call setup request.
3. The method of claim 1, where receiving a service request
comprises receiving a registration request.
4. The method of claim 1, where comparing the electronic serial
number further comprises determining the electronic serial number
does not match any of the at least one electronic serial number,
the method further comprising rejecting the service request.
5. The method of claim 1, where comparing the electronic serial
number further comprises determining the electronic serial number
matches one of the at least one electronic serial number, the
method further comprising completing the service request.
6. The method of claim 1, further comprising: determining the
service request is an emergency service request; and completing the
service request.
7. The method of claim 1, where provisioning the femtocell system
further comprises receiving the list from a base station manager as
a configuration download.
8. The method of claim 1, where the list of at least one electronic
serial number comprises a list of electronic serial numbers of user
equipments registered on a customer account associated with the
femtocell system.
9. A computer-readable medium having computer-executable
instructions for execution by a processing system, the
computer-executable instructions for service screening in a network
system, the computer-readable medium comprising instructions for:
receiving, by a femtocell system, a list of at least one electronic
serial number from a base station manager as a configuration
download, wherein the at least one electric serial number is an
electronic serial number of a user equipment authorized to access
the femtocell system; provisioning the femtocell system with the
list; receiving, by the femtocell system, a service request from a
user equipment; determining an electronic serial number of the user
equipment; and comparing the electronic serial number with the list
of at least one electronic serial number.
10. The computer-readable medium of claim 9, wherein the
instructions for receiving a service request comprise instructions
for receiving a call setup request.
11. The computer-readable medium of claim 9, wherein the
instructions for receiving a service request comprise instructions
for receiving a registration request.
12. The computer-readable medium of claim 9, wherein the
instructions for comparing the electronic serial number further
comprise instructions for determining the electronic serial number
does not match any of the at least one electronic serial number,
the computer-readable medium further comprising instructions for
rejecting the service request.
13. The computer-readable medium of claim 9, wherein the
instructions for comparing the electronic serial number further
comprise instructions for determining the electronic serial number
matches one of the at least one electronic serial number, the
computer-readable medium further comprising instructions for
completing the service request.
14. The computer-readable medium of claim 9, further comprising
instructions for: determining the service request is an emergency
service request; and completing the service request.
15. The computer-readable medium of claim 9, wherein the list of at
least one electronic serial number comprises a list of electronic
serial numbers of user equipments registered on a customer account
associated with the femtocell system.
16. A system configured for service screening in a network system,
comprising: a packet-switched network including a base station
manager server; and a femtocell system communicatively coupled with
the packet-switched network adapted to provide a radio interface
with a user equipment, wherein the femtocell system receives a
configuration download from the base station manager that includes
a list of at least one electronic serial number of at least one
user equipment registered on a customer account associated with the
femtocell system, wherein the femtocell system receives a service
request from a user equipment, determines an electronic serial
number of the user equipment, and compares the electronic serial
number with the list of at least one electronic serial number.
17. The system of claim 16, wherein the service request comprises a
call setup request.
18. The system of claim 16, wherein the service request comprises a
registration request.
19. The system of claim 16, wherein the femtocell system determines
the electronic serial number does not match any of the at least one
electronic serial number and rejects the service request.
20. The system of claim 16, wherein the femtocell system determines
the electronic serial number matches one of the at least one
electronic serial number and completes the service request.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. provisional patent
application Ser. No. 60/936,626 entitled FEMTOCELL filed Jun. 21,
2007, and claims priority to U.S. provisional patent application
Ser. No. 61/003,151 entitled SIP-IOS ADAPTER FUNCTION filed Nov.
15, 2007, the disclosure of each of which is incorporated in its
entirety herein by reference.
FIELD OF THE INVENTION
[0002] The present invention is generally related to radio access
technologies and, more particularly, to mechanisms for access
restriction of user equipment devices to a femtocell system or
network.
BACKGROUND OF THE INVENTION
[0003] Contemporary cellular radio systems, or mobile
telecommunication systems, provide an over-the-air interface to
wireless user equipments (UEs) via a radio access network (RAN)
that interfaces with at least one core network. The RAN may be
implemented as, for example, a CDMA2000 RAN, a Universal Mobile
Telecommunications System (UMTS) RAN, a Global System for Mobile
communications (GSM) RAN, or another suitable radio access network
implementation. A UE may comprise, for example, a mobile terminal
such as a mobile telephone, a laptop computer featuring mobile
telephony software and hardware, a personal digital assistant
(PDA), or other suitable equipment adapted to transfer and receive
voice or data communications with the radio access network.
[0004] A RAN covers a geographical area comprised of any number of
cells each comprising a relatively small geographic area of radio
coverage. Each cell is provisioned by a cell site that includes a
radio tower, e.g., a base transceiver station (BTS), and associated
equipment. BTSs communicate with UEs over an air interface within
radio range of the BTSs.
[0005] Numerous BTSs in the RAN may be communicatively coupled to a
base station controller, also commonly referred to as a radio
network controller (RNC). The BSC manages and monitors various
system activities of the BTSs serviced thereby. BSCs are coupled
with at least one core network.
[0006] BTSs are typically deployed by a carrier network in areas
having a high population density. The traffic capacity of a cell
site is limited by the site's capacity and affects the spacing of
cell sites. In suburban areas, sites are often up to two miles
apart, while cell sites deployed in dense urban areas may be as
close as one-quarter of a mile apart. Because the traffic capacity
of a cell site is finitely limited, as is the available frequency
spectrum, mobile operators have a vested interest in technologies
that allow for increased subscriber capacity.
[0007] A microcell site comprises a cell in a mobile phone network
that covers a limited geographic area, such as a shopping center,
hotel, airport, or other infrastructure that may have a high
density mobile phone usage. A microcell typically uses power
control to limit the radius of the microcell coverage. Typically a
microcell is less than a mile wide.
[0008] Although microcells are effective for adding network
capacity in areas with high mobile telephone usage, microcells
extensively rely on the RAN, e.g., a controlling BSC and other
carrier functions. Because contemporary BSCs have limited
processing and interface capacity, the number of BTSs--whether
microcell BTSs or typical carrier BTSs--able to be supported by the
BSC or other RAN functions is disadvantageously limited.
[0009] Contemporary interest exists in providing enterprise and
office access, including small office/home office (SOHO) radio
access, by an even smaller scale BTS. The radio coverage area of
such a system is typically referred to as a femtocell. In a system
featuring a femtocell, a UE may be authorized to operate in the
femtocell when proximate the femtocell system, e.g., while the UE
is located in the SOHO. When the UE moves beyond the coverage area
of the femtocell, the UE may then be serviced by the carrier
network. The advantages of deployment of femtocells are numerous.
For instance, mobile users frequently spend large amounts of time
located at, for example, home, and many such users rely extensively
on cellular network service for telecommunication services during
these times. For example, a recent survey indicated that nearly
thirteen percent of U.S. cell phone customers do not have a
landline telephone and rely solely on cell phones for receiving
telephone service. From a carrier perspective, it would be
advantageous to have telephone services provisioned over a
femtocell system, e.g., deployed in the user's home, to thereby
reduce the load, and effectively increase the capacity, on the
carrier RAN infrastructure. However, various issues related to
restricting femtocell access to authorized user equipment devices
remain unresolved.
[0010] Therefore, what is needed is a mechanism that overcomes the
described problems and limitations.
SUMMARY OF THE INVENTION
[0011] The present invention provides a system, method, and
computer readable medium for screening services in a network
system. A communication system features an IP-based femtocell
system for provisioning communication services to a user equipment.
A list of electronic serial numbers of handsets in a user
subscription may be compiled by a base station manager. The
femtocell system may connect with the base station manager and
request a configuration download once deployed in a SOHO. The
compiled electronic serial numbers may then be transferred from the
base station manager to the femtocell system in a configuration
download. The femtocell system may then screen electronic serial
numbers of user equipments that attempt to register with the
femtocell system. In an embodiment, the femtocell system may allow
calls to be placed through the femtocell system on an emergency
basis regardless of whether the user equipment has an electronic
serial number that is authorized for access by the femtocell
system. In non-emergency scenarios, only user equipments having an
electronic serial number that matches an electronic serial number
in the femtocell system's electronic serial number list are allowed
to place calls or register with the femtocell system.
[0012] In one embodiment of the disclosure, a method of service
screening in a network system is provided. The method includes
provisioning a femtocell system with a list of at least one
electronic serial number of at least one user equipment authorized
to access the femtocell system, receiving, by the femtocell system,
a service request from a user equipment, determining an electronic
serial number of the user equipment, and comparing the electronic
serial number with the list of at least one electronic serial
number.
[0013] In a further embodiment of the disclosure, a
computer-readable medium having computer-executable instructions
for execution by a processing system, the computer-executable
instructions for service screening in a network system is provided.
The computer-readable medium comprises instructions for receiving,
by a femtocell system, a list of at least one electronic serial
number from a base station manager as a configuration download,
where the at least one electric serial number is an electronic
serial number of a user equipment authorized to access the
femtocell system, provisioning the femtocell system with the list,
receiving, by the femtocell system, a service request from a user
equipment, determining an electronic serial number of the user
equipment, and comparing the electronic serial number with the list
of at least one electronic serial number.
[0014] In a further embodiment of the disclosure, a system
configured for service screening in a network system is provided.
The system includes a packet-switched network including a base
station manager server, and a femtocell system communicatively
coupled with the packet-switched network adapted to provide a radio
interface with a user equipment. The femtocell system receives a
configuration download from the base station manager that includes
a list of at least one electronic serial number of at least one
user equipment registered on a customer account associated with the
femtocell system. The femtocell system receives a service request
from a user equipment, determines an electronic serial number of
the user equipment, and compares the electronic serial number with
the list of at least one electronic serial number.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Aspects of the present disclosure are best understood from
the following detailed description when read with the accompanying
figures, in which:
[0016] FIG. 1 is a diagrammatic representation of a network system
that includes a cellular network adapted to provide macro-cellular
coverage;
[0017] FIG. 2 is a diagrammatic representation of a conventional
network system configuration featuring a femtocell;
[0018] FIG. 3 is a diagrammatic representation of a network system
in which a femtocell system implemented in accordance with an
embodiment of the present invention may be deployed;
[0019] FIG. 4A is a simplified diagrammatic representation of the
femtocell system depicted in FIG. 3 that may be connected with an
IP backhaul in accordance with an embodiment;
[0020] FIG. 4B is a simplified diagrammatic representation of an
alternative embodiment of a femtocell system that may be connected
with an IP backhaul;
[0021] FIG. 5 is a diagrammatic representation of an exemplary
session initiation protocol registration message generated by a
femtocell system on behalf of a user equipment in accordance with
an embodiment;
[0022] FIG. 6 is a diagrammatic representation of a network system
featuring a femtocell network implemented in accordance with an
embodiment;
[0023] FIG. 7 is a diagrammatic representation of an exemplary
software configuration of a user equipment adapted for engaging in
communications with femtocell systems in accordance with an
embodiment;
[0024] FIG. 8 depicts a flowchart of a femtocell system
configuration provisioning routine implemented in accordance with
an embodiment;
[0025] FIG. 9 is a configuration routine that facilitates
generation of femtocell system configuration data implemented in
accordance with an embodiment;
[0026] FIG. 10 is a flowchart that depicts processing of a call
screening routine implemented in accordance with an embodiment;
and
[0027] FIG. 11 is a flowchart that depicts processing of a user
equipment registration screening routine implemented in accordance
with an embodiment.
DETAILED DESCRIPTION OF THE INVENTION
[0028] It is to be understood that the following disclosure
provides many different embodiments or examples for implementing
different features of various embodiments. Specific examples of
components and arrangements are described below to simplify the
present disclosure. These are, of course, merely examples and are
not intended to be limiting.
[0029] FIG. 1 is a diagrammatic representation of a network system
100 that includes a cellular network 110 adapted to provide
macro-cellular coverage to a user equipment. Cellular network 110
may comprise, for example, a code-division multiple access (CDMA)
network, such as a CDMA-2000 network.
[0030] Cellular network 110 may include any number of base
transceiver stations (BTSs) 112a-112c communicatively coupled with
a base station controller (BSC) 114 or RNC. Each individual BTS
112a-112c under the control of a given BSC may define a radio cell
operating on a set of radio channels thereby providing service to a
user equipment (UE) 125, such as a mobile terminal. BSC 114 manages
the allocation of radio channels, receives measurements from mobile
terminals, controls handovers, as well as various other functions
as is understood. BSC 114 is interconnected with a mobile services
switching center (MSC) 116 that provides mobile terminal exchange
services. BSC 114 may be additionally coupled with a packet data
serving node (PDSN) 118 or other gateway service that provides a
connection point between the CDMA radio access network and a packet
network, such as Internet 160, and provides mobility management
functions and packet routing services. MSC 116 may communicatively
interface with a circuit switched network, such as the public
switched telephone network (PSTN) 150, and may additionally be
communicatively coupled with an interworking function (IWF) 122
that provides an interface between cellular network 110 and PSTN
150.
[0031] System 100 may also include a signaling system, such as a
signaling system #7 (SS7) network 170. SS7 network 170 provides a
set of telephony signaling protocols which are used to set up the
vast majority of the world's PSTN telephone calls. SS7 network 170
is also used in cellular networks for circuit switched voice and
packet-switched data applications. As is understood, SS7 network
170 includes various signaling nodes, such as any number of service
control points (SCPs) 172, signal transfer points (STPs) 174, and
service switching points (SSPs) 176.
[0032] BTSs 112a-112c deployed in cellular network 110 may service
numerous network 110 subscribers. Cell cites provided by BTSs
112a-112c commonly feature site ranges of a quarter to a half mile,
e.g., in densely populated urban areas, to one to two miles in
suburban areas. In other remotely populated regions with suitable
geography, site ranges may span tens of miles and may be
effectively limited in size by the limited transmission distance of
relatively low-powered UEs. As referred to herein, a cell provided
by a BTS deployed in carrier network 110 for access by any
authorized network 110 subscriber is referred to as a
macrocell.
[0033] FIG. 2 is a diagrammatic representation of a conventional
network system 200 configuration featuring a femtocell. In the
depicted example, a central BSC 214 deployed in a cellular carrier
network 210 may connect with a soft switch core 212 that is
connected with a MSC 216. MSC 216 connects with the cellular core
network and may interface with other networks, such as the PSTN as
is understood. BSC 214 may be connected with and service numerous
BTSs 212a-212c that provide macrocells to cellular network 210
subscribers.
[0034] BSC 214 may additionally connect with a tunnel gateway
system 218 that is adapted to establish secured tunnels 232a-232x
with respective femtocell systems 250a-250x. Femtocells comprise
cellular access points that connect to a mobile operator's network
using, for example, a residential DSL or cable broadband
connection. Femtocells 250a-250x provide a radio access point for
UE 225 when the UE is within range of a femtocell system with which
the UE has authorized access. For example, femtocell system 250a
may be deployed in a residence of the user of UE 225. Accordingly,
when the user is within the residence, mobile telecommunications
may be provided to UE 225 via an air-interface provided by
femtocell system 250a. In this instance, UE 225 is effectively
offloaded from the macro BTS, e.g., BTS 212a, and communications to
and from the UE are carried out with femtocell system 250a over
Internet 260. Thus, femtocell systems 250a-250x may reduce the
radio resource demands by offloading UEs from macrocells to
femtocells and thereby provide for increased subscriber capacity of
cellular network 210.
[0035] In contemporary implementations such as that depicted in
FIG. 2, a femtocell system 250a comprises a transceiver without
intelligence and is thus required to be connected and managed by
BSC 214. Thus, femtocell systems 250a-250x are reliant on the
carrier network centralized BSC 214 which has limited capacity and
thus does not exhibit desirable scaling characteristics or
capabilities. Moreover, high communications overhead are realized
by the BTS backhaul.
[0036] FIG. 3 is a diagrammatic representation of a network system
300 in which a femtocell system implemented in accordance with an
embodiment of the invention may be deployed. System 300 includes a
radio access network (RAN) 310 that provides an over-the-air
interface with a UE 325, e.g., a mobile terminal. RAN 310 may
comprise, for example, a CDMA radio access network or another
suitable RAN. RAN 310 may comprise various BTSs and associated base
station controllers BSCs as well as other infrastructure as is
understood. UE 325 may be implemented as a personal digital
assistant (PDA), a mobile phone, a computer, or another device
adapted to interface with RAN 310.
[0037] System 300 may include an IP Multimedia Subsystem (IMS) 320
architecture adapted to provide IP service to UE 325. To this end,
RAN 310 is communicatively coupled with a serving general packet
radio service (GPRS) support node (SGSN) 314 and a gateway GPRS
support node (GGSN) 316. SGSN 314 provides the delivery of data
packets from and to UE 325 within its service area. GGSN 316
provides an interface between the GPRS backbone network and
external packet data networks. GGSN 316 is communicatively coupled
with a policy decision function (PDF) 318 that provides
authorization of media plane resources, e.g., quality of service
(QoS) authorizations, policy control, bandwidth management, and the
like. PDF 318 may be communicatively coupled with a call session
control function (CSCF) 320.
[0038] CSCF 320 comprises various session initiation protocol (SIP)
servers or proxies that process SIP signaling packets in IMS 320.
CSCF 320 may include a proxy-CSCF (P-CSCF) that provides a first
point of contact for an IMS-compliant UE. The P-CSCF may be located
in the visited network, or in the UE's home network if the visited
network is not fully IMS-compliant. UE 325 may discover the P-CSCF,
e.g., by using Dynamic Host Configuration Protocol (DHCP), or by
assignment in a packet data protocol (PDP) context. CSCF 320
additionally includes a Serving-CSCF (S-CSCF) that comprises the
central node of the signaling plane. The S-CSCF comprises a SIP
server, but additionally performs session control. The S-CSCF is
located in the home network and interfaces with a home subscriber
server (HSS) 340 to download and upload user profiles. CSCF 320
further includes an Interrogating-CSCF (I-CSCF) that comprises a
SIP function located at the edge of an administrative domain. The
I-CSCF has an IP address that is published in the Domain Name
System (DNS) 372 that facilitates location of the I-CSCF by remote
servers. Thus, the I-CSCF is used as a forwarding point for receipt
of SIP packets within the domain.
[0039] HSS 340 comprises a user database that supports the IMS
network entities that manage calls. HSS 340 stores user profiles
that specify subscription-related information of authorized users,
authenticates and authorizes users, and provides information about
the user's physical location. Various application servers (AS)
342a-342n that host and execute services interface with CSCF 320
via SIP.
[0040] CSCF 320 is coupled with a breakout gateway control function
(BGCF) 322 that comprises a SIP server that provides routing
functionality based on telephone numbers. BGCF 322 is used when a
UE places a call from the IMS to a phone in a circuit switched
network, e.g., PSTN 330, or the public land mobile network. A media
gateway controller Function (MGCF) 324 performs call control
protocol conversion between SIP and ISDN User Part (ISUP) and
interfaces with a signaling gateway (SGW) 326. SGW 326 interfaces
with the signaling plane of a circuit switched network, e.g., PSTN
330. SGW 326 may transform lower layer protocols, such as Stream
Control Transmission Protocol (SCTP), into the Message Transfer
Part (MTP) protocol, and pass ISUP data from MGCF 324 to PSTN 330
or another circuit switched network. A media gateway (MGW) 328
interfaces with the media plane of PSTN 330 or another circuit
switched network by converting data between real-time transport
protocol (RTP) and pulse code modulation (PCM), and may also be
employed for transcoding when the codecs of the IMS and circuit
switched networks differ. Resources of MGW 328 are controlled by
MGCF 324. Fixed access, e.g., IP telephony devices 374a-374b, may
connect with IMS network via Internet 370 that is communicatively
coupled with IMS network 320 by way of border gateway 360.
[0041] As is understood, DNS 372 comprises a scalable namespace
that facilitates access to entities deployed on the Internet or
private networks. DNS 372 maintains various records for host names,
servers, and the like. For example, DNS 372 maintains records
(commonly referred to as "A records") that map hostnames to IP
addresses, pointer (PTR) records that map IP addresses to canonical
names to facilitate reverse DNS lookups, service (SRV) records that
specify information on available services, naming authority pointer
(NAPTR) records that facilitate regular expression based rewriting,
and various other records. DNS 372 may additionally include a
telephone number mapping (ENUM) system that facilitates resolution
of SIP addresses from E.164 number as is understood.
[0042] A base station manager (BSM) 378 may be deployed in Internet
370 and may be adapted to communicate with numerous femtocell
systems and femtocell networks. BSM 378 may provide various
operations, maintenance, and management functions to femtocell
systems. For example, BSM 378 may provide service provisioning of
femtocell systems, e.g., by providing configuration downloads to
femtocell systems and preloading default configuration data for
femtocell systems distributed via sales channels. BSM 378 may
provide various support and maintenance features, such as alarm and
periodic statistics reporting, automatic remote software image
distribution to femtocell systems, provide upgrades and
reconfigurations, and may provide remote access via Internet 370
for diagnostics and customer support.
[0043] In accordance with an embodiment, a femtocell system 350 may
include integrated BTS and BSC functions and may feature additional
capabilities available in the provided femtocell site coverage
area. Femtocell system 350 provides an IP-accessible radio access
network, is adapted for operation with IMS 320, and provides radio
link control functions. Femtocell system 350 may be communicatively
coupled with Internet 370 via any variety of backhaul technologies,
such as an 802.11x link, a 10/100 BaseT LAN link, a T1/E1 Span or
fiber, cable set top box, DSL modem connected with a central office
digital subscriber line access multiplexer, a very small aperture
terminal (VSAT), or another suitable backhaul infrastructure.
[0044] In an embodiment, femtocell system 350 includes a session
initiation protocol (SIP) adapter that supports a SIP client pool
and provides conversion of call set-up functions to SIP client
set-up functions. For example, a SIP client pool allocated by
femtocell system 350 may comprise a plurality of SIP user agents
352a-352c that each may be allocated for a UE authorized to access
femtocell system 350. Additionally, femtocell system 350 includes
electronic serial number (ESN) screening, and/or Mobile Equipment
Identifier (MEID) screening, to allow only designated UEs to access
the femtocell thereby restricting access to authorized home or
small office UEs. For example, femtocell system 350 may be
configured with an ESN and/or MEID list 354 that specifies ESNs
and/or MEIDs of UEs authorized to access femtocell system 350. In
the illustrative example, ESNs of "ESN 1"-"ESN 3" are included in
ESN list 354. Provisioning of ESN(s) and/or MEID(s) may be made as
part of an initial femtocell system 350 activation. In the
illustrative example, femtocell system 350 is allocated an Internet
Protocol (IP) address of "66.249.73.42", and UE 325 is allocated a
mobile services ISDN (MSISDN) number, or E.164 number, of
"12145551212".
[0045] FIG. 4A is a simplified diagrammatic representation of
femtocell system 350 depicted in FIG. 3 that facilitates
provisioning of a femto-RAN in accordance with an embodiment.
Femtocell system 350 includes an antenna 400 coupled with a BTS
410. BTS 410 may be implemented, for example, as a 1xRTT ASIC
device and may comprise a non-diversity receiver featuring a
built-in duplexer. In an embodiment, BTS 410 may feature only one
operational band and may include a transmitter scan receiver and
local oscillator. BTS 410 may be communicatively coupled with a BSC
420 that provides radio control functions, such as receiving
measurements from UEs, such as mobile phones, control of handovers
to and from other femtocell systems, and may additionally
facilitate handoff to or from macrocells.
[0046] Femtocell system 350 includes an electronic serial number
screening function 430 that may facilitate approving or rejecting
service for a UE by femtocell system 350. Additionally femtocell
system 350 includes an Internet Operating System (IOS) and SIP
Adapter (collectively referred to as IOS-SIP Adapter 440). IOS-SIP
adapter 440 may invoke and manage SIP clients, such as a user agent
(UA) pool comprising one or more UAs. In accordance with an
embodiment, each UE 325 authorized to be serviced by femtocell
system 350 may have a UA allocated therefor by the femtocell system
in a manner that facilitates transmission of communications to and
from a UE over an IP backhaul. Accordingly, when an authorized UE
is within the femtocell system 350 site range, telecommunication
services may be provided to the UE via the IP backhaul and the
femtocell system 350 provisioned RAN. When the UE is moved beyond
the service range of femtocell system 350, telecommunication
service may then be provided to the UE via macrocellular
coverage.
[0047] To facilitate routing of calls from circuit switched call
originators, femtocell system 350 may perform a DNS/ENUM
registration on behalf of UEs authorized to obtain service from
femtocell system 350. In the present example, assume UE 325 with a
MSISDN of "12145551212" has a SIP service subscription in the
domain "example.com" and has a SIP uniform resource identifier
(URI) of "12145551212@example.com". An example DNS/ENUM
registration message generated by femtocell system 350 on behalf of
UE 325 and transmitted to DNS 372 is as follows:
TABLE-US-00001 $ORIGIN 2.1.2.1.5.5.5.4.1.2.1.e164.arpa. IN NAPTR
100 10 "u" "E2U+sip" "!{circumflex over (
)}.*$!sip:12145551212@example.com!".
[0048] As is understood, the first line of the registration message
comprises the MSISDN number of the UE converted (i.e., reversed
with each numeral delineated with a "." character and appended with
the e164.arpa domain) for DNS lookup. The second line of the
registration message specifies the NAPTR record for the hosts that
can further process the address--the domain "example.com" (in which
the UE with a URI of 12145551212@example.com is registered) in the
present example.
[0049] Femtocell system 350 may generate and issue a SIP
registration on behalf of UE 325 authorized for service access by
femtocell system 350.
[0050] FIG. 4B is a simplified diagrammatic representation of an
alternative femtocell system 450 that facilitates provisioning of a
femto-RAN in accordance with an alternative embodiment. Femtocell
system 450 includes an antenna 400 coupled with a radio node (RN)
411. RN 411 may be implemented, for example, as a 1xEV-DO ASIC
device. For example, RN 411 may provide a 1xEV-DO Rev. 0 air
interface or a 1xEV-DO Rev. A air interface. RN 411 may be
communicatively coupled with a radio network controller (RNC) 421
that provides radio control functions, such as receiving
measurements from UEs, control of handovers to and from other
femtocell systems, and may additionally facilitate handoff to or
from macrocells. RNC 421 may also provide encryption/decryption
functions, power, load, and admission control, packet scheduling,
and various other services.
[0051] Femtocell system 450 includes an electronic serial number
screening function 430 that may facilitate approving or rejecting
service for a UE by femtocell system 450. Additionally, femtocell
system 450 includes an Internet Operating System (IOS) and SIP
Adapter (collectively referred to as IOS-SIP Adapter 440). IOS-SIP
adapter 440 may invoke and manage SIP clients, such as a user agent
(UA) pool comprising one or more UAs. Each UE 325 authorized to be
serviced by femtocell system 450 may have a UA allocated therefor
by femtocell system 450 in a manner that facilitates transmission
of communications to and from a UE over an IP backhaul.
Accordingly, when an authorized UE is within the femtocell system
450 site range, telecommunication services may be provided to the
UE via the IP backhaul and femtocell system 450 provisioned RAN.
When the UE is moved beyond the service range of femtocell system
450, telecommunication service may then be provided to the UE via
macrocellular coverage. Femtocell system 450 may perform a DNS/ENUM
registration on behalf of UEs authorized to obtain service from
femtocell system 450 and may generate and issue a SIP registration
on behalf of a UE authorized for service access by the femtocell
system 450 in a manner similar to that described above with
reference to femtocell system 350.
[0052] FIG. 5 is a diagrammatic representation of an exemplary SIP
registration message 500 generated by femtocell system 350 on
behalf of UE 325 authorized for service access thereby in
accordance with an embodiment. Registration message 500 may be
transmitted from femtocell system 350 to a location service, such
as a SIP registrar implemented as SIP Registrar 380. Registrar 380
may provide the location and contact information to location
service 382. Registration message 500 includes a REGISTER field 510
that specifies the registration is being made within the domain
"example.com". In accordance with an embodiment, multiple contacts
are included in registration message 500. In the present example,
registration message 500 includes a contact field 512 that
specifies a SIP contact for UE 325. Notably, the SIP contact field
512 for UE 325 specifies the UA registered on behalf of UE with the
URI 12145551212@example.com is located at the IP address of
"66.249.73.42". That is, the SIP contact registered by femtocell
system 350 on behalf of UE 325 is to be addressed at the femtocell
system 350 address of 66.249.73.42 thereby resulting in routing of
SIP signaling messages to femtocell system 325. In turn, femtocell
system 350 may convert SIP call set up messaging to RAN signaling,
allocate an uplink and a downlink channel for UE 325, and set up a
call or data session thereon.
[0053] In the present example, registration message 500 includes a
second contact field 514 that specifies a telephone URI, e.g., the
MSISDN +1-214-555-1212 of UE 325. Thus, a location query for the
SIP URI sip:12145551212@example.com would return two contacts. The
first is the SIP URI that can be used to reach femtocell system
350, and thus UE 325 thereby, and the second is the telephone URI
that can be used to reach UE 325 via macrocellular coverage, i.e.,
via RAN 310. As is understood, the order of contacts 512-514
provides a contact preference, and the multiple contacts may be
registered in separate registration messages. The depicted
registration message including both the SIP contact URI and
telephone URI is exemplary only. Accordingly, in the present
example, an attempt to contact UE 325 may first be made via the SIP
URI 12145551212@example.com. In the event that the session is not
successfully set up via the SIP contact, an attempt may be made to
setup a session via RAN 310 using the telephone URI.
[0054] When the UE 325 moves outside the coverage area of femtocell
system 350, another registration may be generated and submitted by
femtocell system 350 on behalf of UE 325 where the telephone URI is
designated as the preferred contact. Further, the SIP URI may be
removed from the registration when the UE 325 moves outside the
coverage area of femtocell system 350 thereby avoiding any attempts
to establish a session with UE 325 via femtocell system 350 when UE
325 has moved beyond the femtocell system 350 coverage area.
[0055] To better facilitate an understanding of disclosed
embodiments, consider a call placed at circuit switched telephone
332 to UE 325. A gateway receives the call setup request, e.g., an
Initial Address Message (IAM), and a query may be made with DNS 372
from which the domain "example.com" is resolved from the ENUM
function. An INVITE message is then transmitted to the example.com
domain which, in turn, resolves the location of the called UE 325.
Particularly, CSCF 320 may interrogate location server 382 and
determine UE 325 is registered as located at the IP address
66.249.73.42. Accordingly, the INVITE message is routed to proxy
server 376 which forwards the INVITE message to femtocell system
350. Femtocell system 350 may then perform paging, channel
allocation, and other procedures for provisioning a radio interface
with UE 325 and issue SIP responses on behalf of UE 325. Thus, from
a network perspective, femtocell system 350 appears as a user agent
to which the call is directed. Further, UE 325 does not require a
SIP client for receiving the call because femtocell system 350
advantageously performs signaling and media conversion for
signaling and media transmissions over-the-air interface with 325.
Thus, femtocell system 350 may appear as a conventional BTS to UE
325. A call from UE 325 to another terminal, such as
circuit-switched telephone 332, a SIP client such as
packet-switched telephony device 374a, or another device, may
similarly be facilitated by femtocell system 350.
[0056] As a second example, assume UE 325 has moved beyond the
range of femtocell system 350. As noted above, femtocell system 350
may generate and transmit a registration message that excludes the
SIP contact to facilitate provisioning of telecommunication
services via macrocell coverage, e.g., via RAN 310. For instance,
femtocell system 350 may periodically perform power measurements
with UE 325, and upon the power measurement dropping below a
particular power threshold, femtocell system may determine UE 325
is to be serviced by macrocellular coverage. Alternatively, a user
may select macrocellular coverage via a user interface provided on
UE 325. In this instance, UE 325 may provide an indication to
femtocell system 350 that telecommunication services are to be
provided by RAN 310. Other scenarios may similarly result in a
determination that UE 325 is to be serviced by RAN 310. Upon such a
determination, femtocell system 350 may generate and transmit a
registration message on behalf of UE 325 to a registrar service,
e.g., CSCF 320 and SIP registrar 380. The contact information may
then be updated in location server 382 to indicate the telephone
URI as the contact of UE 325. In this scenario, consider a call
placed at circuit switched telephone 332 to UE 325. A gateway
receives the call setup request, e.g., an Initial Address Message
(IAM), and a query may be made with DNS server 372 from which the
domain "example.com" is resolved from the ENUM service. An INVITE
message is then transmitted to the example.com domain which
resolves the location of called UE 325. In the present example,
CSCF 320 may interrogate location server 382 and determine UE 325
has a preferred contact registered as a telephone URI of
2145551212. Accordingly, the INVITE message is routed to a gateway
server, e.g., gateway server 390 which translates the INVITE
message to a RAN-compliant call request signaling. The call may
then be setup via RAN 310 accordingly.
[0057] A network of femtocell systems may be deployed and connected
with an IP backhaul. In this implementation, an authorized UE may
be serviced by the femtocell network, and service may be
transferred from one femtocell to another femtocell via a femtocell
handoff procedure. In the event that the femtocell network is
deployed in an area serviced by a macrocellular network, handoff
routines may provide preference for transferring a UE to a target
femtocell system rather than a macrocell site. In the event that a
suitable femtocell is unavailable for handoff of a UE, the UE may
be transferred to the macrocell site.
[0058] FIG. 6 is a diagrammatic representation of a network system
600 featuring a femtocell network implemented in accordance with an
embodiment of the invention. System 600 includes a RAN 610 that
provides an over-the-air interface with a UE 625, e.g., a mobile
terminal. RAN 610 may comprise, for example, a CDMA radio access
network or another suitable RAN. RAN 610 may comprise various BTSs
612a-612c and associated BSCs 604 as well as other infrastructure
as is understood. Each of BTSs 612a-612c provide a respective
macrocell 602a-602c that may provide telecommunication service to
UE 625. BSC 604 is coupled with a MSC 606 that provides cellular
exchange services, mobility management, and other services within
the area that it serves as is understood.
[0059] RAN 610 may interface with IMS 620 adapted to provide IP
service to UE 625. To this end, RAN 610 may be communicatively
coupled with a SGSN 614 and a GGSN 616. GGSN 616 is communicatively
coupled with a PDF 618 that provides authorization of media plane
resources. PDF 618 may be communicatively coupled with a CSCF
620.
[0060] CSCF 620 comprises various SIP servers or proxies that
process SIP signaling packets in IMS 620. CSCF 620 may include a
P-CSCF, a S-CSCF, and an I-CSCF as is understood. HSS 640 stores
user profiles that specify subscription-related information of
authorized users, authenticates and authorizes users, and provides
information about the user's physical location. Various application
servers 642a-642n may host and execute services and is interfaced
with CSCF 620 via SIP.
[0061] The I-CSCF has an IP address that is published in DNS 672
that facilitates location of the I-CSCF by remote servers. Thus,
the I-CSCF is used as a forwarding point for receipt of SIP packets
within the domain.
[0062] CSCF 620 is coupled with a BGCF 622 that comprises a SIP
server that provides routing functionality based on telephone
numbers. A MGCF 624 performs call control protocol conversion
between SIP and ISDN User Part (ISUP) and interfaces with a SGW 626
that itself interfaces with the signaling plane of a circuit
switched network, e.g., PSTN 630. A MGW 628 interfaces with the
media plane of PSTN 630 or another circuit switched network.
Resources of MGW 628 are controlled by MGCF 624. Fixed access
devices, e.g., IP telephony devices 674a-674b, may connect with IMS
network via Internet 670 that is communicatively coupled with IMS
network 620 by way of border gateway 660.
[0063] A BSM 678 may be deployed in Internet 670 and may be adapted
to communicate with numerous femtocell systems and femtocell
networks. BSM 678 may provide various operations, maintenance, and
management functions to femtocell systems. BSM 678 may provide
service provisioning of femtocell systems, e.g., by providing
configuration downloads to femtocell systems and preloading default
configuration data for femtocell systems distributed via sales
channels. BSM 678 may provide various support and maintenance
features, such as alarm and periodic statistics reporting,
automatic remote software image distribution to femtocell systems,
provide upgrades and reconfigurations, and may provide remote
access via Internet 670 for diagnostics and customer support.
[0064] Femtocell systems 650a-650c may include integrated BTS and
BSC, or alternatively (or additionally) radio node (RN) and radio
network controller (RNC), functions and may feature additional
capabilities available in the provided femtocell site coverage
areas. Femtocell systems 650a-650c provide an IP-accessible radio
access network, are adapted for operation with IMS 620, and provide
radio link control functions. Femtocell systems 650a-650c may be
communicatively coupled with Internet 670 via any variety of
backhaul technologies, such as an 802.11x link, a 10/100 BaseT LAN
link, a T1/E1 Span or fiber, cable set top box, DSL modem connected
with a central office digital subscriber line access multiplexer, a
very small aperture terminal (VSAT), or another suitable backhaul
infrastructure. In the illustrative example, femtocell systems
650a-650c may be coupled with an IP backhaul access device 655,
such as an Ethernet cable or DSL router. For instance, femtocell
systems 650a-650c may be coupled with access node 655 via
respective 10/100 BaseT twisted pair cables, Category 5 cabling, or
other suitable interconnection.
[0065] Each of femtocell systems 650a-650c provide a respective
femtocell site 651a-651c in which UE 625 may be provided
telecommunication services over an air interface. Femtocell systems
650a-650c are communicatively coupled with one another via access
device 655. Femtocells 650a-650c deployed for conjunctively
providing a femtocell service coverage area comprised of the
collective femtocell sites 651a-651c are collectively referred to
herein as a femtocell network. In an embodiment, femtocell systems
650a-650c may exchange messages with one another to facilitate
handoff of a UE from one femtocell to another, e.g., as UE 625
moves out of the radio range of a femtocell and into the radio
range of another. In the depicted example, the femtocell network
provided by femtocell systems 650a-650c is at least partially
overlapped by one or more macrocell sites 602a-602c provisioned by
macrocell BTSs 612a-612c. In such an implementation, femtocell
systems 650a-650c may provide preference to another femtocell for
handoff of a UE thereto. In the event that another femtocell is not
available or is unsuitable for a handoff, the UE may then be
transferred to macrocellular coverage via a handoff to a macrocell
BTS.
[0066] In an embodiment, each of femtocell system 650a-650c include
a respective SIP adapter that supports a SIP client pool and
provides conversion of call set-up functions to SIP client set-up
functions. Additionally, femtocell systems 650a-650c include ESN
and/or MEID screening to allow only designated UEs to access the
femtocells thereby restricting access to authorized home or small
office UES. For example, femtocell system 650a may be configured
with an ESN and/or MEID list 654a that specifies ESNs and/or MEIDs
of UEs authorized to access femtocell system 650. In the
illustrative example, ESNs of "ESN 1"-"ESN 3" are included in ESN
and/or MEID list 654a. Provisioning of ESN(s) and/or MEID(s) may be
made as part of an initial femtocell system 650 activation. Other
femtocell systems 650b-650c may be similarly configured with an ESN
and/or MEID list including ESNs and/or MEIDs of UEs authorized to
access the femtocell system network comprised of femtocell systems
650a-650c. In the illustrative example, femtocell systems 650a-650c
are allocated a respective IP address of "66.249.73.42",
"66.249.73.43", and "66.249.73.44", and UE 625 is allocated a
MSISDN number, or E.164 number, of "12145551212".
[0067] FIG. 7 is a diagrammatic representation of an exemplary
software configuration 700 of a UE, such as UE 625, adapted for
engaging in communications with femtocell systems in accordance
with an embodiment. In the exemplary configuration of FIG. 7, the
UE is configured with access network-specific software entities
760, e.g., protocol and driver software associated with a
particular access network technology, such as CDMA, GSM, UMTS, or
another suitable radio access network, and is dependent on the
particular cellular and femtocell access technology in which the UE
is to be deployed. While configuration 700 depicts a UE adapted for
deployment in a single access network technology type, the UE may
be implemented as a multi-mode device and may accordingly include a
plurality of access-specific entities in accordance with an
embodiment. The particular configuration 700 is illustrative only
and is provided only to facilitate an understanding of embodiments
disclosed herein.
[0068] In the illustrative example, configuration 700 includes a
cellular modem driver 702 for providing a physical interface with
the access network in which the UE is deployed. An access-stratum
704 and a non-access stratum 706 may be included in configuration
700. A cellular radio interface 708 may be communicatively coupled
with lower layers of configuration 700 and may additionally
interface with network and session management layers, e.g., a
network stack 710. Configuration 700 may include an operating
system 714, such as Symbian, Blackberry O/S, or another operating
system suitable for mobile applications, and may coordinate and
provide control of various components within the UE.
[0069] Configuration 700 may include a femto application 712 that
facilitates femtocell network acquisition and handoff of a UE from
a macrocellular network to a femtocell system in accordance with an
embodiment. In one implementation, a femtocell or femtocell
network, such as that comprising femtocell systems 650a-650c, may
be acquired by a micro-pilot assisted handoff routine or a mobile
assisted handoff routine as described more fully hereinbelow.
[0070] Configuration 700 may include a preferred roaming list (PRL)
716 that contains information used during the system selection and
acquisition process. PRL 716 indicates which bands, sub-bands and
service provider identifiers will be scanned, and the priority of
the scan order. In the illustrative example, PRL 716 includes four
entries 716a-716d that respectively specify four networks
(illustratively designated "Femto", "Macro 1", "Macro 2", and "Roam
1"). In the present example, assume "Femto" refers to the network
of femtocell systems 650a-650c. The femtocell network is specified
first in the prioritized list of PRL entries and thus indicates
that the femtocell network is the preferred access network. Assume
"Macro 1" refers to radio access network 610, and "Macro 2" refers
to another cellular network. "Roam 1" specified by PRL entry 716d
may refer to another cellular network that may have a roaming
agreement with the UE home network. As is understood, PRL 716 may
comprise an acquisition table that specifies a list of frequencies
associated with each of the networks specified in the roaming list
on which the UE may scan during search of a particular system and
may further specify PN offsets thereof. The acquisition table may
additionally specify a network type of each listed network and
associated channel blocks.
[0071] In accordance with an embodiment, femtocell systems
650a-650c include ESN and/or MEID screening to allow only
designated UEs to access the femtocells thereby restricting access
to authorized home or small office UEs. To this end, mechanisms for
configuration of femtocell systems 650a-650c with authorized UE
ESNs and/or MEIDs are provided in accordance with embodiments.
[0072] FIG. 8 depicts a flowchart 800 of a femtocell system
configuration provisioning routine implemented in accordance with
an embodiment. The provisioning routine is invoked (step 802), and
the femtocell system may be provisioned with an ID (step 804). The
femtocell system may then be provisioned with a default BSM IP
address (step 806), e.g., the IP address of BSM 678. Provisioning
of the femtocell system ID and default BSM IP address may, for
example, be made at the factory or production facility of the
femtocell system. The femtocell system may then be deployed in a
small office/home office network (step 808). The femtocell system
may then request and receive a configuration download (step 810),
e.g., from the default BSM. In accordance with an embodiment, the
configuration download may include an ESN and/or MEID list that
specifies ESN(s) and/or MEID(s) of UE(s) authorized to access the
femtocell system. The provisioning routine cycle may then end (step
812).
[0073] FIG. 9 is a configuration routine 900 that facilitates
generation of femtocell system configuration data implemented in
accordance with an embodiment.
[0074] The configuration routine is invoked (step 902), and an
account identifier and femtocell ID may be received (step 904),
e.g., at a default BSM. Handset IDs in the customer plan associated
with the femtocell system may then be received (step 906). A
femtocell system identification number (SID)/network identification
number (NID) may then be allocated for the femtocell system (step
908). ESNs and/or MEIDs of UEs authorized to access then femtocell
system may then be compiled (step 910), e.g., from customer account
information. The configuration information may then be transferred
to the femtocell system (step 912), e.g., upon request of the
configuration information from the femtocell system. The
configuration information may include ESN(s) and/or MEID(s) of UEs
authorized to access the femtocell system. Optionally, the
configuration information may include the PRL of one or more UEs
authorized to access the femtocell system. In this instance, the
femtocell system may transfer the PRL to the UE over an
air-interface. On receipt of the configuration information, the
femtocell system may load the ESN and/or MEID list including the
ESNs and/or MEIDs of UES authorized to access the femtocell
system.
[0075] In an implementation, a femtocell system may be configured
for ESN and/or MEID screening by downloading a configuration file
from a BSM. When a UE attempts to register with the femtocell
system, the femtocell system may interrogate an ESN and/or MEID
list that specifies ESNs and/or MEID(s) of UEs authorized to access
the femtocell system. If the ESN or MEID of the UE is included in
the ESN and/or MEID list of authorized ESNs and/or MEIDs, the
registration may be completed, otherwise the registration may be
rejected. In a similar manner, UEs attempting to place a call
through the femtocell system may be screened for an authorized ESN
or MEID. In an implementation, the femtocell system may be
configured to allow a call to be placed by a UE regardless of
whether the UE has an authorized ESN or MEID in the event the call
request comprises an emergency call request, e.g., a 911 call. In a
non-emergency scenario, a call is allowed to be placed through the
femtocell system only if the UE placing the call has an ESN or MEID
that matches an authorized ESN or MEID of the femtocell system's
ESN and/or MEID list.
[0076] FIG. 10 is a flowchart 1000 that depicts processing of a
call screening routine implemented in accordance with an
embodiment. The processing steps of FIG. 10 may be implemented as
computer-executable instructions executable by a processing system,
such as a femtocell system, in accordance with an embodiment.
[0077] The call screening routine is invoked (step 1002), and a
call request is received by the femtocell system (step 1004). A
femtocell system may then evaluate the call request to determine if
the destination number is an emergency number (step 1006), e.g.,
911. In the event the destination number is an emergency number,
the femtocell system may complete the call setup (step 1008). In
the event the UE is equipped with global positioning system (GPS)
capabilities, or alternatively if the network includes GPS or other
suitable location determination services, the GPS or other location
information of the UE may be included in the call setup signaling
transmitted to the core network. The call screening routine cycle
may then end (step 1018).
[0078] Returning again to step 1006, in the event that the
destination number is not an emergency number, the femtocell system
may then determine the ESN or MEID of the call originating user
equipment (step 1010). The femtocell system may then interrogate
the ESN and/or MEID list maintained by the femtocell system (step
1012). An evaluation may then be made to determine if the ESN or
MEID of the origination user equipment matches an ESN or MEID of
the ESN and/or MEID list (step 1014). In the event that the ESN or
MEID of the originating user equipment matches an ESN or MEID of
the ESN and/or MEID list, the call may be setup according to step
1008. If, however, the ESN or MEID does not match an authorized ESN
or MEID maintained in the femtocell system's ESN and/or MEID list,
the call setup may be rejected (step 1016), and the call screening
routine cycle may then end according to step 1018.
[0079] FIG. 11 is a flowchart 1100 that depicts processing of a
user equipment registration screening routine implemented in
accordance with an embodiment. The processing steps of FIG. 11 may
be implemented as computer-executable instructions executable by a
processing system, such as a femtocell system, in accordance with
an embodiment.
[0080] The registration screening routine is invoked (step 1102),
and a registration request is received (step 1104), for example,
when a user equipment is powered on within a femtocell system
service area or when a user equipment is registered in a macrocell
system and moves within range of a femtocell system. The femtocell
system may determine the ESN or MEID of the user equipment (step
1106), and may then evaluate the ESN and/or MEID list of authorized
ESNs and/or MEIDs to determine if the user equipment requesting to
register with the femtocell system is authorized to access the
femtocell system (step 1108). If the ESN or MEID of the user
equipment matches an ESN or MEID of the ESN and/or MEID list,
registration of the user equipment may be completed by the
femtocell system (step 1110), and the registration screening
routine cycle may end (step 1114).
[0081] Returning again to step 1108, if the ESN or MEID of the user
equipment that has requested registration with the femtocell system
does not match an ESN or MEID of the ESN and/or MEID list
maintained by the femtocell system, the femtocell system may reject
the registration request (step 1112), and the registration
screening routine cycle may end according to step 1114.
[0082] As described, a communication system featuring an IP-based
femtocell system for provisioning communication services to a user
equipment is provided. In one implementation, a list of ESNs and/or
MEIDs of handsets in the user subscription may be compiled by a
base station manager. The femtocell system may connect with the
base station manager and request a configuration download once
deployed in a SOHO. The compiled ESNs and/or MEIDs may then be
transferred from the base station manager to the femtocell system
in a configuration download. The femtocell system may then screen
ESNs and/or MEIDs of user equipments that attempt to register with
the femtocell system. In an embodiment, the femtocell system may
allow calls to be placed through the femtocell system on an
emergency basis regardless of whether the user equipment has an ESN
or MEID that is authorized for access by the femtocell system. In
non-emergency scenarios, only user equipments having an ESN or MEID
that match an ESN or MEID in the femtocell system's ESN and/or MEID
list are allowed to place calls or register with the femtocell
system.
[0083] The flowcharts of FIGS. 8-11 depict process serialization to
facilitate an understanding of disclosed embodiments and are not
necessarily indicative of the serialization of the operations being
performed. In various embodiments, the processing steps described
in FIGS. 8-11 may be performed in varying order, and one or more
depicted steps may be performed in parallel with other steps.
Additionally, execution of some processing steps of FIGS. 8-11 may
be excluded without departing from embodiments disclosed
herein.
[0084] The illustrative block diagrams depict process steps or
blocks that may represent modules, segments, or portions of code
that include one or more executable instructions for implementing
specific logical functions or steps in the process. Although the
particular examples illustrate specific process steps or
procedures, many alternative implementations are possible and may
be made by simple design choice. Some process steps may be executed
in different order from the specific description herein based on,
for example, considerations of function, purpose, conformance to
standard, legacy structure, user interface design, and the
like.
[0085] Aspects of the present invention may be implemented in
software, hardware, firmware, or a combination thereof. The various
elements of the system, either individually or in combination, may
be implemented as a computer program product tangibly embodied in a
machine-readable storage device for execution by a processing unit.
Various steps of embodiments of the invention may be performed by a
computer processor executing a program tangibly embodied on a
computer-readable medium to perform functions by operating on input
and generating output. The computer-readable medium may be, for
example, a memory, a transportable medium such as a compact disk, a
floppy disk, or a diskette, such that a computer program embodying
the aspects of the present invention can be loaded onto a computer.
The computer program is not limited to any particular embodiment,
and may, for example, be implemented in an operating system,
application program, foreground or background process, driver,
network stack, or any combination thereof, executing on a single
processor or multiple processors. Additionally, various steps of
embodiments of the invention may provide one or more data
structures generated, produced, received, or otherwise implemented
on a computer-readable medium, such as a memory.
[0086] Although embodiments of the present invention have been
illustrated in the accompanied drawings and described in the
foregoing description, it will be understood that the invention is
not limited to the embodiments disclosed, but is capable of
numerous rearrangements, modifications, and substitutions without
departing from the spirit of the invention as set forth and defined
by the following claims. For example, the capabilities of the
invention can be performed fully and/or partially by one or more of
the blocks, modules, processors or memories. Also, these
capabilities may be performed in the current manner or in a
distributed manner and on, or via, any device able to provide
and/or receive information. Further, although depicted in a
particular manner, various modules or blocks may be repositioned
without departing from the scope of the current invention. Still
further, although depicted in a particular manner, a greater or
lesser number of modules and connections can be utilized with the
present invention in order to accomplish the present invention, to
provide additional known features to the present invention, and/or
to make the present invention more efficient. Also, the information
sent between various modules can be sent between the modules via at
least one of a data network, the Internet, an Internet Protocol
network, a wireless source, and a wired source and via plurality of
protocols.
* * * * *