WO2000056097A1

WO2000056097A1 - Relating network events to subscriber and mobile equipment identities

Info

Publication number: WO2000056097A1
Application number: PCT/SE2000/000486
Authority: WO
Inventors: Patrick Joseph Cronin
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 1999-03-12
Filing date: 2000-03-10
Publication date: 2000-09-21
Also published as: CN1350757A; EP1161846A1; GB2363947A; GB0122312D0; AU3851900A

Abstract

In a radio telecommunications network, such as the Global System for Mobile Communications, and the like, traffic and radio network events are more effectively associated with any one or more corresponding mobile identities. This may be achieved by forwarding a complete mobile identity relationship to the corresponding network manager, which, in turn, uses the mobile identity relationship to update a mobile identity relationship database. Then, whenever the network manager receives a traffic, radio or other type of network event report, along with a single mobile identity, the network manager can effectively relate any or all reported events with any corresponding mobile identity by correlating the single mobile identity with the mobile identity relationship information stored in the mobile identity relationship database.

Description

RELATING NETWORK EVENTS TO SUBSCRIBER AND MOBILE EQUIPMENT IDENTITIES

FIELD OF THE INVENTION

The present invention relates to cellular telecommunications. More particularly, the present invention relates to cellular telecommunications networks which employ an architecture wherein communication and mobility management functions are handled separately from radio resource management functions.

BACKGROUND

