Cellular adjunct to a public wired network

The present invention is the follow-up part of the U.S. patent S/N 08/435,709, which is assigned together and pending approval. This patent is entitled "Cellular Private Exchange Extension" (Agent Case No. WAVEP001) on May 4, 1995 Proposed (hereinafter referred to as S/N08/435,709).

The following is listed as a reference with the pending U.S. patent application: "Cellular Private Exchange Extension" filed on May 4, 1995, attorney case number WAVEP001 (hereinafter referred to as S/N 081435, 709).

Proposed on May 4, 1995, "Smart Exchange Method and Device", US S/N 08/435,838, agent case number WAVEP004 (hereafter referred to as S/N 08/435,838).

At the same time, the "software architecture of cellular communication system" was proposed, US S/N(_), agent case number WAVEP005 (hereinafter referred to as WAVEP005).

Proposed on May 4, 1995, "Distributed Spectrum Communication Network Signal Processor", S/N08/434,554, Agent Case No. A-60910 (hereinafter referred to as 08/434,554).

"Cellular base station with intelligent call transmission" proposed on May 4, 1995, S/N08/434,598, agent case number A-61115 (hereinafter referred to as 08/434,598).

Proposed on May 4, 1995, "A Spread Spectrum Communication Network with Adaptive Frequency Alertness", S/N 08/434,597, Agent Case No. A-60820 (hereinafter referred to as 08/434,597).

For ease of reference, a glossary and abbreviation list are provided as Appendix A.

The present invention relates to a device and method for implementing mobile communication. More specifically, the present invention relates to an innovative cellular accessory system, which advantageously provides cellular services to areas that require low-cost and easy-to-implement mobile communication methods, without having to bear the cost of implementing a full-featured standard cellular system .

Mobile communication is known in the art. A limited form of mobile communication includes advanced technology wireless telephones. In the wireless telephone system of the advanced technology, the wireless telephone generally includes a host unit and a wireless unit. The host unit is usually placed in a home or office, and is usually connected to the public switched telephone network (PSTN) by copper wire or optical fiber. In order to distinguish this phone separately in the public network, each wireless phone has a phone number.

Moreover, each wireless telephone host unit is specifically connected with its wireless unit and communicates with it wirelessly. As long as the user of the wireless unit with advanced technology stays within the limited distance of the host unit (due to the inherent technical limitation of wireless technology, the maximum is less than a quarter of a mile), they can make calls to and from the public network in a wireless way .

However, advanced technology wireless phones have some major disadvantages. In addition to the limited distance, the advanced wireless technology is limited in the number of wireless units that a host unit can support. Generally speaking, in advanced wireless phones, each host unit provides one and no more than two mobile phones. Due to this restriction, telephone service providers still need to set up wires along telephone poles or ditches to every home or business in order to provide telephone service, regardless of whether it is wireless. Therefore, although the wireless unit seems to be mobile for users, the network required to implement this service is basically a wired telephone network.

The user's demand for mobile communication services and the increasing cost of building and maintaining a wired telephone infrastructure have caused many service providers to turn to other wireless technologies to solve them. Among the existing technologies, cellular technology has shown a clear lead in market capture. To be clear, the cellular telephone system using the standard called "Global System for Mobile Communications" (GSM) has steadily gained popularity among service providers and has become the system of choice for implementing cellular services. The popularity of the GSM standard stems from its robustness and its ability to support a rich set of features, such as worldwide travel, telephone mailboxes, data services, and auxiliary services. Information about the GSM standard is widely distributed in the public domain, some of which are listed in Appendix B.

However, the GSM cellular network or any cellular network related to this matter is still quite an expensive undertaking in many communities. Although the above-mentioned patent application S/N 08/435,709 has published methods and devices for implementing a cost-effective cellular system, I know that some communities, especially those in the world, are developing or Those in remote areas do not need a standard cellular network, such as the full set of features provided by those implementing the GSM standard. Such communities include islands, manufacturing facilities in remote areas, and remote villages. As shown, these communities need to choose a traditional wired network (which requires a vast actual basic architecture to implement) or a standardized cellular system, such as the current GSM cellular system, which provides many non-essential features to make it The cost is too high to apply to such communities.

For these communities, what is needed is an innovative Cellular Attachment System (CAS), which provides the advantages of cell-based services, such as the elimination of extensive wired networks, mobile phone mobility, etc., without implementation For example, the overall cost of a standard cell system. This standard system has features that may be impractical or unnecessary, such as global travel or data transfer. However, the important thing is that the cellular accessory system should work seamlessly with any existing wired PSTN network. Moreover, since some of these communities already have some existing central exchange rooms (CO), any communication system implemented in them needs to be integrated with the existing CO, so that these communities can use their existing CO hardware, software, And investment in other existing telephony infrastructure.

Moreover, this innovative cellular accessory system needs to be able to provide substantially seamless call transmission and customer information management between the wired telephone set of the public network and the mobile phone of the innovative cellular accessory system. In order to further reduce operating expenses, the customer and billing data of the innovative cellular subsidiary system should be centrally managed by the same central public customer management system that handles the customers and billing data of existing wired telephone users.

And know that by using widely existing and tested cellular components, GSM mobile phones, GSM base transceiver stations, and base station receiving hardware to implement the above innovative cellular accessory system, further cost savings can be achieved. Even if the innovative cellular accessory system is cost-saving by removing the expensive implementation of the entire set of GSM features in Tai Fu Province.

The use of tested and tested off-the-shelf GSM components not only reduces the costs related to the development and testing of new hardware, but also makes it easy to upgrade the innovative cellular accessory system to a full-featured cellular network, such as a GSM network. For example, when the community develops and requires a more complete set of cellular features, the innovative cellular accessory system can be upgraded to a fully featured SGM cellular network without the user having to change the mobile phone or major network hardware reorganization .

These and other highly needed features that overcome the shortcomings of traditional wireless telephone systems and full-featured cellular systems are achieved by the innovative cellular accessory system, which is described in detail in this specification and its accompanying drawings.

The cellular accessory system of the present invention represents a highly effective method for providing a wireless solution to the wired network without incurring the entire cost and complexity of implementing a fully featured cellular system.

In one embodiment, the present invention relates to a cellular accessory system for extending services provided by a public wired telephone network with wired telephones to multiple cellular phones. The public wired telephone network includes an operation and maintenance center to manage customer information about wired telephones and multiple cell phones.

