A method of associating call back data with an emergency call to a call center

The present invention relates to remote communication, and more particularly to wireless communication.

Emergency service calls in North America are initiated by dialing "9-1-1". In other parts of the world, some other abbreviated dialable digit string can be used, for example "6-1-1" in Mexico. These abbreviated digits share the intent of making it easier to remember numbers and simplifying calls for help. These calls are routed to the local "PSAP-CC" (Public Service Answering Point Call Center) while the caller is answering the call to make an emergency answer (Public Service Answering Point Call Center). For example, police, fire departments, road construction, and / or ambulances) can be started. However, if the call is somehow disconnected or dropped before the emergency report is complete or the respondent arrives, the PSAP-CC will call the caller. You may need to call back to.

Records of "9-1-1" calls initiated over a wired network may include the "ALI" (Automatic Line Identification) or telephone number of the access line from which the call was initiated. Please note that. However, the wireless subscriber's "DN" (the telephone number listed in the directory number telephone directory) or telephone number cannot be associated with a physical line or wireless unit. Instead, calls to roaming radio subscribers are routed to the radio unit using "MSID" (mobile station identification), unlike "MDN" (mobile DN mobile DN). Therefore, performing an emergency call back to the wireless unit imposes hurdles that cannot be achieved, for example, with terrestrial devices.

In general, this MSID can be characterized as a 10-digit "MIN" (mobile identification number) or a 15-digit "IMSI" (International Mobile Subscriber Identifier). The service provider to which the wireless unit user has subscribed to a service contract can program this IMSI in the wireless unit or in a "SIM" (Subscriber Identity Module) card. Therefore, this MSID may not always be a dialable number.

The DN of the wireless unit is a dialable number. This DN is dialed by the caller and is used to route the call to this wireless subscriber's home system over this network. In this subscriber's home system, "HLR" (home location register) includes the MSID associated with this subscriber's DN. Unlike the DN, this MSID can then be used to route the call over this network to this radio serving system and page to this subscriber. This subscriber's DN can be provided from its SIM card to this serving system via a wireless unit, or by its home system in its subscriber profile called in another data file. It can also be provided to a serving system.

The deployment of systems that use different numbers for DNs and MSIDs has been relatively recent in some wireless systems. Other systems have used this technique since its inception. Historically, wireless unit mobile identification numbers can be "WNP" (wireless number portability radio numbers) based on the "LRN" (Local Routing Number) method and "IR" (international roaming international roaming). Transportability) or "TBNP" (thousands block number) Before implementing pooling (thousands of block number pooling), it was the same as the DN for some systems, especially those that support the TIA / EIA-41 standard. However, along with WNP and TBNP, this MDN has become "portable" or "poolable" from one service provider to another. The MSID may not be portable or poolable, so the recipient's service provider can assign a new MSID for a subscriber with a port-in or pooled MDN.

International roaming has also forced the separation of MSID and MDN. This MIN is a 10-digit number modeled according to the MDN of the North American number plan 10-digit, but telecommunications carriers in other countries using the phone number plans listed in different phone books , Their subscribers' DNs may not be able to be equal to the internationally recognized MIN format. Another standard for the MSID is the IMSI. This standard can be used in TIA / EIA-41 and GSM systems around the world. The IMSI is a 15-digit non-dialable number under ITU-T Recommendation E.212 and therefore cannot serve as an MDN for 10-digits.

Historically, when this MDN was the same as the MIN, this MIN should have been sent to PSAP-CC and used as a callback number. The separation of MIN and MDN, as mentioned above, made it mandatory to send this MDN as another callback number to PSAP-CC, as well as the MSID of its caller. However, there are certain issues associated with implementing this solution. One challenge is that the serving system cannot have the MDN of the caller to present this call to this PSAP-CC, only its MSID. Part of the reason for this is related to the way MSID-MDN separation is implemented according to the standard. Another reason is that the network interface used to send this call to PSAP-CC cannot have the capacity to signal both this DN and MSID, or even the entire DN in some cases. That is.