In virtually all cellular telecommunications networks, it is of tremendous interest to be able to relate a traffic or radio network event, such as a successful handover, an unsuccessful handover, a successful call set-up, a dropped or blocked call, with all corresponding mobile identities (e.g., the Temporary Mobile

Subscriber Identity, TMSI; the International Mobile Subscriber Identity, IMSI; the International Mobile Equipment Identity, IMEI; the International Mobile Equipment Identity Software Version, IMEISV). Network managers, including the network operators associated therewith, that are capable of relating traffic and radio network events to all corresponding mobile identities are better able to support, that is, create, implement and/or execute special products or applications for improving cellular service. Examples of such products include radio network performance management products, radio network configuration products, customer/ subscriber care products, and real-time and historical statistical products. For instance, if a subscriber has experienced a number of problems with their cellular service, the subscriber might contact the service provider, who, in turn could employ one or more of these products or applications to retrieve from a database a radio network event history that specifically relates to that subscriber. In so doing, the service provider can more effectively isolate and solve problems. Furthermore, by allowing a network manager to relate traffic or radio network events to all corresponding mobile identities, the network manager is better able to determine when problems are attributable to the subscriber (e.g. , due to the subscriber's location), to a particular type of mobile unit, a particular type of mobile unit, or whether a problem is attributable to the network itself.

A cellular telecommunications network's ability to relate certain traffic or radio network events to all corresponding mobile identities, depends, to a large extent, on the network architecture employed. For example, in the Digital- Advanced Mobile Phone System (i.e, D-AMPS), which is the standard used throughout North America, and in the Japanese digital cellular standard (i.e., PDC), both of which presently employ TDM A circuit switch technology, the network architectures allocate the communication, mobility and radio resource management functions to a single, common network component or node, such as the Mobile Switching Center (i.e., the MSC). Because these functions are handled by a common network node, the traffic or radio network event information and the various mobile identities are all available or accessible from a single network node (e.g., the MSC). Accordingly, traffic or radio network event information along with any corresponding mobile identity information can be forwarded to the network manager for utilization with or by any of a number of network management or customer care products and/or applications as mentioned above.

In contrast, the Global System for Mobile Communications (i.e., the GSM system) employs a network architecture that separately allocates the communication and mobility management functions to one network component (i.e., the MSC/VLR), for example, the Mobile Switching Center with Visiting Location Register and the radio resource management functions to another network component (e.g., a base station controller, BSC). Consequently, the MSC/VLR, which is generally responsible for communication and mobility management functions, may be privy to the mobile identity information, for example, information that relates the subscriber, the mobility unit, and mobility equipment (i.e., hereinafter referred to as the mobile identity relationship information) to a particular call. However, the BSC, which handles the radio resource management functions and, which is generally responsible for recording the traffic or radio network events, is not privy to the mobility identity relationship information. Thus, the BSC in reporting traffic or radio network events to the network manager cannot provide all of the desired, corresponding mobile identity information. The network manager, therefore, is unable to relate each traffic or radio network event to the corresponding mobile identification data, and in addition, is unable to create, implement or execute many of the desired network management and customer care products and applications previously mentioned.

In addition to the fact that the GSM architecture allocates the communication, mobility and radio resource management functions to different network components, a Temporary Mobile Subscriber Identity (TMSI) is often used by a mobile unit and a corresponding BSC to identify a particular call, rather than the actual subscriber identity (i.e., the IMSI), when communicating over the air interface. The TMSI and the IMSI are stored on the Subscriber Information Module (SIM) located in the mobile unit. It will be understood that the SIM can be removed from the mobile unit and installed in another mobile unit.

Nevertheless, the primary purpose of using the TMSI rather than the IMSI is to provide customer security and protection against misuse of the subscriber's true identity. To ensure privacy, the TMSI is generated independent of and wholly unrelated to the IMSI. Thus, while a BSC may be capable of relating a traffic or radio network event to a corresponding TMSI, the BSC cannot relate that traffic or radio network event to the corresponding IMSI or, for that matter, the corresponding IMEI/IMEISV. Therefore, once again, the BSC cannot forward the traffic or radio network event information to the network manager along with all corresponding mobile identity information. Conventional techniques for collecting traffic or radio network event information tend to be counter-based. That is, the occurrence of traffic or radio network events cause counters to be incremented or decremented over some predefined period of time. Then, at the end of the predefined period, the value in a given counter is forwarded to and processed by the network manager. The information forwarded to the network manager, as one skilled in the art will readily appreciate, is an aggregation of traffic or radio network events across the network, or a portion thereof, and the information does not include or reflect any corresponding mobile identity information. Accordingly it would be desirable to provide a technique that would allow a network manager to relate each traffic or radio network event to all corresponding mobile identities (e.g., a TMSI, IMSI, IMEI, IMEISV), particularly in cellular telecommunications systems such as the GSM system, or the like.

SUMMARY

The present invention is of particular relevance to cellular telecommunications systems such as the GSM system. However, it will be understood that the present invention has applicability to other systems including the UMTS and the GPRS. Nevertheless, the present invention will be described herein below with respect to the GSM system for the purpose of simplicity.

More specifically, the present invention provides a technique which allows a network manager in such a cellular telecommunications network to relate traffic or radio network events, as well as other types of network events, to all corresponding mobile and subscriber identity data. Therefore, even if event reports are forwarded to the network manager along with a single mobile identity, for example, the TMSI, the network manager can relate the report (i.e., the event contained therein) to a corresponding IMSI and/or IMEI/IMEISV, which the network manager may need in order to create, implement or execute certain network management and/or customer care products and applications. Accordingly, it is an objective of the present invention to ensure that the network manager is capable of relating traffic or radio network event reports to corresponding mobile equipment identification data and subscriber identification data. It is another objective of the present invention provide a network manager, in a cellular telecommunications system, such as GSM or the like, with the mobile and/or subscriber identity relationship information necessary so that the network manager can create, implement or execute desired network management and customer care applications.

It is still another objective of the present invention to provide a network manager, in a cellular telecommunications system, such as GSM or the like, with the ability to create, implement or execute certain network management and customer care applications so as to improve network performance and quality of service.

In accordance with one aspect of the present invention, the above-identified objectives are achieved by a network configuration capable of and/or a related method for relating network events to a mobile identity. The network and/or method involves forwarding mobile identity relationship information to a network node, where the mobile identity relationship information includes a first and a second mobile identity, and where the first and the second mobile identity are associated with each other. The network node then produces a record which reflects the mobile identity relationship information. When a network event is subsequently reported to the network node, along with an indication that the network event corresponds to the first mobile identity, the network node is able to relate the reported network event to the second mobile identity based on the information contained in the record.

In accordance with another aspect of the present invention, the above- identified and other objectives are achieved by a network configuration capable of and/or a related method for relating traffic and radio network events to a mobile identity. The network and/ or method involves forwarding a mobile identity relationship report to a network node, where the mobile identity relationship report includes information that defines the relationship between a first mobile identity and a second mobile identity, and where the network node maintains a number of mobile identity relationship records. The network node then stores the information contained in the mobile identity relationship report, that is, the information that defines the relationship between the first mobile identity and the second mobile identity, in a mobile identity record. When a network event report is subsequently forwarded to the network node, where the network event report contains an indication of an occurrence of a traffic or radio network event and an indication that the first mobility identity relates to the traffic or radio network event, the network node is able to relate the traffic or radio network event to the second mobile identity based on the relationship between the traffic or radio network event and the first mobile identity, as indicated by the network event report, and based on the relationship between the first mobile identity and the second mobile identity as defined in the mobile identity record.

In accordance with yet another aspect of the present invention, the above- identified and other objectives are achieved by a method for relating traffic and radio network events to one of a number of mobile identities in a GSM based network. The method involves forwarding a mobile identity relationship report to a network manager node, where the mobile identity relationship report contains information that defines the relationship between a first one of the mobile identities and a second one of the mobile identities, and where the network manager node maintains a database comprising a plurality of mobile identity relationship records. The network manager node then updates the database, based on the information contained in the mobile identity relationship report. When an event report is forwarded to the network manager node, where the event report indicates the occurrence of a particular traffic or radio network event, and where the event report indicates that the traffic or radio network event relates to the first one of the mobile identities, the network manager node is able to correlate the first one of the mobile identities indicated in the event report with the second one of the mobile identities, based on the information in the database. The network manager node can the relate the traffic or radio network event to the second one of the mobile identities based on the relationship between the traffic or radio network event and the first one of the mobile identities, and based on the correlation between the first one of the mobile identities and the second one of the mobile identities, as defined in the database.

BRIEF DESCRIPTION OF THE DRAWINGS The objects and advantages of the invention will be understood by reading the following detailed description in conjunction with the drawings in which:

FIG. 1 illustrates the network architecture employed by the Global System for Mobile Communications (GSM);

FIG. 2 depicts a technique in accordance with a general embodiment of the present invention;

FIG. 3 illustrates a technique in accordance with a preferred embodiment of the present invention; and FIG. 4 illustrates a distributed network architecture associated with an alternative embodiment of the present invention.

DETAILED DESCRIPTION

FIG. 1 exemplifies a typical network architecture employed by the Global System for Mobile Communications (GSM). As illustrated, the network nodes include a home location register (HLR), an equipment identity register (EIR), a mobile services switching center with visiting location register (MSC/VLR), a base station controller (BSC), and a network manager. While the functions associated with each of these GSM network nodes are well known in the art, it is of particular importance in the present case that, in accordance with the GSM standard, certain functions are handled by the MSC/VLR (e.g., the communications and mobility management functions), while other important functions are handled by the BSC, as will be explained below. Because the MSC/VLR handles the communications and mobility management functions, only the MSC/VLR is privy to the complete mobile identity relationship, that is, the relationship between the International Mobile Subscriber Identity, IMSI; the International Mobile Equipment Identity, IMEI; and the International Mobile Equipment Identity Software Version, IMEISV, and if applicable, any corresponding Temporary Mobile Subscriber Identity (TMSI). It should be noted, however, that it may be possible to transfer a first portion of a mobile identity relationship to a network node other than the network manager, such as the EIR, which is privy to at least a second portion of the mobility identity relationship, wherein the first portion of the mobile identity relationship when combined with the second portion of the mobile identity relationship is sufficient to establish the complete mobile identity relationship.

While the MSC/VLR is responsible for the communications and mobility management functions, the BSC is primarily responsible for handling the radio resource management functions. As such, the BSC actively acquires traffic and/or radio network event information, which it eventually passes on to the network manager for processing. Examples of traffic or radio network events include successful and unsuccessful handover attempts and successful and unsuccessful call set-up attempts. However, unlike the MSC/VLR, the BSC is not privy to the entire mobile identity relationship. In fact, when the BSC records a traffic or radio network event, the event is generally identified by only one mobile identity, such as the IMSI, or the TMSI (i.e. , if the TMSI function is active), or the IMEI, or the IMEISV. Therefore, in passing traffic or radio network event information on to the network manager, the BSC is capable of providing only the event information itself and, at best, one piece of the mobile identity relationship. This is a problem, particularly if it is desirable that the network manager support network management or customer care products and/or applications that require not only the traffic or radio network event information, but also the mobile identity relationship information, so that specific traffic or radio network events can be associated with specific subscribers, mobile units, and/or mobile unit types. In accordance with an exemplary embodiment of the present invention, the network manager maintains a database, or the like, in which a number of mobile identity relationship records are stored. Thus, whenever a mobile identity relationship is established or changed, that mobile identity relationship is reported to the network manager, which in turn, updates the database or the appropriate record therein. By maintaining this mobile identity database, the network manager is capable of correlating specific traffic or radio network events, which are generally reported to the network manager along with a single, individual mobile identity (e.g., a TMSI, IMSI, IMEI or IMEISV), to a specific subscriber identity, a specific mobile unit, and specific mobile equipment, for the purpose of creating, implementing or executing any number of network management or customer care type products and/or applications.

An overview of this exemplary embodiment is illustrated in FIG. 2, wherein the network manager 205 is shown as comprising, among other features, a mobile identity relationship database 210. It will be understood that the network manager 205 may employ means similar to a database to maintain the mobile identity relationship information, such as a look-up table. It will be further understood that the network manager 205, though illustrated in FIG. 2 as a single node, may comprise a hierarchy of nodes, where each is assigned to handle the functions associated with a different level of the network. In addition, the network manager 205 is illustrated as supporting any number of network management or customer care products and/or applications 215, or the like, which rely on the network manager's ability to correlate specific traffic and radio network events with a specific subscriber, mobile unit and/or mobile equipment. FIG. 2 also indicates that, in a GSM network, the MSC/VLR 220 is the network node that is privy to the most current, complete mobile identity relationship information (e.g., the IMSI/TMSI/IMEI/IMEISV relationships). As such, the MSC/VLR 220 reports the creation of new relationships or changes in existing relationships to the network manager 205, along with a timestamp. As previously stated, the network manager 205 then uses the information in these reports to update the mobile identity relationship database 210. When the occurrence of a traffic or radio network event is reported to the network manager 205 by a BSC, for example, BSC_A or BSC_B, or alternatively a base transceiver station (BTS), along with a single mobile identity (e.g., TMSI, IMSI, IMEI or

IMEISV), the network manager can relate the traffic or radio network event with a specific subscriber, a specific mobile unit, and/or specific mobile equipment based on the information provided in the event report and the information in the mobile identity relationship database 210. FIG 2. further indicates that the MSC/VLR 220 may, on occasion, transmit a traffic or radio network event report to the network manager 205. As the MSC/VLR 220 is privy to the complete mobile identity relationship, either one part of the mobile identity relationship or the complete mobile identity relationship may be sent with the event report to the network manager 205. Therefore, in the case where only one part of the mobile identity relationship (e.g., the IMSI) is received by the network manager 205 in the event report from the MSC/NLR 220, it may still be necessary for the network manager 205 to correlate the traffic or radio network event with the corresponding subscriber, mobile unit and/or mobile equipment, as defined in the database, if the event is to be utilized by the network management or customer care product and/or application.

