WO1996035310A1 - Complement cellulaire de reseau public a cable - Google Patents

Complement cellulaire de reseau public a cable Download PDF

Info

Publication number
WO1996035310A1
WO1996035310A1 PCT/US1996/006299 US9606299W WO9635310A1 WO 1996035310 A1 WO1996035310 A1 WO 1996035310A1 US 9606299 W US9606299 W US 9606299W WO 9635310 A1 WO9635310 A1 WO 9635310A1
Authority
WO
WIPO (PCT)
Prior art keywords
cellular
handsets
call
wired telephone
ceuular
Prior art date
Application number
PCT/US1996/006299
Other languages
English (en)
Inventor
Priscilla Marilyn Lu
Timothy R. White
Original Assignee
Interwave Communications International, Ltd.
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 US08/435,709 external-priority patent/US5734699A/en
Priority claimed from US08/435,838 external-priority patent/US5577029A/en
Application filed by Interwave Communications International, Ltd. filed Critical Interwave Communications International, Ltd.
Priority to EP96915505A priority Critical patent/EP0826291A1/fr
Priority to AU57266/96A priority patent/AU716483B2/en
Publication of WO1996035310A1 publication Critical patent/WO1996035310A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32—Involving wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/14—WLL [Wireless Local Loop]; RLL [Radio Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements

Definitions

  • the present invention relates to apparatuses and methods for implementing mobile communication. More particularly, the present invention relates to a novel cellular adjunct system that advantageously offers cellular-like service to regions in need of an inexpensive and easily implementable mobile communication solution without incurring the expenses of implementing a full-featured, standard cellular system.
  • each cordless phone set typically comprises a base unit and a cordless unit.
  • the base unit typically located inside a residence or a business office, is usually coupled physically by copper wires or fiber optics to the public switched telephone network (PSTN).
  • PSTN public switched telephone network
  • each cordless phone set is specifically associated with a telephone number.
  • each cordless phone's base unit is specifically associated with its cordless unit and communicates therewith in a wireless manner. As long as a user of the prior art cordless unit stays within the limited range of the associated base unit (under a quarter mile in most cases due to technical limitations inherent in cordless technology), calls may be made to and from the public network in a wireless manner.
  • the prior art cordless phone has some significant disadvantages. Besides the limited range, the prior art cordless technology is limited in the number of cordless units that a base unit can support. Typically one, no more than two, handset is provided per base unit in the prior art cordless phone. Because of this limitation, a telephone service provider must still run wires, either along telephone poles or in trenches, to each residence or business to enable telephone service, whether or not cordless. Therefore, although the cordless unit appears mobile to the user, the network that is required to implement this service is still essentially a wired telephone network.
  • GSM Global Systems for Mobile Communication
  • CAS novel cellular adjunct system
  • CO central office switches
  • such a novel cellular adjunct system provides substantially seamless call routing and subscriber information management between the wired phones of the public network and the mobile handsets of the novel cellular adjunct network.
  • subscriber and billing data of the novel cellular adjunct be centrally managed by the same central public subscriber management system that handles the subscriber and billing data of existing wired phone users.
  • the use of proven, off-the-shelf GSM components would not only reduce the expenses associated with developing and testing new hardware but also render the novel cellular adjunct system easily upgradable to a full-featured cellular network such as a GSM network.
  • the novel cellular adjunct system may be upgraded to a full-featured GSM cellular network without requiring users to change handsets or requiring a major reconfiguration of the network hardware.
  • the present inventive cellular adjunct system represents a highly efficient way to provide a wireless solution for a wired network without incurring the full costs and complexities associated with implementing a full-featured cellular system.
  • the present invention relates, in one embodiment, to a cellular adjunct system for extending telephone service offered by a public wired telephone network, which has wired telephone sets, to a plurality of cellular handsets.
  • the public wired telephone network includes an operation and maintenance center for managing subscriber data related to both the wired telephone sets and the plurality of cellular handsets.
  • the cellular adjunct system which facilitates cellular communication among the plurality of cellular handsets and between the plurality of cellular handsets and the wired telephone sets, includes a base station subsystem and a cellular adjunct control block.
  • the base station subsystem includes radio resource management facilities for permitting the plurality of cellular handsets to communicate with the base station subsystem in a cellular manner.
  • the cellular adjunct control block which is coupled between the base station subsystem and switching networks in the public wired telephone network, includes a registry, a mobile switching center, and a mini-central office.
  • the registry contains routing data related to the plurality of cellular handsets to facilitate routing calls thereto, the routing data including data indicating whether a particular cellular handset in the plurality of cellular handsets is available for receiving a call.
  • the mobile switching center is coupled to the registry and facilitates switching of calls among the plurality of cellular handsets.
  • the mini-central office is coupled to the registry and the mobile switching center and ascertains whether signaling data from a first cellular handset of the cellular handsets relates to an internal call or an external call.
  • the internal call represents a call between the first cellular handset and a second cellular handset of the plurality of cellular handsets.
  • the external call represents a call between the first cellular handset and one of the wired telephone sets in the public wired telephone network.
  • the signaling data is forwarded to the mobile switching center for switching the internal call if the signaling data relates to the internal call.
  • the signaling data is forwarded to the public wired telephone network for switching the external call if the signaling data relates to the external call.
  • the plurality of cellular handsets represent standard GSM handsets, thereby simplifying future upgrades of the inventive cellular adjunct system to a full cellular communication system.
  • the mobility management facility confines each of the plurality of handsets to its own base transmitter station home location area, thereby simplifying the implementation of cellular communication to and from the plurality of cellular handsets in the inventive cellular adjunct system.
  • Fig. 1 shows, in one embodiment, a representative cellular adjunct system (CAS);
  • CAS representative cellular adjunct system
  • Fig. 2 illustrates the major functional blocks of the cellular adjunct control block (CACB) 208 of Fig. 1;
  • CACB cellular adjunct control block
  • Fig. 3 shows a representative cellular adjunct system (CAS) subscriber database
  • Fig. 4 illustrates a cellular adjunct system (CAS), including its cellular adjunct control block (CACB) and the call paths made when routing calls;
  • CAS cellular adjunct system
  • CACB cellular adjunct control block
  • FIG. 5 shows in a flowchart format the steps involved when an MS unit wishes to update its location with a CAS HLR registry of a CAS network
  • Fig. 6 shows in a flowchart format the steps involved when a CAS HLR registry processes a received access request
  • Fig. 7 shows in a flowchart format the steps taken by the various subsystems of a CAS network when an MS unit originates a call from inside a CAS network;
  • Fig. 8 shows in a format the steps taken by the various subsystems of the CAS network in disconnecting a call
  • Fig. 9 shows in a flowchart format the steps involved when an MS unit of a CAS network acts as a receiving unit to receive a call initiated either from the public network or from another MS unit in the CAS network;
  • Fig. 10A shows in a flow chart format, from the CACB perspective, the steps taken when an MS unit of the CAS network originates a call;
  • Fig. 10B is a continuation of Fig. 10A.
  • Fig. 11 is a flow chart illustrating the steps taken by the CACB of the present invention, from the CACB perspective, when a call terminates on an MS unit of the CAS network.
  • Fig. 1 shows, in one embodiment, a representative cellular adjunct system (CAS).
  • a CAS 200 which includes a plurality of base transceiver stations (BTS's) 202 and 204, a base station controller (BSC) 206, and a cellular adjunct control block (CACB) 208.
  • BSC 206 and BTS's 202 and 204 are substantially identical to d e respective BSC and BTS's discussed in the aforementioned co-pending patent application WAVEP001.P.
  • the BSC's and the BTS's of the CAS form a base station subsystem (BSS).
  • BSS base station subsystem
  • the BSC and BTS's of Fig. 1 implements the aforementioned GSM standard.
  • the GSM standard is discussed throughout this specification for ease of illustration.
  • the present inventive CAS is not limited to any particular standard, and it should be within the abilities of one skilled in the art to modify the
  • each base station subsystem has radio resource management facilities for handling a finite number of mobile stations (MS units), or cellular handsets.
  • MS units mobile stations
  • BTS 202 is shown to be in radio contact with MS unit 220 and consequently provides radio-related resources for handling cellular communication to and from MS unit 220.
  • BTS 204 provides radio-related resources for handling cellular communication to and from MS units 222 and 224.
  • the mobile stations managed by CAS 200 e.g., MS units 220, 222, and 224, preferably represent standard cellular handsets. In one embodiment, they represent off-the- shelf GSM cellular handsets.
  • the use of standardized handsets advantageously permits the service provider, i.e., those who implement and/or manage CAS 200, to update at a later date CAS 200 to a standard full-featured cellular system without requiring owners of existing MS units 220, 222, and 224 to replace their handsets by purchasing new ones.
  • the use of standard cellular hardware for BSC 206 and BTS's 202 and 204 facilitates easy upgrade to a standard full-featured cellular system at a later date.
  • upgrading may, in one embodiment, simply be a matter of loading new software into the BSC and BTS chassis.
  • each MS unit being a standard GSM handset in one embodiment, may have a range as great as over 20 kilometers or as little as a few hundred meters. These enhanced capabilities represent a clear advantage over the range and capacity limitations of the prior art cordless phone systems.
  • the novel CAS advantageously provides the ability to restrict the roaming area of a given handset to a very small area. Additionally, if the range is at its lower end, as is the case in one embodiment, transmission power may be reduced, thereby providing additional cost savings over traditional, full-featured cellular systems that typically provide a much greater range.
  • CACB 208 communicates with a public network 210, which represents the public switched telephone network (PSTN) in one embodiment, through link 211.
  • PSTN public switched telephone network
  • Link 211 is preferably through a SS7 signaling link although other types of signaling links such as R2 or ISDN signaling may also be used.
  • Link 211 is used for coupling CACB 208 to a PSTN switching resources.
  • the PSTN switching resources represent the switching network (209) of the wired telephone network.
  • the PSTN switching resource may be an existing central office (CO 207).
  • CACB 208 is an integral part of the public network, serving as a gateway to the CAS's MS units. In fact, the CAS network behaves, from the perspective of the public network, as if it is an extension of the wired central office (CO).
  • the extension allows the service provider to offer telephone service to areas where CO implementation may not be practical, e.g., due to economic or geographic factors, and to provide cellular telephone access.
  • the fact that communication between the BTS's of the CAS and its MS units is accomplished in cellular manner is largely transparent to the rest of the public network.
  • OMC 212 associated with public network 210.
  • OMC 212 in public network 210 communicates with CACB 208 via a link 213, which uses an X.25 protocol in one embodiment. In some embodiments, other protocols such as TCP/IP, ATM, and the like, may be used.
  • OMC 212 typically includes a set of applications for managing subscriber- related data such as subscriber information, billing, network maintenance, and the like.
  • OMC 212 manages only the subscriber data related to the wired phone customers.
  • Cellular subscribers who utilizes prior art cellular networks typically have their subscriber data handled by a different subscriber management system, i.e., one specifically associated with the cellular system. For this reason, bills from the PSTN provider and the cellular provider are typically handled separately in the prior art.
  • OMC 212 of public network 210 also provides subscriber data management for the CAS customers.
  • subscriber information such as billing address, billing information, the type of service chosen, the telephone number associated with MS unit 224 is kept track of by OMC 212.
  • a subset of the subscriber information also resides in a home location registry (not shown in Fig. 1) in CACB 208 to facilitate call routing.
  • CACB 208 keeps track of phone usage by its MS units and supplies that information to the public network 210 which, through OMC 212, administers any charge for usage of the CAS network 200. Since both the subscriber data and the billing service are managed by the public network, these tasks are advantageously offloaded from CAS administrators, which in turn advantageously reduces the operational overhead associated with providing cellular service to CAS customers.
  • connection from CACB 208 to public network 210 is typically a wired connection.
  • the connection may be made wireless, e.g., by a microwave link. This is especially advantageous in situations where CAS's are deployed in widely dispersed and remote environment. In this case, the use of a microwave link may provide substantial savings since it obviates the expenses associated with laying wires over long distances.
  • the connection between CACB 208 and BSC 206 is typically a wired connection, as is the connection between a BSC and its BTS's.
  • the cellular portion of the CAS system exists between the BTS, e.g., BTS 202 or BTS 204, and the MS units since infrastructures to handle the MS units in a wireless manner exist in the BTS's 202 and 204, and to a certain extent, in BSC 206.
  • BTS base station
  • BSC mobile switching station
  • connection cross connect may be made at lower levels in the network hierarchy, such as at BSC 206, or at BTS 204.
  • Fig. 1 also shows a wired phone 214, which is coupled to public wired telephone network 210 in a conventional manner. Wired phone 214 is not considered part of CAS network 200.
  • the public network routes the call between wired phone 214 and MS unit 222 by routing between the two endpoints known to the public network, i.e., the CO in charge of wired telephone 214 and CACB 208.
  • CACB 208 will consult its own database, known as a home location registry (CAS HLR) and finds the information to allow it to route the call to MS unit 222.
  • CAS HLR home location registry
  • MS unit 222 wants to call wired phone 214
  • MS unit 222 presents the telephone number of wired phone 214 to CACB 208.
  • CACB 208 will, using for example a dial number tree, ascertain that the phone number sent by MS unit 222 is not one that is associated with one of the MS units in CAS 200.
  • CACB 208 will request the public network to route the call between itself and the CO (not shown) associated with wired phone 214, thereby completing the call path.
  • a MS unit therein may dial and be connected to a MS unit within CAS 200 of Fig. 1 in a manner that is totally transparent to both public network 210 and the origination CAS system.
  • the fact that the call is now MS unit to MS unit is transparent because the public network simply routes the call between two known endpoints, whether each is a CACB, a CO, or the like.
  • Fig. 2 illustrates the major functional blocks of CACB 208 of Fig. 1.
  • IPN public network
  • the interface is internal since, as mentioned earlier, the CAS is considered an integral part of the public network.
  • IPN 250 facilitates communication with the public network, which communication utilizes the SS7 signaling in one embodiment.
  • Fig. 2 further shows in CACB 208 a home location registry (CAS HLR) 254 for storing subscriber data relating to the CAS customers.
  • CAS HLR home location registry
  • each subscriber in the CAS network is considered to have fixed home location, which is limited to a BTS domain in the basic CAS configuration, or may be expanded to include a number of BTS's, the domain of a BSC, the domain of a set of BSC's, or even the domain the entire CAS network in enhanced configurations.
  • OMC interface block 252 facilitates communication between CACB 208, particularly a CAS HLR 254 therein, with OMC 212.
  • OMC interface 252 implements an X.25 protocol for communication between CACB 208 and OMC 212.
  • CAS HLR 254 does not need to know, in one embodiment, all the subscriber information in the public subscriber management system of the public network to enable CACB 208 to perform its routing function. It is contemplated that, in one embodiment, only routing data is required in the CAS HLR 254. In another embodiment, the only information required is that which is necessary for authenticating whether a given MS unit is authorized to use the resources of the CAS system to make and receive calls. Consequently, only a small subset of the subscriber information in the public subscriber management system of the public network needs to reside in CAS HLR 254. In yet another embodiment, however, CAS HLR 254 may have all the subscriber data relating to CAS customers.
  • Fig. 2 also shows a TRAU block 256.
  • TRAU block 256 is located adjacent to IPN 250 and away from its prior art position, which is on the mobile station side of the private mobile switching center (MSC) 258.
  • MSC private mobile switching center
  • Private MSC 258 stays substantially the same as the private MSC disclosed in the aforementioned co-pending patent application WAVEP001.P. In one embodiment, there is only one private MSC 258 per CAS system.
  • TRAU is not automatically provided for calls which are strictly internal to the CAS network, i.e., between two MS units of the CAS network, provides advantages which are discussed extensively both co-pending patent applications WAVEPOOl.P and WAVEP004.P.
  • a mini CO 260 whose main job is to control the switching between calls that either originates from or terminates at one of the MS units of the
  • the mini CO may be made in reference to the aforementioned co-pending patent application (Attorney Docket No. WAVEPOOl.P).
  • no mini CO 260 is provided.
  • the CAS network simply provides call connectivity to the public network, via IPN 250, where call switching actually takes place.
  • Private MSC 258 still handles location update requests and other optional supplemental services.
  • this CAS configuration represents an inexpensive way to provide cellular-like service as an adjunct to existing wired public network.
  • the CACB is connected to a CO within the PSTN, this CO can be used to switch calls to and from MS units of the CAS network.
  • the CO does not even have to be a cellular or GSM CO.
  • wired CO's such as AMPS, POTS, TABS, analog CO's, or the like may be used.
  • AMPS AMPS
  • POTS POTS
  • TABS analog CO's
  • communication between that CO and the CAS may take place through a proper interface, which may be a DSO interface in one embodiment. This is in contrast to prior art cellular systems which require a cellular CO, e.g., a GSM CO.
  • the ability to use a mini CO to implement switching within the CACB allows more flexibility in the implementation of the CAS system and may result in substantial savings. This feature is especially advantageous for markets like small island nations where the public network central office may be hundreds of miles away from the villages where the CAS network is implemented.
  • Using a mini CO permits local calls, i.e., calls between MS units of the CAS network, to be switched locally, thereby alleviating the bottleneck that is present when all calls must be backhauled long distance back to the public network CO for switching.
  • the coupling between the CAS CACB and the switching resources of the public wired network may be accomplished using a wireless link such as a microwave link.
  • administration of subscriber and billing tasks be centralized so as to relieve the CAS administrator of the expenses associated with maintaining a subscriber and/or billing database.
  • Mini CO 260 keeps track of the dial number tree in order to perform call switching and also communicates with CAS HLR 254 to authenticate and validate whether a certain MS unit can perform certain supplemental services such as call forwarding, conference calls, and the like.
  • Fig. 3 shows a representative simple CAS subscriber database, which resides on CAS
  • HLR 254 It should be kept in mind that the CAS subscriber database shown in Fig. 3 is only representative and variations may exist. Within the CAS subscriber database, there exists routing data for the MS units.
  • Field 270 contains the IMSI of the MS units of the CAS network.
  • Field 272 contains the phone number associated with the IMSI in field 270.
  • Field 274 contains the home location of the MS unit whose SI is shown in field 270. In one embodiment of the basic CAS configuration, there is no roaming among BTS's and consequently, the home location may be narrowed down to a specific BTS. However, a given MS unit may be allowed to reside in multiple BTS's location areas.
  • Field 276 indicates the status of the MS unit whose IMSI is shown in field 270. Statuses of an MS unit may include flags to indicate whether the MS unit is within the home location indicated in field 274, whether the MS unit is turned on and has checked in timely, and the like.
  • field 278 there optionally exists a list of supplemental services subscribed to by the MS unit associated with the IMSI list in field 270. Note that the supplemental services are not offered for all CAS configurations, and the omission of these services may, in some cases, advantageously facilitates lower entry cost for service providers who wish to offer cellular-like service as an adjunct to a public wired telephone network.
  • Fig. 4 illustrates CAS network 300 including CACB 208, BSC's 302 and 304, and
  • BTS's 306, 308 and 310 BTS's 306, 308 and 310.
  • BTS 306 is controlled by BSC 202 while BTS's 308 and 310 are controlled by BSC 304.
  • BSC 304 BTS's 308 and 310 are controlled by BSC 304.
  • MS unit 370 is controlled by BTS 306
  • MS unit 372 is controlled by BTS 308, and MS unit 374 is controlled by BTS 310.
  • Fig. 4 further shows a public wired network 320 coupled to CACB 208 of CAS network 300.
  • a wired phone set 330 is coupled to public wired network 320 in a conventional manner.
  • Fig. 4 further shows a plurality of call paths 340 and 342.
  • MS unit 372 wishes to make a call to wired phone set 330, which is outside of CAS network 300, i.e., an external call
  • MS unit 372 requests a connection that connects it to private MSC 258.
  • MS unit 372 provides an initial address message (IAM) to private MSC 258.
  • IAM initial address message
  • the signaling data received by private MSC 258 is then forwarded to mini CO 260.
  • Mini CO 260 by going through the dial number tree, will realize that the phone number dialed does not belong to one of the MS units in CAS network 300.
  • mini CO 260 will forward the received IAM to internal interface to public network (IPN) 250.
  • IPN 250 Through its signaling link, IPN 250 sends the IAM to public wired network 320, where the call is eventually routed to wired phone set 330 in a conventional manner. In the reverse direction, when wired phone set 330 wishes to call an MS unit within
  • CAS network 300 it will send its dialed number to public wired network 320. Based on the number dialed by wired telephone 330, public wired network 320 will find the mini CO 260 in, say, the first six digits of the 10-digit telephone number dialed. In this case, the mini CO 260 is the one associated with CACB 208. Mini CO 260 in CACB 208 will receive the IAM, consults with CAS HLR 254 to ascertain the MS unit associated with the telephone number dialed (which is contained in the IAM). Mini CO 260 also ascertains in the database of CAS HLR 254 whether the status of the MS unit associated with the telephone number dialed indicates whether it is available for taking the incoming call or whether it is busy with another call.
  • mini CO 260 preferably returns a busy indication to the calling CO in the public wired network.
  • a ringing indication e.g., an alert message
  • the status of the destination MS unit may indicate that it is not turned on or has not checked in timely when it, for example, roams out of its allowed home location area (which may be as narrow as a single BTS in the basic CAS configuration or as wide as the entire CAS network in the enhanced configuration). If, however, the destination MS unit has been turned on and is not busy, when the user answers the call, the call will be terminated (connected) at the destination MS unit.
  • the steps for call termination at an MS unit of the CAS network are shown later in Figs. 9 and 11.
  • MS unit 370 For calls that are strictly within CAS network 300, e.g., internal call, between MS units 370 and 374, the procedure is slightly different. Assuming for the moment that MS unit 370 is the calling MS unit and MS unit 374 is the destination MS unit. MS unit 370 would first request a connection that connects it to private MSC 258. MS unit 370 then provides an initial address message (IAM) to private MSC 258. Th signaling data received by private MSC 258 from MS unit 370 is then forwarded to mini CO 260. The mini CO 260 will go through the dial number tree and realize that the destination telephone number belongs to one of the MS units in CAS network 300 (i.e., MS unit 374).
  • IAM initial address message
  • Mini CO 260 then consults with CAS HLR 254 to determine whether the destination MS unit, i.e., MS unit 374, is available to receive a call (i.e., has been turned on, checked in timely, and not busy). If MS unit 374 is available for receiving the phone call, mini CO 260 utilizes private MSC 258 to perform the connection cross connect between MS unit 370 and MS unit 374. The call path between MS unit 372 and MS unit 374 is shown as path 342 in Fig. 4.
  • connection cross connect between MS unit 370 and MS unit 374 may be made at a lower level in the network hierarchy, e.g., between BSC 302 and BSC 304. Further, unless MS units 370 and 374 communicate at different rate, rate conversion via TRAU is not necessary. In the present invention, TRAU is not automatically required since TRAU unit 256 has been moved from the BTS side of the MSC 258 to its public network side. This is unlike the situation in prior art cellular systems where calls between MS units are automatically TRAUed in the call path portion between the MS units and a prior art MSC.
  • Fig. 5 shows in a simplified flowchart format the steps involved when an MS unit wishes to update its location with the CAS HLR registry of the CAS network.
  • Fig. 5 starts at block 700.
  • an updating MS unit sends to a BSC subsystem via a BTS subsystem a location update request.
  • a location update request includes the IMSI of the updating MS unit.
  • the location update request may contain a version of the IMSI, known as a TMSI (temporary MSI that is used in place of the IMSI for, among others, security reasons).
  • TMSI temporary MSI that is used in place of the IMSI for, among others, security reasons.
  • the identity of the MS unit via either the IMSI or TMSI, uniquely identifies the MS unit that desires a location update.
  • the BSC subsystem forwards to the MSC subsystem a SCCP connect request for the MS unit that sent the location update request in block 704.
  • SCCP Signaling System 7
  • SCCP connect request preferably represents, in one embodiment, a message conforming to signaling system 7 (SS7) or the A interface between the BSC and the private MSC function on the CACB.
  • SS7 signaling system 7
  • the SCCP connect request encapsulates the location update request sent by the updating MS unit in block 702.
  • Block 702 and 704 builds the mobility management (MM) session.
  • MM mobility management
  • the MSC subsystem sends to the BSC subsystem a SCCP connect confirm to validate that an MM connection is established.
  • the MSC subsystem sends, in block 708, to the CAS HLR registry a process access request, which request includes the information contained in the location update request received at block 702 ,to ascertain via the CAS HLR registry whether the MS unit that is requesting the location update is "authorized", i.e., allowed to use the CAS network resources, and whether the updating MS unit has roamed away from its last location, necessitating an update in the CAS HLR registry.
  • a MS unit In the basic CAS configuration, a MS unit is only authorized to use the CAS network resources if it is located in the BTS location area assigned to it. In one enhanced embodiment, however, roaming among BTS's is enabled, and a given MS unit is deemed “authorized” to use any BTS of the CAS network as long as it is assigned to one of the BTS's.
  • the CAS HLR registry processes the received access request which was sent in block 708. Block 710 is more fully explained in a subsequent Fig. 6. In block 712, the
  • CAS HLR registry sends the MSC a location update confirm, indicating whether the updating MS unit is authorized to use the resources of the CAS network. If the updating MS unit is authorized to use the resources of the CAS network, the location update confirm preferably further includes information indicating whether a location update has been performed in the CAS HLR registry. In decision box 714, it is ascertained whether the updating MS unit is authorized (from the location update confirm received in block 712). If it is determined in block 714 that the updating MS unit is authorized to use the resources of the CAS network, the method proceeds to block 716 wherein a location update confirmed message is sent from the MSC to the BSC.
  • the SCCP clear message is sent from the MSC subsystem to the BSC subsystem to clear the MM session built in block 702 and block 740. Subsequent to blocks 720, the BSC that receives the SCCP clear message in block 720 clears the channel all the way to the updating MS unit. In block 724, the BSC that receives the SCCP clear message in block 720 returns a clear complete message to the MSC, indicating that the MM session has been completely cleared. In block 726, the steps involved in updating location from an MS unit via an MSC is finished.
  • the method immediately proceeds to block 728-734 to clear the SCCP or MM session.
  • a MS unit may not be authorized if, for example, the CAS system is implemented as a basic configuration (i.e., no roaming among BTS's allowed), and that MS unit has been found in a BTS location area that is different from the one assigned to it.
  • the MSC subsystem sends to the BSC subsystem a location update reject message, indicating that the request to update location by the updating MS unit cannot be processed.
  • the MSC subsystem sends to the BSC subsystem an SCCP clear message to begin clearing the MM session.
  • the BSC clears the channel all the way to the updating MS unit.
  • the BSC subsystem sends to the MSC subsystem a clear complete message, indicating that the MM session built in blocks 702 and 704 is cleared. Thereafter, the method proceeds to blocks 726 where the steps of Fig. 5 end.
  • Fig. 6 shows in a flowchart format the steps involved when the CAS HLR registry processes the received access request in block 710 of Fig. 5.
  • Fig. 6 starts at block 750. From block 750, the method proceeds to block 752 wherein the process access request message sent by the MSC subsystem of block 708 of Fig. 5 is received.
  • the LMSI associated with the updating MS unit is checked, in block 754, against all entries in the CAS HLR registry to determine whether the updating MS unit is authorized to use the resources of the CAS network.
  • a MS unit in the basic CAS configuration is only authorized to use the CAS network resources if it is located in the BTS location area assigned to it.
  • roaming among BTS's is enabled, and a given MS unit is deemed "authorized” to use the resources the CAS network as long as it is assigned to one of the BTS's.
  • the validation procedure may be used to prevent a non-native MS units from using the resources of the CAS network.
  • block 754 may further include certain security functions such as password checking, challenging, authenticating, or the like. If it is ascertained in block 756 that the updating MS unit is authorized the use of resources of the CAS network, the network proceeds to block 758 to update the CAS HLR registry if necessary. In block 758, the identity of the updating MS unit is checked to see whether its location needs to be updated in the CAS HLR registry that receives the process access request.
  • the method proceeds to block 760 wherein the CAS HLR registry sends a location update confirm to the MSC subsystem.
  • the location update confirm sent in block 760 indicates whether the updating MS unit is authorized to use the resources of the CAS network and if it does, whether an update to the CAS HLR registry has been performed.
  • the step of Fig. 6 end.
  • Fig. 7 shows in a flowchart format the steps taken by the various subsystems of the CAS network when an MS unit originates a call from inside the CAS network.
  • the steps of Fig. 7 start where Fig. 5 (MS location update) leaves off following block 716. This is because it is still necessary for the MS unit to build the MM session (blocks 702 to 706), sends a process access request to the CAS HLR registry for processing (blocks 708-712), disabling the MS unit from using the resources of the CAS network if such usage is not authorized (blocks 714, 728, 730, and 734), and permits the call to proceed if the originating MS unit is authorized to use the resources of the CAS network (blocks 714, and 716).
  • the message that piggybacks on the SCCP request of block 704 of Fig. 5 indicates to the MSC that a call and not a location update is being attempted.
  • the calling MS unit may inform the CACB using any method of signaling that is convenient to implement.
  • blocks 758 is not performed in one embodiment when an MS unit is building a call.
  • the method proceeds from block 756 to block 760 directly if it is ascertained that the calling MS unit is authorized to use the resources of the CAS network.
  • the method proceeds to block 802 wherein the calling MS unit sends the MSC (via the BTS and BSC) a setup message which typically includes, among others, the destination phone number and information indicating whether the call to be built is voice, data, fax, and the like.
  • the method then proceeds to block 810 where the CAS HLR registry sends a map complete call, which is a mobile-application-part type of message, to the MSC.
  • the map complete call sent in block 810 is received by the MSC from the CAS HLR registry in block 812.
  • the MSC sends the mini CO an initial address message (IAM) which in the GSM implementation includes the destination phone number to indicate its desire to connect to a particular destination phone.
  • IAM initial address message
  • the MSC in the CACB decides the optimal cross-connect point, e.g., via BTS, BSC, MSC in the CACB or forwards the call to a public network.
  • the MSC sends to the MS unit a call proceeding message responsive to a validation of the destination phone to indicate that the call is being processed.
  • an address complete message (ACM) is sent from the mini CO to the MSC to indicate that the entire destination number (the dialed number) has been received and that the call has been connected to its destination.
  • the receipt of the ACM message by the MSC also signifies a successful alerting on the called party, i.e., the destination phone is ringing.
  • the MSC sends to the MS unit, responsive to the receipt of the ACM message received in block 818, an alerting message to the MS unit to inform the MS unit that the party called is being alerted and to turn on the ringer at the calling MS unit.
  • the MSC sends the BSC an assignment request message to assign channel for the bearer, e.g., the actual voice/data, channel on the A interface and to instruct the BSC to use the assigned channel to build the call.
  • the assigned channel represents the channel on which the calling MS unit may send and receive its bearer data. It should be noted that the steps in block 822 may occur asynchronously with respect to the other steps of Fig. 7.
  • the MSC sends the assignment request to the BSC right after the MSC sends to the mini CO the IAM message (block 814). After the alerting message is received by the MS unit, the ringer circuit at the calling MS unit continues to ring until either the called party picks up the call or the caller hangs up, in which case the MM session is again cleared in the manner earlier discussed.
  • Fig. 8 shows in a flowchart format the steps taken by the various subsystems of the
  • the call may also be disconnected when an MS unit in the call path moves out of range of its assigned home location area.
  • the home location area is limited to the location area of the BTS to which the MS unit is assigned as its home location.
  • the home location area may include a number of BTS's, the domain of a BSC, the domain of a set of BSC's, or even the domain the entire CAS network in enhanced configurations. Further, it is possible, in one embodiment, to provide for full international roaming, e.g., by implementing a full-featured MSC in CACB 208.
  • the call is disconnected when either the calling party disconnects in block 902 or the called party disconnects in block 904.
  • the MSC receives from the calling MS unit a disconnect message, signifying that the calling party either has hung up or has roamed out of range.
  • the MSC receives from the called party via the mini CO a disconnect message, signifying that the called party either has hung up or has also moved out of range.
  • the MSC sends to the mini CO a release message to be forwarded to the called party responsive to the receipt of the disconnect message in either block 902 or block 904.
  • the called party may be in the CAS network or in the public network, in which case the release message is forwarded via the internal interface to the public network (IPN).
  • IPN public network
  • the called party sends to the MSC via the mini CO a release message signifying the release authorization.
  • release completion is acknowledged.
  • the mini CO receives from the MSC a release complete message responsive to the release message sent in block 908.
  • the MSC receives from the mini CO the release complete message responsive to the release message sent in block 906.
  • all resources that are associated with the call being disconnected, e.g., TRAU, echo canceling, or the like, are released.
  • the MSC clears the MM session all the way to the calling MS unit.
  • the MSC sends to the BSC a SCCP clear message to initiate clearing of the MM session. Thereafter, the BSC clears the MM session all the way to the calling MS unit.
  • the BSC sends back to the MSC an SCCP clear complete message indicating that the MM session has been cleared.
  • the steps of Fig. 8 end.
  • Fig. 9 shows in a flowchart format the steps involved when an MS unit of the CAS network acts as a receiving unit to receive a call initiated either from the public network or from another MS unit in the CAS network.
  • Fig. 9 starts at block 950.
  • the MSC receives an initial address message (IAM) message from the network through the mini CO for a call that is terminating at an MS unit in the CAS network. If the calling unit is another MS unit in CAS network, the IAM message received in block 952 represents substantially the same IAM message sent by the calling MS unit in block 814 of Fig. 7.
  • IAM initial address message
  • block 954 the MSC sends a map send information service request for the incoming call to the CAS HLR registry to locate the MS unit represented by the telephone number in the IAM message.
  • block 954 involves determining the current location of the destination MS unit in the CAS network (e.g., whether it has roamed away from its home location area if the configuration is enhanced), the IMSI number that corresponds to the telephone number received in the IAM message, the particular supplemental services subscribed to by the destination MS unit, and the like.
  • the CAS HLR registry after locating the current location area of the destination MS unit in block 954, sends a map page message to the MSC to request the MSC to page the destination MS unit by either its IMSI or some version thereof.
  • the map page message is sent to the MSC where the MS unit is currently located (as determined after consulting with the CAS HLR registry).
  • both map send information message and map page messages are representative of a type of mobile application part message.
  • the MSC responsive to receiving the map page message in block 956, sends to the proper BSC a paging request message.
  • the receiving BSC's may be more than one BSC if the CAS HLR is uncertain regarding which BSC location area the destination MS unit is located. This is particularly true for the enhanced CAS configuration.
  • the CAS HLR registry may, in one embodiment, know the exact BSC/BTS in which the destination MS unit is located (either through updates by the MS unit or because the MS unit is fixed to a particular BTS home location area). Responsive to the paging request, the BSC or BSC's page the destination MS unit and wait to hear the paging response from the destination MS unit.
  • the destination MS unit then sends a paging response to the BSC (via a BTS), which response is then encapsulated in a SCCP connect request that the BSC subsequently forwards to the private MSC.
  • a BTS BTS
  • SCCP connect request a SCCP connect request that the BSC subsequently forwards to the private MSC.
  • the MSC responsive to receiving the SCCP connect message from the BSC in block 960, returns a SCCP connect confirmed message to the BSC.
  • the steps in blocks 960 and 962 build the mobility management (MM) session by associating the destination MS unit with a particular SCCP identifier.
  • the MSC sends to the CAS HLR registry a process access request service request to validate the responding destination MS unit.
  • the destination MS unit is then validated.
  • the MSC sends to the CAS HLR registry a process access request service request to validate the responding destination MS unit.
  • the destination MS unit is then validated.
  • MS unit for which the paging request was sent (block 958) is further checked to see whether it is authorized or appropriate to establish bearer data communication channel to that destination MS unit.
  • the step of processing an access request from MSC to HLR of block 964 may involve exchanges of additional messages therebetween to, for example, perform authentication.
  • the MSC sends a setup message to the destination MS unit to set up a call.
  • the setup message contains the call control information, e.g., the type of services required (e.g., data/voice/fax) and optionally the calling party's phone number that is utilized for setting up the call.
  • the MSC sends to the mini CO an address complete message (ACM), signifying to the network that enough of the address (e.g., the dialed phone number) has been received to enable the CAS network to locate the destination MS unit.
  • ACM address complete message
  • the MSC receives from the destination MS unit an alerting message, indicating that the MS unit has acknowledged that a call that terminates on it has been attempted and that ringing may begin.
  • block 970 the MSC sends an ACM message to the mini CO. It should be noted that although block 970 is shown after block 968 in Fig. 9 , block 970 in fact occurs asynchronously with respect to the blocks of Fig. 9. By way of example, block 970 may occur as early as immediately following block 952.
  • the bearer data channel resources between the MS unit and the MSC are assigned.
  • the MSC sends to the BSC (to be forwarded to the destination MS unit) an assignment request message to assign bearer data channel resources between the MSC and the BSC.
  • the effect is to move the destination MS unit from a signaling only channel (which the MS unit has been on thus far in Fig. 9) to an assigned bearer data channel.
  • blocks 972 and 974 involve intelligent cross-connect that delegates the actual cross-connect between the incoming path and the outgoing path for calls between two MS units of the CAS network to a lower level in the hierarchy.
  • the MSC receives from the destination MS unit a connect acknowledge message, indicating that the destination MS unit is picked up. Responsive to the received connect acknowledge message in block 978, the MSC sends to the mini CO a answer message (ANM) in block 980 to indicate to the calling unit (which may be in the public network or another MS unit in the CAS network) that the destination MS unit has answered by picking up the call. In block 982, the call is now in progress.
  • NAM mini CO a answer message
  • Fig. 10A starts at block 1000.
  • the mini CO receives an initial address message (IAM) from the private MSC.
  • IAM initial address message
  • the IAM message typically includes the destination phone number dialed.
  • all digits of the destination phone number typically arrive all at once. In other implementations, the digits may arrive one at a time as the number is being dialed.
  • the destination network whether it is a PSTN or within the CAS network that originates the call, is found.
  • the destination network is ascertained by walking through a dialing tree one digit at a time to ascertain the outgoing path. The process next proceeds in one of two branches depending on the call path.
  • the process proceeds to block 1012, representing the PSTN path.
  • the CACB assigns the appropriate interface for communication with the PSTN, e.g., internal interface to public network (IPN) 250 of Fig. 4, in block 1014.
  • IPN public network
  • the destination phone set is located outside the cellular domain, it may be necessary to assign rate conversion and echo canceling resources, i.e., TRAU and echo canceller, if necessary in block 1020.
  • block 1014 i.e., the internal interface to public network.
  • block 1024 may further include the exchange of messages, e.g., IAM, ACM, ANM (see, e.g., Fig. 7), and the actual connection from the private MSC to the appropriate interface the GMSC. Thereafter, the call is in progress in block 1026.
  • messages e.g., IAM, ACM, ANM (see, e.g., Fig. 7)
  • the process proceeds to block 1032, signifying that the incoming call path loops back into the same CACB from which the call is originated and that the actual cross-connection of bearer data channels should be made internally either by the MSC of this CACB or by another functional block, e.g., BSC, BTS, further down the hierarchy (if intelligent cross-connect is involved as is disclosed in co-pending patent application WAVEP004.P).
  • an IAM message is sent in block 1036.
  • This IAM message does not go out on an external network interface but it is sent to a new process to terminate the incoming call within the CACB.
  • the IAM sent in block 1036 is received in block 1102 of Fig. 11 by the process that terminates an incoming call.
  • the IAM message may include additional information to indicate that the message in an on-CAS-net type message which may differ from the standard IAM message typically sent off CAS net.
  • the IAM message may include additional information to identify that different resource requirements, e.g., no echo canceling, no TRAU, as well as the communication rates of the MS units. In some cases, some of the above information may be included in the ACM message as well.
  • Enhanced messages of, for example, IAM, ACM, and ANM (referred to as IAM', ACM', and ANM' for convenience) may be utilized to facilitate, for example, intelligent cross-connecting and TRAUing of call paths.
  • IAM', ACM', and ANM' for convenience
  • the process that initiates the call and sends out the IAM message in block 1036 receives an ACM (address complete message) from the process that terminates the call of Fig. 11. Specifically, this ACM came from block 1118 of Fig. 11.
  • ACM address complete message
  • the outgoing and incoming bearer channels are connected together.
  • any required inner working functions IWF's
  • TRAU TRAU
  • echo-cancelling any required inner working functions
  • intelligent cross-connecting and TRAUing may be involved as discussed in the above- mentioned co-pending patent application WAVEP004.P).
  • Fig. 10B is a continuation of Fig. 10A.
  • the process receives, in block 1048, from the outgoing process of Fig. 11 an ANM message.
  • the ANM message is received from block 1122 of Fig. 11.
  • the ANM message indicates that the destination MS unit has answered the call.
  • the mini CO forwards an answer message (ANM) to the MSC associated with the MS unit that initiated the call and sent the IAM message in block 1002 of Fig. 10A.
  • ANM answer message
  • Fig. 11 starts at block 1100. From block 1100, the process proceeds to block 1102 where an initial address message (IAM) is received from either a public network or from an MS unit in the CAS network. If an MS unit within the CLLLS originated the call then the IAM message received in block 1102 is substantially the same one that was sent from block 1036 of Fig. 10A. In this case, the call is considered an internal call, i.e., a call between two MS's of the same CAS network.
  • IAM initial address message
  • the mini CO consults with the CAS HLR registry to locate the destination MS unit in the CAS network.
  • Block 1104 is necessary in the case, for example, where the destination MS unit may have roamed away from its home location area, i.e. out of range, or may have been turned off . If the destination MS unit is not turned on, the signaling session ends after a predetermined time period.
  • block 1106 it is ascertained whether the destination MS unit, whose telephone number is encapsulated in the IAM message received in block 1102, is authorized to use the resources of the CAS network to make calls. If the MS is considered to be unavailable, e.g., if it is busy or deemed unreachable, the process proceeds to block 1108, where a fast busy signal may be generated.
  • the process proceeds to block 1110 wherein the CACB assigns inner working functions as necessary, e.g., echo canceller.
  • the CACB may also assign TRAU.
  • the mini CO forwards the IAM message received in block 1102 to the
  • the address complete message (ACM) is received by the mini CO from the MSC signifying that the destination call has received the complete address.
  • the bearer data channel is connected through from the MSC to the appropriate interface. The connecting through between the appropriate interface and the MSC facilitates full duplex communication.
  • the mini CO forwards the ACM message which was received in block 1114 to the public network or, in the case of internal call, back to the originating process of Fig. 10A, which is received in block 1038 therein.
  • the MSC sends an answer message (ANM) message to the mini CO in block 1120.
  • NAM answer message
  • the mini CO forwards the ANM message which was received in block 1120 to the public network or, in the case of internal call, back to the originating process of Fig. 10B, which is received in block 1048 therein, to the MSC to signify that the called party has picked up the call. Thereafter, the process proceeds to block 1124 as shown in Fig. 11, wherein the call is in progress.
  • ANM Answer Message
  • BCF Base Station Control Function
  • BSC Base station Controller
  • BSS Base Station Subsystem
  • BTS Base Transceiver Station
  • CACB Cellular Adjunct Control Block
  • CCPU Cellular CPU CO: Central Office
  • cPBX cellular Private Branch Exchange
  • GMSC Gateway for MSC
  • GSM Global Systems for Mobile Communication
  • HLR Home Location Registry
  • IAM Initial Address Message
  • IMSI International Mobile Subscriber Identifier
  • ISDN Integrated Services Digital Network
  • IWF InnerWorking Functions
  • LAPD-M Link Access Protocol on the Dm (control) channel
  • MSC Mobile-Services Switching Center OMC Operation and Management Center
  • PSTN Public Switched Telephone Network
  • Radio Link RR Radio Resource Management
  • SMS Short Message Services
  • TDM data Time Division Multiplexed Data
  • TRAU Transcoder-Rate Adapter Unit
  • VLR Visitor Location Registry
  • VME An industry standard bus for interconnecting components wPBX: wired PBX
  • European Telecommunications Standards Institute "European digital cellular telecommunications system (Phase 2): Base Station Controller - Base Transceiver Station (BSC - BTS ⁇ l interface Laver 3 specification (GSM 08.58V . 1994, Valbonne - France.
  • European Telecommunications Standards Institute "European digital cellular telecommunications system (Phase 2): Mobile Application Part (MAP) specification (GSM 09.02)” . 1994, Valbonne - France.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Cables (AREA)

Abstract

Système de complément cellulaire permettant l'extension d'un service téléphonique doté d'un réseau téléphonique à câble à des combinés cellulaires sans que cela n'occasionne les frais associés à la mise en place d'un système cellulaire complet. Ce système de complément cellulaire comporte un sous-système de stations de base et un bloc de commande de complément cellulaire. Le sous-système de stations de base comporte des installations de gestion de ressources radio permettant au groupe de combinés cellulaires de communiquer avec le sous-système de stations de base en mode cellulaire. Le bloc de commande du complément cellulaire qui est couplé entre le sous-système de stations de base et les réseaux de connexion du réseau téléphonique public à câble, comporte un centre d'enregistrement, un centre de commutation mobile et un mini-central téléphonique. Sous la perspective du réseau téléphonique à câble public, les combinés cellulaires sont des combinés téléphoniques câblés gérés par le bloc de commande du complément cellulaire. Le fait que le système de complément cellulaire présente les avantages du sans fil généralement associés à un système cellulaire complet normalisé est évident pour le réseau téléphonique public à câble. Lorsque la gestion d'abonnés pour les combinés cellulaires est assurée par le réseau téléphonique public à câble, la mise en place du système de complément cellulaire est sensiblement simplifiée.
PCT/US1996/006299 1995-05-04 1996-05-03 Complement cellulaire de reseau public a cable WO1996035310A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP96915505A EP0826291A1 (fr) 1995-05-04 1996-05-03 Complement cellulaire de reseau public a cable
AU57266/96A AU716483B2 (en) 1995-05-04 1996-05-03 Cellular adjunct to a public wired network

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US08/435,838 1995-05-04
US08/435,709 US5734699A (en) 1995-05-04 1995-05-04 Cellular private branch exchanges
US08/435,709 1995-05-04
US08/435,838 US5577029A (en) 1995-05-04 1995-05-04 Cellular communication network having intelligent switching nodes
US645495P 1995-11-10 1995-11-10
US60/006,454 1995-11-10

Publications (1)

Publication Number Publication Date
WO1996035310A1 true WO1996035310A1 (fr) 1996-11-07

Family

ID=27358133

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1996/006299 WO1996035310A1 (fr) 1995-05-04 1996-05-03 Complement cellulaire de reseau public a cable

Country Status (5)

Country Link
EP (1) EP0826291A1 (fr)
CN (1) CN1098006C (fr)
AU (1) AU716483B2 (fr)
CA (1) CA2219793A1 (fr)
WO (1) WO1996035310A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0865219A2 (fr) * 1997-03-14 1998-09-16 Telia Ab Dispositif pour la téléphonie mobile
WO2000064204A1 (fr) * 1999-04-19 2000-10-26 Telia Ab Procede et dispositif pour eviter la transmission d'informations redondantes dans un reseau de communication numerique
WO2001024453A1 (fr) * 1999-09-29 2001-04-05 Nokia Corporation Reseau de telecommunication multicouche
WO2002080451A2 (fr) * 2001-03-28 2002-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Agent de terminal representant des terminaux sans fil dans un reseau de communication voix sur ip

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0024705D0 (en) * 2000-10-09 2000-11-22 Nokia Networks Oy Communication system
CN111400640B (zh) * 2020-04-10 2023-09-22 中国铁塔股份有限公司 一种站址全息信息管理系统、构建方法及构建装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0462727A2 (fr) * 1990-06-18 1991-12-27 Nortel Networks Corporation Communications mobiles
WO1993011625A1 (fr) * 1991-12-06 1993-06-10 Motorola Inc. Controleur de systeme radiotelephonique
EP0595392A1 (fr) * 1992-10-26 1994-05-04 Koninklijke Philips Electronics N.V. Système de communication, autocommutateur et carte de ligne
EP0605086A1 (fr) * 1992-12-30 1994-07-06 AT&T Corp. Petit système de télécommunications "sans fil"

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0462727A2 (fr) * 1990-06-18 1991-12-27 Nortel Networks Corporation Communications mobiles
WO1993011625A1 (fr) * 1991-12-06 1993-06-10 Motorola Inc. Controleur de systeme radiotelephonique
EP0595392A1 (fr) * 1992-10-26 1994-05-04 Koninklijke Philips Electronics N.V. Système de communication, autocommutateur et carte de ligne
EP0605086A1 (fr) * 1992-12-30 1994-07-06 AT&T Corp. Petit système de télécommunications "sans fil"

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0865219A2 (fr) * 1997-03-14 1998-09-16 Telia Ab Dispositif pour la téléphonie mobile
EP0865219A3 (fr) * 1997-03-14 1999-06-09 Telia Ab Dispositif pour la téléphonie mobile
WO2000064204A1 (fr) * 1999-04-19 2000-10-26 Telia Ab Procede et dispositif pour eviter la transmission d'informations redondantes dans un reseau de communication numerique
WO2001024453A1 (fr) * 1999-09-29 2001-04-05 Nokia Corporation Reseau de telecommunication multicouche
US7664049B1 (en) 1999-09-29 2010-02-16 Nokia Corporation Multilayer telecommunications network
WO2002080451A2 (fr) * 2001-03-28 2002-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Agent de terminal representant des terminaux sans fil dans un reseau de communication voix sur ip
WO2002080451A3 (fr) * 2001-07-16 2003-05-30 Ericsson Telefon Ab L M Agent de terminal representant des terminaux sans fil dans un reseau de communication voix sur ip

Also Published As

Publication number Publication date
AU5726696A (en) 1996-11-21
CN1098006C (zh) 2003-01-01
EP0826291A1 (fr) 1998-03-04
CN1189282A (zh) 1998-07-29
CA2219793A1 (fr) 1996-11-07
AU716483B2 (en) 2000-02-24

Similar Documents

Publication Publication Date Title
US5953651A (en) Cellular adjunct to a public wired network
AU724375B2 (en) Use of ISDN to provide wireless office environment connection to the public land mobile network
TW396693B (en) Private multiplexing cellular network
EP0993742B1 (fr) Fourniture de communications sans fil a un abonne d'un reseau filaire prive
US5887256A (en) Hybrid cellular communication apparatus and method
US5734699A (en) Cellular private branch exchanges
US6640108B2 (en) Cellular communication system
AU696486B2 (en) System and method relating to cellular communications
US6829477B1 (en) Private multiplexing cellular network
EP0826292B1 (fr) Procede et appareil de communication cellulaire hybride
AU716483B2 (en) Cellular adjunct to a public wired network
CA2353898C (fr) Service d'etablissement d'appel cellulaire-fixe et de transfert d'appels provenant d'un fournisseur de services de reseau cellulaire
EP1037478A1 (fr) Architecture de réseau de communication cellulaire pour des abonnés fixes
MXPA99005576A (en) Use of isdn to provide wireless office environment connection to the public land mobile network
KR19980022227A (ko) 개인통신교환기내의 핸드오프처리방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 96194893.0

Country of ref document: CN

AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG US UZ VN AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref document number: 2219793

Country of ref document: CA

Ref document number: 2219793

Country of ref document: CA

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1996915505

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1996915505

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWW Wipo information: withdrawn in national office

Ref document number: 1996915505

Country of ref document: EP