WO2001047182A2

WO2001047182A2 - Resource tracking and display in a communications system

Info

Publication number: WO2001047182A2
Application number: PCT/SE2000/002557
Authority: WO
Inventors: Kurt-Erik Eriksson; Lars Andersson; Susanne Falk
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 1999-12-21
Filing date: 2000-12-15
Publication date: 2001-06-28
Also published as: AU2564201A; TW533705B; AR029419A1; WO2001047182A3; EP1240749A2

Abstract

A method, system, and apparatus enables a network operator or vendor to dynamically trace (e.g., track) the resources utilized by a connection during all or any portion of the connection. When a call connection is initiated, each node involved in a connection detects the resources therein involved in the connection path. Furthermore, while the connection still exists, the nodes may continue to detect resource changes (e.g., additions, deletions, exchanges) in order to record them during, for example, the entire lifetime of the connection. During or after the connection, the detected utilized resources may be sent to a control and/or management center for display and analysis. The connection resource tracking results may be displayed in a number of ways, such as a chronological, icon-based graphical display; a tree-like, nodal-based graphical display that may be expanded or collapsed in order to focus the display on the connection portion of interest; etc.

Description

RESOURCE TRACKING AND DISPLAY IN A COMMUNICATIONS

SYSTEM

BACKGROUND OF THE INVENTION

Technical Field of the Invention

The present invention relates in general to the field of communications systems, and in particular, by way of example but not limitation, to continuous resource tracing in a wireless communications system with contemporaneous or subsequent display of the tracked resources.

Description of Related Art

Access to wireless networks is becoming increasingly popular for business, social, and recreational purposes. Users of wireless networks now rely on them for both voice and data communication. Additionally, such users demand an ever increasing array of services and capabilities, as well as ever improving quality of service (QoS). To meet such demands, network operators and network vendors constantly strive to create and implement a more diverse variety of features, many of which consume increasingly greater amounts of bandwidth. Designing, installing, and testing the infrastructure necessary to provide these new services and capabilities is an expensive and time-consuming undertaking.

In order to reduce the expense of improving the infrastructure, network operators and network vendors (e.g., during the design, installation, and testing phase(s)) often need to verify the dynamic behavior of hardware and software components for the traffic nodes involved in a call connection. Examples of such situations include: vendor verification of new hardware components, vendor verification of new and changed application software components at system integration, operator verification of new hardware and software components, operator verification of new system deliveries, and operator and vendor tracing of faulty device equipment. Conventional systens provide only a minimal call tracing capability. For example, under the Global System for Mobile Communications (GSM) standard, a function Call Path Tracing (CPT) can provide operating staff with the picture of a call through one Base Station Controller (BSC) in terms of allocated resources for the call. Unfortunately, the picture is only a static snapshot of the allocated resources at a particular moment. Furthermore, the picture provided by the CPT function only reflects the resources in the BSC, but not those of the Base Transceiver Station (BTS).

SUMMARY OF THE INVENTION The deficiencies of the prior art are overcome by the method, system, and apparatus of the present invention. For example, as heretofore unrecognized, it would be beneficial to implement a dynamic connection tracing mechanism. In fact, it would be beneficial if various resources utilized during a call (i) could be tracked as the resources changed during the connection and (ii) simultaneously or subsequently displayed.

An object of certain embodiment(s) of the present invention is to provide a view of resource changes down to the level of individual hardware and software elements. The view of resource changes may correspond to, for example, instances of call setups, times when a device is blocked, mobile terminals (MTs) that are moving around within a wireless network, etc. Another object of certain embodiment(s) of the present invention is to enable viewing of dynamic allocation and deallocation of resources for a connection path through multiple traffic nodes.