As one skilled in the art will appreciate, a timestamp, or the like, should be used by the network manager to determine when a corresponding traffic or radio network event occurred. The network manager can then compare the time of occurrence associated with the traffic or radio network event to the time of occurrence associated with a particular change in the corresponding mobile identity relationship information. In doing so, the network manager can accurately correlate the mobile identity in the traffic or radio network event report to the other mobile identities associated with the corresponding mobile identity relationship. FIG. 3 illustrates, in more detail, a process for accomplishing the exemplary embodiment of the present invention described above, wherein a complete mobile identity relationship is reported to the network manager 205, in accordance with a first procedural step 305. Whenever a new mobile identity relationship is generated, or there is a reallocation or change to an existing mobile identity relationship, the MSC/VLR 220 reports the new or reallocated mobile identity relationship to the network manager 205. In accordance with a preferred embodiment of the present invention, the report containing the mobile identity relationship is transported to the network manager 205 over a data link, such as a Transmission Control Protocol/Internet Protocol (TCP/IP) data link.

Of course, there are any number of reasons why a new mobile identity relationship might be created or an existing mobile identity relationship may be changed. For example, a new mobile identity relationship may be generated when a new subscriber purchases a phone and then uses that phone for the first time. On the other hand, an existing mobile identity relationship may change when a subscriber, as identified by a unique IMSI, obtains or purchases a new phone, wherein the new phone is a different model phone as compared to the subscribers previous phone, thereby causing the IMEI/IMEISV associated with the subscriber's IMSI to change. Regardless whether a new mobile identity relationship is created or an existing mobile identity relationship is modified, the MSC/VLR 220 reports the mobile identity relationship information to the network manager 205 accordingly.