The cellular accessory system facilitates cellular communication among multiple cellular phones and between multiple cellular phones and wired phones, and includes a base station auxiliary system and a cellular accessory control block. The base station secondary system includes radio resource management equipment, so that multiple cell phones can communicate with the base station secondary system in a cellular manner. The cellular accessory control block is connected between the base station auxiliary system and the switching network in the public wired telephone network, which includes a registry, a mobile switching center, and a small central room.

The route data of multiple cell phones contained in the registration is convenient for forwarding calls to that location. The route data includes data indicating whether a particular cell phone of the multiple cell phones can receive a call. The mobile switching center is connected to the registry and facilitates the exchange of calls between multiple cell phones.

The small central room is connected to the registration office and the mobile switching center, and it is determined that the signal data from the first cell phone, one of the cell phones, is related to an internal call or an external call. An internal call is a call between a first cell phone and a second cell phone among multiple cell phones. An external call is a call between the first cell phone and one of the wired telephones in the public wired telephone network. If the signal data is related to an internal call, the signal data is sent to the mobile switching center to transfer the internal call. On the other hand, if the signal data relates to an external call, the signal data is sent to the public wired telephone network to transfer the external call.

In one embodiment, the multiple cell phones are standard GSM phones, thereby simplifying the future upgrade of the cellular accessory system of the present invention to a full cell communication system. In another embodiment, the mobile management device restricts multiple mobile phones to each of its own base station home area, thereby simplifying the implementation of the cellular communication between multiple cellular phones in the cellular accessory system of the present invention.

These and other features of the present invention will be described in more detail in the following description of the present invention, the accompanying drawings, and the scope of the attached patent application.

After reading the following detailed description and referring to the accompanying drawings, other advantages of the present invention can be apparent. In the accompanying drawings: Figure 1 shows a representative cellular accessory system (CAS) in one embodiment; Figure 2 shows a diagram 1 The main functional blocks of the cellular accessory control block (CACB); Figure 3 shows a representative cellular accessory system (CAS) customer database; Figure 4 shows a cellular accessory system (CAS), including its cellular accessory The control block (CACB) and the call path completed when the call is forwarded; Figure 5 shows the steps when the MS unit wants to update its position with the CAS HLR registry of the CAS network in the format of a flowchart; Figure 6 shows the process The format of the picture shows the relevant CAS The steps of HLR registration when processing the incoming and outgoing applications received; Figure 7 shows in the format of a flowchart the steps taken by the sub-systems of the CAS network when an MS unit makes a call from within the CAS network; Figure 8 In the format of a flowchart, the steps taken by the sub-systems of the CAS network when a call is not connected; Figure 9 shows the format of a flowchart when an MS unit of the CAS network is used as a receiving unit to receive from Steps when another MS unit in a public network or a CAS network; Figure 10A shows the steps taken when an MS unit in the CAS network makes a call from the background of CACB in the format of a flowchart; 10B continues with FIG. 10A; and FIG. 11 is a flowchart showing the steps taken by the CACB of the present invention when a call is terminated on an MS unit of the CAS network from the background of the CACB.

Figure 1 shows a representative cellular accessory system (CAS) in one embodiment. Figure 1 shows a CAS 200, which includes a base transceiver station (BTS) 202 and 204, a base station controller (BSC) 206, and a cell attachment control block (CACB). In terms of hardware, BSC206 and BTS202 and 204 are roughly the same as the respective BSC and BTS discussed in the aforementioned pending application S/N 08/435,709. The BSC and BTS of CAS form a base station sub-system (BSS). In one embodiment, the BSC and BTS of FIG. 1 implement the aforementioned GMS standard. Moreover, GSM is discussed throughout this specification for easy illustration. However, the CAS of the present invention is not limited to any specific standard, and those skilled in the art should be able to modify the CAS described here to implement any one of several popular standards.

It should be remembered that the CAS in Figure 1 is only representative. Each BSC206 can have more or fewer BTSs. And each auxiliary control block (CACB) can have any number of BSCs. In one embodiment, each of the base station sub-systems (BSS) has a radio resource management device for handling a limited number of mobile stations or cell phones. The BTS 202 shows that it is in contact with the MS unit 220 on the radio, and therefore provides radio-related resources to handle the cellular communication to and from the MS unit 220. Similarly, BTS204 provides radio-related resources to handle cellular communications between MS units 222 and 224.

Mobile stations managed by CAS200, such as MS units 220, 222, and 224, should represent standard cell phones. In one embodiment, these represent GMS cell phones that are available from stock. The use of standard mobile phones can advantageously enable service providers (ie those who implement and/or manage CAS200) to update CAS200 as a standard full-featured cellular system at a later date without the need for existing MS units 220, 222, and 224 The owner of the phone purchases a new phone to replace his mobile phone. Similarly, the standard cellular hardware of BSC206 and BTS202 and 204 devices is easy to use and can be easily upgraded to a standard full-featured cellular system at a later date. If you use the same pending patent applications S/N 08/435,709 and S/N 08/435,838, and the above-mentioned BSC and BTS of the pending patent WAVEP 005, in one embodiment, upgrade It is only for loading new software into the BSC and BTS chassis.

Using standard cellular technology to implement the cellular accessory system of the present invention advantageously enables each CAS of the CAS network to process thousands of MS units. This is especially true in the GMS embodiment, because the GSM specification is very suitable for supporting a large number of MS units. Moreover, the MS units (a standard GSM mobile phone in one embodiment) can each have a distance as large as 20 kilometers and as small as hundreds of meters. This higher capability represents the distance and capability limit of wireless telephone systems that are significantly better than the prior art. When the distance is at the lower end, the innovative CAS can advantageously limit the roaming area of a particular mobile phone to a very small area. Moreover, if the distance is at its lower end, as in the case of an embodiment, the transmission power can be reduced, thereby saving costs compared to conventional full-featured cell systems that provide far greater distances.

Moreover, the components of CAS200, such as its BSC and BTS, can be strategically placed in a geographic area to form the area covered by the CAS network. This is especially true when using low-power, microcell components, such as those published in the aforementioned patent applications S/N 08/435,709 and S/N 08/435,838. When a change needs to be made, for example, when a manufacturer moves its location, only a few units need to be physically moved. On the contrary, the wired telephone system used to implement the advanced technology of the wireless telephone requires the main actual change to the wired network in this change.

CACB 208 communicates with a public network 210. In one embodiment, this represents the public switched telephone network (PSTN) via link 211. The link 211 should preferably pass through an SS7 signal link, but other types of signal links can also be used, such as R2 or ISDN signals. The link 211 is used to connect the CACB 208 to the PSTN exchange resource. In one embodiment, the PSTN switching resource represents the switching network (209) of the wired telephone network. In another embodiment, the PSTN exchange resource can be an existing central room (CO207). From the background of the public network, CACB208 is an integral part of the public network and is used as a gateway to enter the MS of CAS. In fact, from the background of public networks, CAS network behavior is like an extension of a wired central office (CO). This extension enables service providers to provide telephone services to areas where CO cannot be implemented due to economic and geographic factors, and to provide cell phone in and out. The communication between CAS's BTS and its MS units is achieved in cell mode, most of which are transparently connected to the rest of the public network.