In accordance with the present invention, resources utilized during a connection may be continuously detected during all or a portion of the lifetime of the connection. In one embodiment, once a call connection is initiated, resource tracking trigger mechanisms are activated in all involved nodes. The resource tracking trigger mechanisms dynamically detect changes (e.g., additions, deletions, exchanges/substitutions) in the resources that are utilized in each node during the connection. The tracked resource changes may be recorded (e.g., stored, transmitted, compiled, etc.). The resource tracking may continue until the connection is terminated or a command is received that terminates the tracking. In another embodiment, continuous/dynamic connection tracing (i.e., connection "tracking") enables detected resource changes to be organized into a data structure that facilitates display of the tracking results. The display of the tracking results may be presented graphically to aid in the analysis of a connection or in the diagnosis of the network. For example, the connection resource tracking results may be displayed as a chronological, icon-based graphical display; a tree-like, nodal-based graphical display that may be expanded or collapsed in order to focus the display on the connection portion of interest; etc.

The technical advantages of the present invention include, but are not limited to, the following. It should be understood that particular embodiments may not involve any, much less all, of the following exemplary technical advantages.

An important technical advantage of the present invention is that it enables dynamic call tracing of resources during a connection.

Another important technical advantage of the present invention is that it provides for the recording of various resources utilized during a connection as the resources change.

Yet another important technical advantage of the present invention is the ability to improve analysis of the connection path by graphically displaying the results of the tracking. Yet another important technical advantage of the present invention is the ability to optimally pinpoint faulty device equipment when field testing new user equipment.

Yet still another important technical advantage of the present invention is the ability to accelerate the testing of new and altered hardware and software during system integration and verification. The above-described and other features of the present invention are explained in detail hereinafter with reference to the illustrative examples shown in the accompanying drawings. Those skilled in the art will appreciate that the described embodiments are provided for purposes of illustration and understanding and that numerous equivalent embodiments are contemplated herein. BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the method and system of the present invention may be had by reference to the following detailed description when taken in conjunction with the accompanying drawings wherein: FIGURE 1 illustrates an exemplary multi-network environment in which the present invention may be advantageously practiced;

FIGURE 2 illustrates an exemplary wireless network system with which the present invention may be advantageously practiced;

FIGURE 3 illustrates an exemplary network node in accordance with the present invention;

FIGURE 4A illustrates an exemplary message format having a tracking trigger block in accordance with the present invention;

FIGURES 4B and 4C illustrate exemplary resource tracking data structures in accordance with the present invention; FIGURE 5 illustrates an exemplary method in flowchart form for resource tracking in accordance with the present invention;

FIGURE 6A illustrates an exemplary graphical display of a resource tracking result in accordance with the present invention;

FIGURE 6B illustrates another exemplary graphical display of a resource tracking result in accordance with the present invention; and

FIGURE 6C illustrates yet another exemplary graphical display of a resource tracking result in accordance with the present invention.

DETAILED DESCRIPTION OF THE DRAWINGS In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular circuits, logic modules (implemented in, for example, software, hardware, firmware, some combination thereof, etc.), techniques, etc. in order to provide a thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known methods, devices, logical code (e.g., hardware, software, firmware, etc.), etc. are omitted so as not to obscure the description of the present invention with unnecessary detail.

A preferred embodiment of the present invention and its advantages are best understood by referring to FIGURES 1 -6B of the drawings, like numerals being used for like and corresponding parts of the various drawings.

Referring now to FIGURE 1, an exemplary multi-network environment in which the present invention may be advantageously practiced is illustrated generally at 100. A wireless network system of the multi-network environment 100 includes several exemplary components. These components include radio base stations (RBSs) 1 15(X,Y,Z), which may be in wireless communication with MTs 120, and radio network controllers (RNCs) 110(1,2). The wireless network system also includes a representation of the core network (CN) 105. Optionally, the wireless network system may also incorporate a satellite-based component 125. In accordance with the present invention, a continuous/dynamic tracing (or a "tracking" herein) of resources utilized for a connection (e.g., from the MT 120 to/through the wireless network) may be provided (e.g., displayed) to a network operator or vendor. The CN 105 may be in communication with other networks (e.g., that maybe either separate networks and/or a (possibly overlaid) control network). The exemplary networks illustrated in the multi-network environment 100 include an intelligent network (IN) (e.g., a Signaling System 7 (SS7) network) 130, the Internet 135, a generic network 145, an Integrated

Services Digital Network (ISDN) 140, etc.