By reporting new mobile identity relationships and changes to existing mobile identity relationships to the network manager 205, the network manager 205 is able to ensure that the mobile identity relationship database 210 reflects the most current mobile identity relationship information. Therefore, if the MSC/VLR 220 reports the establishment of a new mobile identity relationship, in accordance with the "NEW" path out of decision step 310, the network manager 205 will cause a new record in the mobile identity database 210 to be created and the mobile identity information associated with the new mobile identity relationship to be stored therein, as shown in procedural step 315. If, however, the MSC/VLR 220 reports a change to an existing mobile identity relationship, in accordance with the "EXIST" path out of decision step 310, the network manager 205 will use the information contained in the report to update the appropriate record in the mobile identity relationship database 210, as shown in procedural step 320.

Further in accordance with the procedure illustrated in FIG. 3, a mobile identity (e.g. , an IMSI, TMSI, IMEI or IMEISV) associated with a given traffic or radio network event is stored in the responsible BSC. For example, in procedural step 325a, the mobile identity contained in an ESTABLISH INDICATION message is stored in the responsible BSC. ESTABLISH INDICATION messages are generated by a mobile unit during a call set-up event, for the purpose of indicating to the BSC that a layer two link has been established. In another example, illustrated by procedural step 325b, the mobile identity in a