Earlier TIA / EIA-41 serving systems cannot support WNP, TBNP or IR. This means that earlier serving systems can expect these MINs and MDNs to be the same. Earlier systems would not even know to look for another MDN in this subscriber's service profile (for example, keyed on to MIN and not keyed on to MDN). This limitation may not allow these subscribers to use basic services, but should allow them to make calls for emergency services. As a result, a roaming service user who dials "9-1-1" while on the previous system will receive the user's call to its PSAP-CC with MSID, but with MDN. Will not be sent. Therefore, callbacks are not possible.

Newer serving systems that allow WNP and IR may not be able to send MDNs to this PSAP-CC. This can happen if this calling radio unit is not registered with any service provider (for example, there is a mobile phone used only for emergency calls). These wireless units are "NSI" (non-subscriber) initialized Non-subscriber Initial setting) Sometimes called a telephone. It is also possible for a subscriber to make an emergency call before the HLR answers to this serving system with this subscriber's service profile that includes the DN. If this subscriber has a call transfer service for all incoming calls, even if this PSAP-CC is provided with a working DN for callbacks, or if this subscriber has a limited prepaid service. If you have the service and there is no outstanding balance available to pay for the incoming callback from this PSAP-CC, the callback for this DN will not pass. Furthermore, if this callback number is a number for an international roaming service user on the way, it may be necessary to make an international call to this PSAP-CC. Some PSAP-CCs may not have the ability to call back international numbers. There is also the risk of network congestion or delays in completing international calls, which should be a disadvantage in handling emergencies in a timely manner. Some PSAP-CCs may not even be equipped to make any outgoing calls over separate outgoing management lines.

This callback DN for international roaming service users requires this PSAP-CC to make international calls to reach subscribers within the "ESZ" (Emergency Service Zone) of their area. There should be. This is impractical, untimely, and reliable enough for PSAP-CC, which normally does not make international calls, and for applications that may require immediate callback information for urgent purposes. Not a possible solution. In addition, if this PSAP-CC only supports 10 digits, then the entire international MDN (up to 15 digits including the country code) cannot be presented to this PSAP-CC for callbacks. ..

It is possible that this calling radio unit is not registered with any service provider. As a result, it is possible that there is no DN associated with this radio unit, or there is no permanent MSID encoded within this radio unit. Such a wireless unit is called, for example, an NSI mobile phone. This is because (a) this NSI phone has never been intended to be registered (there is such a phone used only for emergency calls), (b) this phone is new Yes, the service provider has not yet initialized, (c) its subscription has expired, this NSI phone is no longer registered with the service provider, or (d) its SIM card is lost, The reason is that it has never been stolen, or has been carefully or inadvertently inserted, or has been removed.

Some wireless units also support a "R-UIM" (removable User Identity Module) or subscriber identification module ("SIM") that may contain these MSIDs and DNs. is there. Even if this R-UIM or SIM is not on this phone, this phone can still be used to make emergency calls. However, there is no known DN or MSID for this phone or its serving system that should be provided to this PSAP-CC as a callback number.

Every MS contains a unique "MEIN" (mobile equipment identification number) that the manufacturer encodes in the phone. This MEIN is, for example, "ESN" (electronic serial number) used in ANSI systems / TIA systems / EIA-41 systems, or "IMEI" (International Mobile Equipment Identity International) used in GSM systems. It may be a mobile phone machine identification). This MEIN is independent of this MSID and DN. This MEIN is signaled in the air between the radio unit of the radio system and the base station with or shortly after an attempt to initiate a call. For example, the serving system may request this MEIN if no attempt to initiate the call is provided.

A wireless emergency service to send "9-1-1 + the last 7 digits of this MEIN" to this PSAP-CC as its form callback number when the wireless subscriber is assigned that directory number. -Current standards for calls are not available. This can serve to notify the PSAP-CC that the callback number that works with the call is not available, but this "9-1-1 + the last 7 digits of this MEIN (MEIN7)" , The call is not uniquely identified (ie, a large number of emergency calls can be identified by a similar "9-1-1 + MEIN7") and cannot be routed through this network. The reason for this is that this "9-1-1 + the last 7 digits of this MEIN" does not contain the complete MEIN and is therefore not unique.