Referring now to FIGURE 2, an exemplary wireless network system with which the present invention may be advantageously practiced is illustrated generally at 200. The wireless network 200 may correspond to, for example, the wireless network illustrated as part of the multi -network environment 100 (of FIGURE 1 ). The wireless network 200 may operate in accordance with any of many exemplary wireless network standards, such as the Personal Digital Cellular System (PDC) of Japan (RCR STD-27F) (formerly called the Japanese Digital Cellular System (JDQ), the Global System for Mobile Communications (GSM), the Digital Advanced Mobile Phone System (D-AMPS), Code Division Multiple Access (CDMA)-based systems, etc.

While the principles of the present invention may be implemented in any of the above exemplary systems (and others), they are particularly advantageous when implemented in a Wideband-CDMA (WCDMA) system.

For example, in WCDMA systems more sophisticated handover mechanisms exist as compared to GSM. An MT 120(B), for example, may establish a connection towards more than one RBS 115(X,Y,Z) and/or also towards more than one sector of the same RBS 115(X,Y,Z) simultaneously. As the MT 120(B) moves around the wireless network 200, the resource picture changes accordingly. The resource picture also changes, for example, when the MT 120(B) requests a change in the QoS for an existing connection. In short, the more dynamic resource allocation in WCDMA systems complicate the resource picture and thereby make it more difficult to understand. Consequently, there is an even greater need in Universal Mobile Telephone Service (UMTS) systems to verify that the right resources, from the set up of a connection until the release of the connection, are allocated and deallocated as expected. The present invention meets this need by providing a view of continuous changes in the resource picture. In other words, certain embodiments of the present invention cause the allocated resources of the RBSs 115(X,Y,Z) and the RNCs 110(1,2), for example, to be mirrored in a dynamically changed picture.

With continuing reference to FIGURE 2, the wireless network 200 is illustrated with three MTs 120(A,B,C), although many more MTs may be present in the wireless network 200. The MT 120(A) may be in wireless communication with the RBS

115(X), and the MT 120(C) may be in wireless communication with the RBS 115(Z). The MT 120(B), on the other hand, is located in a handoff area between cells (or sectors of two cells) associated with the RBSs 115(X,Y), and the MT 120(B) may thereof be in simultaneous communication with both of the RBSs 115(X,Y). The CN 105 is also illustrated with a general node 205, which may be part of a signaling and control network, for example. A control and management center (CMC) 210 is also illustrated as being connected to, or part of, the CN 105. A terminal with a display 215 is connected to, or part of, the CMC 210. In accordance with the present invention, resources for a connection between the MT 120(B) and the MT 120(C) (e.g., through the RBS 115(X), the RNC 110(1), possibly one or more nodes 205 in the CN 105, the

RNC 110(2), and the RBS 115(Z)) may be tracked and reported to a network operator or vendor (e.g., at the CMC 210 via the terminal and display 215). The present invention further enables an operator/vendor to acquire a presentation of allocated resources in multiple traffic nodes for a specific call. A call, in this context, may be considered as a number of connections between an MT 120 and the CN 105. And a connection, in this context, may be considered a signaling or logical connection between an MT 120 and a node 205 of the CN 105, the connection providing a specified service between the two access points.

Referring now to FIGURE 3, an exemplary network node in accordance with the present invention is illustrated at 300. The exemplary network node 300 may correspond to, for example, the RNC 110, the RBS 115, the general (CN) node 205, the CMC 210, etc. A communications port 305 (e.g., an antenna for a wireless link, a network adapter device for a wireline link, etc.) of the network node 300 sends and receives signals and forwards them to signal handler 310 (e.g, a transceiver (TRX)). The signal handler 310 may forward the signals to a data extractor 315 (e.g., filters, demodulators, etc.) for further (e.g., baseband) processing. The signal handler 310 and the data extractor 315 may be connected to a bus 320, which interconnects various elements of the network node 300. A controller 325, a processing unit 330, and a memory 335, for example, may also be connected to the bus 320. It should be noted that two separate processors (e.g., a controller 325 and a processing unit 330) are not both necessary for an embodiment of the present invention. Nevertheless, many processors (e.g., one, two, three, or more processors) may alternatively be present and used in accordance with the present invention within the network node 300. These exemplary aspects of the network node 300 maybe interconnected and interrelated in manners known to those of ordinary skill in the art to accomplish standard tasks assigned to respective types of network nodes.

The one or more logic modules 340 may also be part of the network node 300. The one or more logic modules 340 may be designed, programmed, etc. to effectuate the principles of the present invention. In other words, the one or more logic modules 340 may be software residing in the memory 335 (or another memory (not shown)) that may program the processing unit 330 to implement the principles of the present invention. Alternatively, the one or more logic modules 340 may be hardware realized in the controller 325 (e.g., an application specific integrated circuit (ASIC)) that implements the principles of the present invention. Other hardware, software, firmware, some combination thereof, etc. realization(s) of the one or more logic modules 340 are also alternatives within the scope of the present invention for controlling/effectuating the functions and/or operations of the network node 300, including those corresponding to the principles of the present invention.

Furthermore, the one or more logic modules 340 may also represent one or more other resources 345. The other resources 345 may alternatively be a physical device, such as a transceiver; a radio frequency (RF) transmission channel, such as a traffic channel assignable to an MT 120; an Internet Protocol (IP) address from an IP address pool, etc. The other resources 345 may be connected to the bus 320. Other examples of other resources 345 that may be tracked include: (i) within an RNC, a Packet Data Router (PDR), a Common Channel (CC), a Regional Radio Connection (RRC), a Signaling Connection, and a User Data Connection (e.g., a Radio Access Bearer (RAB)); and (ii) between an RNC and an RBS, traffic connection identities.

In accordance with certain embodiment(s) of the present invention, the connection tracking may be activated by command. For example, for a specific MT identity, a trigger mechanism in the RNC where the call is expected to be set up is activated by command. When the connection establishment for this MT is started in the RNC, the trigger mechanism(s) for the same MT may also be activated for the RBS node(s) involved in the connection. Alternatively, a modified MT or a specially configured test MT may include a tracking trigger in a call set-up message.

Referring now to FIGURE 4 A, an exemplary message format having a tracking trigger block in accordance with the present invention is illustrated at 400. The message format 400 includes a destination address block 405 (e.g., an address of a network node), a resource tracking trigger block 410 in accordance with the present invention, a general block 415 (e.g., representing additional elements of the message), and an information block 420 (e.g., containing control or voice data or other type(s) of message payload). The message format 400, including the resource tracking trigger block 410, may be sent, for example, from the CMC 210 to the RNC that initially receives a command to activate the resource tracking. Subsequently, the RNC may send a different message format 400 to the RBS node(s) involved in the connection. The resource tracking trigger block 410 may include various information related to the resource tracking, such as an identification of the connection to be tracked, a nodal address to which tracked resource information is to be sent, etc. When a trigger mechanism in the RNC or any involved RBS node(s) (or other general nodes in the CN) detects that a resource for the specified MT and connection is being or has been allocated or deallocated, the resource change information is transferred to a function that sorts the information into an appropriate data structure (e.g., a queue). As long as the function is active, detected resource changes are transferred to the function. The function may be, for example, a software application

(or other logic module) that is either a part of or separate from the trigger mechanism (which may also be a logic module). A recording functionality is therefore introduced into the network for tracking resource changes. The sorting scheme is established in such a manner so that every specific connection path for a call, through all involved traffic nodes, can be easily extracted for (e.g., graphical) presentation.

The detected resource changes may be amalgamated and/or organized in many ways. For example, each individual node involved in a resource-tracked connection can record resource changes into its own memory and transmit (e.g., using the message format 400) the entire data structure of resource changes after the connection or tracking is terminated. Transmitting the entire set of resource at once minimizes signaling load on the network. As another example, each individual node involved in a resource-tracked connection can transmit (e.g., using the message format 400) each resource change to a "controlling" node (e.g., the RNC first receiving or sending a tracking activation command, the CMC 210, etc.) as the resource change is detected. Transmitting each resource change as the change is detected does increase the signaling load on the network, but it enables a real-time view of resource changes as they occur when they are displayed (e.g., on the terminal and display 215) as the resource changes are received. Other resource change transmission schemes may alternatively be implemented. Regardless of the resource change transmission scheme in use for a specific connection, the detected resource changes can be saved temporarily or persistently. Referring now to FIGURES 4B and 4C, exemplary resource tracking data structures in accordance with the present invention are illustrated at 430 and 460, respectively. The exemplary resource tracking data structures 430 and 460 may include a connection identifier 435, which includes information that identifies the connection (e.g., the involved MT, the call time, etc.). The exemplary resource tracking data structures 430 and 460 may also include additional information relating to the (e.g., call) connection, such as a notation when a connection extends beyond the CN 105 and into an auxiliary network (e.g., the IN 130, the Internet 135, generic network 145, the ISDN 140, etc.). The resource tracking data structure 430 differs from the resource tracking data structure 460 in terms of storage organization of the resources tracked. For example, the tracked resources 445 (of FIGURE 4B) are stored chronologically as each resource is allocated and/or deallocated, regardless of the location of the resource. Each resource entry therefore includes a corresponding nodal identifier. The resources that have been tracked in the resource tracking data structure 460

(of FIGURE 4C), on the other hand, are stored/grouped by network node 465. Each network node grouping 465 includes entries (e.g., listed chronologically) that correspond to tracked resources. For both resource tracking data structures 430 and 460, an allocation/deallocation exchange of resources may be stored, for example, as either a single entry or a pair of entries. It should also be noted that each resource entry includes a time stamp to facilitate the ultimate display of the tracked resources in a manner designed to aid network analysis. For example, a network operator or vendor can elect to see all the resources being utilized at a particular instant of time. Once a connection's resources have been recorded into a data structure and the connection is released, the resource tracking trigger mechanisms of involved nodes may be automatically deactivated. Alternatively, the trigger mechanisms can be deactivated by command (e.g., as transmitted in a message format 400).

Referring now to FIGURE 5, an exemplary method in flowchart form for resource tracking in accordance with the present invention is illustrated generally at 500. (The exemplary flowchart 500 is now described with additional reference to

FIGURE 2 in order to further illuminate the exemplary method with an exemplary call connection event.) Flowchart 500 begins when a connection is initiated (step 505). For example, the MT 120(B) may initiate a connection to the CN 105 via the RNC 110(1) and the RBS 115(X). The resource tracking trigger mechanisms in the involved nodes are activated/engaged for the initiated connection (step 510). The activation may be instituted, for example, via a command (e.g., using the message format 400) sent to the RNC 110(1) from the terminal and display 215 of the CMC 210 or directly in the RNC 110(1) responsive to detection of a preselected MT identification associated with a connection. The trigger mechanisms (e.g., which may be logic module(s) of the one or more logic modules 340) in each of the involved nodes cause the resources utilized in the connection to be recorded (step 515). The resources may be recorded in data structures equivalent or similar to the resource tracking data structures 430 and 460.

As the connection continues, the triggering mechanisms detect allocation and/or deallocation changes in the resource picture (step 520). If a resource change is detected (at step 520), then the change is recorded (step 515). If, on the other hand, a resource change is not detected (at step 520), then it is determined whether the connection is terminated (step 525). If the connection is terminated (at step 525), then the tracking results are reported (step 530). If, on the other hand, the connection is not terminated (at step 525), then it is determined whether the tracking has been terminated (step 535). The tracking may be terminated by a command (e.g., issued by the relevant network vendor or operator) or by a predetermined condition. If the tracking is not terminated (at step 535), then the triggering mechanism(s) can again attempt to detect a resource change (step 520). It should be understood that the processes/threads/etc. that may be the selected embodiment(s) of the present invention maybe essentially running concurrently. Consequently, steps 520, 525, and 535, for example, may occur essentially simultaneously, instead of in the exemplary order presented in flowchart 500.

If, on the other hand, the tracking is terminated (at step 535), then the tracking results may be reported (step 530). The tracking results may be reported, for example, by sending any recorded resources (e.g., the data structures 430, 460 or any remaining portions thereof) to the CMC 210. The tracking results may thereafter be presented for analysis using the terminal and display 215. It should be noted that other manners and locations may alternatively be selected for the reporting and the display of the tracking results. The network operator or vendor responsible for the resource tracking may request to view the changes of the resource picture that have been stored in a queue (or other data structure) one after the other in a forward or backward direction.

The dynamic changes of the resources may be represented on the terminal and display 215. A play functionality of the resource tracking is thus introduced into the network system. The dynamic resource presentation may be presented in a multitude of formats. These formats include a chronological, icon-based graphical display; a tree- like, nodal-based graphical display; a listing in tabular form (e.g., similar to the illustrated representations of the data structures 430 and 460 of FIGURES 6B and 6C); etc.

Referring now to FIGURE 6A, an exemplary graphical display of a resource tracking result in accordance with the present invention is illustrated generally at 600. The graphical display 600 is a chronological, icon-based graphical display that shows an example of how resource allocation and deallocation dynamically changes during the lifetime of a connection. Time elapses from the top of the graph to the bottom. A new connection path and resource diagram is displayed each time the resource picture changes. The specifics of the graphical display 600 reflect the exemplary call connection event described above with reference to FIGURE 5. In other words, a connection between the MT 120(B) and the RNC 110(1) is established through the RBS 115(X) in the first graph. In the second graph, a resource is removed/deleted from the connection path in the RNC 110(1), and a resource exchange occurs along the connection path in the RBS 115(X). In the third graph, a resource is added to the connection path through the RNC 110(1 ), and a new resource picture is presented for the connection path through the RBS 115(Y) (e.g., after a handover). The display may also include a precise indication of the actual resource (name, number, or other designation) on the icon for each resource. Alternatively, such a precise indication may be displayed after a graphical user interface (GUI) pointer (e.g., an arrow) is moved over or actually clicks on the icon for a particular resource. Referring now to FIGURE 6B, another exemplary graphical display of a resource tracking result in accordance with the present invention is illustrated generally at 650(1) and 650(2). These graphical tree views are sorted per connection through involved nodes. The network operator or vendor may expand or collapse such views to focus on the information that is most useful for a given task or at a given moment. (The specifics of the graphical displays 650(1) and 650(2) also reflect the exemplary call connection event described above with reference to FIGURE 5.) The graphical display 650(1) is a detailed diagram that shows all the resources used during the entire connection, which is divided into three graphs in the graphical display 600 (of FIGURE 6A). It should be noted that the 'Rsrc A' of 'RBS(x)' is not necessarily identical to the 'Rsrc A' of 'RBS(y)'. It should be understood that the resources may be further subdivided into resources of resources, as appropriate.

The graphical display 650(2), on the other hand, is a higher-level diagram that shows the nodes used during the entire connection, without "confusing" or "cluttering" the display with lower-level details. Advantageously, this collapsibility and expandibility enhances a vendor's or operator's ability to diagnose a call connection event. Also shown on graphical displays 650(1) and 650(2) are possible connections to the Internet and to the RNC 110(2) (not included as part of the example described above with reference to FIGURE 5). If the connection from the MT 120(B) were to extend beyond the CN 105 into other auxiliary networks or to other RNCs, for example, the graphical displays 650(1) and 650(2) (and 650) can display such a progression of the connection.

Referring now to FIGURE 6C, yet another exemplary graphical display of a resource tracking result in accordance with the present invention is illustrated generally at 660. These graphical tree views are sorted per connection through involved nodes. The network operator or vendor may expand or collapse such views (e.g., using the box with a horizontal line in the center) to focus on the information that is most useful for a given task or at a given moment. The exemplary preferred treelike, nodal-based graphical display 660 illustrates both a circuit-switched connection 665 and a packet-switched connection 670 that are routed through a CN1 and a CN2, respectively. Each connection 665 and 670 is also routed through the "Stockholm" RNC and the "Kista" RBS, albeit via different cells. The graphical display 660, in addition to providing a picture of the nodes through which the connections traverse, provides indications of the resources utilized in such connections. For example, the signaling connection 675 utilizes "RRC 2", and the traffic connection 680 utilizes the "PDR 3", the "RRC 1", and the "CC 2".

In an alternative embodiment, the presentation of allocated and deallocated resources may be filtered a number of ways. For example, a network vendor or operator may request that only certain resources that fit a particular criterion or criteria be displayed. The criterion/criteria may be requested to be Radio Network resources only, Transport Network resources only, resources allocated for a specific Packet Data

Connection, a combination of such criteria, etc.

Embodiment(s) of the present invention therefore enable network operators and vendors to review the dynamic behavior of resource allocation/deallocation during the lifetime of a connection. Operators and vendors can therefore verify that the intended devices are allocated and deallocated as expected in different traffic situations, especially during the setup and release of a call. The present invention provides significant improvements over conventional systems when detecting faulty device equipment or testing new user equipment, especially in field environments. New user equipment, such as new MTs with new characteristics and features, will have an influence on resource allocation and deallocation in traffic nodes. The present invention ameliorates testing difficulties associated with rolling out such new characteristics and features, especially when introducing a new system such as UMTS. Consequently, the present invention not only reduces the difficulty in testing new or changed hardware and software during system integration and verification, but it also reduces the time required for doing so.

Although preferred embodiment s) of the method and system of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it will be understood that the present invention is not limited to the embodiment(s) disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit and scope of the present invention as set forth and defined by the following claims.