HANDOVER REQUEST message, associated with an inter-BSS (Base Station System) handover event, is stored in the target BSC (i.e., the BSC to which the corresponding mobile unit is being handed over). Then, in accordance with procedural step 325, the BSC forwards an event report to the network manager 205, wherein the event report identifies the traffic or radio network event (e.g., a successful or unsuccessful handover or a successful or unsuccessful call set-up) the corresponding mobile identity (i.e., the IMSI, TMSI, IMEI, or IMEISV), and preferably, a timestamp as illustrated in FIG. 2.

Further with respect to procedural step 325, it will be understood that event reports could be forwarded to the network manager by a network node other than a BSC. For example, an event report could be forwarded by a BTS or, quite possibly, the MSC/VLR.

Upon receiving an event report from a BSC, the network manager 205 determines whether the mobile identity contained in the event report is, for example, a TMSI, an IMSI, an IMEI or an IMEISV, in accordance with decision step 330. If the mobile identity is determined to be a TMSI, in accordance with the "TMSI" path out of decision step 330, the network manager 205 correlates the TMSI with the corresponding IMSI and IMEI or IMEISV using the appropriate mobile identity relationship record in the mobile identity relationship database 210, as shown in procedural step 335. Similarly, if the mobile identity contained in the event report is determined to be an IMSI, in accordance with the "IMSI" path out of decision step 330, the network manager 205 correlates the IMSI with the corresponding IMEI or IMEISV, as shown in procedural step 340. Finally, if the mobile identity contained in the event report is determined to be an IMEI or

IMEISV, in accordance with the "IMEI/IMEISV" path out of decision step 330, the network manager 250 correlates the IMEI or IMEISV with the corresponding IMSI, as shown in procedural step 345.

Once the network manager 205 has correlated the mobile identity contained in the event report with the other corresponding mobile identities, in accordance with the appropriate mobile identity relationship record in the mobile identity relationship database 210, the network manager 204 can relate the traffic or radio network event identified in the event report to a specific subscriber, mobile unit and/or mobile equipment, as illustrated by procedural step 350. Consequently, the traffic or radio network event information, as well as the corresponding subscriber identity, mobile unit, and mobile equipment information, can be used by the aforementioned network management or customer care products and/or applications.

It will be understood that the process illustrated in FIG. 3 is exemplary and that procedural steps alternative to those described above are feasible. For instance, procedural step 305 involves reporting a complete mobile identity relationship to the network manager 205, as stated above. Accordingly, a number of alternative techniques associated with procedural step 305 are described herein below. In a first alternative technique associated with procedural step 305, the network manager queries the MSC/VLR on-demand in order to receive the desired mobile identity relationship information. Similarly, the network manager may query the MSC/VLR for the desired mobile identity relationship information on a periodic basis.

In a second alternative technique associated with procedural step 305, the MSC/VLR tags a complete mobile identity relationship onto a first A-interface message corresponding to a particular call or connection between the MSC/VLR and the BSC. The BSC then includes the complete mobile identity relationship in any corresponding traffic or radio network event reports to the network manager. Alternatively, the MSC/VLR tags the mobile identity relationship to the first, or any traffic or radio network event report to the network manager.

In a third alternative technique associated with procedural step 305, it is possible for a "third party" node which is privy to a portion of the mobile identity relationship to receive the remaining portion of the mobile identity relationship. Then, upon piecing the different portions of the mobile identity relationship together to obtain the complete mobile identity relationship, the third party node forwards the complete mobile identity relationship to the network manager. For example, if the EIR is privy to a portion of a mobile identity relationship including the IMSI and the IMEI/IMEISV, and if the MSC/VLR or a BSC transfers a second portion of the mobile identity relationship including the TMSI and the IMSI, the EIR then has the complete mobile identity relationship. The EIR, in this case, rather than the MSC/VLR could transfer the complete mobile identity relationship to the network manager. In yet a fourth alternative associated with procedural step 305, the BSC can utilize the mobility management identification procedure normally utilized by the MSC/VLR to request mobile identification information from a mobile unit. At call setup, after the ESTABLISH INDICATION message is received by the BSC, the BSC may optionally receive one component of the mobile identity relationship. The BSC can then utilize the IDENTITY REQUEST message to request any other component of the mobile identity relationship (i.e., the TMSI, or the IMSI, or the IMEI, or the IMEISV) from the mobile unit. The associated IDENTITY RESPONSE message, which can be captured by the BSC discriminating on the mobility management protocol discriminator and IDENTITY RESPONSE message type, contains the requested component of the mobile identity relationship, if that component is available in the mobile unit. The BSC can repeat this procedure until it builds the complete mobile identity relationship. The complete mobile relationship can then be sent with any traffic or radio network event to the network manager.