FIG. 1 also shows an operation and maintenance center (OMC) 212, which is attached to the public network 210. The OMC212 in the public network 210 communicates with the CACB via a link 213, which uses an X.25 protocol in one embodiment. In some embodiments, other protocols may be used, such as TCP/IP, ATM, etc. In a typical PSTN network, OMC212 generally includes a set of application devices to manage customer information, such as customer information, bills, network maintenance, and so on. In an ordinary PSTN network configuration, that is, if it is not connected to the CAS system of the present invention in FIG. 1, the OMC212 only manages customer data related to wired telephone customers. The customer data of the cellular customer using the advanced technology of the cellular network is generally processed by a different customer management system, that is, the one specially assigned to the cellular system. For this reason, bills from PSTN providers and cellular providers are generally handled separately in the prior art.

In the CAS system of the present invention in FIG. 1, the OMC212 of the public network 210 provides customer data management for CAS customers. For example, when a possible CAS customer wants to activate the service of MS224, customer information such as the billing address of the MS unit 224, billing information, selected service type, telephone number and other customer information is kept track by OMC212. As shown later, the customer information of a group is also placed in the home location registration office of CACB208 (not shown in Figure 1) to facilitate call forwarding. In one embodiment, the CACB 208 keeps track of the phone used by its MS, and supplies the information to the public network 210, which manages the charges for using the CAS network 200 through the OMC 212. Since customer information and billing services are managed by the public network, CAS administrators advantageously offload these tasks, which in turn advantageously reduces the operating costs related to the provision of cellular services to CAS customers.

In FIG. 1, the connection from the CACB 208 to the public network 210 is generally a wired connection. However, in some configurations, this connection may be wireless, for example by a microwave link. This is particularly advantageous when the CAS is deployed in a widely dispersed and remote environment. In this case, the use of microwave links can be greatly saved, because this saves the cost of laying wires over long distances. The connection between CACB208 and BSC206 is generally wired, as is the connection between BSC and BTS. The cellular part of the CAS system exists between the BTS, such as the BTS202 or BTS204 and the MS unit, because the infrastructure used to process the MS unit wirelessly exists in the BTS202 and 204, and some are in the BSC. However, for the public wired telephone network, the cell communication between the MS unit and the BSS is basically transparent.

In the case of a call between the MS unit 222 and the MS unit 224, that is, the call made locally in the CAS system 200, the data-carrying channel connection cross-connection can be performed at the CACB208 level, and more specifically, a mobile switching station (MSC ), which is set in CACB208. For more detailed information about an embodiment of the MSC, please refer to the aforementioned patent application S/N 08/435,838. However, as published in the aforementioned patent S/N 08/435,838, which is pending approval, this connection can be implemented at the lower level of the network hierarchy, such as BSC or BTS.

FIG. 1 also shows a wired telephone 214, which is connected to the public wired telephone network 210 in an ordinary manner. The wired telephone 214 is not regarded as part of the CAS network 200. When the wired telephone 214 wants to establish a call with one of the MS units in the CAS network 200, such as the MS unit 222, the public network forwards the call between the wired telephone 214 and the MS unit 222, which is forwarded to the public network The two known endpoints are executed between the CO of the wired telephone 214 and the CACB 208. CACB208 consults its own database, which is called the Home Location Registry (CAS HLR), and finds out the information so that it can forward the call to the MS unit 222.

In the opposite direction, when the MS unit 222 wants to call the wired telephone 214, the MS unit 222 provides the telephone number of the wired telephone 214 to the CACB 208. CACB uses, for example, a dial tree to determine that the phone number sent by the MS unit does not belong to one of the MS units in CAS200. CACB208 applies for the public network to forward the call between itself and the CO (not shown) to which the wired telephone 214 belongs, thereby completing the call route.

If there is another CAS system connected to the public network 210, one of the MS units can dial and connect to one of the MS units in the CAS200 in FIG. 1, in a way that is completely transparent to the public network 210 and the original CAS. Now the call from the MS unit to the MS unit is transparent, because the public network only forwards the call between two known endpoints, regardless of whether each is CACB, CO, etc.

Figure 2 shows the main functional blocks of CACB208 in Figure 1. In CACB208, there is an internal interface (IPN) 250 to the public network. This interface is internal, because, as mentioned above, CAS is regarded as an integral part of the public network. IPN250 facilitates communication with public networks, and this communication uses SS7 signals in one embodiment. Figure 2 also shows a location registry (CAS HLR) 254, which is used to store customer information about CAS customers in CACB208.

In one embodiment, the CAS network does not provide for roaming outside the CAS domain. In order to further reduce the implementation cost, in another embodiment (basic CAS configuration), there is no wandering among the BTSs of the CAS network. Therefore, each customer in the CAS network is considered to have a fixed home location. This is limited to one of the BTS domains in the basic CAS configuration, or in the enhanced configuration, it can be expanded to include multiple BTSs, one BSC The field, a group of BSC fields, or even the entire CAS field. Moreover, in one embodiment, a full international tour can be provided, for example, by implementing a full-featured MSC in CACB. Note that even in its most limited form, there is still a considerable degree of mobility in the BTS domain.

Information about the location of the customer's home is registered in the central public customer management system of the public network, and is provided to CAS HLR254 via OMC212 and an OMC interface block 252. When one of the customers in the public network customer management system moves out or the customer service is updated, CAS HLR254 is also updated. The OMC interface block 252 facilitates the communication between the CACB208, especially one of the CAS HLR254 and the OMC212. In one embodiment, the OMC interface 252 implements an X.25 protocol for communication between CACB208 and OMC212.

Note that in one embodiment, the CAS HLR254 does not need to know all the customer information in the public customer management system of the public network, so that the CACB208 can perform its forwarding function. In one embodiment, it is contemplated that CAS HLR254 only needs to transfer data. In another embodiment, the only information required is to confirm whether a specific MS unit is allowed to use the resources of the CAS system to make and receive calls. Therefore, in the public customer management system of the public network, only a small group of customer information needs to be placed in the CAS HLR254. However, in yet another embodiment, the CAS HLR 254 may have all customer information about the CAS customer.