<p> While the above approaches in this specification provide the PSAP-CC with some measures to implement emergency callbacks for wireless units, some hurdles still exist. For example, the callback number for a radio unit in certain situations may be no different than a dummy number with the user's location information. Therefore, there is a need for a method and system architecture for this PSAP-CC to receive the actual callback number for the radio unit initiating the "9-1-1" call.</p>

<p> The present invention provides a method and system architecture for ensuring that an actual callback number can be reliably provided for a radio unit that initiates a "9-1-1" call. More specifically, the present invention is based on at least one tag identifier, regardless of whether the caller of its origin "9-1-1" was located on a wireless or wired communication infrastructure. This allows call centers such as the regional public service response point call center (PSAP-CC) to initiate callbacks. For the purposes of this disclosure, tag identifiers correspond to names or labels that uniquely associate signals from different sources, for example, associating voices with related data transmitted on different channels or in different messages. can do. Therefore, this tag identifier is one or more reference keys to a database, such as an emergency call register or an emergency service message entity. key) can also be included. Thus, this one (or more) tag identifier can correspond to, for example, an emergency service routing key, a local public safety number, a paging identity and / or a mobile device identification number.</p><p> In one embodiment of the invention, the communication method is provided to at least one radio unit that initiates an emergency call. The method comprises the step of receiving at least one tag identifier in response to the emergency call initiated by at least one radio unit. After receiving this tag identifier, the radio callback number corresponding to at least one tag identifier can be transmitted. Note that the public service answer point emergency call register can receive this one (or more) tag identifier on the D interface and send this radio callback number.</p><p> In another embodiment of the invention, a method for establishing an emergency call initiated by at least one radio unit within a communication system having an emergency call register is provided. This method, for example, in answering this emergency call from at least one radio unit, E_xIt can include the step of transmitting at least one tag identifier from the mobile switching center associated with at least one radio unit on the interface. As in this previously detailed embodiment, this one (or more) tag identifier can include a reference key to this emergency call register. In addition, this one (or more) tag identifier can correspond to at least one of the emergency service routing key, local public safety number, paging identity, and mobile device identification number. This one (or more) transmitted tag identifier can then be entered into its emergency call register (eg, serving system emergency call register or public service response point emergency call register).</p><p> Yet another embodiment of the invention provides a method for establishing an emergency callback initiated by at least one radio unit within a communication system having an emergency call register. This method is B_eThe process of transmitting at least one tag identifier from this emergency call register on the interface can be included. This tag identifier can then be received and entered into a database such as an emergency service message entity. You can then request this emergency callback corresponding to this entered tag identifier.</p><p> Yet another embodiment of the invention provides a method for establishing an emergency callback initiated by at least one radio unit within a communication system having an emergency service message entity. This method is B_eIt can include the step of receiving at least one tag identifier from the emergency call register on the interface and the step of entering this one (or more) tag identifier into this emergency service message entity. You can then request this emergency callback corresponding to this at least one received tag identifier entered.</p><p> Yet another embodiment of the invention provides a method for establishing an emergency call initiated by at least one radio unit associated with a mobile switching center. This method responds to this emergency call from this at least one radio unit by providing at least one tag identifier from the mobile switching center associated with this one (or more) radio units to the emergency service entity. Includes the step of transmitting. This method can include sending callback and location information related to this one (or more) radio units from this emergency service message entity on the D interface, where this callback The information and location information correspond to at least one tag identifier.</p><p> These and other embodiments will become apparent to those skilled in the art from the following detailed description by reading the appended claims and the accompanying drawings herein.</p><p> The present invention will be better understood by reading the following description of non-limiting embodiments with reference to the accompanying drawings.</p>

The drawings of the present application are not shown to scale but merely schematic, and therefore are not intended to depict the particular dimensions of the invention, which are considered as a review of what is disclosed herein. It should be emphasized that one of ordinary skill in the art can make a decision.