Although FIGs. 1-3 show but a single network manager, the functions associated with network management may be distributed among several network components or nodes. For example, as illustrated in FIG. 4, each network element l...n, at the network element level, may employ a corresponding network element network manager 1...N, wherein a network element comprises, for instance, a BSC or a MSC/VLR. In addition, a network manager may also be employed at the network level, wherein each of the network element level network managers 1...N are in communication with the network level network manager.

Given the distributed network architecture illustrated in FIG. 4, a complete mobile identity relationship may be stored in a database (not shown) associated with the network level network manager, in accordance with another exemplary embodiment of the present invention. The network element level network managers 1...N could then query, periodically or on-demand, the database associated with the network level network manager in order to obtain the most current mobile identity relationship information to support applications being executed at the network element level, or to simply update their own mobile identity relationship databases (not shown). Alternatively, the most current mobile identity relationship information might be maintained in a database associated with each of the network element level network managers 1...N, wherein the mobile identity relationship information being maintained therein is used to update the database associated with the network level network manager.

In accordance with yet another alternative embodiment of the present invention, events other than traffic or radio network events may be related to corresponding mobile identities, using a procedure substantially similar to that which is described above and illustrated in the flowchart of FIG. 3. For example, it is feasible to associate mobile identities with corresponding network equipment related events, for instance, events associated with fault management (e.g., the base station equipment management part of a BSC). It is also feasible to associate mobile identities with corresponding transmission related events, for instance, events that occur with respect to transmissions between the BSC and the BTS, or between the BSC and the MSC/VLR. Such information would be well suited to support various customer care applications.

As stated, the present invention is described herein above with respect to the GSM system merely for purposes of simplicity. In fact, the present invention is applicable to any telecommunications system having an architecture that separates radio resource management from communication and mobility management, such as, the Universal Mobile Telecommunications System (UMTS) and any system that employs the General Packet Radio Service (GPRS). Accordingly, one skilled in the art will appreciate the fact that the present invention may involve system components other than those generally associated with the GSM system (e.g., the MSC/VLR, BSC and BTS), for example, a serving GPRS support node (SGSN), which is, of course, associated with the GPRS. Similarly, one skilled in the art will appreciate the fact that the present invention may involve mobile identities other than those associated with the GSM system

(e.g., the TMSI or IMSI), such as the Temporary Logical Link Identity (TLLI) or the Packet Temporary Mobile Subscriber Identity (P-TMSI), also associated with the GPRS. The present invention has been described with reference to exemplary embodiments. However, it will be readily apparent to those skilled in the art that it is possible to embody the invention in specific forms other than those specifically described herein above; furthermore, this may be done without departing from the spirit of the invention. These embodiments are merely illustrative and should not be considered restrictive in any way. The scope of the invention is given by the appended claims, rather than the preceding description, and all variations and equivalents which fall within the range of the claims are intended to be embraced therein.

Claims

WHAT IS CLAIMED IS:

1. In a cellular radio telecommunications network, a method for relating network events to a mobile identity comprising the steps of: forwarding mobile identity relationship information to a network node, wherein the mobile identity relationship information includes a first mobile identity and a second mobile identity, wherein the second mobile identity is associated with the first mobile identity; producing a record in the network node which reflects the forwarded mobile identity relationship information; reporting an occurrence of a network event to the network node, along with an indication that the network event corresponds to the first mobile identity; and relating the reported network event to the second mobile identity based on the information contained in the record.

2. The method of claim 1, wherein said step of producing a record in the network node which reflects the forwarded mobile identity relationship information comprises the step of: generating a record that reflects a new mobile identity relationship.

3. The method of claim 1, wherein said step of producing a record in the network node which reflects the forwarded mobile identity relationship information comprises the step of: updating a record that reflects a change to an existing mobile identity relationship.