Figure 2 also shows a TRAU block 256. Note that the TRAU block 256 is placed in the vicinity of the IPN 250 and is away from the position of its prior art, which is on the mobile station side of the Private Mobile Switching Center (MSC) 258. The private MSC258 stays at approximately the same location as the private MSC published in the aforementioned patent application S/N 08/435,709, which is also pending approval. In one embodiment, there is only one private MSC258 per CAS. TRAU is not automatically provided for calls within the CAS network, that is, calls between the two MS units of the CAS network. This has advantages. This is the same as the pending patent application S/N 08/435, 709 and S /N 08/435,838 has a detailed discussion.

You can also choose to set up a small CO260, whose main job is to control the transfer between calls sent or terminated by one of the MS units of the CAS system. Moreover, for information about small COs, please refer to the above-mentioned patent applications pending approval, especially Figures 3B, 4B, 5B, 6B and the component PBX256 in the descriptions to which they belong. In one embodiment, no small CO260 is provided. In this case, the CAS network only provides a call connection to the public network via the IPN250, where call forwarding actually occurs. The private MSC258 still handles location update applications and other optional ancillary services. If no small CO is set up, this CAS configuration represents an inexpensive way to provide cellular services and is attached to the existing wired public network.

If the CACB is connected to a CO in the PSTN, this CO can be used to transfer calls to and from the MS unit of the CAS network. This CO should not even have a cell or GSM CO. In fact, it is envisaged that wired CO, such as AMPS, POTS, TABS, analog CO, etc. can be used. When using this non-GSM CO, the CO and CAS can communicate through an appropriate interface, which in one embodiment can be a DSO interface. This is different from a cellular system that requires a cellular CO, such as the advanced technology of a GSM CO.

The ability to use a small CO to implement intra-CACB transfers makes the implementation of the CAS system more flexible and leads to significant savings. This feature is particularly beneficial to markets such as small island countries, where the public network center can be hundreds of miles away from the village where the CAS network is implemented. The use of a small CO enables local calls, that is, calls between MS units in the CAS network, to be transferred locally, thereby eliminating the bottleneck that occurs when all calls need to be dragged back to the public network CO for transfer over a long distance. In order to further reduce the cost of implementing the CAS system, the connection between the CAS CACB and the switching resources of the public wired network can be achieved using wireless links, such as microwave links.

However, regardless of whether the transfer is performed at the CAS or back to the public network CO, in one embodiment, the customer management and billing work should be centralized, so as to relieve the CAS administrator from maintaining the customer and/or billing database The cost. This feature advantageously enables service providers to enter the mobile communications market at a low price and introduce users to low-cost cellular services, which can be easily and cheaply updated to full-featured cellular services in the future.

In Figure 2, in the discussion, it is assumed that there is a small CO. The small CO keeps track of the dialing tree to perform call transfer and communicate with CASHLR to confirm and verify whether a certain MS unit can perform some auxiliary services, such as call transfer, conference call, etc.

Figure 3 shows a representative simple CAS customer database, which is placed in CAS HLR254. It should be remembered that the CAS customer database shown in Figure 3 is representative and subject to change. In the CAS customer database, the route data of the CAS unit is stored. Column 270 contains the IMSI of the MS unit of the CAS network. Column 272 contains the telephone number of the IMSI in column 270. Column 274 contains the MS unit home location of the IMSI shown in column 270. In an embodiment of the basic CAS configuration, there is no wandering between BTSs, so the home location can be retracted to a specific BTS. However, it is possible to allow a specific MS unit to be placed in multiple BTS areas. When multiple BTS areas are listed in the general 274 of a particular MS unit, the MS unit can travel between these multiple BTS areas and still be regarded as being in the distance. The column 276 indicates the status of the MS unit of the IMSI shown in the column 270. The status of the MS unit may include a flag to indicate whether the MS unit is in the home location shown in column 274, whether the MS unit is connected, and when to register on time. In column 278, it is optional to set an auxiliary service table subscribed by the MS unit related to the IMSI table in column 270. Note that ancillary services are not provided for all CAS configurations, and in some cases, the omission of these services can be beneficial to reduce the entry cost of the service provider, who hopes to provide it as a subsidiary of the public wired telephone network Service.

Figure 4 shows the CAS network 300, which includes CACB208, BSC302 and 304, and BTS306, 308, and 310. In the example of FIG. 4, BTS306 is controlled by BSC302, and BTS308 and 310 are controlled by BSC304. Of course, more or fewer BSCs and BTSs can be set up, depending on the CAS network capacity and field requirements. MS unit 370 is controlled by BTS306, MS unit 372 is controlled by BTS308, and MS unit 374 is controlled by BTS310.

FIG. 4 also shows a public wired network 320 connected to the CACB209 of the CAS network 300. A wired telephone 330 is connected to the public wired network 320 in an ordinary manner.

To illustrate the operation of the CAS network 300, FIG. 4 also shows multiple call routes 340 and 342. When an MS unit wants to call a wired telephone 330 outside the CAS network 300, it is an external call, and the MS unit applies to connect it to the private MSC258 connection. In its application. The MS unit 372 provides an initial address message (IAM) to the private MSC258. The signal data received by the private MSC258 is then sent to the small CO260. The small CO260 knows through the dialing tree that the dialed phone number does not belong to one of the MS units in the CAS network 300. Therefore, the small CO260 transmits the received IAM to the internal interface of the public network (IPN) 250. Through its signal link, the IPN 250 sends the IAM to the public wired network 320, where the call is finally forwarded to the wired telephone 330 in the usual way.

In the reverse direction, when the wired telephone 330 wants to call one of the MS units in the CAS network 300, it sends the dial to the public wired network 320. According to the number dialed by the wired telephone 330, the public wired network 320 finds a small CO260 in, for example, the first six digits of the dialed 10-digit telephone number. In this example, the small CO260 is attached to the CACB208. The small CO260 in CACB208 receives IAM and consults with CAC HLR254 to determine the MS unit belonging to the dialed phone number (which is included in IAM). The small CO260 also determines in the database of CAS HLR254 whether the status of the MS unit to which the dialed phone number belongs indicates that it can accept incoming calls or is busy with another call.

If the destination MS unit is in the appropriate home area (this is stated in CAS HLR254), but the line is busy, the small CO260 should reply a busy line indication to the CO calling on the public wired network. On the other hand, if the status of the destination MS unit indicates that it is not connected, or if the MS does not respond to its paging, a ringing instruction is sent back, such as a call-up message to the calling CO in the public network. The calling CO can then appropriately notify the calling phone about the status of the destination MS unit. The status of the destination MS unit can indicate that it is not connected, or when, for example, it is from its authorized home area (this can be as small as a single BTS in the basic CAS configuration, or as large as in the enhanced configuration) The entire CAS network) did not report in time when traveling. However, if the destination MS unit is connected and the line is not busy, when the user answers the call, the call is terminated (connected) to the destination MS unit. The steps for the call termination at an MS unit of the CAS network are later shown in Figures 9 and 11.