Claims

WHAT IS CLAIMED IS:

1. A method for resource tracking for a connection in a network, comprising the steps of: activating a connection tracing; ascertaining a first plurality of resources utilized for said connection; recording said first plurality of resources; ascertaining a second plurality of resources utilized for said connection, said first plurality of resources differing from said second plurality of resources by at least one resource; and recording said second plurality of resources.

2. The method according to Claim 1, further comprising the step of displaying recorded results of said connection tracing.

3. The method according to Claim 2, wherein said step of displaying recorded results of said connection tracing comprises the step of displaying said recorded results in a chronological, icon-based graphical display.

4. The method according to Claim 2, wherein said step of displaying recorded results of said connection tracing comprises the step of displaying said recorded results in a tree-like, nodal-based graphical display.

5. The method according to Claim 4, wherein said tree-like, nodal-based graphical display may be expanded and collapsed in order to alter the amount of resource detail provided thereby.

6. The method according to Claim 1 , wherein said step of recording said first plurality of resources and said step of recording said second plurality of resources occur responsive to said step of activating a connection tracing.

7. The method according to Claim 1, further comprising a step of initiating a connection by establishing a call connection from a mobile terminal.

8. The method according to Claim 1, further comprising a step of initiating a connection by establishing said connection from a network node for the purpose of testing said network.