4. The method of claim 1, wherein said step of relating the reported network event to the second mobile identity based on the information contained in the record comprises the step of: correlating the first mobile identity, reported to the network node along with the occurrence of the network event, to the second mobile identity using the association between the first mobile identity and the second mobile identity as reflected in the record; and relating the reported network event to the second mobile identity based on said step of correlating the first mobile identity to the second mobile identity using the association between the first mobile identity and the second mobile identity as reflected in the record.

5. The method of claim 1, wherein the network node provides functions for said cellular radio telecommunications network.

6. The method of claim 1, wherein said network events are traffic or radio network events.

7. The method of claim 1, wherein said network events are network equipment related events

8. The method of claim 1, wherein said network events are transmission related events.

9. In a cellular radio telecommunications network, a method for relating traffic and radio network events to a mobile identity comprising the steps of: forwarding a mobile identity relationship report to a network node, wherein the mobile identity relationship report includes information that defines a relationship between a first mobile identity and a second mobile identity, and wherein the network node maintains a plurality of mobile identity relationship records; storing the information included in the mobile identity relationship report that defines the relationship between the first mobile identity and the second mobile identity in a mobile identity record in the network node; forwarding a network event report to the network node, wherein the network event report includes an indication of an occurrence of a traffic or radio network event and an indication that the first mobility identity relates to the traffic or radio network event; and relating the traffic or radio network event to the second mobile identity based on the relationship between the traffic or radio network event and the first mobile identity, as indicated by the network event report, and based on the relationship between the first mobile identity and the second mobile identity as defined in the mobile identity record.

10. The method of claim 9 further comprising the step of: generating the mobile identity record in which the information defining the relationship between the first mobile identity and the second mobile identity is stored.

11. The method of claim 9, wherein said step of storing the information in the mobile identity relationship report comprises the step of: updating one of the plurality of mobile identity records.

12. The method of claim 9, wherein said step of relating the traffic or radio network event to the second mobile identity comprises the step of: correlating the first mobile identity, which is related to the traffic or radio network event, as indicated by the network event report, with the second mobile identity based on the relationship between the first mobile identity and the second mobile identity, as defined in the mobile identity record.

13. The method of claim 9, wherein network node serves as a network manager for said cellular radio telecommunications network.

14. In a Global System for Mobile Communications (GSM) based network, a method for relating traffic and radio network events to one of a number of mobile identities, said method comprising the steps of: forwarding a mobile identity relationship report to a network manager node, wherein the mobile identity relationship report contains information which defines a relationship between a first one of said number of mobile identities and a second one of said number of mobile identities, and wherein the network manager node maintains a database comprising a plurality of mobile identity relationship records; updating the database in the network manager node based on the information contained in the mobile identity relationship report; forwarding an event report to the network manager node, wherein the event report indicates the occurrence of a particular traffic or radio network event, and wherein the event report indicates that the traffic or radio network event relates to the first one of said number of mobile identities; correlating the first one of said number of mobile identities indicated in the event report with the second one of said number of mobile identities based on the information in the database; and relating the traffic or radio network event to the second one of said number of mobile identities based on the relationship between the traffic or radio network event and the first one of said number of mobile identities, and based on the correlation between the first one of said number of mobile identities and the second one of said number of mobile identities as defined in the database.

15. The method of claim 14, wherein the first of said number of mobile identities is a Temporary Mobile Subscriber Identity.

16. The method of claim 15, wherein the second of said number of mobile identities is an International Mobile Subscriber Identity.

17. The method of claim 15, wherein the second of said number of mobile identities is an International Mobile Equipment Identity.

18. The method of claim 15, wherein the second of said number of mobile identities is an International Mobile Equipment Identity Software Version.

19. The method of claim 14, wherein the first of said number of mobile identities is an International Mobile Subscriber Identity.

20. The method of claim 19, wherein the second of said number of mobile identities is an International Mobile Equipment Identity.

21. The method of claim 19, wherein the second of said number of mobile identities is an International Mobile Equipment Identity Software Version.

22. The method of claim 14, wherein said step of updating the database in the network manager node based on the information contained in the mobile identity relationship report comprises the steps of: creating a new database record; and storing the information which defines the relationship between the first one of said number of mobile identities and the second one of said number of mobile identities in the new database record.

23. The method of claim 14, wherein said step of updating the database in the network manager node based on the information contained in the mobile identity relationship report comprises the step of: modifying an existing database record by storing therein the information which defines the relationship between the first one of said number of mobile identities and the second one of said number of mobile identities.

