Movatterモバイル変換


[0]ホーム

URL:


US7181207B1 - Method and apparatus for over-the-air activation of neighborhood cordless-type services - Google Patents

Method and apparatus for over-the-air activation of neighborhood cordless-type services
Download PDF

Info

Publication number
US7181207B1
US7181207B1US11/175,825US17582505AUS7181207B1US 7181207 B1US7181207 B1US 7181207B1US 17582505 AUS17582505 AUS 17582505AUS 7181207 B1US7181207 B1US 7181207B1
Authority
US
United States
Prior art keywords
ibs
subscriber
call
message
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US11/175,825
Inventor
Albert Chow
Spencer Wang
Wenchu Ying
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Corp
Original Assignee
AT&T Corp
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
Priority claimed from US09/223,318external-prioritypatent/US6594488B1/en
Application filed by AT&T CorpfiledCriticalAT&T Corp
Priority to US11/175,825priorityCriticalpatent/US7181207B1/en
Priority to US11/649,650prioritypatent/US8712405B1/en
Application grantedgrantedCritical
Publication of US7181207B1publicationCriticalpatent/US7181207B1/en
Priority to US14/263,997prioritypatent/US9578590B2/en
Priority to US15/437,295prioritypatent/US9942417B2/en
Anticipated expirationlegal-statusCritical
Expired - Fee Relatedlegal-statusCriticalCurrent

Links

Images

Classifications

Definitions

Landscapes

Abstract

A method for providing a local cordless-type service comprises the steps of receiving subscriber neighborhood zone selection input so that a mobile telephone equipped subscriber may place or receive calls for a fixed rate, for example, per month without having to pay radio frequency air time charges any time they are located within their selected subscribed-to zones. If the subscribed-to zones are adjacent to one another and the mobile subscriber roams from one zone to another, the subscriber may continue their free call uninterrupted and without paying air time charges. However, when the subscriber roams outside their subscribed-to zones they may be switched from the present local cordless-type services to conventional personal communications services and pay air time charges. However for an active call, no air-time charges are incurred as the user transitions between the cellular/DPCS environment and the local cordless service environment. Associated apparatus comprises an IBS for automatically changing radio frequency channels as the subscriber roams within a subscribed-to neighborhood zone, roams to another subscribed-to zone or roams outside a subscribed-to zone. Subscribers may choose to use their mobile identification number, their current directory telephone number for wired public switched telephone service or obtain a new directory number. Subscribers can actuate their service over-the-air automatically without service personnel assistance from their home neighborhood zone.

Description