For calls strictly within CAS network 300, such as internal calls between MS units 370 and 374, the procedures are slightly different. It is temporarily assumed that the MS unit 370 is the calling unit, and the MS unit 374 is the destination MS unit. The MS unit 370 first applies for its connection to one of the private MSC258. The MS unit 370 then provides an initial address message (IAM) to the private MSC258. The signal data from the MS unit 370 received by the private MSC258 is then sent to the small CO260. The small CO 260 goes through the dial tree and knows that the destination phone number belongs to one of the MS units in the CAS network 300 (ie, the MS unit 374).

The small CO260 then inquires the CAS HLR254 to determine whether the destination MS unit, that is, the MS unit 374 can receive a call (that is, connected, reported in time, and not busy). If the MS unit 374 can receive the phone call, the small CO260 uses the private MSC258 to implement the connection between the MS unit 370 and MS374. The call route between MS unit 370 and MS374 is shown as route 342 in FIG. 4. However, note that if there is a smart switch (as published in the pending patent application S/N 08/435,838), the connection between MS unit 370 and MS unit 374 can be organized in the network class At a lower level, for example, it is executed between BSC302 and BSC304. Moreover, unless the MS units 370 and 374 communicate on different frequencies, there is no need to change the frequency via TRAU. In the present invention, TRAU is not automatically required because TRAU256 has moved from the BTS side of MSC258 to its public network side. This is different from the case of the advanced technology cell system. In the advanced system, the call between MS units is automatically TRAU in the call path between the MS unit and an advanced technology MSC.

Figure 5 shows in a simple flow format the steps involved when an MS unit wants to update its position in the CAS HLR registry of the CAS network. Figure 5 starts at block 700. At block 702, the updated MS unit sends a location update request via a BTS secondary system to a BSC secondary system. Generally speaking, a location update application includes updating the IMSI of the MS unit. In one embodiment, the location update application may include a version of IMSI called TMSI (for security reasons, it is used to replace a temporary MSI of IMSI). The identity of the MS unit is identified by IMSI or TMSI to identify the MS unit whose location is to be updated.

In block 704, the BSC secondary system transmits one of the MS units (where a location update request is issued in block 702) an SCCP connection application to the MSC secondary system. In one embodiment, the SCCP (Signal Connection Control Part) connection application should provide a message that complies with Signal System 7 (SS7) or "an interface between private MSC functions on BSC and CACB". Generally speaking, the SCCP connection application includes the location update application issued in block 702 by the update MS unit. Blocks 702 and 704 establish the movement management (MM) phase.

At block 706, the MSC secondary system sends an SCCP connection confirmation to the BSC secondary system to confirm the establishment of an MM connection. From the background of the MSC, the MSC sub-system sends a program entry/exit application to the CAS HLR registry in block 708. This application includes the information contained in the location update application received in block 702 to pass the CAS HLR registry. To determine whether the MS unit applying for location update has been "approved", that is, whether it can use CAS network resources, and whether the updated NS unit has wandered away from its last location and needs to be updated in the CAS HLR registry. In the basic CAS configuration, an NS unit is only allowed to use CAS network resources in its designated BTS location. However, in an enhanced embodiment, it can walk between BTSs, and a specific MS is deemed to be "approved" to use any BTS in the CAS network, as long as it obtains a designated BTS.

In block 710, the CAS HLR register processes the received in and out request issued in block 708. Block 710 is described in more detail in FIG. 7 later. At block 712, the MSC-location update confirmation sent by the CAS HLR registry indicates whether the updating MS unit is allowed to use CAS network resources. If the updated MS unit is allowed to use CAS network resources. The location update confirmation should also contain information indicating whether the location update has been performed in the CAS HLR registry. In decision block 714, it is determined whether the updated MS unit is approved (determined from the location update confirmation received in block 712). If the MS unit determined to update in block 714 is allowed to use CAS network resources, the method proceeds to block 716, where the MSC sends a location update confirmation message to the BSC.

In block 720, the MSC sub-system sends an SCCP vacating message to the BSC sub-system to vacate the stages established in blocks 702 and 704. Then to block 720, the BSC that received the SCCP vacate message vacates in block 720 to the entire channel of the updated MS unit. In block 724, the BSC that received the SCCP vacant message in block 720 replies with a vacant completion message to the MSC, indicating that the MM phase has been completely vacated. At block 726, the steps including updating the location from an MS unit via the MSC are completed.

On the other hand, if it is determined in block 714 that the updated MS unit is not approved to use the resources of the CAS network, the method immediately proceeds to blocks 728-734 to end the SCCP or MM phase. For example, if the CAS system is made into a basic configuration (that is, it does not walk between BTSs), and the MS unit is in a BTS area different from the designated one. In block 728, the MSC sub-system sends a location update rejection message to the BSC sub-system, indicating that it cannot process the location update request from the updated MS unit. At block 730, the MSC sub-system sends an SCCP victory message to the BSC sub-system to start the vacant MM phase. Thereafter, the BSC vacated all channels of the updated MS unit. In block 734, the BSC sub-system sends a vacant completion message to the MSC sub-system, indicating that the stage established in blocks 702 and 704 is vacated. Thereafter, the method proceeds to block 726, where the steps of FIG. 5 terminate.

FIG. 6 shows in the format of a flowchart the steps involved when the CAS HLR registration processes the inbound and outbound application received in block 710 in FIG. 5. Figure 6 starts at block 750. From block 750, the method proceeds to block 752, where the program access request message sent by the MSC secondary system in block 708 of FIG. 5 is received. According to one aspect of the fundamental invention, in block 754, in accordance with all the registrations in the CAS HLR registry, the IMSI to which the updated MS unit belongs is checked to determine whether the updated MS unit is allowed to use the resources of the CAS network. As mentioned above, in the basic configuration, an MS unit is only allowed to use CAS network resources if it is in the designated BTS area. However, in an enhanced embodiment, a specific MS unit that can walk between BTSs is considered "approved" to use the resources of the CAS network, as long as it is designated in a BTS. This confirmation procedure can be advantageously used to prevent non-local MS units from using the resources of the CAS network.