The present invention provides a method and system architecture for ensuring that an actual callback number can be reliably provided for a radio unit that initiates a "9-1-1" call. More specifically, the present invention is based on at least one tag identifier, regardless of whether the caller of its origin "9-1-1" was located on a wireless or wired communication infrastructure. This allows call centers such as the regional public service response point call center (PSAP-CC) to initiate callbacks. For the purposes of the present disclosure, tag identifiers can correspond to names or labels that uniquely associate signals from different sources, for example voice associations. Thus, this tag identifier can also include one or more reference keys for databases such as emergency call registers and emergency service message entities. Thus, this one (or more) tag identifier can correspond to, for example, an emergency service routing key, a local public safety number, a paging identity and / or a mobile device identification number.

With reference to FIGS. 1 and 2, a set of embodiments of the present invention is shown. Figure 1 shows the architecture 10 of the "NRM" (network reference model) that supports mobile emergency services, while Figure 2 shows the message flow Figure 100 corresponding to this NRM in Figure 1. Shown. More specifically, the embodiments of FIGS. 1 and 2 send a call on the specified interface to the call center without the required data to process this particular call on this specified interface. Can be associated with the "NCAS" (non-call associated signaling) technique.

As shown in Figure 1, the radio unit 20 for transmitting a "9-1-1" call to architecture 10 is shown. For the purposes of this disclosure, the "9-1-1" call is an emergency call and / or a request for one (or more) emergency services (eg, police, fire department, road construction, and / or ambulance). It corresponds. The communication initiated by the radio unit 20 is the air interface U_mAbove, it is transmitted to "MSC" (mobile switching center) 40 via base station 30. This process of transmitting a "9-1-1" call to Architecture 10 corresponds to the message flow 110 in Figure 100 of Figure 2.

After this "9-1-1" call is received by the MSC40, the identification information associated with the radio unit 20 is transferred to the "ECR-SS" (emergency call register at a serving system) 50. Can be told to. This process of transmitting information to the ECR-SS50 corresponds to the message flow 120 in Fig. 2. More specifically, the information associated with the radio unit 20 includes, for example, a mobile device identification number (MEIN). This MEIN transfer to ECR-SS50 is the first NRM interface E_xImplemented by MSC40 above. When transferred to the ECR-SS50, this MEIN will be the aircraft identification ("IMEI"), electronic serial number ("ESN"), "pESN" (pseudo ESN pseudo ESN) and / or "MEID" (mobile) of the international mobile phone. It should be noted that equipment identity can be achieved by mobile phone aircraft identification).

Along with transferring this MEIN, the MSC40 can also convey the "PGID" (paging identity) to the ECR-SS50 as part of the message flow 120. If a "9-1-1" call from radio unit 20 is dropped or disconnected from base station 30 and MSC40, this PGID can be used to page to radio unit 20. To page to radio unit 20 in a dropped or disconnected situation, to uniquely identify the switch servicing the caller of "9-1-1" (eg, radio unit 20). In addition, MSC40 "LPN" (local public safety) number Local public safety number) may be required. This LPN can be achieved by a dialable number from the native assigned to the MSC40, or a non-portable number block. This LPN helps identify the ECR-SS50 and initiate a callback to this "9-1-1" caller in the event of a call dropout or disconnection within Architecture 10. obtain.

In addition to this LPN, "ESRK" (Emergency Service Routing Key) to uniquely identify the caller of this "9-1-1" as part of the message flow 120 in Figure 2. ) Can also be used. The ESRK can support the communication of the location information of the radio unit 20 as related to this "9-1-1" call. These network elements and interfaces involved in providing ESRK can be implemented using existing communication standards in one embodiment.