This application is a continuation of U.S. application Ser. No. 09/987,610, filed on Nov. 15, 2001, now U.S. Pat. No. 6,980,817 which is a continuation of U.S. application Ser. No. 09/223,318, filed on Dec. 30, 1998 now U.S. Pat. No. 6,594,488.
All United States patents referred to herein should be deemed to be incorporated by reference as to their entire contents. The following copending patent applications, which have each been filed on the same day as the present application (the third one listed below being the present application), are hereby incorporated by reference as to their entire contents:
BACKGROUND OF THE INVENTION
1. Technical Field
This invention relates to the field of providing neighborhood cordless-type services at a single rate such that there is no air time charge for calls made within a home neighborhood zone or subscribed-to visiting neighborhood zone(s), and, more particularly to a method of activating such services over-the-air without any need for service personnel assistance.
2. Description of the Related Arts
It is known to provide wireless services for a fixed fee and to charge additional air time fees for each period of time that a subscriber to the wireless services is using the radio frequency spectrum. Such services were initiated in the 1970's as analog wireless services and have become digital over time, for example, the relatively new digital personal communications services (DPCS).
It has been known up until recently to permit users to have cordless telephone apparatus comprising a base station and a mobile unit such that the mobile unit may communicate with the base station over limited distances of several hundred feet. Recently, in the United States, however, a band of frequencies has been made available in the 900 MHZ range for providing cordless telephone service where the mobile station can be as far removed from the base station portion of the station apparatus by as much as one mile under optimal conditions. Consequently, a user would not have to pay for air time charges as in wireless services such as personal communications services if a mobile station is confined within one mile radius of the typically home-located base station.
Fixed wireless subscriber loop services are also known. Equipment for providing such services is available from suppliers such as Diva Communications and OptoPhone Systems. The fixed wireless subscriber loop concept has been used successfully to provide telephone services to remote, for example, mountainous regions. To provide a copper wire subscriber loop to such customers can cost hundreds of thousands of dollars per subscriber. Subscribers to a fixed wireless subscriber loop system have an antenna mounted to their home or business and receive an equivalent of wired services over a wireless link to an antenna site, for example, on the top of the mountain. Service can be provided for a fixed rate, the copper subscriber wired loop eliminated and no air time charges are charged.
There is still a need in the art for a wireless service that would permit a mobile subscriber to roam within a zone close to their home in the same way as a 900 MHZ cordless customer is free to carry their cordless phone from room to room. A mobile subscriber should be able to roam and also move from one zone to another or make calls from non-contiguous zones without having to pay for air time charges. In today's cellular environment, airtime is charged. The current fee structure thus has very little incentive for customers to continue to use their cellular phones when they have access to a home-based landline phone. In order to achieve the objectives of one phone, one number anytime and anywhere communications, it is imperative that a neighborhood or local ‘cordless-type’ of services be provided to all the public cellular/PCS subscribers and with incentive to use the same PCS phone in the home/office and around the neighborhood area without air time charges. A subscriber should not lose a call in progress as they move from one subscribed-to zone to another adjacent subscribed zone, and should have the opportunity to switch automatically to known DPCS services and pay air time charges should they so choose. A subscriber to such services should be able to activate their service over-the-air from their subscriber to home neighborhood zone without having to obtain service personnel assistance.
TIA/EIA Interim Standard—Addendum No. 1 to TIMEIA/IS-136.1-A provides suggested messages for an over-the-air activation teleservice, which permits a subscriber to activate cellular service without the intervention of a third party. There is provision for point-of-sale data entry or preregistration so that a subscriber may be properly validated. Nevertheless, these suggested messages should be preferably supported in an over-the-air activation service.
SUMMARY OF THE PRESENT INVENTION
Subscribers to a local cordless-type service according to the present invention may subscribe to a home neighborhood zone and optionally one or more visiting neighborhood zones from which the subscribers may place telephone calls without having to pay air time charges. By local cordless-type service is intended a mobile wireless subscriber loop service wherein stations are mobile and the subscriber loop to the customer's premises may be replaced with a wireless loop. The subscriber need not maintain their wired connection to a local exchange carrier (LEC). If the subscribers are current public digital PCS service users, they may use their existing cellular phone and unique mobile identification number (MIN) for subscription to the service. Subscribers may also have the option of electing new wireline numbers to be assigned to their cellular phone for subscription of the service and the numbers assigned may be the traditional PSTN directory number (DN). Alternatively, the subscribers can elect to port their existing wireline DNs to this service. If the subscriber is not a public cellular user, they will need a cellular phone or other mobile station (MS) assigned with either a new DN or their ported DN from the incumbent local exchange carder (ILEC).
The subscriber buys their phone at a retail outlet and the retail outlet records the purchase in a service provider database. The point-of-sale information may include subscriber name, address, credit card number, unique mobile station identification number (MSID), optional personal identification number (PIN) and other verification numbers. Alternatively or in addition, the subscriber may preregister for services with their network service provider of choice. The user initiates their service by activating their phone over-the-air when they first communicate from their selected home neighborhood zone. A feature code comprising a part of the over-the-air activation message may comprise one or more of a uniquely chosen sequence of bits, a manufacturer's electronic serial number and a personal identification number (PIN) selected by the user. The system automatically verifies the user by comparing the point-of-sale/preregistration information with the information input by the subscriber from their home neighborhood zone. Over-the-air activation occurs without the assistance of service personnel.
According to one embodiment of the present invention, a subscriber to such a mobile service pays a flat rate that is competitive with or even less expensive than a subscriber to conventional wired public switched telecommunications services. In their home zone, which may be approximately the same size as, or even slightly larger in size than, the range of a standard 900 MHZ cordless phone, the subscriber may carry or otherwise receive services at one flat rate (regardless of air time used). For additional flat fees, the subscriber may also make calls in one or more visited zones which may be contiguous with or remote from the home zone.
When a subscriber travels between the subscribed home zone and an adjacent visiting zone or between adjacent visiting zones, the call may be handed off to the other zone without interruption to the call in progress. Also, when a subscriber moves from any subscribed zone to a public cellular/PCS environment, the call may be handed off without air time charges for the duration of the same call.
As a subscriber leaves their home zone and roams toward a remote (i.e., non-adjacent) visited zone, there exist at least three alternative ways of billing a call in progress. In one embodiment, the call in progress will be terminated when the boundaries of the subscribed-to zone are reached. In another embodiment, the call will be allowed to continue without air time charges for a predetermined period of time as a public cellular carrier (e.g., a conventional digital personal communications service call). In this invention the preferred method is to allow the call to continue but the subscriber will be switched over to public cellular carrier frequency without air-time charges for the duration of the same call
These and other features of the present invention will be understood from studying the drawings and the following detailed description of various embodiments.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a functional block schematic drawing of an exemplary network architecture for providing LCS Local Cordless-type Services (LCS) and for describing call processing.
FIG. 2 is a functional block schematic drawing of the intelligent base station (130) shown inFIG. 1.
FIG. 3 shows the message flow process between a mobile station (MS) and a network server platform (NSP) and associated database (ID) for downloading a number assignment module (NAM).
FIG. 4ashows an exemplary call processing flow for registration of a mobile station with a mobile identification number (MIN) in its associated home neighborhood zone (HNZ).
FIG. 4bshows an exemplary call processing flow for registration of a mobile station with a directory number (DN) in its associated home neighborhood zone (HNZ).
FIG. 4cshows an exemplary call processing flow for registration of a DN-based mobile station in a subscribed-to visiting neighborhood zone (VNZ).
FIG. 5ashows an exemplary call processing flow for a call delivered to a mobile station with a mobile identification number (MIN).
FIG. 5bshows an exemplary call delivery to a DN-based subscriber in the HNZ via the home IBS.
FIG. 5cshows an exemplary call delivery to a visiting neighborhood zone for a DN-based subscriber registered with the visited V-NSP.
FIG. 5dshows an exemplary call processing for a ported DN based subscriber in their HNZ.
FIG. 5eshows an exemplary call processing for a ported DN based subscriber in a visited zone.
FIG. 5fshows an exemplary call delivery for a DN-based subscriber using the Advance Intelligent Network triggers.
FIG. 6ashows an exemplary intra-cell call hand-off.
FIG. 6bshows an exemplary inter-cell call hand-off within, for example, NSP145-1.
FIG. 7 shows an exemplary outgoing call from a LCS subscriber from a registered zone.
DETAILED DESCRIPTION
Referring toFIG. 1, there is shown an exemplary system architecture for providing local cordless-type services (LCS) according to the present invention. LCS according to the present invention essentially provides a mobile wireless subscriber loop. If a subscriber so chooses, the subscriber may disconnect their wired telephone service provided by their incumbent local exchange carrier (ILEC) and utilize their same directory number (DN) via the present local cordless-type service. The system architecture ofFIG. 1 may be overlaid on an existing public switched telephone service network (PSTN)100 shown above and to the right of a public cellular network cell101-2 of known cellular wireless service (WS). The LCS service may likewise be overlaid and be provided from the same antenna sites as a conventional cellular wireless service or personal communications service. It is envisioned that the LCS radio equipment (IBS)130-1,130-2 can also be attached to telephone poles. For ease of understanding,FIG. 1 presents thePSTN100 as a separate network entity away from the LCS. Thus,FIG. 1 is simplified to the extent that the conventionalwired PSTN100 may actually surround and include a local cordless-type services network according to the present invention in much the same way that today aPSTN network100 surrounds and includes a typical cellular mobile wireless service (WS) network comprising cells101-1 to101-7 or digital personal communication service (DPCS) network. As will be further described herein, the LCS service network defines a plurality of neighborhood zones, which may comprise home neighborhood zones (HNZs)105-1 and visiting neighborhood zones (VNZs)115-1,115-2 from the point of view of an individual subscriber to the LCS service of the present invention.
In fact, the present LCS service may utilize WS, PCS, and/or DPCS infrastructure such as antenna sites and subscriber apparatus. One advantage of the LCS service is its efficient use of the surrounding network's bandwidth capacity. As will be further described herein, unused channels in the 800 MHZ and 1800 MHZ spectra for WS, PCS, and/or DPCS service may be dynamically allocated to LCS service as taught by U.S. Pat. No. 5,809,423 (issued Sep. 15, 1998), U.S. Pat. No. 5,787,352 (issued Jul. 28, 1998), U.S. Pat. No. 5,740,536 (issued Apr. 14, 1998), U.S. Pat. No. 5,513,379 (issued Apr. 30, 1996), U.S. Pat. No. 5,404,574 (issued Apr. 4, 1995), and U.S. Pat. No. 5,345,499 (issued Sep. 6, 1994), all issued to B. Mathilde et al., which are all incorporated by reference herein in their entireties. Moreover, as taught by these patents, the radio frequency cells may be dynamically configured according to algorithms described therein.
LCS service also differs from current cellular/DPCS service in that the LCS radio equipment interfaces to a local digital line switch and not to a mobile switching center. The local digital switch provides bearer channels and feature applications as well as the switching fabric for wired lines. The mobile switching center provides comparable capabilities to the cellular/DPCS network. Utilizing a local digital line side switch enables LCS to provide feature applications to the LCS subscriber currently available to wired telephony but unavailable via theMSC180 in wireless telephony. Another feature of LCS is that the LCS radio equipment, the IBS,130-1,130-2,130-3 interfaces to the local digital switch via ISDN BRI lines and the IBS uses Q.931 signaling for call processing with the LDS140-1,140-2. IBS130-1 and130-2 interface via ISDN BRI lines to remote digitalterminal RDT178 which is a remote digital terminal for concentrating lines known in the art to aGR303 line to LDS140-2. IBS130-3 communicates with LDS140-1 via ISDN BRI135-3. This interface is a widely supported open standard interface and thus the LCS radio equipment, for example, IBS130-1,130-2,130-3, can interwork with any local digital switch that supports the integrated services digital network (ISDN). Therefore LCS radio equipment appears to the switch as an ISDN terminal station and the radio equipment is responsible for terminating Q.931 protocol and establishing the RF link.
Asubscriber10 in a home neighborhood zone (HNZ)105-1 of wireless service (WS) cell101-2 may be aPSTN100 service subscriber and have a hard-wired telephone (not shown) at their residence within the HNZ105-1. Local cordless-type services according to the present invention are not limited by the extensive investment in copper cable distribution facilities which will be referred to herein as a wired subscriber loop. That copper investment (made in aPSTN 100 environment) is avoided with local cordless-type services according to the present invention. Thus, LCS service is expected to be less expensive to subscribers than conventional wired PSTN service.
Subscriber MS10 to a copper-wiredPSTN100 may pay, for example, a fixed rate for telephone service each month and receive unlimited incoming calls within a local calling zone, for example, HNZ105-1. The typical subscriber atMS10 may also place free outgoing calls from their residence within the same local calling zone.
According to the present invention of providing local cordless-type services in the same area,subscriber MS10 may not have wired, fixed location apparatus but may be equipped with a mobile cellular telephone or digital personal communications service telephone, for example, a TIA/EIA/Interim Standard-136 compliant DPCS mobile station (MS)10. For the same monthly rate or a lower monthly rate than the same subscriber may pay for fixed,wired PSTN 100 service, the subscriber withMS10 may receive local cordless-type services. Thus, the LCS subscriber will have equivalent, or in many respects superior, features (such as one number type of mobility service) as a wired PSTN subscriber for the same or lower cost.
Now the present invention of providing a local cordless-type services also differs from a typical cellular telephone service or personal communications service (PCS), in that both of these conventional services charge air time beyond a fiat rate for service. In other words, these conventional services apply an additional per-minute charge for use of the radio frequency spectrum. The present invention of providing a local cordless-type services permits unlimited air time within the home neighborhood zone105-1 and any subscribed visiting neighborhood zone(s), for example VNZ115-1,115-2, such that the amount billed per service period is fixed, regardless of the amount of airtime used.
Also, the present invention is comparable with the provision of conventional so-called 900 MHZ cordless handsets which communicate with a wired home base station. While it is urged by proponents of such apparatus that such phones are portable and may be used as far away as one mile (or more) from associated home base stations, in practice, many such phones are not capable of operating further than hundreds of feet from their wired base stations, for example, because of unfortunate antenna location, the personal use of the mobile handset portion or the placement of the base station or handset portion within a radio frequency shielded residence or automobile or because of other environmental factors. Another limitation for using a 900 MHz phone is that free airtime can only be achieved when using it around the wired home base station. There is no such concept of visiting zone(s)115-1,115-2.
The Home Neighborhood Zone (HNZ)
According to the present invention, each subscriber with LCS mobile station (MS)10 (this subscriber may or may not have a landline phone but must have a cellular phone or other mobile station (MS) in order to use the invention) will be given the opportunity to make calls free of air time charges anywhere within their home neighborhood zone105-1.Subscriber MS10 may roam throughout the home neighborhood zone and make calls for free within that zone. Another subscriber, for example,subscriber MS150 may have a different home neighborhood zone that is defined by their residence location within that zone. The subscriber may be coincidentally located near the center of their HNZ105-1 or toward its perimeter. The HNZ thus is a fixed geographic pattern that may have any desired shape surrounding an intelligent base station (IBS) and antenna site, in this example, IBS130-2. The HNZ105-1 may have other shapes as well, such as an elongated shape, to obtain, for example, a large calling and callable population of subscribers. For the purposes of this description and by way of example only a circle is shown in the drawing but such use of a circle should not be construed to be limiting. In one embodiment, the pattern may have a radius of between one and one half mile and two miles. In another embodiment, the pattern may have a radius of one half of a mile to one and one half mile, or two to 4 miles. In another embodiment, the HNZ105-1 may have a diameter of as much as seven to ten miles. In another embodiment, the shape of the pattern in relation to the neighboring zones may be that of an ellipse. The design of HNZ's and visiting neighborhood zones (VNZ's) may be a process involving the calculation of frequent calling patterns and the desirability of inclusion within the zone of frequently called commercial and retail establishments. The design may become an art as well as a science. The concept, however, is clearly to provide at least equivalent service to 900 MHZ cordless telephone service and to provide better than equivalence with respect to the mobility of the phone withwired PSTN 100 service.
The Visiting Neighborhood Zone (VNZ)
The LCS service may comprise a first flat monthly rate for a home neighborhood zone105-1 and permit additional air time free calling zones named herein as visiting neighborhood zones (VNZ)115-1,115-2 for an additional nominal flat rate per each additional visiting neighborhood zone. Forsubscriber MS10 whose HNZ is zone105-1,subscriber MS10 may have one or more visiting neighborhood zones (VNZ)115-1,115-2. The VNZ need not be contiguous with the HNZ, for example, as VNZ115-1 is contiguous with HNZ105-1 and VNZ115-2 is not contiguous with HNZ105-1. The VNZ's may overlap other VNZ's or HNZ's more than is shown inFIG. 1. When loosely overlapping, for example, the buffer zone195-1 within the HNZ or buffer zone195-2 within VNZ115-1 may provide subscriber with the ability to travel without loosing a connection between VNZ and VNZ or between HNZ and VNZ. The rate the subscriber must pay may vary with the subscribed-to visiting zone VNZ or simply be constant for each VNZ added. In another rate plan, the first VNZ may be offered at a given rate and the next VNZ may be added at a lesser additional flat rate. What may be a visiting neighborhood zone115-1,115-2 for one subscriber such assubscriber10 will be a home neighborhood zone for another subscriber whose home is located within the zone. Each VNZ is designed in the same way and manner as an HNZ. For example, VNZ115-1 surrounds IBS and antenna site130-1 and VNZ115-2 surrounds IBS and antenna site130-3 in the same way as HNZ105-1 surrounds IBS and antenna site130-2.
The subscriber to LCS service need not select a VNZ for their service that is proximate to or overlaps their HNZ.Subscriber MS10, for example, may choose VNZ115-1 or the more remote VNZ115-2 or both zones in addition to their HNZ105-1. The subscriber, thus, may choose a VNZ115-2 that is considerably remote from their HNZ such as a zone surrounding their place of employment, their school or the neighborhood of a family member. The VNZ selected may be a VNZ so remote from their HNZ that a call from their HNZ to the VNZ might be a toll call if it were a wired line PSTN service call.
Whensubscriber MS10 roams from HNZ105-1 into VNZ115-1 by way of the labeled buffer zones, there will be no charge for airtime and the call in progress will be maintained. Whensubscriber10 roams from HNZ105-1 into VNZ115-2, then, there is no overlapping buffer zone, the call in progress may or may not be maintained. If the LCS subscriber happens to be also a public PCS/cellular service subscriber, the call in progress is handed over to the public PCS/cellular system using public cellular spectrum frequency, there will be no air time charges for the duration of the same call. There exist at least three alternative embodiments for thesubscriber MS10 that travels outside an HNZ or a VNZ to which they have subscribed. These include 1) allowing the subscriber to continue the call they have initiated or have received without additional charge at least for a predetermined length of time, 2) disconnecting the subscriber from the connection they have for a given call after the subscriber leaves their HNZ or subscribed-to VNZ's or3) allowing the call to continue outside their HNZ or subscribed-to VNZ's and billing the subscriber for the air time. When the subscriber is within the third alternative, the subscriber may receive a conventional wireless service such as DPCS. As a subscriber reaches a borderline of a subscribed-to zone, the subscriber may see a lit warning lamp, and/or receive an audible or other alert to their status as is further described in copending application, U.S. patent application Ser. No. 09/223,320, entitled, “Automatic Status Indicators for Neighborhood Cordless Services,” filed on the same day as the present application and invented by A. Chow, R. Miller II, J. Russell, W. Ying, and S. Wang.
The buffer zone is inherent to each HNZ or VNZ. It is the area that defines the perimeter of the zone where service quality may not be at the optimal level, but service can still be rendered. (NOTE: “buffer zones” also exists in cellular/DPCS, they are just the periphery of a cell, the buffer one is not unique to LCS.)
Intra-Building Utilization of HNZ and VNZ, for Example, by an Employer
The concept of HNZ and VNZ can be extended to providing an intra-building or intra-office complex LCS. LCS can be used to provide wireless intra-building communications. A home zone may be one location of a company and visiting zones may be frequently visited locations of the same company within the same company premises or another company premises. Service may be provided at one rate for all wireless use of a company owned phone or phone system at a company location. Moreover, in the spirit of U.S. Pat. No. 4,456,793, hereby incorporated by reference in its entirety, the service may be extended to comprising, for example, an infrared light link between the phones and the IBS and antenna sites. In one embodiment of LCS within a building, different floors of the building, hallways and certain radio frequency shielded or isolated rooms may be equipped with IBS and antenna sites. For example, one sector of one floor may be distinguished from a sector of another floor, if appropriate and depending on the application.
System Architecture
The LCS system architecture will now be described in further detail with reference toFIG. 1. The subscriber'sMS10 may be equipped with a typical DPCS or WS mobile telephone. A DPCS telephone in compliance with IS-136 is preferred in the present invention. Certain enhancements to the basic IS-136 design include audible, light (such as LED), and/or other means of alerting a subscriber of a change in service and/or other status. Without limiting any invention, and by way of example, a set of LEDs may present colored indications of red for no service, a green light for service A, such as conventional cellular or PCS service, a brown light for cellular roaming service and a blue light for service B, the LCS service. By A no service is intended those times when the mobile telephone is powered and has received a user request, but the mobile station is not able to establish a connection with any service provider. When a subscriber is in their HNZ or VNZ, the station may first try to establish an LCS connection and if not possible, due to low signal strength or because the subscriber is out of a zone, the mobile station will try to establish a conventional WS, PCS or DPCS connection, and also can not establish a connection to these systems.
Another enhancement is the capability for the mobile phone to automatically select the appropriate service provider for the given coverage area. For example, if a customer is a subscriber to both cellular/DPCS and LCS service, it would be cumbersome for the user to remember when to select the correct service profile on their MS (for example, such as the IS-136 Number Assignment Module (NAM) A for cellular/DPCS service, and NAM B for LCS service.) The mobile phone working in conjunction with the cellular/DPCS or LCS network intelligence will determine the correct service profile (e.g., IS-136 NAM) that should be active thus permitting the user to transition between services seamlessly and accurately. In other words, whether a subscriber's MIN is ported or not, a subscriber MIN may have a plurality of allocated different services including cellular/DPCS and the present LCS. It will generally be the case that a subscriber will be a subscriber to cellular/DPCS and may not be a subscriber to LCS. But if a subscriber subscribes to LCS, it would be beneficial to also subscribe to DPCS so theirMS10 may be more universally usable.
A user subscribes to multiple wireless services and theMS10 stores the service specific information (e.g., IS-136 NAM) to access the appropriate network. The network(s) associated with all the subscribed services also maintains adatabase ID146 including the subscriber's profile, service subscription, service preferences and priorities. When the customer enters a coverage area and turns on their Mobile Station (MS), theMS10 remembers the last service environment it registered and attempts to use the same profile with the current network. The network recognizes the customer and retrieves the subscriber profile from the database. Based on the user's current location information, the network determines the preferred service profile for the user. If the current coverage area offers the preferred service environment, the network accepts the registration and the MS is ready for service. If the preferred service environment is available in the coverage area but under another MS service profile, the network directs the MS to switch to that service profile. The MS retrieves the correct service profile data and registers for the new services. These services can be offered by the previously attempted network or by a new network. In either case, the (previously attempted or new) network will again determine if the user is in the correct service environment and using the right profile. If so, the network accepts the registration, the MS informs the subscriber of service (audibly and/or visually), and the subscriber begins to use the service.
Referring tosubscriber10 located in HNZ105-1, there is shown an intelligent base station (IBS) and antenna site130-2 at the center of the HNZ105-1 with whichsubscriber10 communicates via their DPCS or WS mobile station. The IBSs130-1,130-2 and130-3 each may comprise a digital software radio station that supports an IS-136 based time division multiple access (TDMA) common air interface. For example, each IBS may support three TDMA frames (this comprises eight IS-136 digital traffic channels, a digital Control channel) and four ISDN-BRI (basic rate interface 2B+D) lines for providing up to eight simultaneous telephone calls. Again by way of example, respective links135-1 and135-2 may couple IBS and antenna sites130-1 and130-2 to remote digital terminals (RDT) (only asingle RDT178 is shown by way of example), for traffic concentration or relay of the calls to a local digital switch (LDS)140-2 via a GR-303trunk interface185, as appropriate. GR-303 relates, for example, to a known remote terminal (RDT) to local digital switch interface comprising an integrated digital loop carrier system and associated requirements. In an alternative embodiment, the IBS130-3 may communicate directly via ISDN BRI link135-3 to a local digital switch140-1.
Preferably, all NSP's are linked together for communication via, for example, an IPbased LCS intranet or virtual private network (VPN) comprising of arouter165. During operation, the IP-based network is utilized for passing call and subscriber registration, mobility management and LCS Operation Administration & Maintenance (OA&M) related information. Also coupled via the IP-based intranet or VPN are connections to an authentication center (AC)190, to a LCS Customer Service Center (CSC)160, a network management and operations center (not shown), and a operations support systems center (not shown).
LDS140-1 or140-2 may preferably comprise any local digital switch known in the art including, but not limited to, a No. 5 ESS switch manufactured by Lucent Technologies, Inc., or a DMS-100 switch manufactured by Northern Telecom which is also called a digital telecommunications switch in the art. These switches perform the switching function necessary to connect LCS subscribers to PSTN customers, WS customers, PCS or DPCS customers or other LCS subscribers wherever situated. A network server platform (NSP) (e.g., NSP145-1,145-2) of an LCS system may be an adjunct to each LDS140-1 and140-2. The NSP may preferably comprise a pair of fully redundant (i.e., for hot standby fault tolerance) Sun Sparc work stations available from Sun Microsystems or other comparable processor programmed as will be further described herein for registration, call processing, and/or call hand-off. Each NSP will have an intelligent database (ID) containing subscriber profile information. Each site may be backed-up by an intelligent spare NSP and ID and program memory backed up on disc or other memory back-up. InFIG. 1, LDS140-2 is coupled to NSP145-1 and LDS140-1 is coupled to NSP145-2. Each NSP operates to effectively control all activities associated with subscriber registration, call setup and tear down, radio frequency engineering, handoffs, feature applications, and operation, administration and maintenance (OA&M) functions. Each respective NSP for a LDS manages all its subtending IBS's and antenna sites. In the depicted example, a single LDS140-2 and NSP145-1 may serve multiple neighborhood zones, in this instance, HNZ105-1 and VNZ115-1. The number of zones served by a single NSP need not be limited to two but may comprise 3 or more.
Preferably, all NSP's are linked together for communication via, for example, an IP-based LCS intranet or virtual private network (VPN) comprising of arouter165. During operation, the IP-based network is utilized for passing call and subscriber registration, mobility management and LCS Operation Administration & Maintenance (OA&M) related information. Also coupled via the IP-based intranet or VPN are connections to an authentication center (AC)190, to a LCS Customer Service Center (CSC)160, a network management and operations center, and a operations support systems center.
Each NSP may have an associated intelligent database (ID). For example, intelligent database146-1 is associated with NSP145-1. The ID may store LCS subscriber profiles, which includes information regarding each LCS subscriber within the HNZ, such as subscribed features and/or calling preferences. The ID also uses the information for communication with other ID's in the event the subscriber has roamed to a VNZ not handled by the associated NSP. For example, in ID146-1, there would exist subscriber profiles for all subscribers in neighborhood zones115-1 and105-1.
The LCS Customer Service Center (LCS CSC)160 may provide a human or automated service representative interface to any potential or existing subscriber. Typically, the LCS CSC may comprise a known service representative position system or voice response system. The LCS CSC supports at least service registration of a MS from a retail location and/or a subscriber, activation for subscribers to LCS service and administration of service (for example, facility, trouble and billing queries).
The LCS authentication center (AC)190 may be a shared resource of the LCS network as is theLCS CSC160. As will be further described herein, a subscriber to LCS may preserve their directory numbers (DN) if they disconnect their wired PSTN number and connect to LCS service. TheLCS AC190 may utilize IS-136 cellular authentication voice encryption (CAVE) to assist in validating and authenticating subscribers and to provide voice privacy and encryption capabilities. ACAC Gateway (GW)170 sits within the IP-based LCS intranet orVPN110 and provides a TCP/IP data link to theSS7 network120. This IP-based network, as explained above, provides access to and interworks with the home location register for registration of MIN-based LCS subscribers for delivery of calls, for example, fromsubscriber150 to LCS subscribers within the neighborhood zones115-1,115-2 and105-1. TheGW170 is responsible for the TCP/IP to SS7/TCAP protocol conversion between the SS7 network and the LCS network. TheGW170 is also responsible for global location management on a perNSP 145 location basis, for example, MIN-based call delivery. TheAC190 supports registration of subscribers, over-the air activation and call hand-off.
For this invention, we use the radio frequency self-configuration algorithm known in, e.g., U.S. Pat. No. 5,809,423 (issued Sep. 15, 1998), U.S. Pat. No. 5,787,352 (issued Jul. 28, 1998), U.S. Pat. No. 5,740,536 (issued Apr. 14, 1998), U.S. Pat. No. 5,513,379 (issued Apr. 30, 1996), U.S. Pat. No. 5,404,574 (issued Apr. 4, 1995), and U.S. Pat. No. 5,345,499 (issued Sep. 6, 1994), all issued to B. Mathilde et al., and all hereby incorporated by reference in their entireties. This algorithm is designed to sniff and designate unused and interference-free traffic and control channels (such as IS-136 Digital Traffic Channels and digital control channels) from the public macrocellular network for use by an underlying/stacked cell use. The algorithm will also be able to detect when the public macrocellular network begins to use these channels, and will automatically adjust by re-selecting another unused frequency. This algorithm greatly simplifies the radio frequency engineering and deployment processes. Without this algorithm, the LCS service will need to reserve radio frequencies specifically for LCS use.
The Intelligent Base Station (IBS) and Antenna Site
The intelligent base station (IBS) can be any currently existing radio base station that is known in the art. The IBS should be capable of performing automatic frequency allocation functions, which are known in the art. For this invention, the preferred embodiment further provides self-configuration in accordance with U.S. Pat. No. 5,724,665. Other patents utilized in the design ofIBS130 include U.S. Pat. Nos. 5,608,780; 5,592,470; 5,574,775 and 5,406,615. Referring toFIG. 2, there is shown a generalized software radio architecture for anIBS130 shown inFIG. 1.Line201 may be an ISDN BRI line as shown or other equivalent data line.Line201, although not shown, may be coupled via a remote_terminal4-80178 to a LDS_140 or directly to the switch perFIG. 1.Line201 is connected to a communications processor ofprocessing module270. Communications processor272 handles all wire line interface control functions. The communications processor is coupled to a network compatibility processing module for handling incoming and outgoing calls requiring either LCS or DPCS or other network compatibility.Main controller274 is coupled to a source/error correction coding/decoding module230 and achannel coding module240. A frequency reference orclock276 is divided to provide all the reference frequencies needed by any other module includingchannel coding module240.
Associated withmain controller274 isvariable memory280,core program memory285 andcritical parameter memory290. Program executable software and data are stored invariable memory280. Boot code and compressed executable code are stored incore program memory285 and non-volatile data are stored incritical parameter memory290.
Networkcompatibility processing module220 comprises acoding engine222 and adecoding engine226. Source/errorcorrection coding module230 comprises adigital signal processor232 and coder algorithm for encoding and adigital signal processor236 anddecoder algorithm236 for decoding. Thechannel coding module240 contains adigital signal processor242 for interfacing with theradio frequency processor250 and includes a modulator/demodulator244.
Radiosignal processing module250 contains a digital upconverter252 and adigital down converter254. When up converting, the output is fed via amixer261 to anamplifier262 for outputting viaantenna267 viafilter263. On the antenna receive side, the received signal is fed viafilter263 andamplifier264 tomixer265 and the result passed todigital down converter254.Frequency synthesis circuit266 provides frequencies at whatever channel frequencies are utilized at a particular point in time.
Antenna267 may be a sectorized antenna system in one embodiment collecting and radiating energy in 800 MHZ and 1800 MHZ spectra or other suitable spectra. Each zone105-1 may comprise several such as three sectors or small cells such that an intra-cell hand-off may be required (as will be discussed in connection withFIG. 6a).
Flexibility in Addressing a Subscriber
An LCS subscriber may elect to discontinue their current PSTN directory number (DN) and use that same number as their LCS address (i.e., Local Number Portability—LNP). Alternatively, the LCS subscriber may receive a new LCS directory number. A third option is for the LCS subscriber to use the mobile identification number (MIN) the subscriber may have as a subscriber to wireless cellular services or personal communications services.
On the air interface side, in this embodiment, each IBS has 9 full-rate TDMA channels. Note: Number of full rate channels for the IBS should be made as a variable for this patent, since the number of radio channels per radio port can be designed according to different services applications and coverage density requirements. IBS can provide as many radio channels as long as it meets the design and service deployment financial criteria. Among these channels, one full-rate channel will be designated as the Digital Control Channel (DCCH) and the remaining 8 channels will be used as the Digital Traffic Channel (DTC). In order to support up to 8 simultaneous conversations, for instance, four ISDN-BRI lines may be used to connect theIBS130 to the LDS140 (FIG. 1). Therefore, an IBS with 8 DTCs can support up to 8 simultaneous calls. When a user subscribes to the LCS services as a DN-based user, the subscriber will be given a DN during registration or service activation (that is, each DN is assigned with a TEI designated to an IBS) and the MS is in effect assigned to a specific IBS in the subscribed HNZ for call delivery purposes. For example,subscriber10 will be assigned to IBS130-2.
Referring again toFIG. 1, sinceIBS130 will be connected to an LDS LCS local digital switch such as the No. 5 ESS or DMS-100digital switch140, a DN based network switching element, the call routing between the local digital switch and the IBS must also be DN-based. The LCS service may use Cellular/DPCS RF infrastructure that is a MSC/MIN based switching platform. Therefore, these two different switching algorithms creates alternative call delivery scenarios for LCS calls. Consider the following LCS call delivery scenarios.
Referring again toFIG. 1, sinceIBS130 will be connected to an LCS local digital switch such as the No. 5 ESS or DMS-100digital switch140, a DN based network switching element, the call routing between the local digital switch and the IBS must also be DN-based. The LCS service may use Cellular/DPCS RF infrastructure that is a MSC/MIN based switching platform. Therefore, these two different switching algorithms creates alternative call delivery scenarios for LCS calls. Consider the following LCS call delivery scenarios:
When a MIN-based LCS subscriber enters an LCS coverage area and receives an incoming call, the localdigital switch140 will not deliver a MIN based call (that is, only an MSC does it). The local NSP, for example, NSP145-1 dynamically assigns a DN that belongs to the IBS130-2 thatMS10 is currently registered to deliver the call.
When the PSTN delivers a call to a DN-based MS, the localdigital switch140 routes the call to the IBS associated with that DN. If the MS is registered with another IBS (which may be referred to as a Target-IBS or T-IBS which could be located in VNZ/HNZ) at that time, the IBS works with the NSP and the local switch to transfer the incoming call to an NSP dynamically assigned DN supported by that T-IBS.
However, if these dynamically assigned DNs as described from the above scenario are assigned previously to a subscriber as a permanent DN, then the LCS system will not immediately be able to deliver the incoming call for lacking of the DN necessary for the local digital switch to process the incoming call. Two out of the 8 DNs of each IBS's 4 ISDN/BRI lines will be reserved for this purpose and used only for call processing purposes by the local digital switch. These dynamically assigned DNs should not be assigned to any subscriber. These dynamically assigned DNs from each IBS will be referred to herein as the call Forward DNs (FDNs). The FDNs will be used for MIN-based call delivery and DN-based roaming capabilities. FDNs are transparent to the end-users; they are used internally by the LCS system. When the local digital switch delivers a call to a MIN-based or visiting DN-based MS, after the NSP locates the MS, the NSP assigns an FDN from the currently registered IBS to the MS in order for the local digital switch to terminate the call.
PSTN call delivery of DN-based mobiles can also occur using the Advanced Intelligent Network. All DNs associated with DN-based mobiles have triggers set on the local digital switch such that when the localdigital switch140 receives the call, the switch requests additional routing instructions from the NSP. The NSP pages the MS to determine its current location, T-IBS. If the MS is registered in its home IBS, the NSP directs the switch to complete the call to the DN. If the MS is registered in another IBS, the NSP assigns an available FDN from T-IBS and directs the switch to forward the call to the T-IBS/FDN.
Numbering Schemes
As already introduced above, there exist three numbering options for LCS services: 1) Use an existing cellular/DPCS MIN, 2) Use a new DN or 3) Use a ported ILEC DN (the subscriber's former wired PSTN service telephone number ported from the local exchange carrier).
Call routing differs slightly between a DN-based MS and a MIN-based MS because the MIN-based MS requires interaction with the HLR while the DN-based MS does not.
Numbering Scheme One: Mobile Identification Number
In this addressing scheme option, the new LCS subscriber is an existing wireless service (WS) customer and desires to keep the same MIN for their new LCS services. These subscribers will be identified in this document as MIN-based LCS subscribers.
Numbering Scheme Two: LCS Service Provider Assigns New LCS Phone Directory Number
In this addressing scheme option, the new subscribers may or may not have an existing IS-136 phone. However, a DN will be assigned by local service representatives. The DN may be programmed into the IS-136 phone via IS-136 based Over-the-air Activation Teleservice (OATS), described subsequently herein. These subscribers will be identified in this document as DN-based LCS subscribers.
Numbering Scheme Three: Ported Local ILEC DN
LCS subscribers who give up their conventional wired service can port their existing residential landline phone numbers (i.e., from their local exchange carrier, ILEC) to LCS services. The DN can be programmed into the IS-136 phone via IS-136 based OATS. These subscribers will be identified in this document also as DN-based LCS subscribers.
The Process of Actuating an LCS Subscriber
A new LCS subscriber may purchase MS apparatus at a retail outlet, preferably, an IS-136 compliant mobile station set with a display. The subscriber buys their phone at a retail outlet and the retail outlet records the purchase in a service provider database,ID146. Manufacturers may or may not provide retail outlets with secure information of the electronic manufacturer's serial number which is secret to the purchaser. A retailer may register a subscriber with a chosen network service provider. The point-of-sale information may include subscriber name, address, credit card number, home directory number (DN), unique electronic serial identification number (MSID), optional personal identification number (PIN) and other verification number. Subscriber data will be referred to herein as a subscriber profile preferably maintained at anNSP ID146. The new subscriber then may alternatively or in addition dial a telephone number provided for customer service center (LCS CSC)160 and is connected to a service representative or a voice interactive response unit known in the art to preregister for services. While a subscriber or retailer can dial from a retail outlet, causing the subscriber to callLCS CSC160 provides an additional validation of subscriber data as a subscriber profile is built. For example, an ANI check can compare a point-of-sale entered DN against a dialed number recovered via ANI and reported at aCSC160. Either the device or a service representative may welcome the new subscriber's call and thank the new subscriber for subscribing to LCS. Either may then request of the subscriber their personal profile data for verifying or completing their subscriber profile which may be verified by known processes with point-of-sale data. The new subscriber is requested to particularly select an option for addressing: 1) do they wish to disconnect their wired PSTN service and reuse the associated DN, 2) obtain a new LCS number or 3) use their MIN from an existing mobile wireless service. The subscriber is also advised of the rate selection opportunities and boundaries of neighborhood zones they may be interested in.
TheLCS CSC160 then processes and temporarily stores all subscriber information in a subscriber profile of anNSP145 including such information as selected home neighborhood zone, visiting neighborhood zone(s) they have subscribed to, calling features, the make and model and electronic serial number of the subscriber's MS (MSID), if available, personal identification number (PIN) and billing address and payment information. The electronic manufacturer's serial number may comprise, for example, less than 34 or 45 bits according to known MIN and IMSI systems. The PIN should be of reasonable length, for example, not to exceed ten alphanumeric characters. All the related subscriber service profile data will be populated into the LCS CSC database at registration and communicated, for example, by the IP-based intranet or VPN to populate a database at LCS authentication center (AC)190. Service profile data is also normally stored here which includes channel frequency tables for, for example, 800 MHz or 1900 MHz services/frequencies available in real time.
Once the new subscriber is validated and their profile completed, theLCS CSC160 generates a unique data word that the subscriber will use later to actuate service, referred to herein as a feature code. Also, a personal identification number which may be of the new subscriber's choice may be mutually agreed upon and stored. The feature code may preferably comprise in combination a manufacturer's serial number, a PIN and a unique sequence of bits, not to exceed a length permissible within the IS-136 OATS message. The unique bit sequence and PIN in combination will be given to the new subscriber so the subscriber may actuate their LCS service automatically via a self-activating and authenticating process to be referred to herein as over-the-air activation teleservice (OATS). The subscriber profile including PIN is further downloaded, in a preferred embodiment, via the IP-based intranet or VPN tointelligent databases146 for their HNZ and any VNZ to which they have subscribed. For example,subscriber10 may be a subscriber to HNZ105-1, VNZ115-1 and VNZ115-2. In such an instance, the subscriber profile will be provided to intelligent databases146-1 and146-2.
Henceforth in the detailed description of the invention, call registration, call processing and call hand-off features will be described inFIGS. 3-7 with reference to generic elements, for example, switch140 or specific elements such as switch140-1 with no intention to be limited by the use of the specific elements ofFIG. 1. The invention is not limited by the specific arrangement of elements ofFIG. 1. However, the reader may find the specific references useful in understanding call processing functions from the viewpoint of one example of anLCS subscriber10.
NAM Downloading and a Self-Actuating LCS Service (OATS)
In order for the subscriber to actuate their LCS service, they should be in their selected HNZ105. For example,new subscriber MS10 must be in the boundaries of their HNZ105-1.Subscriber10 then turns on theirMS10 and enters their unique bit sequence and/or PIN. (The PIN may be used in a similar manner to the manner that PIN's are presently used in wireless services generally, namely, to promote call security and prevent service piracy and, consequently, may be optional). The preamble consists of the MS locking onto the IBS130-2, transmitting an IS-136 Origination message including the feature code/PIN to the IBS130-2 and IBS130-2 forwarding the message viaRDT178, R-303link185, and local digital switch140-2 to its associated intelligent switch controller (NSP)145-1. TheMS10 generates the feature code FC portion of the message from the stored unique MSID, the unique bit sequence given the subscriber (which they enter by using their phone keypad) and their PIN (also using the keypad). The order of bits in the FC should be predetermined so that the FC can be decoded at the NSP. Since the ID146-1, after the subscriber registration process is completed, should have the subscriber profile stored for that subscriber including their feature code, unique bit sequence and/or PIN, the NSP145-1 validates the MS by comparing the entered feature code including PIN with data stored in the ID146-1. A further validation may include the comparison of a collected electronic serial number of the MS with an associated database entry if obtainable from the manufacturer or the retail outlet that sold the phone. If there is no match of all or any of the two (or three), a message may be returned to suggest the subscribercontact LCS CSC160. After the NSP145-1 verifies that the subscriber profile is in the ID146-1, it initiates OATS to activate the MS by sending the Configuration Data Request message to the MS via IBS130-2. The MS responds with Configuration Data Response to the NSP145-1 via IBS130-2. Altogether the preamble and the configuration data request and response comprise process step “a” shown inFIG. 3.
As shown inFIG. 3 step “b”, once a download request message is received by MS, a download response requesting a download is transmitted to NSP145-1. This message includes a request for the downloading of all algorithms and data necessary for LCS service including a number assignment module (NAM) giving the MS its subscriber opted-for address (MIN or DN). After the NSP receives the download response message, step “c” begins and a NAM commit request message is transmitted to the MS. This message instructs the MS to program/populate and commit a designated number assignment module area of memory (NAM(x)) with the downloaded data. If a subscriber decides to use their directory number as the number to be called, NAM(x) will be designated for LCS DN programming, and likewise if the subscriber decides to use their MIN as their reach number, NAM(x) will be designated for LCS MIN programming. Now the registration processes will be discussed for each of the options of MIN or DN based LCS service and when either must register in a visiting neighborhood zone to which the subscriber has subscribed. These processes are carried out in real-time.
Registration Process for a MIN-Based MS
Referring toFIG. 4a, there are shown steps “a”, “b”, “c” and associated with registration processes for a MIN-based subscriber in their home neighborhood zone. In step “a”, the DCCH process consists ofIBS130 broadcasting system-wide andIBS130 specific parameters (such as system andIBS130 identification) on its DCCH and theMS10 locking onto the DCCH when theMS10 powers up. TheMS10 sends an IS-136 registration message to theIBS130.IBS130 forwards the registration message to its associatedNSP145 via the LDSlocal switch140. This message contains IS-136 registration data.
In step “b” thehome zone NSP145 checks the MS's status with its Intelligent Database (ID)146 and determines that the MS is a valid MIN-based LCS service subscriber. Since the MS is MIN-based, NSP must interact with the WS HLR for the registration process. If the optional MS authentication is required (this is determined by the LCS service provider and indicated to theMS10 as one of the DCCH broadcast parameters), the MS IS-136 Registration message will include the authentication information. TheNSP145 will initiate the authentication procedure withLCS AC190 by sending an authentication message viarouter165. TheNSP145 sends an IP-based message containing IS-41-like authentication information to the LCS AC. After successful authentication of the MS, the LCS AC sends an IP-based IS-41-like auth message back to theNSP145.
In step “c”, after successful MS authentication, or if no authentication is required,NSP145 must register theMS10 by sending a registration message to the WS HLR175-2 viagateway170 to update the MS's new location for call delivery purposes. TheNSP145 sends a TCP/IP-based message containing IS41-like registration information to the TCP/IP to SS7 Gateway (GW)170. TheGW170 receives the registration message which also includes the NSP's unique IP address, translates the message into an SS7/TCAP/IS41 REGNOT message and sends it to the HLR175-2.
After a successful registration, the HLR175-2 sends an SS7/TCAP/IS-41 regnot message back to theGW170. The GW receives the IS-41 regnot message, translates the message into a TCP/IP based registration accept req accept message. Since theGW170 stores eachNSP145 unique IP address based on information gathered during MS registration message, the GW sends the registration accept req accept message back toNSP145 based on the NSP's unique IP address. TheNSP145 processes the registration accept req accept message and sends it to theIBS130.NSP145 notes that the mobile is successfully registered and active.
In step “d”, theIBS130 sends an IS-136 Reg. Accept message to theMS10 to complete the MS registration procedures.
There are two possibilities when a MIN-basedMS10 registers in a VNZ115. The first one is where the VNZ and the HNZ are covered by the same NSP (cell101-2 inFIG. 1 comprising HNZ105-1 and VNZ115-1). The second is where the VNZ and the HNZ are covered by different NSPs (HNZ105-1 and VNZ115-2). As far as the LCS system is concerned, both MIN-based registration signaling flows are the same as discussed in the previous section (MIN-based MS registered in the HNZ). The HLR175-2 is updated when the latest registration location occurs regardless of whether theMS10 is in the HNZ or the VNZ.
Registration Process for a DN-Based MS
Referring toFIG. 4b, there is depicted the signaling flow scenario of an MS that uses an assigned directory number (DN) or a ported ILEC DN as the number to be used in the subscribed-to neighborhood LCS zones. Since the MS is DN-based, there is no requirement for interaction with an HLR175-2 during registration. During service activation, the subscriber's profile is downloaded to every NSP/ID that covers the subscribed-to zones, the HNZ and any subscribed-to VNZs. The subscriber has already activated the LCS service via OATS.
The signaling flow shown inFIG. 4bdescribes the scenario where a DN-basedMS10 registers that requires just two steps “a” and “b”. In step “a” the DCCH process consists ofHIBS130 broadcasting system-wide and H-IBS130 specific parameters (such as system andHIBS130 identification) on its DCCH and the MS locking onto the DCCH when the MS powers up. The MS sends an IS-136 registration message to the home zone H-IBS130. The H-IBS130 forwards the registration message to the H-NSP145 via theLDS140. This message contains IS-136 registration data.
In step “b” the H-NSP145 checks the MS's status with the Intelligent Database (ID)146 which already has the subscriber profile, determines that theMS10 is a valid DN-based LCS subscriber. If the optional authentication procedure is required (as determined by the LCS service provider), the H-NSP145 sends an IS-41-like AUTHREQ message in IP format to the LCS Authentication Center (AC)190 in order to authenticate the mobile. When the authentication is successful, theAC190 returns an authentication request response message auth red to the H-NSP145. The H-NSP145 sends the reg. accept message to the H-IBS130. The H-IBS130 sends an IS-136 Reg. Accept message to the MS to complete the MS registration procedures.
When a LCS subscriber roams or otherwise moves to a subscribed-to visiting zone, as far as the subscriber is concerned, the same DN number will be used for all call delivery (i.e., roaming-like situation). A dynamically assignable FDN, described previously, is used to terminate the call.
Referring toFIG. 4c, three steps are required to process a registration of a DN-basedMS10 in a VNZ. In step “a” the DCCH process consists of V-IBS130-3 broadcasting system-wide and V-IBS130-3 specific parameters (such as system and V-IBS130 identification) on its DCCH and the MS locking onto the DCCH when the DN-based MS powers up. TheMS10 sends an IS-136 registration message to the visited V-IBS130. V-IBS130, for example, V-IBS130-3, forwards the REG. REQUEST message to the V-NSP145-2 via the LCS local switch140-1. This message contains IS-136 registration data.
In step “b” the V-NSP145-2 checks the MS's status with the Intelligent Database ID146-2 which has the subscriber profile previously downloaded by theLCS CSC160 and determines that the MS is a valid DN-based LCS subscriber. The V-NSP145-2 sends an IS-41-like authreq message in IP format to theAC190 for subscriber authentication. TheAC190 validates the subscriber with its internal database and returns an authreq response message back to the V-NSP145-2.
In step “c” the V-NSP145-2 sends a registration notification message to H-NSP145-1 to indicate the new location of the MS for proper delivery of incoming calls to the MS. The H-NSP145-1 records the current MS location as being in a subscribed-to visiting zone115-2. The H-NSP145-1 sends a reg. notification response message to the V-NSP145-2. In return, the V-NSP145-2 sends registration accept message to the V-IBS130-3. V-IBS130-3 sends an IS-136 Reg. Accept message to the visiting MS to complete the registration process.
Call Delivery to an LCS Subscriber
Call processing of a call to or from a subscriber visiting a neighborhood zone involves the utilization of one, two or more reserved forwarding directory numbers (FDN's) in the visited zone. For example, thesubscriber MS10 that visits VNZ115-2 will be dynamically assigned one of these reserved FDN's while they are in the visited zone. These same FDN's may be used by another subscriber when that subscriber visits the zone from their home zone after the first subscriber no longer needs it.
The call delivery process from an originating switch in thePSTN100 to a MIN-based LCS subscriber are shown inFIG. 5a. To the extent possible, similar reference characters are borrowed fromFIG. 1 to represent similar elements for an incoming call tosubscriber MS10. Process step “a” takes the incoming call request to the home zone NSP145-1. The LDS140-3 ofPSTN100 processes the MIN-based incoming call and sends an ISUP Initial Address Message (IAM) to a PSTN-basedMSC180. TheMSC180 provides services and coordination between mobile users in the public cellular network and between the mobile users and the external network such asPSTN100. When a PSTN user dials a MIN, the PSTN LDS will always route the call to the MSC switch for call delivery. One way to look at the phonenetworks including PSTN100, public cellular network and LCS is that all the switches from each network are fully connected and they all have connections to the Common Signaling Network Number 7 (SS7). The Mobile Switching Center,MSC180, provides switching functions for the cellular network and coordinates the establishments of calls to and from cellular/DPCS subscriber. The MSC interfaces with the cellular network(s) and the public switch networks. Since the MSC does not have the MIN-based user currently registered, the MSC sends a SS7/TCAPfIS-41 location request (LOCREQ) message to HLR175-2. The HLR175-2 knows the current registration location of the MIN-based MS because of prior registration notification from the home zone NSP (H-NSP)145-1 via the gateway (GW)170. HLR175-2 sends a SS7/TCAP/IS-41 route request (ROUTREQ) message to the H-NSP145-1 via theGW170 for routing instructions to theMS10. TheGW170 translates the message to an IP message and sends it to the H-NSP145-1 (ROUTE REQ (MIN)). This completes process step “a”.
Process step “b” involves letting theMSC180 know the result. The H-NSP145-1 verifies that theMS10 is still registered in the home zone and is presently idle. H-NSP145-1 reserves an available forward directory number (FDN) and a B-channel for its transmission in the home zone IBS (H-IBS)130-2. Then, H-NSP145-1 returns a route request response message including the reserved FDN to theGW170. If no FDN is available, of course, the H-NSP145-1 rejects the request. Continuing a favorable call-completion scenario, theGW170 translates the IP message to a SS7/TCAP/IS-41 routreq response message and sends it to the HLR175-2. This completes process “b”.
Process step “c” takes the call from HLR175-2 to a set-up request of H-IBS130-2. The HLR returns the reserved FDN information in the IS-41 TCAP locreq response message to the MSC. TheMSC180 initiates call setup by sending an ISUP IAM message to the LDS140-2 based on the FDN. The LDS140-2 sends a Q.931 call setup message to the H-IBS130-2 based on the reserved DN. This concludes process “c”.
Process step “d” relates to acknowledgment. The H-IBS130-2 sends a call request message to the H-NSP145-2 to validate the call request. Note: H-NSP145-1 may initiate IS-136 authentication procedure when necessary. The H-NSP145-1 uses the ID database146-1 to locate the record of FDN-to-MIN mapping to validate the call. If the request is valid and RF resources are available, H-NSP145-1 will reserve a digital traffic channel (DTC) for call delivery. H-NSP145-1 then sends a call request ack message with the MIN, DTC, and B-channel (reserved when the FDN was assigned to the call) to the H-IBS130-2. If the call request is not valid or no resources are available, the H-NSP145-21 will return a call request nack (stands for negative acknowledgment) and the H-IBS130-2 will release the call. This concludes process “d”.
In process step “e”, the H-IBS130-2 starts to page the MIN-basedMS10. H-NSPH-IBS (Note: The IS-136 MS paging process is as follows: the H-IBS130-2 broadcasts an IS-136 page for the MIN-basedMS10. TheMS10 must respond with an IS-136 page response message within a specified time period. If theMS10 does not respond, the H-IBS130-2 will release the call.) After theMS10 successfully responds to the page, the H-IBS130-2 sends a Q.931 call proceeding message to the LDS140-2.
In process step “f”, the H-IBS130-2 sends a DTC designation message to theMS10 and verifies the MS is on the DTC by monitoring the returning DVCC code status change. After theMS10 locks onto the DTC (DVCC status change), the H-IBS130-2 sends an IS-136 alert with info message to theMS10 to initiate a ringing indication to the user. H-IBS130-2 also sends a Q.931 alert message to the LDS140-2. The LDS140-2 sends an ISUP address complete message (ACM) to the MSC to complete the end-to-end call connection. TheMSC180 sends an ISUP ACM message to thePSTN100.
Process step “g” is similar to a cellular/DPCS connect process. The LDS140-2 generates alerting (ring back tone) to the originating user. When the MIN-baseduser10 picks up the call and theMS10 sends an IS-136 connect message to the H-IBS130-2, the H-IBS130-2 sends a Q.931 connect message to the LDS140-2. The LDS140-2 sends an ISUP address answer message (ANM) to the MSC. TheMSC180 sends an ISUP ANM message to the PSTN switch140-3, the PSTN switch140-3 connects the caller and thus the voice path is established and completes the call delivery process.
Call Delivery to a DN-Based Subscriber, the DN Being Assigned for LCS
FIG. 5bdescribes the signaling flow scenario of a PSTN caller dialing the LCS subscriber's DN when the DN is registered with the H-IBS in the HNZ. In step “a” an originating PSTN switch (somewhere in PSTN100) processes the DN-based incoming call and sends an ISUP IAM message to the HNZ LP (H-LDS)140-2 based on the DN dialed. The H-LDS140-2 sends a Q.931 call setup message to the H-IBS130-2 based on the DN dialed. The H-IBS130-2 sends a CALL REQUEST message to the H-NSP145-1 to validate the call request. The H-NSP145-1 may initiate an authentication procedure with anAC190 when and if necessary.
In step “b” the H-NSP145-1 validates the call by searching the ID146-1 and discovers that theMS10 is registered in its home IBS, H-IBS130-2. If the request is valid and resources are available, H-NSP145-1 will reserve a DTC and a B-channel. H-NSP145-1 then sends a call request ack message with the resource information to the H-IBS130-2. H-IBS130-2 starts to page the DN-based MS. If the call request is not valid or no resources are available, the H-NSP145-1 will return a call request nack and the H-IBS130-2 will reject the call.
The IS-136 MS paging process is as follows: the H-IBS130-2 broadcasts an IS-136 page for the DN-based MS. TheMS10 must respond with an IS-136 page response within a specified time period. If theMS10 does not respond, the H-IBS130-2 will release the call.
After successfully paging the MS, the H-IBS130-2 then sends a Q.931 call proceeding message to the H-LDS140-2. This connects the B-channel to the H-LDS140-2.
In step “c” the H-IBS130-2 sends a DTC designation message to the MS and verifies the MS is on the DTC by monitoring the returning DVCC code status change.
In step “d” after the MS locks onto the DTC (DVCC status change), the H-IBS130-2 sends an IS-136 alert with info message to the MS to initiate ringing indication to the user. It also sends a Q.931 alert message to the LDS, H-LDS140-2. The H-LDS140-2 sends an ISUP address complete message (ACM) to the PSTN switch to complete the end-to-end connection. The H-LDS140-2 generates alerting (ringback tone) to the originating user.
In step “e” when the DN-based MS user picks up the call, the MS sends an IS-136 connect message to the H-IBS130-2. The H-IBS130-2 sends a Q.931 connect message to the H-LDS140-2. The H-LDS140-2 sends an ISUP address answer message (ANM) to the PSTN switch, the PSTN switch connects the caller and thus the voice path is established, completing the incoming call delivery process.
The called MS's DN may be registered with a visited V-NSP, for example, V-NSP145-2 in the VNZ115-2. Referring toFIG. 5c, step “a” the originating PSTN switch processes the DNbased incoming call by sending an ISUP Initial Address Message (IAM) to the H-LDS140-2 based on the DN dialed. The H-NSP145-1 sends a Q.931 call setup message to the H-LDS140-2 based on the DN dialed. The H-IBS130-2 sends a CALL REQUEST message to the H-NSP145-1 to validate the call request. The H-NSP145-1 may initiate authentication procedure when necessary withAC190.
In step “b” the H-NSP145-1 validates the call by searching the ID146-1 and discovers that the MS is currently registered in a subscribed-to VNZ (V-NSP)115-2. Consequently, H-NSP145-1 sends an IS-41-like ROUTREQ message in IP format to the V-NSP145-2 for routing instructions to the DN-based MS. The V-NSP145-2 confirms via ID146-2 that the MS is still registered and idle in V-IBS130-3. It reserves an available FDN from V-IBS130-3, and returns a route request response message including FDN to the H-NSP145-1. The V-NSP145-2 also reserves a B-channel for the FDN. If no FDNs are available, V-NSP145-2 rejects the call which ultimately results in rejecting the call to the originating user. The H-NSP145-1 sends call req ack to the H-IBS130-2 with an indication to forward the call to the FDN from V-NSP145-2.
In step “c” the H-IBS130-2 sends a Q.932 facility message to the H-LDS140-2 to reroute the call to the forward FDN. The H-LDS140-2 sends the facility return result in a disconnect message for response to the facility invoke message to the H-IBS130-2; on receipt of the disconnect message, the H-IBS130-2 sends a release message to the H-LDS140-2, and the H-LDS140-2 sends a release complete message in return. Immediately after sending the disconnect message, the H-LDS140-2 sends an ISUP IAM message to the V-LDS140-1 based on the FDN.
In step “d” the V-LDS140-1 now has the call. The V-LDS140-1 sends a Q.931 call setup message to the V-IBS130-3 based on the FDN. The V-IBS130-3 sends a call request message to the V-NSP145-2 to validate the call request. The V-NSP145-2 may initiate authentication procedures withAC190 when necessary. The V-NSP145-2 uses the ID146-2 database to locate the record of FDN-to-DN mapping to validate the call. If the request is valid, and RF resources are available, the V-NSP145-2 reserves the RF resource, the DTC, for call delivery. The V-NSP145-2 then sends a call request ack message with the DTC and B-channel (reserved when the FDN was assigned to the call) to the V-IBS130-3. The V-IBS130-3 starts to page the DN-based MS (the paging process is described above in respect toFIG. 5b, step “b”). If the call request was not valid or if no resources are available, the V-NSP145-2 will return a call req nack and the V-IBS130-3 will release the call. The V-IBS130-3 sends a Q.931 call proceeding message to the V-LDS140-1 after successfully paging the MS. This connects the B-channel to the V-LDS140-1.
In step “e” the V-IBS130-3 sends a DTC designation message to the MS and verifies the MS is on the DTC by monitoring the returning DVCC code status change. After the MS locks onto the DTC (DVCC code status change), the V-IBS130-3 sends an IS-136 alert with info message to the MS to indicate ringing to the user. The V-IBS130-3 also sends a Q.931 alert message to the V-LDS140-1. The V-LDS140-1 sends an ISUP address complete message (ACM) to the H-LDS140-2 and the H-LDS140-2 sends an ISUP ACM message to thePSTN100 to complete the end-to-end connection. The V-LDS140-1 generates alerting (ringback tone) to the originating user.
In step ‘f’ when the DN-based visiting subscriber picks up the call, the MS sends an IS-136 connect message to the V-IBS130-3. The V-IBS130-3 sends a Q.931 connect message to the V-LDS140-1. The V-LDS140-1 sends an ISUP address answer message (ANM) to the H-LDS140-2 and the H-LDS140-2 sends an ISUP ANM message to the PSTN switch. The PSTN switch connects the caller and thus the new VNZ voice path is established.
Call Delivery to a DN-Based Subscriber, the DN Being a Ported Number from ILEC
FIG. 5ddescribes the signaling flow scenario of a PSTN caller dialing the DN-based LCS subscriber when the called MS's DN is a ported number from ILEC. As already described, LCS subscribers may carry their existing residential landline phone numbers to the subscribed HNZ for LCS services. The MS is registered with the H-IBS130-2 in the HNZ105-1. In step “a” the originating PSTN switch receives a call with a ported DN; so the PSTN switch sends a TCAP LRN REQUEST message to the STP for a 6-digit LRN Global Tide Translation (GTT) for call routing information. The STP performs GTT on the DN to determine the point code of the appropriate SCP database and sends a TCAP LRN routing instruction request to the SCP. The SCP's LRN application does 10-digit translation to determine the LRN of the terminating office and sends an LRN reply message to the originating PSTN switch based on the originating point code in the incoming message. The STP forwards the LRN reply to the PSTN switch without changing any protocol elements.
In step “b” the originating PSTN switch receives the LRN reply message, processes the message and uses the information for call routing. The PSTN switch sends an ISUP LAM message to the HNZ LDS (H-LDS)140-2 based on the LRN reply. The H-LDS140-2 sends a Q.931 call setup message to the H-IBS130-2 based on DN.
In step “c” the H-IBS130-2 sends a CALL REQUEST message to the H-NSP145-1 to validate the call request. The H-NSP145-1 may initiate an authentication procedure withAC190 when necessary. The H-NSP145-1 validates the call request by searching the ID146-1 and discovers that the MS is currently registered in its H-IBS130-2. If the request is valid and resources are available, H-NSP145-1 will reserve the DTC and the B-channel. H-NSP145-1 then sends a call request ack message with the resource information to the H-IBS130-2. H-IBS130-2 starts to page the DN-based MS. If the call request is not valid or no resources are available, the H-NSP145-1 will return a call request nack and the H-IBS130-2 will reject the call. The IS-136 MS paging process has already been described above.
In step “d” the H-IBS130-2 sends a Q.931 call proceeding message to the H-LDS140-2 after successfully paging the MS. This connects the B-channel to the H-LDS140-2. The H-IBS130-2 sends a DTC designation message to the MS and verifies the MS is on the DTC by monitoring the returning DVCC code status change. After the MS locks onto the DTC (DVCC status change), the H-IBS130-2 sends an IS-136 alert with info message to the MS to indicate ringing to the user. H-IBS130-2 also sends a Q.931 alert message to the H-LDS140-2. The H-LDS140-2 sends an ISUP address complete message (ACM) to the originating PSTN switch to complete the end-to-end connection.
In step “e” the H-LDS140-2 generates the alerting (ring back tone) to the originating user. When the DN-based MS user picks up the call, the MS sends a IS-136 connect message to the H-IBS130-2. The H-IBS130-2 sends a Q.931 connect message to the H-LDS140-2. The H-LDS140-2 sends an ISUP address answer message (ANM) to the PSTN switch, the PSTN switch connects the caller and thus the voice path is established, completing the call delivery process.
The MS with a DN carried from a local exchange carrier (LEC) may be registered in the VNZ, for example, VNZ115-2. Referring toFIG. 5e, step “a” the originating PSTN switch receives a call with a ported DN and the PSTN switch sends a TCAP LRN REQUEST message to the STP for a 6-digit LRN Global Title Translation (GTT) for call routing information. The STP performs GTT on the DN to determine the point code of the appropriate SCP database and sends a TCAP LRN routing instruction request to the SCP. The SCP's LRN application does a 10-digit translation to determine the LRN of the terminating office, sends a LRN reply message to the PSTN switch based on the originating point code in the incoming message. The STP forwards the LRN reply to PSTN switch without changing any protocol elements.
In step “b” the originating PSTN switch receives the LRN reply message, processes the message and uses the information for call routing. The PSTN switch sends an ISUP IAM message to the HNZ LDS (H-LDS)140-2 based on LRN reply. The H-LDS140-2 sends a Q.931 setup message to the H-IBS130-2 based on the DN. The H-IBS130-2 sends a CALL REQUEST message to the H-NSP145-1 to validate the call.
In step “c” the H-NSP145-1 validates the call by searching the ID146-1, and discovers that the MS is registered in a subscribed VNZ (V-NSP)115-2. It sends an IS-41-like ROUTREQ message in IP format to the V-NSP145-2 for routing instructions to the DN-based MS. The V-NSP145-2 verifies via the ID146-2 that the MS is still registered and is idle in V-IBS130-3. It reserves an available FDN from V-IBS130-3, and returns a route request response message including FDN to the H-NSP145-1. The V-NSP145-2 also reserves a B-channel for the FDN. If no FDNs are available, the V-NSP145-2 rejects the call which ultimately results in rejecting the call to the originating user.
In step “d” the H-NSP145-1 sends a call req ack message to the H-IBS130-2 with an indication to forward the call to the FDN from the V-NSP145-2. The H-IBS130-2 sends a Q.932 facility message to the H-LDS140-2 to reroute the call to the DN-based MS using FDN. The H-LDS140-2 sends the facility return result in a disconnect message for response to the facility invoke message to the H-IBS130-2; on receipt of the disconnect message, the H-IBS130-2 sends a release message to the H-LDS140-2, and H-LDS140-2 sends a release complete message in return. Immediately after sending the disconnect message, the H-LDS140-2 sends an ISUP IAM message to the V-LDS140-1 based on the FDN.
In step “e” the V-LDS140-1 now has the call. V-LDS140-1 sends a Q.931 setup message to the V-IBS130-3 based on the FDN. The V-IBS130-3 sends a call request message to the V-NSP145-2 to validate the call. As before, the VH-NSP145-2 may initiate authentication procedures via an authentication center when and if necessary. The V-NSP145-2 uses the ID database146-2 to locate the record of FDN-to-DN mapping to validate the call. If the request is valid and resources are available, V-NSP145-2 will reserve the DTC and the B-channel (reserved when the FDN was assigned to the call). V-NSP145-2 then sends a call request ack message with the resource information to the V-IBS130-3. V-IBS130-3 starts to page the DN-based MS. If the call request is not valid or no resources are available, the V-NSP145-2 will return a call request nack and the V-IBS130-3 will reject the call. Briefly, the IS-136 MS paging process is as follows: the V-IBS130-3 broadcasts an IS-136 page for the DN-based MS. The MS must respond with an IS-136 page response within a specified time period. If the MS does not respond, the V-IBS130-3 will release the call. The V-IBS130-3 sends a Q.931 call proceeding message to the V-LDS140-1 after successfully paging the MS. This connects the B-channel to the V-LDS140-1.
In step “f” the V-IBS130-3 sends a DTC designation message to the MS and verifies the MS is on the DTC by monitoring the returning DVCC code status change. After the MS locks onto the DTC (DVCC status change), the V-IBS130-3 sends an IS-136 alert with info message to the MS to indicate ringing to the user. It also sends a Q.931 alert message to the V-LDS140-1. The V-LDS140-1 sends an ISUP address complete message (ACM) to the H-LDS140-2, and the H-LDS140-2 sends an ISUP ACM message to thePSTN100 originating switch to complete the end-to-end connection. The V-LDS140-1 generates the alerting (ring back tone) to the originating user.
In step “g” when the DN-based visiting subscriber picks up the call, the MS sends an IS-136 connect message to the V-IBS130-3. The V-IBS130-3 sends a Q.931 connect message to the V-LDS140-1. The V-LDS140-1 sends an ISUP address answer message (ANM) to the H-LDS140-2. The H-LDS140-2 sends an ISUP ANM message to the PSTN switch. The PSTN switch connects the caller and thus the new voice path is established.
Advanced Intelligent Network triggers may also be used for call delivery for DN based MS. The LCS subscriber's DN is provisioned for the AIN Termination Attempt Trigger (TAT) in the serving LDS. When a call is delivered to the LDS for the subscriber's DN, the TAT is encountered and the LDS sends a call treatment query message to the NSP. The NSP locates the mobile in their serving IBS and reserves an FDN in this IBS. NSP then directs theLDS140 to deliver the call to the MS based on the FDN.
Referring toFIG. 5f, step “a”, a PSTN user dials a LCS subscriber's DN. TheLDS140 receives the ISUP LAM message from PSTN. The incoming call to a TAT provisioned DN directs theLDS140 to request for routing instructions from H-NSP. H-NSP finds that the subscriber's MS is active in an IBS, and pages theMS10.
In step “b”, after theMS10 responds to the page, H-NSP directs LDS to forward the call to the FDN of the serving IBS.
In step “c”,LDS140 sends Q.931 Setup message to the IBS. IBS sends Digital Traffic Channel (DTC) Designation message toMS10 and sends Q.931 Call Proceeding message to the LDS. MS tunes to the traffic channel. IBS then detects the MS is on the traffic channel via DVCC status change.IBS130 alerts theMS10 and theMS10 acknowledges.
In step “d”,IBS130 sends ISDN Alerting message to LDS.LDS140 sends an ISUP ACM message to the PSTN and an alerting ringback to the calling mobile station. When the MS answers, IBS sends Q.931 Connect message to LDS. LDS then sends ISUP ANM message to PSTN switch and cuts through the voice path.
The Intra-Cell Mobile Assisted HandOff (MAHO)
There are two handoffs possible in LCS service: an intra-cell mobile assisted hand-off (MAHO) and an inter-cell hand-off (for example, from an HNZ105-1 to a VNZ115-1 via a buffer zone). This section describes the end-to-end signaling flow scenario of Mobile Assisted HandOff (MAHO) between different RF channels within an IBS such as IBS130-2 or cell such as home neighborhood zone (HNZ)105-1.
In this invention, the preferred method is to use the radio frequency self-configuration algorithms as described above, which may be implemented in the LCS network system to utilize the available RF channels that are not used by the primary macro-cellular system (represented by WS cell101-2 inFIG. 1) for intra-cell hand-off. However, such a radio frequency self-configuration is an option and not mandatory for this invention.
When the LCS system does use a radio frequency self configuration algorithm, whenever the primary system starts to use the same RF channel, the radio in the LCS system and the active user may be required to move to another RF channel through the assistance of the RF self-configuration subsystem. As already described, each zone in a LCS system preferably has only oneIBS130. Once a RF channel is determined as noisy (e.g., from data received signal strength, RSSI, and/or the bit error rate), all the TDMA time slots within the channel may be considered to be noisy. In the intra-cell handoff scenario, therefore, all the active mobile stations using the noisy channel would re-tune to a new frequency.
Intra-cell handoff is attempted when the BER is high (bad) and the RSSI is good. (The threshold values for the BER and the RSSI may be provided by the RF Self-configuration subsystem). Upon receiving the request from theIBS130 when handoff is needed, the RF Self-configuration subsystem may perform a calculation and return a new carrier frequency to theIBS130 and the active MSs to re-tune to, or it may return a reject message when no carrier is available. If a new channel is available, theIBS130 must re-tune to that new channel before theMS10 does.
When no new channel is available for the intra-cell handoff (i.e., the intra-cell handoff attempt has failed) but the RSSI from a neighboringIBS130 is acceptable, the LCS system may attempt to handoff the active MSs to the neighboring IBS (V-IBS)130 through intra-NSP handoff procedures (described in the next section).
If no channel is available for the handoff and the RSSI and BER measurement results of the current channel reach threshold values, the call may be dropped. TheMS10 may be capable of performing the IS-136 channel measurement (RSSI and BER) procedures. Units of RF measurement used by theMS10 can be normalized by theIBS130 if they are not consistent with IBS RF measurement units. DTX Control is disabled (Discontinuous Transmission not supported). The IS-136 Channel Quality messages are sent over the SACCH.
The carrier channels may always be turned on even when the channel is not currently used by any MS. Therefore, it is possible for theMS10 to perform channel measurement on these channels. No reconfiguration of the ISDN connection as a result of the intra-cell handoff is necessary.
Referring toFIG. 6a, step “a” an active call between theMS10 and the PSTN user (or another MS user) involving an LDS (for example, LDS140-2) and an IBS, such as IBS130-2 is in progress using air interface channel A.
In step “b” the RF Self-configuration subsystem in the IBS130-2 performs an RF Self-configuration algorithm and exchanges information with other IBSs (in the present example, IBS130-1) in the subscribed-to zones.
In step “c” based on the information collected by the algorithm the RF Self-configuration the subsystem determines which RF channels have to be measured by the MS. The IBS130-2 sends the Measurement order (over the FACCH) to the registeredMS10. TheMS10 acknowledges the instruction by sending the Measurement order ACK message back to the IBS130-2 (over the FACCH). TheMS10 follows the MAHO procedures defined in the IS-136.2 specification and sends channel quality message to the IBS130 (over the SACCH) in response to the Measurement order message.
In step “d” when the IBS130-2 detects an intra-cell handoff condition based on the received channel quality message (i.e., BER and RSSI), the IBS130-2 sends an intra-cell handoff request for a new channel to the RF Self-configuration subsystem. The subsystem performs a calculation and/or sends a new carrier frequency information to the IBS130-2. Upon receiving the information, the IBS130-2 sends a handoff command, in accordance with the IS-136.2 specification, to the MS (over the FACCH) requesting the MS to re-tune to a new RF channel (along with other channel assignment information). Handoff ACK is sent by the MS (over the FACCH). Responsive to receiving the acknowledgment from the MS, the IBS130-2 re-tunes to the new RF (channel B).
In step “e” the MS turns off its transmitter, adjusts its power level, tunes to a new RF channel b, sets stored DVCC to the DVCC information element of the handoff message, sets the transmit and receive rate to that indicated by the Rate information element, and sets the time slot to that indicated by the Timeslot Indicator information element. Once synchronized, the MS turns on its transmitter. The IBS130-2 then detects that theMS10 is on the new channel via DVCC status change. Upon detecting theMS10 on new channel, the IBS130-2 sends Handoff Result messages to the NSP145-1. The handoff is completed, and the call continues.
An Intra-NSP Inter-Cell MAHO(HNZ to Contiguous VNZ or VNZ to Contiguous VNZ))
When an active call is in progress, the MS measures the neighboring setup channels and the current active channel for RSSI and BER among other things. These IS-136 Channel Quality measurements help the system determine if the MAHO procedure is necessary to preserve the call. Furthermore, in order to perform a smooth, lossless handoff between the IBSs, LCS uses the Directed Call Pickup (DPU) with Barge-in feature of theLDS140. DPU establishes a three-way call without disturbing the current call.
Referring toFIG. 6b, step “a” a mobile station is on an active call. H-IBS130-2 directs the MS to start measuring the channel quality of the neighboring control channels and the current channel. The MS acknowledges the order and starts sending the IS-136 Channel Quality messages.
In step “b”, when H-IBS130-2 detects a handoff condition based on the received channel quality messages (a low threshold value is reached), the H-IBS130-2 sends a handoff request message. This message includes a priority list of the neighboring IBSs (V-IBS) such as V-IBS130-1 along with the serving mobile MSID to the H-NSP145-1. H-IBS130-2 also starts the handoff request timer (T1). Once the H-NSP145-1 receives the handoff request message, the HNSP145-1 will start at the top of the neighboring IBS (V-IBS) list and check the radio channel and B-channel availability of each entry. When an available neighboring IBS (V-IBS), such as V-IBS130-1 is found, H-NSP130-2 will request the V-IBS130-ito prepare for a handoff for the MS (MSID) and starts timer T2. In response, the V-IBS130-1 will reserve the B-channel and the RF resources and start to initiate a three-way call using the directed call pickup with barge-in. IBS n sends a Q.931 Setup message to LDS140-2 that includes a feature activation code for DPU and the DN for theIBS130 to barge-in upon, IBSo. IBS n130-1 then waits for the LDS to indicate that the call has connected to IBSo130-2 via Q.931 set up ACK, Q.931 call Proceeding and Q.931 Connect. IBSn130-1 then sends a Handoff Directive to IBSo130-2 to inform the IBS that IBSn130-1 has successfully established a three-way call (DPU) as well as sending a Q.931 Connect ACK toLDS140.
In step “c”, after receiving the Handoff Directive, IBSo130-2 cancels timer T1. IBSosends an IS-136 Handoff order to the MS requesting it to retune to the new RF channel on IBSn130-1. After the MS acknowledges the order, IBSo130-2 starts to release the ISDN B-channel via Q.931 disconnect. LDS140-2 returns a Q.931 release to IBSo130-2, which then sends Q.931 release complete to LDS140-2. Simultaneously IBSo130-2 informs H-NSP145-1 that it has completed the handoff to the new IBS, IBSn130-1. H-NSP145-1 acknowledges this notification.
In step “d”, when the MS arrives on the new channel, detected by IBSn130-1 by the DVCC status change, IBSn130-1 sends a Handoff Result message to H-NSP145-1. H-NSP145-1 notes that the handoff is completed to the new IBS and cancels timer T2. Voice path is established via a new route and the call continues.
Call Processing for an LCS Subscriber Who Makes an Outgoing Call
This section describes the signaling flow scenario for a call originated by the LCS subscriber from a subscribed-to neighborhood zone.
Referring toFIG. 7, step “a” the subscriber, for example,subscriber10 in HNZ105-1 dials a number on the MS; the MS sends an IS-136 origination message to the serving IBS130-2. The IBS130-2 sends a call request message to the NSP145-1 to validate the call. The NSP145-1 may initiate an authentication procedure viaAC190 when necessary. The NSP145-1 validates the MS via its associated Intelligent Database (ID)146-1. If the resources are available, it reserves a B-channel and DTC, and sends a call req ack message to the IBS130-2 with the resource information. If no resources are available, NSP145-1 send a call req nack and the IBS130-2 rejects the call.
In step “b” the IBS130-2 sends a Q.931 call setup message to the LDS140-2. The LDS140-2 sends an ISUP IAM message to the destination switch in thePSTN100 to initiate end-to-end connection. The LDS140-2 sends a Q.931 call proceeding message to the IBS130-2 to connect the B-channel to the LDS140-2.
In step “c” the IBS130-2 sends an IS-136 DTC designation message to the MS and verifies the MS is on the DTC by monitoring the returning DVCC code status change. The LDS140-2 receives an ISUP ACM message from thePSTN switch100 and sends a Q.931 alert message to the IBS130-2. The ring back tone is established between the LDS140-2 and the MS.
Finally, in step “d” the LDS140-2 receives an ISUP ANM message from thePSTN switch100 when the destination user finally answers. The LDS140-2 sends a Q.931 connect message to the IBS130-2 to complete the end-to-end connection. The IBS130-2 sends an IS-136 connect message to the MS and the voice path is established, thus completing the outgoing call process.
Thus, there has been described a complete system for providing a new local cordless-type services where a mobile subscriber may receive and make free calls within their subscribed-to neighborhood zones.

Claims (2)

1. A network architecture for providing local cordless-type service to a plurality of wireless telephone terminals, comprising:
a plurality of directory numbers (DNs) coupled by respective bearer channels to a line side of a digital telecommunications switch, each of said bearer channels assigned from a pool of available radio frequencies over which one of said plurality of wireless telephone terminals sends and receives radio frequency signals;
at least one intelligent base station (IBS) for receiving radio frequency signals from said plurality of wireless telephone terminals; and
a local digital telecommunications switch coupled to said at least one IBS, said local digital telecommunications switch providing a bearer channel line interface to said IBS, said local digital telecommunications switch further providing a trunk side interface to a public switched telecommunications network, wherein said RDT communicates with said digital telecommunication switch using a GR-303 standard interface.
2. A method for providing local cordless-type service, comprising the steps of:
receiving a telecommunications call in a neighborhood zone for which a subscriber has selected said local cordless-type service;
assigning at least one directory number (DN) to each of a plurality of wireless telephone terminals for which said local cordless-type service has been initiated;
assigning, by one of a plurality of intelligent base stations (IBSs), a bearer channel from a pool of available radio frequencies to said telecommunications call initiated by said subscriber using one of said plurality of wireless telephone terminals; and
processing, by one of said IBSs, of said telecommunications call via a local digital telecommunications switch in communication with a public switched telecommunications network (PSTN), said digital telecommunications switch providing a bearer channel line interface to said IBS, said digital telecommunications switch further providing a trunk side interface to said PSTN, wherein a remote digital terminal (RDT) is coupled to the plurality of IBSs and provides bearer channel interfaces over an ISDN/BRI bearer channel between each of the IBSs, and further wherein said RDT functions as a concentrator for radio frequency signals sent from said plurality of IBSs over said ISDN/BRI bearer channel;
wherein the method further comprises the step of communicating between said RDT and said digital telecommunications switch using a GR303 standard.
US11/175,8251998-12-302005-07-06Method and apparatus for over-the-air activation of neighborhood cordless-type servicesExpired - Fee RelatedUS7181207B1 (en)

Priority Applications (4)

Application NumberPriority DateFiling DateTitle
US11/175,825US7181207B1 (en)1998-12-302005-07-06Method and apparatus for over-the-air activation of neighborhood cordless-type services
US11/649,650US8712405B1 (en)1998-12-302007-01-04Method and apparatus for over-the-air activation of neighborhood cordless-type services
US14/263,997US9578590B2 (en)1998-12-302014-04-28Method and apparatus for over-the-air activation of neighborhood cordless services
US15/437,295US9942417B2 (en)1998-12-302017-02-20Method and apparatus for over-the-air activation of neighborhood cordless-type services

Applications Claiming Priority (3)

Application NumberPriority DateFiling DateTitle
US09/223,318US6594488B1 (en)1998-12-301998-12-30Method and apparatus for over-the-air activation of neighborhood cordless-type services
US09/987,610US6980817B1 (en)1998-12-302001-11-15Method and apparatus of a network architecture for providing a local neighborhood cordless-type services
US11/175,825US7181207B1 (en)1998-12-302005-07-06Method and apparatus for over-the-air activation of neighborhood cordless-type services

Related Parent Applications (1)

Application NumberTitlePriority DateFiling Date
US09/987,610ContinuationUS6980817B1 (en)1998-12-302001-11-15Method and apparatus of a network architecture for providing a local neighborhood cordless-type services

Related Child Applications (1)

Application NumberTitlePriority DateFiling Date
US11/649,650ContinuationUS8712405B1 (en)1998-12-302007-01-04Method and apparatus for over-the-air activation of neighborhood cordless-type services

Publications (1)

Publication NumberPublication Date
US7181207B1true US7181207B1 (en)2007-02-20

Family

ID=37745072

Family Applications (4)

Application NumberTitlePriority DateFiling Date
US11/175,825Expired - Fee RelatedUS7181207B1 (en)1998-12-302005-07-06Method and apparatus for over-the-air activation of neighborhood cordless-type services
US11/649,650Expired - Fee RelatedUS8712405B1 (en)1998-12-302007-01-04Method and apparatus for over-the-air activation of neighborhood cordless-type services
US14/263,997Expired - Fee RelatedUS9578590B2 (en)1998-12-302014-04-28Method and apparatus for over-the-air activation of neighborhood cordless services
US15/437,295Expired - Fee RelatedUS9942417B2 (en)1998-12-302017-02-20Method and apparatus for over-the-air activation of neighborhood cordless-type services

Family Applications After (3)

Application NumberTitlePriority DateFiling Date
US11/649,650Expired - Fee RelatedUS8712405B1 (en)1998-12-302007-01-04Method and apparatus for over-the-air activation of neighborhood cordless-type services
US14/263,997Expired - Fee RelatedUS9578590B2 (en)1998-12-302014-04-28Method and apparatus for over-the-air activation of neighborhood cordless services
US15/437,295Expired - Fee RelatedUS9942417B2 (en)1998-12-302017-02-20Method and apparatus for over-the-air activation of neighborhood cordless-type services

Country Status (1)

CountryLink
US (4)US7181207B1 (en)

Cited By (93)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US20060023657A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US20060025139A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for account balance restriction on application of cellular-PBX integration service
US20060023658A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for location-based restriction on application of cellular-PBX integration service
US20060025140A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US20100281161A1 (en)*2009-04-302010-11-04Ucontrol, Inc.Method, system and apparatus for automated inventory reporting of security, monitoring and automation hardware and software at customer premises
US8417264B1 (en)2009-05-142013-04-09Spring Spectrum L.P.Method and apparatus for determining location of a mobile station based on locations of multiple nearby mobile stations
US8712405B1 (en)1998-12-302014-04-29At&T Intellectual Property Ii, L.P.Method and apparatus for over-the-air activation of neighborhood cordless-type services
US9037109B1 (en)2012-03-022015-05-19Sprint Spectrum L.P.Controlling billing for use of one system based on device location in other system
US20160274759A1 (en)2008-08-252016-09-22Paul J. DawesSecurity system with networked touchscreen and gateway
US10051078B2 (en)2007-06-122018-08-14Icontrol Networks, Inc.WiFi-to-serial encapsulation in systems
US10062273B2 (en)2010-09-282018-08-28Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US10062245B2 (en)2005-03-162018-08-28Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US10078958B2 (en)2010-12-172018-09-18Icontrol Networks, Inc.Method and system for logging security event data
US10079839B1 (en)2007-06-122018-09-18Icontrol Networks, Inc.Activation of gateway device
US10091014B2 (en)2005-03-162018-10-02Icontrol Networks, Inc.Integrated security network with security alarm signaling system
US10127801B2 (en)2005-03-162018-11-13Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US10140840B2 (en)2007-04-232018-11-27Icontrol Networks, Inc.Method and system for providing alternate network access
US10142166B2 (en)2004-03-162018-11-27Icontrol Networks, Inc.Takeover of security network
US10142394B2 (en)2007-06-122018-11-27Icontrol Networks, Inc.Generating risk profile using data of home monitoring and security system
US10142392B2 (en)2007-01-242018-11-27Icontrol Networks, Inc.Methods and systems for improved system performance
US10156959B2 (en)2005-03-162018-12-18Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US10156831B2 (en)2004-03-162018-12-18Icontrol Networks, Inc.Automation system with mobile interface
US10200504B2 (en)2007-06-122019-02-05Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US10237237B2 (en)2007-06-122019-03-19Icontrol Networks, Inc.Communication protocols in integrated systems
US10313303B2 (en)2007-06-122019-06-04Icontrol Networks, Inc.Forming a security network including integrated security system components and network devices
US10339791B2 (en)2007-06-122019-07-02Icontrol Networks, Inc.Security network integrated with premise security system
US10348575B2 (en)2013-06-272019-07-09Icontrol Networks, Inc.Control system user interface
US10365810B2 (en)2007-06-122019-07-30Icontrol Networks, Inc.Control system user interface
US10382452B1 (en)2007-06-122019-08-13Icontrol Networks, Inc.Communication protocols in integrated systems
US10380871B2 (en)2005-03-162019-08-13Icontrol Networks, Inc.Control system user interface
US10389736B2 (en)2007-06-122019-08-20Icontrol Networks, Inc.Communication protocols in integrated systems
US10423309B2 (en)2007-06-122019-09-24Icontrol Networks, Inc.Device integration framework
US10498830B2 (en)2007-06-122019-12-03Icontrol Networks, Inc.Wi-Fi-to-serial encapsulation in systems
US10522026B2 (en)2008-08-112019-12-31Icontrol Networks, Inc.Automation system user interface with three-dimensional display
US10523689B2 (en)2007-06-122019-12-31Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US10530839B2 (en)2008-08-112020-01-07Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US10559193B2 (en)2002-02-012020-02-11Comcast Cable Communications, LlcPremises management systems
US10616075B2 (en)2007-06-122020-04-07Icontrol Networks, Inc.Communication protocols in integrated systems
US10666523B2 (en)2007-06-122020-05-26Icontrol Networks, Inc.Communication protocols in integrated systems
US10721087B2 (en)2005-03-162020-07-21Icontrol Networks, Inc.Method for networked touchscreen with integrated interfaces
US10747216B2 (en)2007-02-282020-08-18Icontrol Networks, Inc.Method and system for communicating with and controlling an alarm system from a remote server
US10785319B2 (en)2006-06-122020-09-22Icontrol Networks, Inc.IP device discovery systems and methods
US10841381B2 (en)2005-03-162020-11-17Icontrol Networks, Inc.Security system with networked touchscreen
US10979389B2 (en)2004-03-162021-04-13Icontrol Networks, Inc.Premises management configuration and control
US10999254B2 (en)2005-03-162021-05-04Icontrol Networks, Inc.System for data routing in networks
US11089122B2 (en)2007-06-122021-08-10Icontrol Networks, Inc.Controlling data routing among networks
US11113950B2 (en)2005-03-162021-09-07Icontrol Networks, Inc.Gateway integrated with premises security system
US11146637B2 (en)2014-03-032021-10-12Icontrol Networks, Inc.Media content management
US11153266B2 (en)2004-03-162021-10-19Icontrol Networks, Inc.Gateway registry methods and systems
US11182060B2 (en)2004-03-162021-11-23Icontrol Networks, Inc.Networked touchscreen with integrated interfaces
US11201755B2 (en)2004-03-162021-12-14Icontrol Networks, Inc.Premises system management using status signal
US11212192B2 (en)2007-06-122021-12-28Icontrol Networks, Inc.Communication protocols in integrated systems
US11218878B2 (en)2007-06-122022-01-04Icontrol Networks, Inc.Communication protocols in integrated systems
US11240059B2 (en)2010-12-202022-02-01Icontrol Networks, Inc.Defining and implementing sensor triggered response rules
US11237714B2 (en)2007-06-122022-02-01Control Networks, Inc.Control system user interface
US11244545B2 (en)2004-03-162022-02-08Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US11258625B2 (en)2008-08-112022-02-22Icontrol Networks, Inc.Mobile premises automation platform
US11277465B2 (en)2004-03-162022-03-15Icontrol Networks, Inc.Generating risk profile using data of home monitoring and security system
US11310199B2 (en)2004-03-162022-04-19Icontrol Networks, Inc.Premises management configuration and control
US11316958B2 (en)2008-08-112022-04-26Icontrol Networks, Inc.Virtual device systems and methods
US11316753B2 (en)2007-06-122022-04-26Icontrol Networks, Inc.Communication protocols in integrated systems
US11343380B2 (en)2004-03-162022-05-24Icontrol Networks, Inc.Premises system automation
US11368327B2 (en)2008-08-112022-06-21Icontrol Networks, Inc.Integrated cloud system for premises automation
US11398147B2 (en)2010-09-282022-07-26Icontrol Networks, Inc.Method, system and apparatus for automated reporting of account and sensor zone information to a central station
US11405463B2 (en)2014-03-032022-08-02Icontrol Networks, Inc.Media content management
US11423756B2 (en)2007-06-122022-08-23Icontrol Networks, Inc.Communication protocols in integrated systems
US11424980B2 (en)2005-03-162022-08-23Icontrol Networks, Inc.Forming a security network including integrated security system components
US11451409B2 (en)2005-03-162022-09-20Icontrol Networks, Inc.Security network integrating security system and network devices
US11489812B2 (en)2004-03-162022-11-01Icontrol Networks, Inc.Forming a security network including integrated security system components and network devices
US11496568B2 (en)2005-03-162022-11-08Icontrol Networks, Inc.Security system with networked touchscreen
US11582065B2 (en)2007-06-122023-02-14Icontrol Networks, Inc.Systems and methods for device communication
US11601810B2 (en)2007-06-122023-03-07Icontrol Networks, Inc.Communication protocols in integrated systems
US11615697B2 (en)2005-03-162023-03-28Icontrol Networks, Inc.Premise management systems and methods
US11646907B2 (en)2007-06-122023-05-09Icontrol Networks, Inc.Communication protocols in integrated systems
US11677577B2 (en)2004-03-162023-06-13Icontrol Networks, Inc.Premises system management using status signal
US11700142B2 (en)2005-03-162023-07-11Icontrol Networks, Inc.Security network integrating security system and network devices
US11706045B2 (en)2005-03-162023-07-18Icontrol Networks, Inc.Modular electronic display platform
US11706279B2 (en)2007-01-242023-07-18Icontrol Networks, Inc.Methods and systems for data communication
US11729255B2 (en)2008-08-112023-08-15Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US11750414B2 (en)2010-12-162023-09-05Icontrol Networks, Inc.Bidirectional security sensor communication for a premises security system
US11758026B2 (en)2008-08-112023-09-12Icontrol Networks, Inc.Virtual device systems and methods
US11792036B2 (en)2008-08-112023-10-17Icontrol Networks, Inc.Mobile premises automation platform
US11792330B2 (en)2005-03-162023-10-17Icontrol Networks, Inc.Communication and automation in a premises management system
US11811845B2 (en)2004-03-162023-11-07Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US11816323B2 (en)2008-06-252023-11-14Icontrol Networks, Inc.Automation system user interface
US11831462B2 (en)2007-08-242023-11-28Icontrol Networks, Inc.Controlling data routing in premises management systems
US11916928B2 (en)2008-01-242024-02-27Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US11916870B2 (en)2004-03-162024-02-27Icontrol Networks, Inc.Gateway registry methods and systems
US12003387B2 (en)2012-06-272024-06-04Comcast Cable Communications, LlcControl system user interface
US12063220B2 (en)2004-03-162024-08-13Icontrol Networks, Inc.Communication protocols in integrated systems
US12063221B2 (en)2006-06-122024-08-13Icontrol Networks, Inc.Activation of gateway device
US12184443B2 (en)2007-06-122024-12-31Icontrol Networks, Inc.Controlling data routing among networks
US12283172B2 (en)2007-06-122025-04-22Icontrol Networks, Inc.Communication protocols in integrated systems

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US10447740B2 (en)*2015-07-142019-10-15Tata Communications (America) Inc.System and method for call termination via an over-the-top (OTT) call service, based on connection characteristics
CN105182919A (en)*2015-07-202015-12-23成都弘毅天承科技有限公司Smart home control system with security protection and fire extinguishing function
US11395371B2 (en)*2018-05-312022-07-19Roku, Inc.Real-time assessment of multimedia service in a particular environment

Citations (2)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US5325419A (en)*1993-01-041994-06-28Ameritech CorporationWireless digital personal communications system having voice/data/image two-way calling and intercell hand-off
US5787354A (en)*1994-02-241998-07-28Gte Mobile Communications Service CorporationMethod and apparatus for locating a radiotelephone within a cellular system

Family Cites Families (60)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US4456793A (en)1982-06-091984-06-26Bell Telephone Laboratories, IncorporatedCordless telephone system
US5687218A (en)1990-02-151997-11-11Canon Kabushiki KaishaCordless telephone
CA2083515A1 (en)1990-05-221991-11-23Charles Gregory AmadonCellular telephone system with remote programming, voice responsive registration, and real time billing
US5159625A (en)1990-10-241992-10-27Gte Mobile Communications Service Corp.Method of selecting the cellular system with which a cellular mobile radiotelephone communicates
US5463623A (en)1991-07-311995-10-31At&T Ipm Corp.Integrated wireless telecommunication and local area network system
US5345499A (en)1992-03-231994-09-06At&T Bell LaboratoriesMethod for increasing two tier macrocell/microcell subscriber capacity in a cellular system
US5600706A (en)1992-04-081997-02-04U S West, Inc.Method and system for determining the position of a mobile receiver
US5295180A (en)1992-04-081994-03-15U S West Newvector Group, Inc.Cellular telephone zone system
AU655360B2 (en)1992-05-221994-12-15American Telephone And Telegraph CompanyApparatus and method for non-regular channel assignment in wireless communication networks
JPH06112889A (en)1992-09-291994-04-22Uniden CorpCordless system telephone set
US6088590A (en)1993-11-012000-07-11Omnipoint CorporationMethod and system for mobile controlled handoff and link maintenance in spread spectrum communication
US5854985A (en)*1993-12-151998-12-29Spectrum Information Technologies, Inc.Adaptive omni-modal radio apparatus and methods
US5761621A (en)*1993-12-151998-06-02Spectrum Information Technologies, Inc.Apparatus and methods for networking omni-modal radio devices
US5956643A (en)1994-01-131999-09-21Lucent Technologies Inc.Apparatus and method for adaptive dynamic channel assignment in wireless communication networks
EP1257135A3 (en)1994-02-242003-02-12Gte Mobile Communications Service CorporationCellular radiotelephone system with remotely programmed mobile stations
US5703934A (en)1994-02-241997-12-30Gte Mobile Communication ServiceCordless telephone with integral caller ID display
US5774805A (en)1994-02-241998-06-30Gte Mobile Communications Service CorporationMulti-mode communication network with handset-selected channel assignments
MX9603658A (en)1994-02-241997-12-31Gte Mobile Comm Service CorpMultiple mode personal wireless communications system.
US5457736A (en)1994-04-121995-10-10U S West Technologies, Inc.System and method for providing microcellular personal communications services (PCS) utilizing embedded switches
US5513379A (en)1994-05-041996-04-30At&T Corp.Apparatus and method for dynamic resource allocation in wireless communication networks utilizing ordered borrowing
US5742905A (en)1994-09-191998-04-21Bell Communications Research, Inc.Personal communications internetworking
US5602903A (en)*1994-09-281997-02-11Us West Technologies, Inc.Positioning system and method
FR2725579B1 (en)1994-10-061996-10-31Despres Francois COMMUNICATION METHOD IN A TELECOMMUNICATIONS NETWORK
US5673308A (en)1994-10-121997-09-30Bell Atlantic Network Services, Inc.Personal phone number system
US5592470A (en)1994-12-211997-01-07At&TBroadband wireless system and network architecture providing broadband/narrowband service with optimal static and dynamic bandwidth/channel allocation
US6018652A (en)1995-08-312000-01-25Telefonaktiebolaget Lm Ericsson (Publ.)Cellular telephone system having mobile charging region and area based pricing method and apparatus
US5675629A (en)1995-09-081997-10-07At&TCordless cellular system base station
JP3834677B2 (en)1995-10-172006-10-18テレフオンアクチーボラゲツト エル エム エリクソン(パブル) Method for performing handover and roaming in a wireless communication environment
US5812950A (en)1995-11-271998-09-22Telefonaktiebolaget Lm Ericsson (Publ)Cellular telephone system having prioritized greetings for predefined services to a subscriber
US5740536A (en)1995-12-291998-04-14At&T Corp.System and method for managing neighbor-channel interference in channelized cellular systems
US5787352A (en)1995-12-291998-07-28At&T Corp.System and method for management of neighbor-channel interference with power control and directed channel assignment
US6167279A (en)1996-03-132000-12-26Telcordia Technologies, Inc.Method and system for supporting PACS using a GSM mobile switching center
US5774802A (en)1996-04-101998-06-30Motorola Inc.Apparatus and method for billing in a wireless communication system
US5887254A (en)1996-04-261999-03-23Nokia Mobile Phones LimitedMethods and apparatus for updating the software of a mobile terminal using the air interface
US5943425A (en)1996-05-101999-08-24Lucent Technologies, Inc.Re-authentication procedure for over-the-air activation
US6073015A (en)1996-07-112000-06-06Telefonaktiebolaget L M Ericsson (Publ)System and method of providing services when the mobile is home registered in a microcellular network and receives support from a macrocellular network
US5819180A (en)1996-07-311998-10-06Ericsson Inc.Automatic call generator with a mobile telecommunications network based upon mobile subscriber's location
US5987318A (en)1996-07-311999-11-16Ericsson Inc.Call conference within a home zone
EP0925699B1 (en)1996-09-122002-12-18Telefonaktiebolaget L M Ericsson (Publ)A multimode telecommunication terminal device
US5918172A (en)1996-09-271999-06-29Highwaymaster Communications, Inc.Multiple number assignment module communication
US5905953A (en)1996-12-021999-05-18Lucent Technologies Inc.Method for implementing private wireless telecommunications networks
US5960356A (en)1996-12-061999-09-28Ericsson, Inc.Paging a mobile station within a public land mobile network (PLMN)
US5907802A (en)*1996-12-311999-05-25Mci Communications CorporationSystem and method for cellular reseller control of inbound calls to a mobile station
US5940755A (en)*1996-12-311999-08-17Mci Communications CorporationSystem and method for wireless network of unlicensed personal communications service areas with local switch interfaces and enhanced customer features
US6167261A (en)1997-02-272000-12-26At&T Wireless Svcs. Inc.Wireless communication service management
US5950130A (en)1997-03-181999-09-07Sbc Technology Resources, Inc.Mobile station with intelligent roaming and over-the-air programming features
US6021332A (en)*1997-04-012000-02-01Motorola, Inc.Multi-mode radiotelephone having a multiple battery arrangement
US5974331A (en)*1997-04-041999-10-26U S West, Inc.Method and system for dynamically assigning features and users to wireline interfaces
US6047071A (en)1997-04-152000-04-04Nokia Mobile PhonesNetwork-initiated change of mobile phone parameters
US6064880A (en)1997-06-252000-05-16Nokia Mobile Phones LimitedMobile station having short code memory system-level backup and restoration function
US5995829A (en)1997-07-031999-11-30Nokia Mobile PhonesProgrammable system determination in dual-mode wireless communications systems
US6144849A (en)1998-02-232000-11-07Adc Newnet, Inc.Method and apparatus for over-the-air service provisioning of a mobile telephone
US6148197A (en)1998-03-062000-11-14Sbc Technology Resources, Inc.Intelligent roaming system with over the air programming
US6154650A (en)1998-06-032000-11-28Ericsson, Inc.System and method for delivering a call for a mobile station using either a wireless network or a wireline network
US6263211B1 (en)1998-09-242001-07-17Telefonaktiebolaget L M Ericsson (Publ)System and method of automatically conveying a Wireless Office System (WOS) frequency set to mobile stations
US6141544A (en)1998-11-302000-10-31Telefonaktiebolaget Lm EricssonSystem and method for over the air activation in a wireless telecommunications network
US6594488B1 (en)1998-12-302003-07-15At&T Corp.Method and apparatus for over-the-air activation of neighborhood cordless-type services
US7181207B1 (en)1998-12-302007-02-20At&T Corp.Method and apparatus for over-the-air activation of neighborhood cordless-type services
US6445911B1 (en)*1998-12-302002-09-03At&T CorpMethod and apparatus for providing neighborhood cordless services
US6243572B1 (en)*1998-12-302001-06-05At&T Corp.Method and apparatus for billing a neighborhood cordless service

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US5325419A (en)*1993-01-041994-06-28Ameritech CorporationWireless digital personal communications system having voice/data/image two-way calling and intercell hand-off
US5787354A (en)*1994-02-241998-07-28Gte Mobile Communications Service CorporationMethod and apparatus for locating a radiotelephone within a cellular system

Cited By (194)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
US8712405B1 (en)1998-12-302014-04-29At&T Intellectual Property Ii, L.P.Method and apparatus for over-the-air activation of neighborhood cordless-type services
US9942417B2 (en)1998-12-302018-04-10At&T Intellectual Property Ii, L.P.Method and apparatus for over-the-air activation of neighborhood cordless-type services
US9578590B2 (en)1998-12-302017-02-21At&T Intellectual Property Ii, L.P.Method and apparatus for over-the-air activation of neighborhood cordless services
US10559193B2 (en)2002-02-012020-02-11Comcast Cable Communications, LlcPremises management systems
US10979389B2 (en)2004-03-162021-04-13Icontrol Networks, Inc.Premises management configuration and control
US11810445B2 (en)2004-03-162023-11-07Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US10692356B2 (en)2004-03-162020-06-23Icontrol Networks, Inc.Control system user interface
US11489812B2 (en)2004-03-162022-11-01Icontrol Networks, Inc.Forming a security network including integrated security system components and network devices
US11588787B2 (en)2004-03-162023-02-21Icontrol Networks, Inc.Premises management configuration and control
US10735249B2 (en)2004-03-162020-08-04Icontrol Networks, Inc.Management of a security system at a premises
US11449012B2 (en)2004-03-162022-09-20Icontrol Networks, Inc.Premises management networking
US12253833B2 (en)2004-03-162025-03-18Icontrol Networks, Inc.Automation system with mobile interface
US11244545B2 (en)2004-03-162022-02-08Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US11310199B2 (en)2004-03-162022-04-19Icontrol Networks, Inc.Premises management configuration and control
US11343380B2 (en)2004-03-162022-05-24Icontrol Networks, Inc.Premises system automation
US10142166B2 (en)2004-03-162018-11-27Icontrol Networks, Inc.Takeover of security network
US10754304B2 (en)2004-03-162020-08-25Icontrol Networks, Inc.Automation system with mobile interface
US12063220B2 (en)2004-03-162024-08-13Icontrol Networks, Inc.Communication protocols in integrated systems
US11991306B2 (en)2004-03-162024-05-21Icontrol Networks, Inc.Premises system automation
US11368429B2 (en)2004-03-162022-06-21Icontrol Networks, Inc.Premises management configuration and control
US11916870B2 (en)2004-03-162024-02-27Icontrol Networks, Inc.Gateway registry methods and systems
US11893874B2 (en)2004-03-162024-02-06Icontrol Networks, Inc.Networked touchscreen with integrated interfaces
US11378922B2 (en)2004-03-162022-07-05Icontrol Networks, Inc.Automation system with mobile interface
US11201755B2 (en)2004-03-162021-12-14Icontrol Networks, Inc.Premises system management using status signal
US11410531B2 (en)2004-03-162022-08-09Icontrol Networks, Inc.Automation system user interface with three-dimensional display
US11184322B2 (en)2004-03-162021-11-23Icontrol Networks, Inc.Communication protocols in integrated systems
US11537186B2 (en)2004-03-162022-12-27Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11182060B2 (en)2004-03-162021-11-23Icontrol Networks, Inc.Networked touchscreen with integrated interfaces
US11175793B2 (en)2004-03-162021-11-16Icontrol Networks, Inc.User interface in a premises network
US11159484B2 (en)2004-03-162021-10-26Icontrol Networks, Inc.Forming a security network including integrated security system components and network devices
US10156831B2 (en)2004-03-162018-12-18Icontrol Networks, Inc.Automation system with mobile interface
US10691295B2 (en)2004-03-162020-06-23Icontrol Networks, Inc.User interface in a premises network
US11153266B2 (en)2004-03-162021-10-19Icontrol Networks, Inc.Gateway registry methods and systems
US11811845B2 (en)2004-03-162023-11-07Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US11082395B2 (en)2004-03-162021-08-03Icontrol Networks, Inc.Premises management configuration and control
US11782394B2 (en)2004-03-162023-10-10Icontrol Networks, Inc.Automation system with mobile interface
US11757834B2 (en)2004-03-162023-09-12Icontrol Networks, Inc.Communication protocols in integrated systems
US11043112B2 (en)2004-03-162021-06-22Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11037433B2 (en)2004-03-162021-06-15Icontrol Networks, Inc.Management of a security system at a premises
US10992784B2 (en)2004-03-162021-04-27Control Networks, Inc.Communication protocols over internet protocol (IP) networks
US11677577B2 (en)2004-03-162023-06-13Icontrol Networks, Inc.Premises system management using status signal
US11277465B2 (en)2004-03-162022-03-15Icontrol Networks, Inc.Generating risk profile using data of home monitoring and security system
US11656667B2 (en)2004-03-162023-05-23Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11626006B2 (en)2004-03-162023-04-11Icontrol Networks, Inc.Management of a security system at a premises
US10890881B2 (en)2004-03-162021-01-12Icontrol Networks, Inc.Premises management networking
US11625008B2 (en)2004-03-162023-04-11Icontrol Networks, Inc.Premises management networking
US10796557B2 (en)2004-03-162020-10-06Icontrol Networks, Inc.Automation system user interface with three-dimensional display
US10447491B2 (en)2004-03-162019-10-15Icontrol Networks, Inc.Premises system management using status signal
US11601397B2 (en)2004-03-162023-03-07Icontrol Networks, Inc.Premises management configuration and control
US20060023657A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US20110211531A1 (en)*2004-07-292011-09-01Sprint Spectrum L.P.Method and System for Selective Application of Cellular-PBX Integration Service
US20060023658A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for location-based restriction on application of cellular-PBX integration service
US20060025140A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US20060025139A1 (en)*2004-07-292006-02-02Sprint Spectrum L.P.Method and system for account balance restriction on application of cellular-PBX integration service
US8254989B2 (en)*2004-07-292012-08-28Sprint Spectrum L.P.Method and system for account balance restriction on application of cellular-PBX integration service
US8180393B2 (en)*2004-07-292012-05-15Sprint Spectrum L.P.Method and system for location-based restriction on application of cellular-PBX integration service
US8169952B2 (en)2004-07-292012-05-01Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US8064951B2 (en)2004-07-292011-11-22Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US8060135B2 (en)*2004-07-292011-11-15Sprint Spectrum L.P.Method and system for selective application of cellular-PBX integration service
US11792330B2 (en)2005-03-162023-10-17Icontrol Networks, Inc.Communication and automation in a premises management system
US11595364B2 (en)2005-03-162023-02-28Icontrol Networks, Inc.System for data routing in networks
US11451409B2 (en)2005-03-162022-09-20Icontrol Networks, Inc.Security network integrating security system and network devices
US10721087B2 (en)2005-03-162020-07-21Icontrol Networks, Inc.Method for networked touchscreen with integrated interfaces
US12277853B2 (en)2005-03-162025-04-15Icontrol Networks, Inc.Gateway integrated with premises security system
US11496568B2 (en)2005-03-162022-11-08Icontrol Networks, Inc.Security system with networked touchscreen
US10062245B2 (en)2005-03-162018-08-28Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US11367340B2 (en)2005-03-162022-06-21Icontrol Networks, Inc.Premise management systems and methods
US10091014B2 (en)2005-03-162018-10-02Icontrol Networks, Inc.Integrated security network with security alarm signaling system
US11615697B2 (en)2005-03-162023-03-28Icontrol Networks, Inc.Premise management systems and methods
US11424980B2 (en)2005-03-162022-08-23Icontrol Networks, Inc.Forming a security network including integrated security system components
US10841381B2 (en)2005-03-162020-11-17Icontrol Networks, Inc.Security system with networked touchscreen
US10380871B2 (en)2005-03-162019-08-13Icontrol Networks, Inc.Control system user interface
US10930136B2 (en)2005-03-162021-02-23Icontrol Networks, Inc.Premise management systems and methods
US10127801B2 (en)2005-03-162018-11-13Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11700142B2 (en)2005-03-162023-07-11Icontrol Networks, Inc.Security network integrating security system and network devices
US10999254B2 (en)2005-03-162021-05-04Icontrol Networks, Inc.System for data routing in networks
US11706045B2 (en)2005-03-162023-07-18Icontrol Networks, Inc.Modular electronic display platform
US11824675B2 (en)2005-03-162023-11-21Icontrol Networks, Inc.Networked touchscreen with integrated interfaces
US10156959B2 (en)2005-03-162018-12-18Icontrol Networks, Inc.Cross-client sensor user interface in an integrated security network
US11113950B2 (en)2005-03-162021-09-07Icontrol Networks, Inc.Gateway integrated with premises security system
US11418518B2 (en)2006-06-122022-08-16Icontrol Networks, Inc.Activation of gateway device
US10616244B2 (en)2006-06-122020-04-07Icontrol Networks, Inc.Activation of gateway device
US12063221B2 (en)2006-06-122024-08-13Icontrol Networks, Inc.Activation of gateway device
US10785319B2 (en)2006-06-122020-09-22Icontrol Networks, Inc.IP device discovery systems and methods
US10225314B2 (en)2007-01-242019-03-05Icontrol Networks, Inc.Methods and systems for improved system performance
US10142392B2 (en)2007-01-242018-11-27Icontrol Networks, Inc.Methods and systems for improved system performance
US11418572B2 (en)2007-01-242022-08-16Icontrol Networks, Inc.Methods and systems for improved system performance
US11706279B2 (en)2007-01-242023-07-18Icontrol Networks, Inc.Methods and systems for data communication
US12120171B2 (en)2007-01-242024-10-15Icontrol Networks, Inc.Methods and systems for data communication
US11412027B2 (en)2007-01-242022-08-09Icontrol Networks, Inc.Methods and systems for data communication
US10747216B2 (en)2007-02-282020-08-18Icontrol Networks, Inc.Method and system for communicating with and controlling an alarm system from a remote server
US11809174B2 (en)2007-02-282023-11-07Icontrol Networks, Inc.Method and system for managing communication connectivity
US11194320B2 (en)2007-02-282021-12-07Icontrol Networks, Inc.Method and system for managing communication connectivity
US10657794B1 (en)2007-02-282020-05-19Icontrol Networks, Inc.Security, monitoring and automation controller access and use of legacy security control panel information
US10140840B2 (en)2007-04-232018-11-27Icontrol Networks, Inc.Method and system for providing alternate network access
US11132888B2 (en)2007-04-232021-09-28Icontrol Networks, Inc.Method and system for providing alternate network access
US11663902B2 (en)2007-04-232023-05-30Icontrol Networks, Inc.Method and system for providing alternate network access
US10672254B2 (en)2007-04-232020-06-02Icontrol Networks, Inc.Method and system for providing alternate network access
US10444964B2 (en)2007-06-122019-10-15Icontrol Networks, Inc.Control system user interface
US11089122B2 (en)2007-06-122021-08-10Icontrol Networks, Inc.Controlling data routing among networks
US10382452B1 (en)2007-06-122019-08-13Icontrol Networks, Inc.Communication protocols in integrated systems
US12284057B2 (en)2007-06-122025-04-22Icontrol Networks, Inc.Systems and methods for device communication
US11237714B2 (en)2007-06-122022-02-01Control Networks, Inc.Control system user interface
US12283172B2 (en)2007-06-122025-04-22Icontrol Networks, Inc.Communication protocols in integrated systems
US11316753B2 (en)2007-06-122022-04-26Icontrol Networks, Inc.Communication protocols in integrated systems
US12250547B2 (en)2007-06-122025-03-11Icontrol Networks, Inc.Communication protocols in integrated systems
US12184443B2 (en)2007-06-122024-12-31Icontrol Networks, Inc.Controlling data routing among networks
US10051078B2 (en)2007-06-122018-08-14Icontrol Networks, Inc.WiFi-to-serial encapsulation in systems
US10079839B1 (en)2007-06-122018-09-18Icontrol Networks, Inc.Activation of gateway device
US11218878B2 (en)2007-06-122022-01-04Icontrol Networks, Inc.Communication protocols in integrated systems
US11894986B2 (en)2007-06-122024-02-06Icontrol Networks, Inc.Communication protocols in integrated systems
US11212192B2 (en)2007-06-122021-12-28Icontrol Networks, Inc.Communication protocols in integrated systems
US10423309B2 (en)2007-06-122019-09-24Icontrol Networks, Inc.Device integration framework
US11611568B2 (en)2007-06-122023-03-21Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US10142394B2 (en)2007-06-122018-11-27Icontrol Networks, Inc.Generating risk profile using data of home monitoring and security system
US10200504B2 (en)2007-06-122019-02-05Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US10237237B2 (en)2007-06-122019-03-19Icontrol Networks, Inc.Communication protocols in integrated systems
US10389736B2 (en)2007-06-122019-08-20Icontrol Networks, Inc.Communication protocols in integrated systems
US11423756B2 (en)2007-06-122022-08-23Icontrol Networks, Inc.Communication protocols in integrated systems
US11722896B2 (en)2007-06-122023-08-08Icontrol Networks, Inc.Communication protocols in integrated systems
US10313303B2 (en)2007-06-122019-06-04Icontrol Networks, Inc.Forming a security network including integrated security system components and network devices
US10339791B2 (en)2007-06-122019-07-02Icontrol Networks, Inc.Security network integrated with premise security system
US10666523B2 (en)2007-06-122020-05-26Icontrol Networks, Inc.Communication protocols in integrated systems
US10616075B2 (en)2007-06-122020-04-07Icontrol Networks, Inc.Communication protocols in integrated systems
US10365810B2 (en)2007-06-122019-07-30Icontrol Networks, Inc.Control system user interface
US11646907B2 (en)2007-06-122023-05-09Icontrol Networks, Inc.Communication protocols in integrated systems
US11582065B2 (en)2007-06-122023-02-14Icontrol Networks, Inc.Systems and methods for device communication
US10523689B2 (en)2007-06-122019-12-31Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US11632308B2 (en)2007-06-122023-04-18Icontrol Networks, Inc.Communication protocols in integrated systems
US10498830B2 (en)2007-06-122019-12-03Icontrol Networks, Inc.Wi-Fi-to-serial encapsulation in systems
US11625161B2 (en)2007-06-122023-04-11Icontrol Networks, Inc.Control system user interface
US11601810B2 (en)2007-06-122023-03-07Icontrol Networks, Inc.Communication protocols in integrated systems
US11815969B2 (en)2007-08-102023-11-14Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11831462B2 (en)2007-08-242023-11-28Icontrol Networks, Inc.Controlling data routing in premises management systems
US12301379B2 (en)2007-08-242025-05-13Icontrol Networks, Inc.Controlling data routing in premises management systems
US11916928B2 (en)2008-01-242024-02-27Icontrol Networks, Inc.Communication protocols over internet protocol (IP) networks
US11816323B2 (en)2008-06-252023-11-14Icontrol Networks, Inc.Automation system user interface
US12244663B2 (en)2008-08-112025-03-04Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US11962672B2 (en)2008-08-112024-04-16Icontrol Networks, Inc.Virtual device systems and methods
US11641391B2 (en)2008-08-112023-05-02Icontrol Networks Inc.Integrated cloud system with lightweight gateway for premises automation
US11316958B2 (en)2008-08-112022-04-26Icontrol Networks, Inc.Virtual device systems and methods
US11190578B2 (en)2008-08-112021-11-30Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US10530839B2 (en)2008-08-112020-01-07Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US12267385B2 (en)2008-08-112025-04-01Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US11792036B2 (en)2008-08-112023-10-17Icontrol Networks, Inc.Mobile premises automation platform
US10522026B2 (en)2008-08-112019-12-31Icontrol Networks, Inc.Automation system user interface with three-dimensional display
US12341865B2 (en)2008-08-112025-06-24Icontrol Networks, Inc.Virtual device systems and methods
US11616659B2 (en)2008-08-112023-03-28Icontrol Networks, Inc.Integrated cloud system for premises automation
US11711234B2 (en)2008-08-112023-07-25Icontrol Networks, Inc.Integrated cloud system for premises automation
US11258625B2 (en)2008-08-112022-02-22Icontrol Networks, Inc.Mobile premises automation platform
US11729255B2 (en)2008-08-112023-08-15Icontrol Networks, Inc.Integrated cloud system with lightweight gateway for premises automation
US11368327B2 (en)2008-08-112022-06-21Icontrol Networks, Inc.Integrated cloud system for premises automation
US11758026B2 (en)2008-08-112023-09-12Icontrol Networks, Inc.Virtual device systems and methods
US20160274759A1 (en)2008-08-252016-09-22Paul J. DawesSecurity system with networked touchscreen and gateway
US10375253B2 (en)2008-08-252019-08-06Icontrol Networks, Inc.Security system with networked touchscreen and gateway
US11356926B2 (en)2009-04-302022-06-07Icontrol Networks, Inc.Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces
US11997584B2 (en)2009-04-302024-05-28Icontrol Networks, Inc.Activation of a home automation controller
US10237806B2 (en)2009-04-302019-03-19Icontrol Networks, Inc.Activation of a home automation controller
US11601865B2 (en)2009-04-302023-03-07Icontrol Networks, Inc.Server-based notification of alarm event subsequent to communication failure with armed security system
US11284331B2 (en)2009-04-302022-03-22Icontrol Networks, Inc.Server-based notification of alarm event subsequent to communication failure with armed security system
US11778534B2 (en)2009-04-302023-10-03Icontrol Networks, Inc.Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces
US10275999B2 (en)2009-04-302019-04-30Icontrol Networks, Inc.Server-based notification of alarm event subsequent to communication failure with armed security system
US11553399B2 (en)2009-04-302023-01-10Icontrol Networks, Inc.Custom content for premises management
US20100281161A1 (en)*2009-04-302010-11-04Ucontrol, Inc.Method, system and apparatus for automated inventory reporting of security, monitoring and automation hardware and software at customer premises
US11665617B2 (en)2009-04-302023-05-30Icontrol Networks, Inc.Server-based notification of alarm event subsequent to communication failure with armed security system
US11856502B2 (en)*2009-04-302023-12-26Icontrol Networks, Inc.Method, system and apparatus for automated inventory reporting of security, monitoring and automation hardware and software at customer premises
US12245131B2 (en)2009-04-302025-03-04Icontrol Networks, Inc.Security, monitoring and automation controller access and use of legacy security control panel information
US11223998B2 (en)2009-04-302022-01-11Icontrol Networks, Inc.Security, monitoring and automation controller access and use of legacy security control panel information
US12127095B2 (en)2009-04-302024-10-22Icontrol Networks, Inc.Custom content for premises management
US10813034B2 (en)2009-04-302020-10-20Icontrol Networks, Inc.Method, system and apparatus for management of applications for an SMA controller
US10674428B2 (en)2009-04-302020-06-02Icontrol Networks, Inc.Hardware configurable security, monitoring and automation controller having modular communication protocol interfaces
US10332363B2 (en)2009-04-302019-06-25Icontrol Networks, Inc.Controller and interface for home security, monitoring and automation having customizable audio alerts for SMA events
US11129084B2 (en)2009-04-302021-09-21Icontrol Networks, Inc.Notification of event subsequent to communication failure with security system
US8417264B1 (en)2009-05-142013-04-09Spring Spectrum L.P.Method and apparatus for determining location of a mobile station based on locations of multiple nearby mobile stations
US11900790B2 (en)2010-09-282024-02-13Icontrol Networks, Inc.Method, system and apparatus for automated reporting of account and sensor zone information to a central station
US10223903B2 (en)2010-09-282019-03-05Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US10127802B2 (en)2010-09-282018-11-13Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US11398147B2 (en)2010-09-282022-07-26Icontrol Networks, Inc.Method, system and apparatus for automated reporting of account and sensor zone information to a central station
US10062273B2 (en)2010-09-282018-08-28Icontrol Networks, Inc.Integrated security system with parallel processing architecture
US12088425B2 (en)2010-12-162024-09-10Icontrol Networks, Inc.Bidirectional security sensor communication for a premises security system
US11750414B2 (en)2010-12-162023-09-05Icontrol Networks, Inc.Bidirectional security sensor communication for a premises security system
US10078958B2 (en)2010-12-172018-09-18Icontrol Networks, Inc.Method and system for logging security event data
US12100287B2 (en)2010-12-172024-09-24Icontrol Networks, Inc.Method and system for processing security event data
US11341840B2 (en)2010-12-172022-05-24Icontrol Networks, Inc.Method and system for processing security event data
US10741057B2 (en)2010-12-172020-08-11Icontrol Networks, Inc.Method and system for processing security event data
US11240059B2 (en)2010-12-202022-02-01Icontrol Networks, Inc.Defining and implementing sensor triggered response rules
US12021649B2 (en)2010-12-202024-06-25Icontrol Networks, Inc.Defining and implementing sensor triggered response rules
US9037109B1 (en)2012-03-022015-05-19Sprint Spectrum L.P.Controlling billing for use of one system based on device location in other system
US12003387B2 (en)2012-06-272024-06-04Comcast Cable Communications, LlcControl system user interface
US10348575B2 (en)2013-06-272019-07-09Icontrol Networks, Inc.Control system user interface
US11296950B2 (en)2013-06-272022-04-05Icontrol Networks, Inc.Control system user interface
US11943301B2 (en)2014-03-032024-03-26Icontrol Networks, Inc.Media content management
US11405463B2 (en)2014-03-032022-08-02Icontrol Networks, Inc.Media content management
US11146637B2 (en)2014-03-032021-10-12Icontrol Networks, Inc.Media content management

Also Published As

Publication numberPublication date
US9578590B2 (en)2017-02-21
US9942417B2 (en)2018-04-10
US20170163820A1 (en)2017-06-08
US8712405B1 (en)2014-04-29
US20140235291A1 (en)2014-08-21

Similar Documents

PublicationPublication DateTitle
US9942417B2 (en)Method and apparatus for over-the-air activation of neighborhood cordless-type services
US6243572B1 (en)Method and apparatus for billing a neighborhood cordless service
US6470179B1 (en)Automatic service selection feature for neighborhood residential cordless service
US7805141B1 (en)Neighborhood cordless service call handoff
US6445911B1 (en)Method and apparatus for providing neighborhood cordless services
US6546253B1 (en)Neighborhood cordless service call handoff
US6980817B1 (en)Method and apparatus of a network architecture for providing a local neighborhood cordless-type services
US5805997A (en)System for sending control signals from a subscriber station to a network controller using cellular digital packet data (CDPD) communication
CA2230041C (en)Method and system for providing wireless communications to a subscriber of a private wireline network
US5579379A (en)Personal communications service having a calling party pays capability
US5771275A (en)Use of ISDN to provide wireless office environment connection to the public land mobile network
US5953651A (en)Cellular adjunct to a public wired network
US5353331A (en)Personal communications service using wireline/wireless integration
US6516190B1 (en)Method and apparatus for calculating call charge rates in a mobile telecommunication system
US5845211A (en)Wireless digital network
US6223055B1 (en)Wireless office architecture and method of operation thereof
EP0800748B1 (en)A method for improving charging criteria in a mobile telephone network
US20100303232A1 (en)Wireless Digital Personal Communications System Having Voice/Data/Image Two-Way Calling and Intercell Hand-Off Provided Through Distributed Logic Resident in Portable Handset Terminals, Fixed Terminals, Radio Cell Base Stations and Switched Telephone Network
US7043248B2 (en)System and method for providing telecommunication services
CA2332030A1 (en)System and method for delivering a call for a mobile station using either a wireless network or a wireline network
EP0826292B1 (en)Hybrid cellular communication apparatus and method
CA2353898C (en)Cellular-fixed call completion and call transfer service from a cellular network provider
WO1999059371A1 (en)Mobile switching center that completes a call to a roaming mobile station as if the mobile station were a local mobile station
WO1999038342A1 (en)Communication system and method for ringing wired telephones and wireless telephones substantially simultaneously
EP0844799A2 (en)Integration of manual registration and personal base station registration

Legal Events

DateCodeTitleDescription
FPAYFee payment

Year of fee payment:4

REMIMaintenance fee reminder mailed
LAPSLapse for failure to pay maintenance fees
STCHInformation on status: patent discontinuation

Free format text:PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FPLapsed due to failure to pay maintenance fee

Effective date:20150220


[8]ページ先頭

©2009-2025 Movatter.jp