Or, the block 754 may additionally include some security functions, such as password checking, challenge, and verification. If it is determined in block 756 that the updated MS unit is allowed to use the resources of the CAS network, the network proceeds to block 758 to update the CAS HLR registry if necessary. At block 758, the identity of the update unit is checked to see if its location needs to be updated in the CAS HLR registry that receives the program entry and exit application.

After the CAS HLR registry is updated in block 758, or the updated MS unit is not allowed to use the resources of the CAS network (in some configurations, and as determined in block 756), the method proceeds to block 760, where, The CAS HLR registry sends a location update confirmation to the MSC secondary system. As previously described in block 712 of FIG. 5, the location update confirmation sent in block 760 indicates whether the updated MS unit is allowed to use the resources of the CAS network, and if so, whether the update of the CAS HLR registry has been performed . At block 762, the step of FIG. 6 ends.

Figure 7 shows in the format of a flowchart the steps taken by the sub-systems of the CAS network when the MS unit makes a call from within the CAS network. The steps of FIG. 7 start at block 716 after the departure of FIG. 5 (MS location update). This is still because the MS unit still needs to establish the MM stage (blocks 702 to 706), and send a program entry and exit application to the CAS HLR registry for processing (blocks 708-712), so that the MS unit cannot use the resources of the CAS network, such as It is not allowed to use (blocks 714, 728, 730, and 734), and is allowed to make calls, if the sending MS unit is allowed to use the resources of the CAS network (blocks 714 and 716).

Since the steps in FIG. 7 involve an MS unit making a call instead of just applying for a location update (as in the case of FIG. 5), the message sent on the SCCP application in block 704 of FIG. 5 indicates to the MSC that a call is to be made. Not a location update. Those skilled in the art know that the calling MS unit can inform CACB and use any notification method that is convenient for implementation. Moreover, since the steps in FIG. 7 are not intended to be a location update, when a call is to be made, there is generally no need to update the location of the MS unit of the call related to the CAS HLR registration. In the scope of this implementation, when an MS unit establishes a call, block 758 is not executed in one embodiment. In a specific implementation described here, if it is determined that the calling MS unit is allowed to use the resources of the CAS network, the method proceeds directly from block 756 to block 760.

The method proceeds from block 800 to block 802, where the calling MS unit sends an establishment message (via BTS and BSC) to the MSC, which usually contains the destination telephone number and indicates that the call to be established is voice, data, fax, etc.Information. Information. The method then proceeds to block 810, where the CAS HLR register sends a map to complete the call to the MSC, which is a mobile application partial message. The map completion call sent in block 810 is received by the MSC from the CASHLR registration in block 812. At block 814, the MSC sends an initial location message (IAM) to the small CO, in a GSM implementation. This message contains the destination phone number, indicating that it wants to connect to a specific destination phone that contains smart transfer. As envisaged in one embodiment, the MSC in the CACB determines the best cross-connection point, for example, through BTS , BSC, MSC in CASB, or transfer the call to a public network.

In block 816, the MSC responds to the confirmation of the destination phone and sends a call progress message to the MS unit indicating that the call is in progress. At block 818, the small CO sends an address completion message (ACM) to the MSC, indicating that the entire destination number (dial) has been received and the call has been connected to the destination. The receipt of the ACM message by the MSC also indicates that the called party has been successfully awakened, that is, the destination phone is ringing. In block 820, the MSC responds to the ACM message received in block 818, and sends a wake-up message to the MS unit to inform the MS unit that the called party has been awakened and connects the ringing of the calling MS unit.

At block 822, the MSC sends a designated request message to the BSC to designate the channel for transmission, such as the actual voice/data channel on the A interface, and instruct the BSC to use the designated channel to establish a call. The designated channel means the channel on which the calling MS unit can send and receive the data it carries. It should be noted that the steps in block 822 of FIG. 7 may occur asynchronously with other steps. In one embodiment, after the MSC sends the IAM message to the small CO (block 814), the MSC immediately sends a designation application to the BSC. After the MS unit receives the call-up message, the ringing circuit at the calling MS unit continues to ring until the called party accepts the call or the caller hangs up. In this case, the MM phase is vacated again, as described above.

In block 824, it is assumed that the called party accepts the call, and the CACB sends an answer message (ANM) to the MSC, indicating that the called party has answered the call by acceptance. In block 826, the MSC responds to the ANM message received in block 824 and sends a connection awareness message to the BSC to instruct the BSC to connect the receiving (incoming) route and the calling (outgoing) route. At block 823, the calling and called parties are fully connected, and a call can now be made.

Figure 8 shows in the format of a flowchart the steps taken by each sub-system of the CAS network when a call is not connected. A call is not connected because the calling party hangs up the phone or the called party does not connect to the call. It should be noted in one embodiment. When one of the MS units in the call route moves away from the designated home area, the call may not be connected. In the basic CAS configuration, the home area is limited to the BTS area assigned to the MS unit as its home location. In the enhanced CAS configuration, the home area can include multiple BTSs, a BSC area, a group of BSC areas, a group of BSC areas, or even the entire CAS network in an enhanced configuration. Moreover, in one embodiment, a full international tour can be provided, for example, by implementing a full-featured MSC in CACB208.

When the calling party does not connect in block 902 or the called party does not connect in block 904, the call is interrupted. In block 902, the MSC receives a disconnected message from one of the calling MS units, indicating that the calling party hangs up the phone or travels out of distance. On the other hand, in block 904, the MSC receives a disconnected message from one of the called parties via the small CO, indicating that the called party hangs up the phone or travels out of distance. In block 906, the MSC responds to receiving a disconnect message in block 902 or 904, and sends a release message to the small CO. To be forwarded to the called party. The called party may be on the CAS network or on the public network. In this case, the release message is forwarded to the public network (IPN) via the internal interface. In block 908, the called party sends a release message to the MSC via the small CO, indicating the release approval.

In blocks 910 and 912, it is confirmed that the release is complete. In block 910, the small CO receives a release completion message from one of the MSCs, reflecting the release message sent in block 908. Similarly, in block 912, the MSC receives the release completion message from the small CO, reflecting the release message sent in block 906. In block 914, all resources related to the disconnected call, such as TRAU, echo cancellation, etc., are released.

In blocks 916 and 918, the MSC vacates to the MM stage of the calling MS unit. In block 916, the MSC sends an SCCP empty message to the BSC to initiate the emptying of the MM phase. After that, the BSC vacated the MM stage until the calling MS unit. In block 918, the BSC sends back a SCCP vacating complete message to the MSC, indicating that the MM phase is vacated. In block 920, the step of FIG. 8 ends.