From the above, this PGID is an identifier based on several communication standards that supports paging to the wireless unit 20 sending incoming calls if this "9-1-1" call is dropped or disconnected. Can be one of. For GSM-based systems, the radio unit 20 includes the "IMSI" (international mobile station identity) provided by the radio unit 20 and the "TMSI" (temporary mobile station identity) associated with this IMSI. Identification) and / or can be paged via the IMEI from the radio unit 20. In a CDMA2000 system, this paging step is a "dMS ID" (default mobile station) from the mobile identification number ("MIN"), IMSI, one (or more) non-subscriber default ("NSI") radio units. identity This can be achieved using the default mobile station identification), the ESN from the radio unit 20, and / or the pESN generated from the MEID in the radio unit 20.

Using the identification information associated with the radio unit 20 received from the MSC40, the SS-ECR50 is then followed by the network interface E._yThis information can be transferred above to another emergency call register (ECR) associated with public service response point 70 (PSAP). This activity corresponds to message flow 130 in Figure 2. As a result, this MEIN, LPN, dMSID and / or ESRK can be retransmitted from SS-ECR50 to ECR-PSAP70. Note that the PSAP-ECR database is shown in relation to "ESME" (emergency service message entity) 80. However, other relevant databases in ESME80 can be keyed on to ESRK, MEIN, mobile station identification (eg, MIN or IMSI) and / or phone numbers listed in this caller's phone book.

This ESRK can then be signaled from the MSC40 to the "ESNE" (emergency service network element) 60 with a "9-1-1" call. This transmission is another network interface A_ixImplemented above. This activity corresponds to message flow 140 in Figure 2.

After being sent to ESNE60, this ESRK is then retransmitted to "PSAP-CC" (public safety access point call center) 90. Further transmission of this ESRK can be performed on another network interface C. This activity corresponds to the message flow 150 in Figure 2.

Therefore, the PSAP-CC90 can use this ESRK to query the ESME80 about the radio unit 20 from which this "9-1-1" call was initiated. ESME80 is interface E_yNote that it should now contain information previously transferred from to ECR-PSAP70. This query for ESME80 can be made on another network interface D. This activity corresponds to message flow 160 in Figure 2.

In response to a query from PSAP-CC90, ESME80 will send a "CBN" (callback number callback number), as well as its cell site location and / or its radio unit location, LPN of this serving system, and radio. The MEIN of unit 20 can be provided for PSAP-CC90. This information can be directed to the PSAP-CC90 on its D interface. This activity corresponds to message flow 170 in Figure 2. In one embodiment of the invention, this CBN directed to the PSAP-CC90 is the telephone number or non-dialable number listed in the telephone directory of this wireless unit as specified by existing standards for NSI telephones. Note that this may not be the case. In contrast, here this callback number can consist of the LPN of the MSC40 servicing the radio unit 20 and the MEIN of the radio unit 20.

Using this CBN for its processing, the PSAP-CC90 can further signal the PSAP-ECR70 and ESME80 on this D interface using this ESRK as the database key. In the unlikely event that this "9-1-1" start call is dropped or disconnected, a step of transmitting this signal can be performed to request a callback via the MSC40. Callbacks via the MSC40 allow any PSAP-CC that does not have the ability to make outgoing calls immediately to use this D interface instead to signal this PSAP-CC within ESME and request the MSC40. You will be able to make new 9-1-1 calls between your mobile phone and this PSAP-CC. Here, this request for a callback is E_yIt can be relayed to SS-ECR50 via PSAP-ECR70 on the interface. After that, SS-ECR50 then E_xCallbacks can be requested via the MSC40 on the interface. This activity corresponds to the message flows 180-200 in Figure 2.

In an alternative embodiment, if the PSAP-CC90 is equipped with the appropriate lines and equipment, participants in the PSAP-CC90 will use this LPN and / or MEIN to the radio unit 20 serviced by the MSC40. You can initiate a callback directly on it. Here, this MEIN can be inserted in the "ISUP" (ISDN user part) related to the "GAP" (global address parameter). Note that PSAP-CC90 can also use this ESRK to send requests to ESME80 on this D interface to request ESNE60. This request can be intended to initiate a callback from PSAP-CC90 to MSC40 using these LPNs and MEINs. This activity corresponds to the message flows 210-220 in Figure 2.