9. The method according to Claim 1, wherein said step of activating a connection tracing comprises the step of activating said connection tracing responsive to a command issued from a network node.

10. The method according to Claim 1, wherein said step of activating a connection tracing comprises the step of activating said connection tracing responsive to a command or code embedded in a call origination request.

11. The method according to Claim 1 , wherein said step of recording said first plurality of resources comprises the step of storing in a memory of a node, said node including at least one of said first plurality of resources.

12. The method according to Claim 1 , wherein said step of recording said first plurality of resources comprises the step of adding an identifier corresponding to at least one of said first plurality of resources to a connection-related message.

13. The method according to Claim 1 , wherein said step of recording said first plurality of resources comprises the step of storing said first plurality of resources in a control node of said network, said network comprised of a wireless network.

14. The method according to Claim 1 , wherein said step of recording said second plurality of resources comprises the step of recording only one or more differences between said first and second plurality of resources.

15. The method according to Claim 14, wherein said one or more differences comprise at least one of an addition of a resource, a deletion of a resource, and an exchange of resources.

16. A method for dynamic call tracing of a call connection in a network, comprising the steps of: activating a connection path tracking of a connection path associated with said call connection; ascertaining a plurality of resources along said connection path; and wherein said connection path tracking detects at least one resource change from said plurality of resources during said call connection.