24. The method of claim 14, wherein the event report is forwarded to the network manager node from a base station controller.

25. The method of claim 14, wherein the event report is forwarded to the network manager node from a mobile switching center with visiting location register.

26. The method of claim 14, wherein the event report is forwarded to the network manager node from a base transceiver station (BTS).

27. The method of claim 14, wherein the mobile identity relationship report is forwarded to the network manager node from a mobile switching center, and wherein the mobile switching center is privy to information that defines a complete mobile identity relationship.

28. The method of claim 14, wherein the network manager node queries the mobile switching center to forward the mobile identity relationship report.

29. The method of claim 14, wherein the mobile identity relationship report is forwarded to the network manager node from a network node that is privy to information that defines a partial mobile identity relationship, and wherein the network node constructs a complete mobile identity relationship prior to forwarding the mobile identity relationship report to the network manager node.

30. The method of claim 14, wherein the mobile identity relationship report is forwarded to the network manager node from a base station controller.

31. The method of claim 30, wherein a mobile switching center tags mobile identity relationship information, upon which the mobile identity relationship report is based, in an A-interface message to the base station controller, prior to the base station controller forwarding the mobile identity relationship report to the network manager.

32. The method of claim 30, wherein the base station controller solicits mobile identity relationship information from a corresponding mobile unit, and therefrom, constructs a complete mobile identity relationship, upon which the mobile identity relationship report is based, prior to forwarding the mobile identity relationship report to the network manager node.

33. A cellular radio telecommunications network capable of relating network events to a mobile identity comprising: means for forwarding mobile identity relationship information to a network node, wherein the mobile identity relationship information includes a first mobile identity and a second mobile identity, wherein the second mobile identity is associated with the first mobile identity; means for producing a record in the network node which reflects the forwarded mobile identity relationship information; means for reporting an occurrence of a network event to the network node, along with an indication that the network event corresponds to the first mobile identity; and means for relating the reported network event to the second mobile identity based on the information contained in the record.

34. The network of claim 33, wherein said means for producing a record in the network node which reflects the forwarded mobile identity relationship information comprises: means for generating a record that reflects a new mobile identity relationship.

35. The network of claim 33, wherein said means for producing a record in the network node which reflects the forwarded mobile identity relationship information comprises: means for updating a record that reflects a change to an existing mobile identity relationship.

36. The network of claim 33, wherein said means for relating the reported network event to the second mobile identity based on the information contained in the record comprises: means for correlating the first mobile identity, reported to the network node along with the occurrence of the network event, to the second mobile identity using the association between the first mobile identity and the second mobile identity as reflected in the record; and means for relating the reported network event to the second mobile identity based on said step of correlating the first mobile identity to the second mobile identity using the association between the first mobile identity and the second mobile identity as reflected in the record.

37. The network of claim 33, wherein the network node provides network management functions for said cellular radio telecommunications network.

38. The network of claim 33, wherein said network events are traffic or radio network events.

39. The network of claim 33, wherein said network events are network equipment related events.

40. The network of claim 33, wherein said network events are transmission related events.

41. A cellular radio telecommunications network capable of relating traffic and radio network events to a mobile identity comprising: means for forwarding a mobile identity relationship report to a network node, wherein the mobile identity relationship report includes information that defines a relationship between a first mobile identity and a second mobile identity, and wherein the network node maintains a plurality of mobile identity relationship records; means for storing the information included in the mobile identity relationship report that defines the relationship between the first mobile identity and the second mobile identity in a mobile identity record in the network node; means for forwarding a network event report to the network node, wherein the network event report includes an indication of an occurrence of a traffic or radio network event and an indication that the first mobility identity relates to the traffic or radio network event; and means for relating the traffic or radio network event to the second mobile identity based on the relationship between the traffic or radio network event and the first mobile identity, as indicated by the network event report, and based on the relationship between the first mobile identity and the second mobile identity as defined in the mobile identity record.

42. The network of claim 41 further comprising: means for generating the mobile identity record in which the information defining the relationship between the first mobile identity and the second mobile identity is stored.

43. The network of claim 41, wherein said means for storing the information in the mobile identity relationship report comprises: means for updating one of the plurality of mobile identity records.

44. The network of claim 41 , wherein said means for relating the traffic or radio network event to the second mobile identity comprises: means for correlating the first mobile identity, which is related to the traffic or radio network event, as indicated by the network event report, with the second mobile identity based on the relationship between the first mobile identity and the second mobile identity, as defined in the mobile identity record.

45. The network of claim 41, wherein the network node serves as a network manager for said cellular radio telecommunications network.