Note that this MEIN can identify the radio unit 20 and complete this callback for paging with the MSC40. The phone number listed in this phone book of PSAP-CC90 can be included in its calling party field of this call initiation message. This number is known by MSC40 and can be inspected in this caller field to allow this caller to be authorized for emergency callback services.

With reference to FIGS. 3 and 4, another set of alternative embodiments of the present invention is shown. Figure 3 shows one architecture 300 of the network reference model (NRM) that supports mobile emergency services, while Figure 4 shows the message flow Figure 400 corresponding to this NRM in Figure 3. Is. More specifically, the embodiments in FIGS. 3 and 4 may also relate to alternative techniques for establishing a call by a call center.

As shown in Figure 3, a radio unit 320 is shown to make a "9-1-1" call to Architecture 300. This communication initiated by the radio unit 320 is an aerial interface U_mAbove, it is communicated to MSC340 via base station 330. This process of delivering a "9-1-1" call to Architecture 300 corresponds to the message flow 410 in Figure 400 of Figure 4.

After the MSC340 receives this "9-1-1" call, the identification information associated with the radio unit 320 can be passed on to the ECR-SS350. This process of transmitting information to the ECR-SS350 corresponds to the message flow 420 in Fig. 4. More specifically, this information related to the radio unit 320 includes, for example, MEIN. This MEIN transfer to ECR-SS350 is the first NRM interface E_xImplemented by MSC340 above. Note that this MEIN transferred to the ECR-SS350 can be implemented by IMEI, ESN, pESN and / or MEID.

Along with forwarding this MEIN, the MSC340 can also pass the PGID to the ECR-SS350 as part of the message flow 420. If this "9-1-1" call from radio unit 320 drops out or disconnects from base station 330 and MSC340, this PGID can be used to page to radio unit 320. In order to call the radio unit 320 in a call dropout or disconnect situation, the LPN of the MSC340 is this "9-1-1" caller (eg, radio unit 320) serviced by a particular switch or end office. May need to be uniquely identified. This LPN can be realized by a dialable number from the native assigned to the MSC340, or a non-portable number block. This LPN helps identify the ECR-SS350 and initiate a callback to this "9-1-1" caller in the event of a call dropout or disconnection within Architecture 300. obtain.

In addition to this LPN, ESRK can also be used to uniquely identify the caller of this "9-1-1" (eg, radio unit 320) as part of the message flow 420 in Figure 4. .. The ESRK can support the communication of the location information of the radio unit 320 as related to this "9-1-1" call. These network elements and interfaces involved in providing ESRK can be implemented using existing communication standards in one embodiment.

From the above, this PGID is one of several communication standard-based identifiers that support paging to the radio unit 320 if this "9-1-1" call is dropped or disconnected. be able to. For GSM-based systems, the radio unit 320 can be paged via the IMSI provided by the radio unit 320, the TMSI associated with this IMSI, and / or the IMEI from the radio unit 320. In a CDMA2000 system, this paging step is generated from the MIN, IMSI, dMSID from one (or more) NSI radio units, ESN from radio unit 320, and / or MEID in radio unit 320. Can be achieved using.

In contrast to the approaches of embodiments in Figures 1 and 2, Architecture 300 and Message Flow Figure 400 show a combination of "CAS" (call associated signaling call-related signals) and non-call-related signals ("NCAS"). ing. More specifically, this CAS technique can be associated with ESNE360, but this NCAS method is associated with PSAP-CC390, which is based on the separation of PSAP-ECR370 from ESME380. Therefore, this technique can be named Hybrid CAS and NCAS (Hybrid CAS and NCAS) for mobile emergency services.

Architecture 300 is the network interface E between SS-ECR350 and PSAP-ECR370._yIs using. In addition to the addition of network interface E between MSC340 and ESME380, network interface B can then be placed between ESNE360 and ESME380 without including PSAP-ECR370. Therefore, the direct interface between ESNE360 and PSAP-ECR370 is not shown. In addition, additional network interface B_eIs also included between PSAP-ECR370 and ESME380. Network interface D can then be placed between ESME380 and PSAP-CC390. Finally, another additional network interface D_eIs embedded between PSAP-ECR370 and PSAP-CC390.