17. The method according to Claim 16, wherein said at least one resource change comprises at least one of an addition of a resource, a deletion of a resource, and an exchange of resources.

18. The method according to Claim 16, wherein said connection path tracking continuously records changes to said plurality of resources.

19. A node in a network that is capable of dynamic resource tracing for a connection, comprising: at least one port; a processor; a memory, said memory operatively connected to said processor; at least one logic module, said at least one logic module inteoelated with at least one of said processor and said memory, said at least one logic module adapted to cause said processor to: activate resource tracking for a connection; determine a plurality of resources utilized in the node for said connection; monitor said connection for changes to said plurality of resources; and record said changes to said plurality of resources.

20. The node according to Claim 19, wherein said network is comprised of a wireless network, said port comprises an antenna, and the node is comprised of a radio base station.

21. The node according to Claim 19, wherein said network is comprised of a wireless network, said port comprises a network adapter device, and the node is comprised of a radio network controller.

22. The node according to Claim 19, wherein said plurality of resources comprise at least one of a Packet Data Router (PDR), a Common Channel (CC), a Regional Radio Connection (RRC), a Signaling Connection, a User Data Connection, and a traffic connection identity.

23. The node according to Claim 19, wherein said at least one logic module comprises a trigger mechanism for detecting changes to said plurality of resources.