Fig. 9 shows in the format of a flowchart the steps when an MS unit of the CAS network is used as a receiving unit to receive a call from the public network or from another MS unit in the CAS network. Figure 9 starts at block 950. In block 952, the MSC receives an initial location message (IAM) of the call from the network via the small CO, and the call is terminated at an MS unit in the CAS network. If the calling unit is another MS unit in the CAS network, the IAM message received in block 952 displays roughly the same IAM message sent by the calling MS unit in block 84 in FIG. 7.

In block 954, the MSC sends a map sending information service application to the CAS HLR registry for the incoming call to find out the MS unit indicated by the phone number in the IAM message. In one embodiment, the block 954 includes determining the current location of the destination MS unit in the CAS network (that is, if it has traveled away from its home area if it is an enhanced configuration), and the information received in the IAM message The MMSI number corresponding to the phone number, the specific auxiliary services ordered by the destination MS unit, etc.

In block 956, after finding the current area of the destination MS unit in the block 954 of the CAS HLR registration location, it sends a map paging message to the MSC to apply for the MSC to call the destination MS unit by the IMSI or some version thereof. In block 956, the map paging message is sent to the MSC, where the current location of the MS unit is found (determined after consulting the CAS HLR registry). In one embodiment, both the map sending information message and the map paging message represent a mobile application partial message type.

In block 958, the MSC responds to the map paging message received in block 956, and sends a paging request message to the relevant BSC. If the CAS HLR cannot determine the BSC area of the destination MS, there may be more than one BSC received. This is especially true in the case of enhanced CAS configuration. In one embodiment, the CAS HLR registry can know the exact BSC/BTS where the destination MS unit is located (via the update of the MS unit, or because the MS unit is fixed in a specific BTS home area). In response to this paging request, the BSC calls the destination MS unit and waits to hear the paging response from the destination MS unit.

In block 960, if the paging request sent in block 958 reaches the destination MS unit, the destination MS unit then sends a paging response to the BSC (via BTS), and this response is then included in an SCCP connection request, The BSC then transmits this application to the private MSC. In one embodiment, if no paging response is received within a predetermined period, it is assumed that the destination MS unit has traveled out of distance or turned off, and the circuit connection is rejected.

In block 962, the MSC responds to the SCCP connection message received from the BSC in block 960, and responds with an SCCP connection confirmation message to the BSC. Thus, the steps in blocks 960 and 962 are to attach a specific SCCP identification code to the destination MS unit to establish a mobile management (MM) phase.

At block 964, the destination MS unit is then confirmed, which reflects the destination MS unit of a paging response (block 960). MSC sends a program entry and exit application service application to the CAS HLR registry to confirm the corresponding destination MS unit. In block 964, the destination MS unit sought for sending the paging request (block 958) is further checked to determine whether it is approved or appropriate to establish a data communication channel to the destination MS unit. In one embodiment, the processing step of the in/out application from the MSC to the HLR in block 964 may include exchanging additional information therebetween to perform, for example, verification.

In block 966, the MSC sends a setup message to the destination MS unit to establish a call. The establishment message contains call control information, for example, the type of service requested (such as data/voice/fax), and the telephone number of the caller that can be selected, which is used to establish a call. In block 967, the MSC sends an address completion message (ACM) to the small CO to inform the network that enough addresses (such as the dialed phone number) have been received so that the CAS network can find the destination MS unit. In block 968, the MSC receives a prompt message from one of the destination MS units, indicating that the MS unit has confirmed that a call is sent there and can start ringing.

In block 970, the MSC sends an ACM message to the small CO. It should be noted that although the block 970 is shown after the block 968 in FIG. 9, the block 970 does not actually occur at the same time as the block in FIG. 9. For example, block 970 may occur as early as immediately after block 952.

In blocks 972 and 974, the designated MS unit and the MSC carry data channel resources. In block 972, the MSC sends a designated request message to the BSC (for forwarding to the destination MS unit) to designate the data channel resource between the MSC and the BSC. Its role is to transfer the destination MS unit from only the notification channel (the MS unit is on this channel so far in Fig. 9) to a designated data-carrying channel.

In block 974, the MSC receives a designated confirmation message from the BSC (which in turn receives from the destination MS unit), confirms the receipt and successfully processes the designated application message sent by the MSC in block 972. In block 974, the MSC is notified that a carrier channel resource has been successfully designated, which can carry data communications. In one aspect of the present invention, the blocks 972 and 974 include smart connections, which authorize the incoming path and the outgoing path for the call between the two MS units of the CAS network. A lower class. For further information on intelligent cross-connections, please refer to the aforementioned patent application S/N 08/435,838.

At block 978, the MSC receives a connection confirmation message from one of the destination MS units, indicating that the destination MS unit has been found. In response to receiving the connection confirmation message in block 978, the MSC sends a reply message (ANM) to the small CO in block 980 to the calling unit (this can be in the public network, or another in the CAS network). One MS unit) indicates that the destination MS unit has answered by accepting the call. In block 982. The call is now in progress.

From the background of CACB, the procedure of a call made by an MS unit of the CAS network is shown in the step of FIG. 10A. Figure 10A starts at block 1000. At block 1002, the small CO receives the initial address message (IAM) from the private MSC. In one embodiment, the IAM message generally contains the dialed destination phone number. Moreover, in the implementation of GMS, all digits of the destination telephone number usually arrive together at the same time. In another embodiment, when dialing a number, each digit can arrive one at a time.

At block 1004, the destination network is found, whether it is the PSTN or the caller within the CAS network. In one embodiment, the destination network is determined by tracing a digit each time through a dial tree to determine the way out. This procedure is followed by one or two branches, depending on the route of the call.

If the called party is a wired telephone in the PSTN network, the process proceeds to block 1012, which represents the PSTN route. In this case, the CACB designates an appropriate interface in block 1014, for example, an internal interface to the public network (IPN) 250 of FIG. 4 for communication with the PSTN. Since the destination phone is outside the cellular domain, it may be necessary to specify the frequency conversion and echo cancellation resources in block 1020, namely the TRAU and the echo canceller, if necessary.

In block 1024, the process connects the call to the public network through the interface specified in block 1014, that is, the internal interface. As those skilled in the art can understand, the box 1024 may also contain information, such as the exchange of IAM, ACM, ANM (for example, see Figure 7), and the actual connection of the relevant interface from the private MSC to the GMSC. Thereafter, the call is made in block 1026.

If the destination of the call is an MS unit in the field of the CAS network, and the call is made since then, the process proceeds to block 1032, displaying the incoming call path looping back to the same CACB that made the call, and the wave of data carried The actual connection of the Tao is executed by the MSC of CACB, or by another functional block, such as BSC, BTS, and a lower level of hierarchical organization. N 08/435, 838).