Using the identification information associated with the radio unit 320 received from the MSC340, unlike the embodiments in Figures 1 and 2, the SS-ECR350 provides this information about this new emergency call on the PSAP- on the Ey interface. Can be communicated to ECR370. This activity corresponds to message flow 430 in Figure 4. Note that PSAP-ECR370 is logically separated from ESME380. Therefore, this LPN, MEIN, and ESRK are B_eYou can also communicate from PSAP-ECR370 to ESME380 on the interface.

After that, this ESRK was A with LPN and MEIN by MSC340._ixIt can be communicated to ESNE360 on the interface with a call (eg, a signal associated with the call). This activity corresponds to message flow 440 in Figure 4. This ESRK can be sent from ESNE360 to PSAP-CC390 on the C interface, while the LPNs and MEINs can be sent from ESNE360 to ESME380 on the B interface in response to message flow 450. Please note that you can.

After the ESRK is transmitted with this call and transmitted over this C interface, the PSAP-CC390 can use this ESRK to query the ESME380. This query is intended to provide PSAP-CC390 with its callback number associated with radio unit 320 (ie, this LPN and MEIN). This activity corresponds to message flow 460 in Figure 4.

ESME380 can then respond to PSAP-CC390. More specifically, the ESME 380 can provide the PSAP-CC390 handling this emergency call with a callback number, radio unit location, and other relevant information needed. This activity corresponds to the message flow 470 in Figure 4.

If this "9-1-1" call is dropped or disconnected, the PSAP-CC390 can use this ESRK to signal the ESME380 on this D interface. By doing so, you can request a callback via the MSC340. This activity corresponds to the message flow 480 in Figure 4. ESME380 can then request a callback from PSAP-ECR370 via MSC340 in response to message flow 490 using the MEIN associated with this ESRK in its database. Alternatively, the PSAP-ECR370 uses this MEIN to signal, or the PSAP-CC390 uses this MEIN to signal this D._eSignals can be signaled directly to the PSAP-ECR370 on the interface to request a callback via the MSC340 in response to message flow 495.

The PSAP-ECR370 can then use this MEIN to request a callback via the MSC service. Here, this callback is made by the MSC340 using the request from the PSAP-ECR370 sent via this SS-ECR350. This activity corresponds to the message flow 500 in Figure 4. Finally, the SS-ECR350 can provide the MSC340 with a PGID and request a callback to the radio unit 320 and PSAP-CC390 via the MSC340.

Although this particular invention has been described with respect to exemplary embodiments, this description is not intended to be construed in a limited sense. Although the present invention has been described, reference to this description without departing from the spirit of the invention described in the appended claims, as well as various modifications of the exemplary embodiments, as well as additional embodiments of the invention. Please understand that it will be clear to those skilled in the art. Thus, methods, systems, and parts of these described methods and systems can be implemented in different locations, such as radio units, base stations, base station controllers and / or mobile switching centers. .. In addition, the processing circuits required to implement and use this described system are application-specific integrated circuits, software-driven processing circuits, firmware, programmable, as will be appreciated by those who benefit from this disclosure. -It can be implemented in the form of a logic device, hardware, discrete components, or a configuration consisting of the above components. These and various other modifications, configurations, and methods are provided to the present invention without rigorously following the exemplary uses exemplified and described herein, and without departing from the spirit and scope of the invention. It will be easily understood by those skilled in the art that it can be done. Accordingly, the appended claims are intended to include any such modification or embodiment contained within this true scope of the invention.

<figref num="1">It is a figure which shows the architecture of one Embodiment of this invention.</figref><figref num="2">It is a figure which shows the flow chart of one Embodiment of this invention.</figref><figref num="3">It is a figure which shows the architecture of another embodiment of this invention.</figref><figref num="4">It is a figure which shows the flow chart of another embodiment of this invention.</figref>