Data is commonly transmitted over telecommunications networks such as 2G and 3G networks (i.e., 2nd and 3rd Generation wireless communication networks). Although various ways of analyzing data transmitted over such networks exist today, new and better ways to analyze data are always being sought.
Illustrative embodiments of the invention are illustrated in the drawings, in which:
As a preliminary manner, it is noted that, in the following description, like reference numbers appearing in different drawing figures refer to like elements/features. Often, therefore, like elements/features that appear in different drawing figures will not be described in detail with respect to each of the drawing figures.
The method 100 begins with the receipt of data carried by a plurality of data tributaries (at block 102). As the data is received, a stored mapping of data tributaries to one or more tributary sets is accessed, and common data tags are assigned to the data carried by ones of the data tributaries mapped to common ones of the one or more tributary sets (at block 104). The data is then filtered based on the common data tags (at block 106); the filtered data is analyzed (at block 108); and a result of the analysis is output (at block 110).
In one embodiment, the system 200 may be a 3G system, wherein the network controller 202 is a Radio Network Controller (RNC), the network base stations 204, 206 are Node B's (cell phone towers), and the primary data link is an lub link.
One possible physical implementation of the lub link is via a set of four STM-1 or OC-3 optical fibers, each having a data transmission rate of 155.52 Megabits/second (Mbits/sec). Each STM-1 fiber may be internally configured to carry 84 T1 data tributaries or 63 E1 data tributaries, for a total lub capacity of 336 T1's or 252 E1's.
Each of the T1 or E1 data tributaries may carry ATM data, including both signaling information and user data (such as voice, internet or video data).
In another embodiment, the system 200 may be a 2G system, wherein the network controller 202 is a Base Station Controller (BSC), the network base stations 204, 206 are Base Transceiver Stations (BTS's), and the primary data link is an A-bis link.
The network analyzer 216 also comprises a stored mapping of data tributaries to one or more tributary sets 304. The data tagger 306 is configured to i) access the stored mapping of data tributaries to one or more tributary sets 302, and ii) assign common data tags to the data carried by ones of the data tributaries that are mapped to common ones of the one or more tributary sets. Thus, for example, the data carried by all of the data tributaries mapped to a first tributary set would be assigned a first tag, and the data carried by all of the data tributaries mapped to a second tributary set would be assigned a second tag. In one embodiment, all of the data tributaries provisioned to a particular network base station (204 or 206) are mapped to a common tributary set, and the data tributaries provisioned to different network base stations 204, 206 are mapped to different tributary sets.
A data filter 308 is configured to filter data based on the data tags that are assigned by the data tagger 306. In this manner, data items may be filtered (or grouped) based on the commonality of their data tags.
Optionally, a framer 310 may be configured to i) receive tagged data from the data tagger 306, ii) delineate ATM cells in the tagged data, and iii) provide the tagged data of the delineated ATM cells to the data filter 308.
A data analysis unit 312 is configured to analyze the filtered data and output a result of the analysis (e.g., to a user or network controller). In one embodiment, the data analysis unit 312 may be configured to generate a report that identifies an item of the filtered data as being associated with a particular tributary set (e.g., a report of data items transmitted to or from a particular one of the network base stations 204, 206, such as a call or data trace report). In another embodiment, the data analysis unit 312 may be configured to generate a report that includes statistics by tributary set (e.g., statistics for one or more of the network base stations 204, 206, such as packet count, CRC error count, or utilization).
The network analyzer 216 is useful in that it enables data to be analyzed in useful groupings, such as groupings by network base station 204, 206. In the context of a call or data trace, for example, the network analyzer 216 enables the trace of calls or other data items carried on data tributaries that are assigned the same identifier by different network base stations 204, 206.
In one embodiment, the network analyzer 216 may comprise a graphical user interface (GUI) 314 that is configured to receive user input for mapping the data tributaries to the one or more tributary sets. See,
As shown in
After selecting a number of data tributaries via the bingo card 402, a user may graphically click an “Add” button 404 or “Delete” button 406, to add or delete the selected data tributaries to a particular tributary set selected in the window 408.
As shown in
Although the network analyzer 216 is shown in