24. The node according to Claim 19, wherein said at least one logic module is further adapted to cause said processor to: store said changes to said plurality of resources in said memory when recording said changes to said plurality of resources.

25. The node according to Claim 19, wherein said at least one logic module is further adapted to cause said processor to: transmit to another node said changes to said plurality of resources when recording said changes to said plurality of resources.

26. An electronically-accessible data structure for organizing resource utilization information for a connection, comprising: an identifier of said connection; a plurality of entries, each of said plurality of entries including a resource indicator and an associated time stamp; and wherein said data structure is configured to facilitate display of said plurality of entries by a data processor for visual analysis.

27. The electronically-accessible data structure according to Claim 26, wherein said associated time stamp reflects when a resource cooesponding to said resource indicator becomes utilized.

28. The electronically- accessible data structure according to Claim 26, wherein said plurality of entries are configured chronologically and said each of said plurality of entries includes a network node indicator.

29. The electronically-accessible data structure according to Claim 26, wherein said plurality of entries are configured by network node.

30. A method for tracking resources utilized in a connection in a wireless network system, comprising the steps of: activating a resource tracking for said connection responsive to a predetermined condition; ascertaining a plurality of resources utilized for said connection in a plurality of nodes; recording said plurality of resources; detecting a change to said plurality of resources; recording said change; and wherein said steps of detecting a change and recording said change are performed responsive to said step of activating a resource tracking.