To complete an incoming call, an IAM message is sent in block 1036. This IAM message is not sent on an external network interface, but sent to a new program to terminate the incoming call in CACB. Specifically, the IAM sent in block 1036 is received by a program in block 1102 in FIG. 11, which terminates the incoming call.

In one embodiment, the IAM message may include additional information to indicate that the message is a CAS network message, which is different from the standard IAM message sent by the CAS network. In one embodiment, the IAM message may include additional information to indicate different resource requirements, such as no echo cancellation, no TRAU, and communication frequency of MS units. In some cases, some of the above information may also be included in the ACM message. Enhanced messages such as IAM, ACM, and ANM (referred to as IAM', ACM', and ANM' for convenience) can be used to facilitate intelligent cross-connection and TRAU such as call routes. For a more thorough discussion on the use of enhanced information, please refer to the aforementioned patent application S/N 08/435,838, which is also pending approval.

In block 1038, the process of initiating a call and sending an IAM message in block 1036 receives the ACM (Address Completion Message) from the process of terminating the call of FIG. 11. Specifically, this ACM comes from block 1118 in FIG. 11. In block 1039, the outgoing and incoming carrier channels are connected together. In block 1039, if necessary, any required internal working functions (IWF), such as TRAU, echo cancellation, etc., are also used. Moreover, it can include intelligent cross-connection and TRAU processing, as discussed in the above-mentioned patent application S/N 08/435,838 pending approval.

In block 1040, the procedure of initiating a call and receiving an ACM message in block 1039 sends an ACM message to the MSC associated with the outgoing call. From block 1040 in FIG. 10A, the process proceeds to block 1042 in FIG. 10B.

Figure 10B continues Figure 10A. Referring now to FIG. 10B, the program receives an ANM message from one of the outgoing programs of FIG. 11 in block 1048. Specifically, one of the ANM messages from block 1122 in FIG. 11 is received. The ANM message indicates that the destination MS unit has answered the call. In block 1050, the small CO sends an answer message (ANM) to the MSC to which the MS unit belongs, which initiates a call and sends an IAM message in block 1002 of FIG. 10A.

From the background of CACB, the procedure for terminating an incoming call at an MS unit of the CAS network is shown in the steps in Figure 11. Figure 11 starts at block 1100. From block 1100, the process proceeds to block 1102, where it receives an initial address message (IAM) from the public network or from one of the MS units in the CAS network. If an MS unit in the CAS makes the call, the IAM message received in block 1102 is roughly the same as that sent by block 1036 in FIG. 10A. In this case, the call is regarded as an internal call, that is, a call between two MSs on the same CAS network. At block 1104, the small CO consults the CAS HLR registry to find the destination MS unit in the CAS network. For example, in situations where the destination MS unit may have traveled away from its home area, that is, traveled out of distance, or may be turned off, this block 1104 is required. If the destination MS unit is not connected, the notification phase is terminated after a predetermined time.

In block 1106, it is determined whether the destination MS unit (whose phone number is included in the IAM message received in block 1102) is allowed to use the resources of the CAS network to make the call. If the MS is deemed inconvenient, for example, it is busy or cannot be found, the procedure proceeds to block 1108, where a continuous busy signal can be generated.

On the other hand, if it is determined in blocks 1104 and 1106 that the destination MS unit is now in its home area, the process proceeds to block 1110, where CACB specifies internal working functions, such as echo cancellation, as necessary. In one embodiment, when the call is placed on the public network, CACB also specifies TRAU.

In block 1112, the small CO transmits the IAM message received in block 1102 to the MSC. At block 1114, the small CO receives an address completion message (ACM) from the MSC, indicating that the destination call has received the full address. At block 1116, the data-carrying channel is connected from the MSC through the appropriate interface. The connection between the proper interface and MSC equipment facilitates full-duplex communication. In block 1118, the small CO transmits the ACM message received in block 1114 to the public network, or in the case of an internal call, and returns to the sending procedure of FIG. 10A, which is received in block 1038.

If the call is accepted at the destination MS unit, the MSC sends an answer message (ANM) to the small CO in block 1120. In block 1122, the small CO transmits the ANM message received in block 1120 to the public network, or in the case of an internal call, and returns to the generation procedure of FIG. 10B, which is received in block 1048, to the MSC, to Indicates that the called party has accepted the call. Thereafter, the process proceeds to block 1124, as shown in FIG. 11, where a call is made.

Although the present invention has been explained in detail above for clarity, it is obvious that some changes and modifications can be made within the scope of the attached patent application. For example, although the GSM system is mainly used to illustrate the present invention, it should be understood that the present invention is not so limited. It is specifically envisaged that the cellular accessory system described herein can be implemented in systems using other specific protocols. Moreover, although the present invention uses communication between two MS units to illustrate the concept of the present invention, it should be noted that conference calls can be performed between more than two MS units, such as 3, 4, or more MS units. Modifications of the published devices and methods to achieve this goal are within the capabilities of those skilled in the art. Based on this description, it is obvious that ordinary people skilled in the art know that cocoa can be combined and substituted without departing from the spirit and scope of the present invention. Therefore, the scope of the present invention is not limited by the specific examples mentioned here, but is stated in the appended patent scope.

Appendix A

Glossary and abbreviation

<img file="TW357516B_D0001.tif" /><img file="TW357516B_D0002.tif" /><img file="TW357516B_D0003.tif" />

Appendix B

This description is written for those skilled in the art to be easy to understand. For others, the following documents listed for reference can be regarded as additional information.

Mouly, Michel and Pautet of Marie-Bernadette, "GSM System for Mobile Communication", Mouly, Michel and Pautet of Marie-Bernadette, 1992.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); General Aspects of Mobile Radio Interface Signal Layer 3 (GSM 04.07)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Mobile Radio Interface Layer 3 Specification (GSM 04.08)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Mobile Service Switching Center-Base Station System (MSC-BBS) Interface Layer 3 Specification (GSM 08.08)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Specification of Information Transmission Mechanism for Base Station System-Mobile Service Switching Center (BBS-MSC) Interface (GSM 08.06)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Base Station Controller-Base Transceiver Station (BSC-BTS) Interface Layer 3 Specification (GSM 08.58)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Mobile Application Part (MAP) Specification (GSM 09.02)", 1994, Valbonne, France.

European Institute for Communication Standards, "European Digital Cellular Communication System (Phase 2); Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSDN and Public Land Mobile Network (PLMN) Internet Signaling Demand (GSM) 09.07)", 1994, V-albonne, France.

Cellular accessory system for public wiring network