31. The method according to Claim 30, wherein said predetermined condition comprises at least one of reception of a resource tracking command and detection of a predetermined mobile terminal identification associated with said connection.

32. The method according to Claim 30, wherein said step of detecting a change comprises at least one of the following steps: detecting that one of said plurality of resources has been deleted; detecting that a new resource had been added to said plurality of resources; and detecting that one of said plurality of resources has been exchanged for a new resource.

33. The method according to Claim 30, wherein said step of recording said change comprises at least one of the following steps: storing said change in a memory of a node in which said change occurred; and transmitting said change to a node in which said change did not occur.

34. The method according to Claim 30, further comprising the steps of: detecting termination of said connection; displaying resource tracking results as a chronological, icon-based graphical display or a tree-like, nodal-based graphical display.

35. The method according to Claim 34, further comprising at least one of the following steps: expanding said tree-like, nodal-based graphical display; and collapsing said tree-like, nodal-based graphical display.

36. A node in a wireless network system that is capable of resource tracking for a connection, comprising: at least one port; a processor; a memory, said memory operatively connected to said processor; at least one logic module, said at least one logic module interrelated with at least one of said processor and said memory, said at least one logic module adapted to cause said processor to: activate resource tracking for a connection; and record changes to resources utilized for said connection during substantially an entire life of said connection.

37. A resource allocation viewer for a communications network, comprising: means for receiving a resource tracking data structure cooesponding to a connection established in said communications network, said resource tracking data structure including a plurality of nodes and a plurality of resources; means for extracting said plurality of nodes and said plurality of resources from said resource tracking data structure; and display means for displaying said plurality of nodes and said plurality of resources in graphical format.

38. The resource allocation viewer according to Claim 37, wherein said graphical format comprises at least one of a chronological, icon-based display and a tree-like, nodal-based display.

39. The resource allocation viewer according to Claim 38, further comprising means for collapsing and expanding said tree-like, nodal-based display responsive to user input.