[go: up one dir, main page]

WO1999023849A1 - Systeme et procede d'analyse de fichiers-journaux mobiles - Google Patents

Systeme et procede d'analyse de fichiers-journaux mobiles Download PDF

Info

Publication number
WO1999023849A1
WO1999023849A1 PCT/US1998/022767 US9822767W WO9923849A1 WO 1999023849 A1 WO1999023849 A1 WO 1999023849A1 US 9822767 W US9822767 W US 9822767W WO 9923849 A1 WO9923849 A1 WO 9923849A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile station
determining whether
base stations
message
messages
Prior art date
Application number
PCT/US1998/022767
Other languages
English (en)
Inventor
Raghu Challa
Parag A. Agashe
Samir S. Soliman
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to AU12816/99A priority Critical patent/AU1281699A/en
Publication of WO1999023849A1 publication Critical patent/WO1999023849A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements

Definitions

  • the present invention relates generally to the field of telecommunications, and more specifically to a system and method for enhancing analysis of mobile log files used by field and systems engineers to determine the network performance of a wireless communication system.
  • Test mobile stations are for the most part the same as regular mobile stations, except that they are connected to a computer, such as a laptop computer.
  • the connection with the laptop enables all over-the-air messages transmitted between the test mobile station and the base stations to be recorded.
  • the test mobile stations transmit these signals to the laptop at a very high rate.
  • the laptop queues the messages and quickly stores them on a hard drive in a log file, for example in an ASCII format.
  • ASCII log files are vast in size, making it extremely difficult for a systems engineer to decipher useful information from them.
  • a simple message like the System Parameters message sent by a base station in a CDMA cellular system is displayed in 15-20 lines.
  • the present invention is a performance analysis tool that analyzes the over-the-air messages transmitted between a test mobile station and one or more base stations.
  • the analysis tool views a mobile log file, generated by a specialized laptop computer (called a Mobile Diagnostic Monitor), containing these messages.
  • Trigger messages the analysis tool transitions between different states.
  • a series of state transitions comprise a "case.”
  • a case is defined as a series of messages seen in the log file which culminates in a critical event, including call-related successes and failures and other non-call specific failure mechanisms (e.g., those defined in the standard IS-95-A for cellular systems and those defined in the standard JST-008 for PCS systems).
  • the analysis tool of the present invention can operate in either of two different embodiments.
  • the first embodiment assumes perfect logging.
  • the second embodiment is a robust mode.
  • the analysis tool accounts for the fact that often the mobile station transmits messages (notably trigger messages) to the mobile diagnostic monitor faster than the monitor can save these messages, causing a situation where the log file is missing messages even though these messages were actually transmitted.
  • the perfect logging mode embodiment and the robust mode embodiment differ in that the robust mode permits additional state transitions, based on the detection of trigger messages in predetermined states, that are not permitted in the perfect logging mode embodiment.
  • state transitions can be normal or abnormal.
  • a normal state transition indicates that the detected trigger message is an appropriate message that either the mobile station is expecting to receive from the base station, or the base station is expecting to receive from the mobile station.
  • the analysis tool emulates the normal functions of the mobile station, in order to recreate the states of the mobile station. This can include maintaining timers and counters. Timers are used to count time periods during which pre-determined events must occur, whereas counters count the number of times pre-determined events must occur. When timers "time out” or counters "count out,” the mobile station indicates a failure condition. The analysis tool also maintains these failure conditions upon viewing the occurrence of the trigger messages and their time stamps in the log file.
  • An abnormal transition occurs when detection of a trigger message is not expected in a state. Abnormal transitions are handled by ignoring them if they are considered nonconsequential to maintaining valid communications, or determining their causes if they are considered consequential. Notably, if a trigger message invokes a state transition between any initial state (including the first two states) and the first two states, the state transition is always considered consequential and is diagnosed.
  • the analysis tool views a variety of information from the log file to diagnose the problem, including both trigger and non-trigger messages, time stamps, time outs, count outs, pilots, signal strengths, received power and multipath conditions. Diagnoses involve an integration of information available from the log files, the wireless communication standards of the system, and knowledge available only to an experienced systems engineer.
  • the diagnoses result in outputs indicating the failures found.
  • the analysis tool provides an output of its analysis.
  • One type of output is a case study, where the trigger messages (including relevant information about each of them) and diagnosis outputs are provided.
  • Other important outputs include statistics that may reveal problems associated with detections of neighbor lists, handoff distributions, handoff setup time, call setup time, pilot acquisition time, multipath, jumping to hyperspace, etc.
  • FIG. 1 is illustrates the inventive mobile station environment
  • FIG. 2 is a flow chart illustrating the functions of the inventive performance analysis tool
  • FIG. 3 is a high level state diagram illustrating the substates of the first inventive state
  • FIG. 4 is a high level state diagram illustrating the inventive state transitions
  • FIG. 5 is a low level state diagram illustrating state transitions under perfect logging conditions
  • FIG. 6 is a low level state diagram illustrating robust state transitions
  • FIG. 7 is a low level state diagram illustrating a combination of figures 5 and 6 to provide a robust logging state diagram
  • FIG. 8 is a flow chart illustrating diagnose state transitions for a transition from state 1 back to state 1
  • FIG. 9 is a flow chart illustrating diagnose state transitions for a transition from state 2 to state 1;
  • FIG. 10 is a flow chart illustrating diagnose state transitions for a transition from state 2 to state 2;
  • FIG. 11 is a flow chart illustrating diagnose state transitions for a transition from state 3 to state 1;
  • FIG. 12 is a flow chart illustrating diagnose state transitions for a transition from state 3 to state 2;
  • FIG. 13 is a flow chart illustrating diagnose state transitions for a transition from state 4 to state 2;
  • HG. 14 is a flow chart illustrating diagnose state transitions for a transition from state 4 to state 1;
  • FIG. 15 is a flow chart illustrating diagnose state transitions for a transition from state 5 to state 1, as well as a transition from state 6 to state 1;
  • FIG. 16 is a flow chart illustrating diagnose state transitions for a transition from state 7 to state 1;
  • FIGs. 17A and 17B illustrate the diagnostic messages that the inventive analysis tool can output for cases
  • FIG. 18 illustrates the format used by the inventive analysis tool to output trigger messages for case studies
  • FIG. 19 illustrates sample case studies performed for two exemplary log files
  • FIGs. 20A-20D illustrate outputs of additional observations performed
  • FIG. 21 illustrates an implementation of the invention.
  • FIG. 1 illustrates a mobile station environment 100 used to explain the invention.
  • mobile station environment 100 is a Code Division Multiple Access (CDMA) cellular system.
  • Mobile station environment 100 includes base stations (BSs) 102, 104, cell coverage areas 106, 108 and mobile station (MS) 110.
  • BSs base stations
  • MS 110 is a test mobile station used by a field test engineer to determine whether communications is properly established and conducted in mobile station environment 100.
  • MS 110 is connected to a Mobile Diagnostic Monitor (MDM) 112.
  • MDM 112 logs over-the-air messages that are exchanged between MS 110 and BSs 102, 104 in an MS log file (hereinafter "log file").
  • log file an MS log file
  • MDM 112 is laptop-based tool developed by QUALCOMM Incorporated, although those skilled in the relevant arts will recognize that any comparable computer can perform a similar function.
  • the over-the-air messages correspond to the IS-95-A standard (TIA/EIA Interim Standard, "Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System", TIA/EIA/IS-95-A, May 1995).
  • IS-95-A is the digital CDMA standard for cellular systems in the United States and abroad.
  • the over-the-air messages correspond to the J-STD-008 standard. Both this standard and the IS-95-A standard are well known to those skilled in the relevant arts.
  • the log file contains a variety of information which can be used to characterize the performance of MS 110, the BSs 102, 104, and the system as a whole.
  • the log file is very useful to field test engineers not only during the deployment stage, when mobile station environment 100 is first deployed, but also during the subsequent optimization stage of the CDMA system, to optimize the performance of mobile station environment 100.
  • the log file can be a human-readable file, derived from a binary machine-readable file where the messages are initially stored, or instead can be a binary machine- readable file, itself. This will be recognized by those skilled in the art.
  • mobile station environment 100 is described as a CDMA cellular or a CDMA PCS system.
  • the mobile station environment represents any wireless communication system.
  • the wireless communication system can be a digital or an analog system.
  • Some examples include an AMPS system, a TDMA system, a GSM system, any future implementations of CDMA systems, or any other PCS or cellular systems (e.g., other than CDMA).
  • WLL wireless local loop
  • the inventive performance analysis tool is a performance analysis tool (hereinafter
  • analysis tool used to study mobile station environment 100 by analyzing the over-the-air messages stored in one or more log files.
  • the analysis tool can be any combination of hardware and software, including a hardware state machine.
  • the analysis tool comprises one or more "C" language programs running on a DOS operating system on a laptop personal computer, the same laptop that is running MDM 112.
  • C "C” language programs running on a DOS operating system on a laptop personal computer, the same laptop that is running MDM 112.
  • the present invention can be implemented using any known language running on any known operating system using any known type of type of computer.
  • FIG. 2 is a high-level flowchart that illustrates the functions of the analysis tool.
  • one or more log files e.g., Log_File_l, Log_File_2
  • log files are input to the analysis tool. These log files are preferably processed sequentially.
  • the log files are in an ASCII format.
  • step 204 the first log file, i.e., Log_File_l, is opened.
  • step 206 the analysis tool starts a new "case.”
  • a case is defined as a series of messages seen in the log file which culminates in a critical event, including call- related successes and failures and other non-call specific failure mechanisms (e.g., those defined in the standard IS-95-A for cellular systems and those defined in the standard JST-008 for PCS systems).
  • a case is the series of over-the-air messages seen after the end of a previous case until the culmination of a critical event, which have been exchanged between MS 110 and a base station, e.g., BS 102.
  • each case can denote a series of transitions between when MS 110 is powered-up, or enters a service area system, and when communications between MS 110 and the base station is effectively halted (either through a normal call termination or through a failure).
  • step 208 the over-the-air signaling messages are read, beginning with the first message of the first case of the first log file.
  • step 210 for each over- the-air message, the analysis tool performs state transitions. These state transitions are explained in detail below with reference to FIGs. 3-7. During these state transitions, the analysis tool collects relevant information and prints relevant over-the-air messages in output files as shown in step 212. These printouts are explained in detail below with reference to FIGs. 17A-20D.
  • Steps 214 and 220 are recursive decision steps to ensure that the processing is performed for each over-the-air message in each log file. From step 220, analysis is ended (in step 222) if the last log file is reached, or analysis continues (in step 204) if there are more unprocessed log files. Similarly, step 216 is a recursive decision step to ensure that the processing is performed for each new case.
  • step 218 a series of diagnostic algorithms are run to categorize each case, into one of several scenarios. These diagnostics are run when a transition to a low state occurs or, if no such low-state transition occurs, when the case ends. The diagnostic algorithms are explained in detail with respect to HGs. 8-16.
  • the diagnostic messages and relevant statistics are printed to output files. These output files are illustrated in FIGs. 17A-20D. 3.
  • CDMA time limits and constants The present invention makes wide use of CDMA time limits and constraints. Tables 1 and 2 contain such constraints as defined by the IS-95-A standard (for cellular systems). As will be recognized by those skilled in the art, the relevant time limits and constraints will depend upon the type of wireless communication system used, and hence the Usted time limits and constraints in no way limit the present invention.
  • Table 1 provides time limits, denoted as T nm or T n ⁇ (where n is an integer), with corresponding descriptions and values.
  • timers are set to these time limit values to indicate the occurrence of events.
  • T- ⁇ m is the maximum time that the mobile station waits for an acknowledgment, and is set to 0.4 seconds. Accordingly, a timer set to Ti will time out after 0.4 seconds.
  • the subscript "m” indicates that a time limit or constraint is for a mobile station, whereas the subscript "b" indicates a time limit or constraint is for a base station.
  • N ⁇ m is the maximum number of times that a mobile station transmits a message requiring an acknowledgment on the reverse traffic channel.
  • FIG. 1 illustrates two links between BS 102 and MS 110. These links are a forward link 114 and a reverse link 116. a. Forward link
  • Forward link 114 refers to the communication directed from BS 102 to MS 110. Communication over forward link 114 is over a pilot channel, a sync channel, a paging channel, and a forward traffic channel. i. Pilot channel
  • the pilot channel is transmitted at all times by BS 102 on each active forward CDMA channel.
  • the pilot channel is an unmodulated spread spectrum pseudo random (PN) signal that is used for synchronization by MS 110 operating within the coverage area 106 of BS 102.
  • PN spread spectrum pseudo random
  • the base stations are distinguished by a PN offset value chosen from a set of integers in the range of 0-512, with increments determined by the system setup.
  • the PN offset is used to delay a short code PN sequence to produce PN sequences that have good correlation properties and are used to uniquely identify the base stations. ii. Sync channel
  • the sync channel (hereinafter "SCH") is a channel used to provide time and frame synchronization to MS 110. Only one message, the SCH message, is sent on the SCH. iii. Paging channel
  • the paging channel (hereinafter "PCH") is a channel used to send control information to MS 110 if it is an unassigned mobile station area.
  • MS 110 is an unassigned mobile station area if it has not yet been assigned to a traffic channel.
  • PCH paging channel
  • the forward traffic channel (hereinafter “forward TCH”) is used for transmission of user and signaling information to MS 110 during a call.
  • the maximum number of forward TCHs that can be simultaneously supported by a given forward CDMA channel is 63 minus the number of PCHs and
  • Reverse link Reverse link 116 is the communication directed from MS 110 to BS
  • Communication over the reverse link is over an access channels and a reverse traffic channel.
  • the access channel (hereinafter "ACH") is used by MS 110 to initiate communication with BS 102 and to respond to PCH messages.
  • An ACH transmission is a spread-spectrum signal that is coded, interleaved, and modulated.
  • the ACH uses a random-access protocol.
  • ACH signals are uniquely identified by their long codes. ii. Reverse traffic channel
  • the reverse traffic channel (hereinafter “reverse TCH”) is similar to the forward TCH.
  • the reverse TCH is used for transmission of user and signaling information to BS 102 during a call.
  • the analysis tool of the present invention uses state analysis to analyze MS environment 100.
  • FIGs. 3 and 4 are high level state diagrams used to illustrate the state analysis.
  • the state transitions are triggered by the viewing of recorded over-the-air messages in the log files. Specifically, the state transitions are performed for each individual case for each log file. When the analysis tool is in a given state, certain messages viewed in the log file will cause the tool to transition to different transition states. After each state transition, the analysis tool collects important information regarding the states of MS 110, BS 102 (assuming MS 110 is in cell coverage area 106 of BS 102), and mobile station environment 100 in general. It is important to note that these states of the inventive analysis tool correspond to modes of MS 110, itself. Therefore, the analysis tool states are in actuality analysis states corresponding to the mode of MS 110.
  • column A shows the trigger messages that invoke state transitions for the analysis tool. These trigger messages are transmitted between MS 110 and BS 102. For convenience, arrows are used to indicate the direction of these messages.
  • Column B shows the transition states of the analysis tool.
  • Column C shows certain counters and timers used to detect failures in each of the transition states. As noted, the counters and timers respectively "count out” or “time out” when counted and timed events are not satisfied within pre-defined constraints. a. State 0
  • FIG. 4 begins with the analysis tool in state 0. This is the step where MS 110 is initially powered up, or every time the mobile station ends a call in or is brought into cell coverage area 106 of BS 102. b. State 1
  • FIG. 3 is a detailed view of state 1.
  • State 1 itself, comprises four substates: system determination substate 302, pilot channel acquisition substate 304, SCH acquisition (or SCH) substate 306 and idle substate 308.
  • FIG. 3 begins with the system determination substate 302. During system determination substate 302, MS 110 selects which cellular system
  • pilot acquisition substate 304 After system determination is performed, the pilot acquisition substate 304 is entered.
  • MS 110 attempts to acquire the strongest pilot signal it is receiving from neighboring base stations. If MS 110 is in cell coverage area 106 of BS 102, MS 110 sequentially runs through a list of prestored PNs (pseudorandom pilot signals), to find a match with the PN transmitted from BS 102. If the pilot channel is acquired within T2 Qm (see Table 1), then the
  • SCH acquisition substate 306 is entered, where the SCH is opened for communications.
  • MS 110 awaits an SCH messages on the SCH to obtain configuration and timing information for the CDMA system. This information is required for a transition to idle substate 308, where the PCH is acquired. However, if a valid SCH message is not received in T21 m , indicating an error condition, then a transition back to system determination substate 302 occurs. As noted, the SCH message causes a transition from SCH substate
  • the SCH message is a trigger between substates 306 and 308 of MS
  • FIG. 4 shows state 1 of the analysis tool as a combination of the four substates 302-308 of MS 110.
  • SCH message 408 (for the case being analyzed) is read from the log file, the analysis tool transitions from the SCH substate to the idle substate within state 1.
  • MS 110 has acquired the PCH and receives communications from BS 102 on the PCH.
  • the Tg Qm timer is maintained. If a valid PCH message is not received within T ⁇ Q ⁇ then the analysis tool returns to the system determination substate.
  • MS 110 can transmit communications on the reverse link to BS 102 over an opened ACH.
  • the messages are typically transmitted using access probes. As recognized by those skilled in the art, access probes are messages that begin as weak signals and become greater in strength, until they are heard by the receiver, which is in this case BS 102. Access probes are used to conserve the energy of MS 110 and to reduce interference in the system.
  • the Origination message is a message indicating MS 110 desires to originate a call.
  • the Page Response message is a message by MS 110 indicating its response to an incoming call (i.e., a call terminating at MS 110, which is also known as a terminating call).
  • the Registration message is a message by MS 110 indicating that it desires to register in the current CDMA system.
  • MS 110 awaits a Base Station Acknowledgment
  • the Base Station Ack Order message on the PCH is a confirmation message indicating that BS 102 has heard the Origination message access probes, Page Response message access probes, or Registration message access probes sent by MS 110.
  • the counter max_probes After the first message probe is sent in the idle substate of state 1, i.e., as soon as access state 2 is entered, the counter max_probes begins maintaining a count of the number of access probes transmitted. If the number of access probes transmitted exceeds max_probes (which is defined by the IS-95-A standard), then a failure condition is indicated.
  • the T Qm timer is also maintained in access state 2, timing out if a valid PCH message is not received within T ⁇ Qm seconds.
  • the ⁇ Qm timeout is always used to determine whether the PCH is good, meaning that there has not been any loss (or fade) in signal.
  • a T ⁇ Qm timeout indicates a failure condition.
  • State 3 When a valid Base Station Ack Order message 412 acknowledging the access probes is received by MS 110 over the PCH, then access state 3 (a second access state) is entered, i.e., when the access probe is for call origination or call termination and indicates that MS 110 is waiting for a Channel Assignment message. If MS 110 is in the registration procedure (i.e., it had sent out a
  • MS 110 is already registered at this point.
  • the T ⁇ Q ⁇ n timer is also maintained in access state 3, timing out if a valid PCH message is not received within T ⁇ Qm seconds.
  • the T ⁇ Qm timeout is always used to determine whether the PCH is good.
  • a T ⁇ Qm timeout indicates a failure condition.
  • MS 110 awaits a Channel Assignment message 414 on the PCH from BS 102.
  • the Channel Assignment message 414 is a message containing the frequency and code channel on which a user using MS 110 can communicate.
  • the frequency and code channels identify and open the forward TCH from BS 102 to MS 110.
  • the T 42m timer is maintained. If the Channel Assignment message 414 is not received within T42 m seconds from the time the Base Station Ack Order message 412 is received, then a failure condition is indicted. e. State 4 Once BS 102 sends the Channel Assignment message 414 and it is viewed in the log file, a transition to state 4 occurs. State 4 is the jump to the
  • MS 110 determines whether the forward TCH is set up properly, and once this determination is made, MS 110 sets up the reverse
  • TCH This is performed by way of receiving a forward link preamble, sending a reverse link preamble, and maintaining timers.
  • MS 110 maintains two timers in jump to TCH state 4.
  • the first timer is T ⁇ Qm . This is the maximum time given for N ⁇ m consecutive valid null data frames to be received on the forward TCH from BS 102. These forward TCH null data frames comprise the forward link preamble. If the T ⁇ Qm timer expires, a failure condition is indicated. However, if this test is passed, MS 110 then sets up the reverse TCH by sending out the reverse link preamble on the reverse TCH.
  • MS 110 also maintains the timer. This is the maximum time permitted for a Base Station Ack Order message 416 from BS 102 over the forward TCH, acknowledging that the null data frames (comprising the reverse link preamble) transmitted from MS 110 have been received by BS 102. Time out of timer T ⁇ - j ⁇ indicates a failure condition. f. States 5, 6 and 7 Once BS 102 sends the Base Station Ack Order message 416 on the
  • TCH a transition to state 5 occurs, which is called the first Base Station Ack Order message on the TCH state. Transition to state 5 indicates that both the forward and reverse TCHs have been successfully initialized, for full duplex communications . Any TCH messages received after state 5 forces a transition to state 6, which is the TCH messaging state. During this state, full duplex communications over the forward and reverse TCHs occurs between MS 110 and BS 102. State 6 transitions to state 7 when either party (either the MS 110 or the BS 102) transmits to the other a Release Order message 420. State 7, referred to as the call ends state, is the last state.
  • the TCHs (both forward and reverse links) are monitored via the T 5m' T 52m' ⁇ 55 timers anc * * ⁇ e N ⁇ m counter. If any of these timers "time out” or these counters "count out,” then a failure conditions is indicated. Expiration of the T- m timer indicates that there is a fade in the signal and the forward TCH is effectively lost. For a call termination, expiration of the Tc2 m timer indicates that MS 110 did not receive an Alert With
  • FIGs. 5-7 illustrate the state diagrams for the present invention at a lower level.
  • the level A diagram of FIG. 5, the level B diagram of FIG. 6, and the level C diagram of FIG. 7 provide a more detailed view of the inventive state transitions, particularly during abnormal call conditions.
  • a. State Transitions assuming perfect logging The level A state diagram of FIG. 5 illustrates basic state transitions between states 1-7 under the assumption that logging is perfect. Perfect logging means that every over-the-air message transmitted between MS 110 and BS 102 is reproduced in its entirety in the log file.
  • the analysis tool transitions between the states depending upon whether certain trigger messages, transmitted between MS 110 and BS 102, are detected in the log file.
  • Table 3 illustrates abbreviations for these trigger messages. These abbreviated messages are used in FIGs. 5-7.
  • the letters a, e represents detection of an Origination message, a Page Response message, or a Registration message (transmitted by way of access probes) in the log file.
  • the letter b represents the detection of an SCH message.
  • the letter c represents detection of a Base Station Ack Order message on the PCH.
  • the letter d represents detection of a Channel Assignment message in the log file.
  • the letter f represents detection of a first Base Station Ack Order message on the TCH.
  • the letter g represents detection of TCH messages, other than the first Base Station Ack Order message, on the TCH.
  • the letter h represents detection of a Release Order message, either from MS 110 to BS 102 or from BS 102 to MS 110.
  • Table 3 illustrates abbreviations for these trigger messages. These abbreviated messages are used in FIGs. 5-7.
  • the letters a, e represents detection
  • Table 4 explains in detail the state transitions of the level A state diagram of FIG. 5.
  • the state transitions of FIG. 5 are those state transitions for cases where logging is perfect.
  • Table 4 also includes the state transitions of the level B state diagram of FIG. 6 and the level C state diagram of FIG. 7.
  • Diagnose message indicates that the paging channel is lost due to (1) loss of paging channel in the idle substate (T3 m ), or (2) loss of acquisition after sleep (slotted mode), or (3) new system exit, or (4) a timing change substate problem, or (5) the phone could have been redirected to the analog system.
  • T3 m idle substate
  • slotd mode loss of acquisition after sleep
  • new system exit new system exit
  • a timing change substate problem or (5) the phone could have been redirected to the analog system.
  • Diagnose message State 2 indicates that the mobile station aborted the access attempt for one of the following reasons: (1) the mobile station sent the maximum number of access probes, or (2) if the current access attempt is a registration procedure, the base station could have sent a Registration Accepted message or a Rejected Order message, or (3) for call origination or call termination procedures, the base station could have sent a Release
  • the mobile station could have aborted the access attempt for one of the following reasons: (1) if the current access attempt is a registration procedure, the base station could have sent a Registration Accepted message or a Rejected Order message, or (2) for call origination or call termination procedures, the base station could have sent a Release
  • Diagnose message State 4 indicates that the mobile station could not successfully get onto the traffic channel.
  • Reasons for the message include: (1) the mobile station could have rejected the
  • Access Channel Order message because it is no longer in the access state, or (2) due to loss of the paging channel in the access state (T4 Qm ), or
  • Diagnose message State 7 indicates that the call ended with release orders.
  • One of the following scenarios is possible: (1) a normal release occurred with a mutual exchange of Release Order messages between the mobile station and the base station, or (2) a release state time out (T55 m ) occurred with the base station not sending a Release Order message in response to the one sent by the mobile station, or (3) the base station sent the first Release Order message, indicating in some cases a possible confusion at the base station end of call processing, or (4) a possible problem with mobile station when not it does not respond to the Release Order message from the base station.
  • T55 m release state time out
  • the over-the-air messages are continuously transmitted from MS 110 to MDM 112 during the communications between MS 110 and BS 102.
  • MS 110 has as its highest priority to keep the call up, i.e., to maintain communications with BS 102.
  • Logging of the over-the-air signaling messages is secondary. Therefore, if MS 110 is not capable of transmitting these over-the-air messages to MDM 112 as quickly as it is communicating with BS 102, then the over-the-air messages may not be transmitted to MDM 112.
  • MDM 112 After these over-the-air messages are received by MDM 112, it is possible that these messages are not stored in the log file as quickly as they are transmitted, causing a problem of overwriting of earlier messages. Again, this results in incomplete recordation of messages in the log file.
  • the present invention provides the level B state diagram of FIG. 6.
  • the level B state diagram improves the robustness of the state transitions by providing state transitions that do not actually exist in the real world.
  • FIG. 6 illustrates a state transition from state 2 to state 4 by a dotted line.
  • a state transition from state 4 to state 2 is acceptable, there is no acceptable state transition of the analysis tool from state 2 to state 4.
  • the present invention is able to detect that a transition from state 2 to state 4 has occurred despite missing portions from the log file.
  • d message (Channel Assignment message) is received when the analysis tool is in state 2 and has transitioned to state 4. This indicates that (1) BS 102 is sending the Channel Assignment message for no apparent reason, or (2) BS 102 did not send a Base Station Ack Order message on the PCH, or (3) that an insufficient logging problem has occurred where the Base Station Ack Order message has been sent, but has not been logged in the log file.
  • the embodiment of FIG. 6 assumes that an insufficient logging problem has occurred and permits the transition. The same reasoning applies if a d message is received when the analysis tool is in state
  • the analysis tool permits the state transition to maintain robustness to the insufficient logging problem. iii. f 15 , f 25 , f 35
  • FIG. 7 illustrates a level C state diagram.
  • the level C state diagram of FIG. 7 combines the state diagram that assumes perfect logging of FIG. 5 and the state transitions that are designed to take care of insufficient logging of FIG. 6 into a single state diagram. In other words, the level C state diagram of FIG. 7 is robust to insufficient logging. d.
  • the mobile station maintains timers to keep track of the various failure mechanisms.
  • the analysis tool has a corresponding set of timers to detect and keep track of the failure mechanisms in the log files.
  • the difference between the mobile station's timers and the analysis tool's timers lies in the way the analysis tool maintains its timers.
  • the tool has no concept of a real-time clock. Instead, the analysis tool uses the time-stamp information provided with each message in the log file. Since there is nothing like a "running clock" in the mobile log files, the tool cannot increment or decrement its timers. It uses the end events to compute the effective values of the timers and determines if any of the timers have expired.
  • the standard states that the mobile station should wait for the Channel Assignment message for T42 m seconds, after receiving the Base Station Ack Order on the
  • the inventive analysis tool defines the time of receipt of the Base Station Ack Order message as t_3 and the time of the event indicating the receipt/non-receipt of the Channel Assignment message as t_4.
  • the time difference between the two events, delta_t t_4 - t_3, is compared with the constant T 2 m as defined by the standard. If delta_t is less than T42 m , then the tool declares that the Channel
  • a diagnostic state transition is a state transition from any state to either state 1 or access state 2.
  • the diagnose state transitions include Since state transitions to state 1 and state 2 are considered serious errors, the analysis tool uses the information collected during the previous state transitions to perform a detailed analysis for each diagnostic state transition.
  • FIG. 8-16 i. Diagnose b ⁇
  • FIG. 8 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition b ⁇ made. This diagnosis occurs when an SCH message is received by MS 110 when it is the idle substate of state 1. In step 802, it is inquired why MS 110 has gone to the system determination substate of state 1 while monitoring the PCH.
  • step 804 it is determined whether a Global Service Redirection message has been received. This message is sent by BS 102 to MS 110 to ask
  • MS 110 to go to another system, such as a different CDMA system or another type of system (e.g., AMPS) altogether. Accordingly, if a Global Service
  • Redirection message is received, it is logical to assume that the PCH has been dropped to go to another system. If this is the case, then in step 806, a diagnostic message is printed indicating the condition.
  • FIGs. 17A and 17B illustrate the diagnostic messages that the analysis tool can output. As indicated in step 806, diagnostic message 8.g is printed. In FIG. 17B, 8.g is line 1787, which states "Phone redirected to Analog in Paging Channel.” Obviously, this message is for a switch to an analog system, and other messages are permissible.
  • t_exit and t_p are times indicated by time stamps.
  • the value t_p is the time that the last valid PCH message was seen in the log file.
  • the value t_exit is the time when MS 110 went to the system determination substate. The mobile log indicates that MS 110 is in system determination by displaying that the
  • MS 110 is using a pilot PN (pseudo random noise) signal with offset 0.
  • the difference value t_exit-t_p indicates the time MS 110 was on the PCH without showing valid PCH messages. If the value is greater than T3 Qm , then MS 110 has abandoned the PCH for some reason. In other words, the phone waited for T Qm seconds before bailing out of the PCH.
  • step 810 it is desired to determine the reason why MS 110 abandoned the PCH. Specifically, it is determined whether Ec/Io is above -15 dB and there is still no valid PCH message (which must be the case at this step). Ec/Io is the received bit energy to interferences ratio. A valid demodulable pilot is preferably above -15 dB. If Ec/Io is below -15 dB, it is unlikely that MS 110 can demodulate a signal on the PCH. If in step 810 Ec/Io is greater than -15 dB, indicating a good signal to noise ratio, then control passes to step 812.
  • step 812 diagnostic message a of FIG. 17A (line 1711) is printed. If Ec/Io is not greater than -15 dB, as shown in step 814, then the loss of the PCH was not due to a poor pilot signal. In this case, a loss of PCH in the idle substate of state 1 is determined after a T Qm time out. As indicated in step 814, here again diagnostic message l.a of FIG. 17A (line 1711) is printed.
  • step 816 it is determined whether MS 110 slept just before the bail out occurred.
  • MS 110 goes to "sleep" (i.e., reverts to the slotted mode). During such conditions, MS 110 is in an effective state of hibernation where it is not listening to incoming messages. MS 110 is in such a sleep condition in order to conserve energy.
  • MS 110 and the BS 102 are always aware of when MS 110 will be in a sleep condition, so that BS 102 can schedule the MS 110 specific messages and times when MS 110 is awake.
  • step 816 If in step 816 it is determined that MS 110 was asleep just before the bailout of the PCH, then control passes to step 818.
  • step 818 it is determined that a "loss of acquisition after sleep" condition has occurred.
  • diagnostic message l.c of FIG. 17A line 1713 is printed, indicating that the PCH was dropped after sleep.
  • step 816 If it is determined in step 816 that MS 110 did not sleep just before exiting the PCH, then control is passed to step 820.
  • step 820 it is assumed that a new system exit has occurred. The following explains a new system exit.
  • MS 110 After MS 110 is powered up, it goes into the system determination substate 302, where the CDMA system is determined, followed by the pilot acquisition substate 304, where MS 110 sequentially runs through a list of prestored PNs, attempting to find a best pilot signal. After these earlier substates, which are known collectively as the system determination, MS 110 has acquired the pilot signal denoted by the PN value transmitted from BS 102.
  • BS 102 also transmits to MS 110 a Neighbor List message.
  • the Neighbor List message includes the PN values of all the base stations neighboring with BS 102.
  • the Neighbor List message also contains configuration information for the pilot signals (PN values) of these neighboring base stations, which includes frequency information pertaining to these pilot signals.
  • PN values pilot signals
  • MS 110 travels outside of the cell coverage area 106 of BS 102, under normal circumstances a handoff occurs with another base station. In other words, MS 110 attempts to acquire the pilot signal of the other base station, which is stronger than the pilot signal received from BS 102.
  • MS 110 normally uses only the PN sequences received from BS 102 in the previous Neighbor List message. This reduces the efforts of MS 110 in attempting to acquire the pilot signal of the new base station.
  • MS 110 will pick up a pilot signal that it had not received in the Neighbor List message. Under this circumstance, MS 110 does a new system exit, where MS 110 will go back to the system determination and attempt to acquire the unrecognized pilot signal by sequentially running through all of the prestored PN sequences. In other words, during a new system exit, MS 110 will act as though it were just powered up. As indicated in step 820, diagnostic message l.c of FIG. 17A (line 1713) is printed.
  • step 822 After each of steps 812 (timing change substate detection), 814 (loss of the PCH in the idle substate detection), 818 (loss of acquisition after sleep detection) or 820 (new system exit detection), control passes automatically to 822. After each of these steps, it is possible that a new pilot signal has been acquired by MS 110. Therefore, in step 822, it is determined whether the new pilot signal acquired by MS 110 is in the Neighbor List message of the old pilot signal previously acquired. If this condition is true, it indicates that one or more of the base stations have insufficient information with respect to their neighboring base stations. The analysis tool indicates neighbor list problems in its output, as discussed with respect to FIG. 18 below. ⁇ . Diagnose
  • FIG. 9 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition is made. This diagnosis occurs when an SCH message is received by MS 110 when it is in access state 2. In step 902, it is inquired why MS 110 has gone to system determination while MS 110 is sending an Origination message, a Page Response message, or a Registration message via access probes to BS 102 on the ACH.
  • step 904 it is determined whether the total number of access probes sent is approximately equal to max_probes.
  • Max_probes is the maximum number of access probes that can be sent as defined by the IS-95-A standard.
  • the reason step 904 determines whether the number of probes sent approximately (rather than exactly) equals max_probes is because the number of access probes actually sent may not have been recorded in the log file. This, again, is an example of the insufficient logging problem. Therefore, the number of access probes that are required to satisfy step 904 can be set based upon the prevalence of insufficient logging problems. If in step 904 the total number of access probes approximately equals max_probes, then control passes to step 906.
  • step 906 it is determined that MS 110 has exhausted the maximum number of access probes, and the forward and reverse links are checked for a potential problem.
  • an attempt is made to determine why the maximum number of access probes has been exhausted. This may have been caused by a problem with the reverse link, where BS 102 cannot hear MS 110. This may also have been caused by a problem with the forward link, where BS 102 hears MS 110 and transmits a Base Station Ack Order message on the PCH, but MS 110 cannot hear this message, or if both the links are bad.
  • diagnostic message 2.a of FIG. 17A (line 1721) is printed.
  • the Release Order message indicates that BS 102 does not have sufficient resources to support the call.
  • the Lock Until Power-Cycled Order message indicates to MS 110 that it is to lock and not transmit any other messages until further notification. This latter message is transmitted from BS 102 to MS 110 when BS 102 determines that MS 110 is malfunctioning, resulting in uncontrolled interference in the system.
  • a Service Redirection message is transmitted by BS 102 to MS 110 when BS 102 is redirecting the service to another base station. This may occur, for example, when BS 102 has insufficient resources to support MS 110.
  • a Registration Reject Order message occurs when BS 102 indicates to MS 110 that it is rejecting the attempt by MS 110 to register in its system.
  • step 922 MS 110 and the analysis tool transition back to the system determination substate. As indicated in step 922, diagnostic messages 2.b, 2.e, 8.e, 8.f, or 7.b of FIG. 17A and 17B (lines 1722, 1725, 1785, 1786, or 1772) are printed, respectively. If none of the messages of step 908 are received, then control passes to step 910. In step 910, it is determined whether MS 110 received a Reorder
  • step 910 the analysis tool goes to the idle substate of state 1.
  • MS 110 is in the same condition as for diagnose b- , i.e., in the idle substate of state 1, where an SCH message has been received from BS 102. Therefore, control passes to step 920, where the diagnose state transition for b ⁇ of FIG. 8 is repeated.
  • step 914 it is determined (1) whether MS 110 did an idle handoff or (2) if within a period of T42 m seconds following the transmission of the last access probe, MS 110 returned to the system determination substate.
  • step 918 it is determined that BS 102 sent the Base
  • step 918 diagnostic message 3.b of FIG. 17A (line 1732) is printed. From step 918, control passes to step 920 and diagnose b- ⁇ is repeated, for the same reasons as noted for step 912.
  • step 914 If in step 914 it is determined that MS 110 did an idle handoff or it went to system determination within T42 m seconds, then control passes to step 916.
  • step 916 it is determined whether the PCH was lost in access state 2 and a T Qm time out has occurred. The analysis tool transitions to the idle substate of state 1. As indicated in step 916, diagnostic message b of
  • FIG. 17A (line 1712) is printed. From step 916, control passes to step 920 and diagnose b-... is repeated, for the same reasons as noted for step 912. iii. Diagnose a 22
  • FIG. 10 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition a22 is made. This diagnosis occurs when an Origination message, a Page Response message or a Registration message access probe is transmitted from MS 110 to BS 102 over the ACH, when MS 110 is in access state 2. In step 1002, it is inquired why MS 110 is aborting the current access attempt and starting a new access attempt.
  • step 1004 it is determined whether MS 110 received a Reorder Order message, a Registration Accepted Order message, or an Intercept Order message from BS 102 on the PCH. If any of these messages were received, then control passes to step 1006. In step 1006, MS 110 ends the previous access attempt and transitions to the idle substate of state 1. As indicated in step 1006, diagnostic messages 2.c, 7.a, or 2.d of FIG. 17A and 17B (lines 1723, 1771, or 1724) are printed, respectively.
  • step 1008 it is determined whether the previous access attempt was an attempt at registration and the new access attempt is an Origination message or a Page Response message.
  • a call origination from MS 110 or a call termination at MS 110 are given priority over attempts at registering MS 110. Therefore, it is considered normal for MS 110 to abort an attempt at registration if MS 110 transmits an Origination message (to originate a call from MS 110) or MS 110 transmits a Page Response message (to respond to a call terminating at MS 110). Therefore, if the condition in step 1008 is true, control passes to step
  • step 1012 it is determined whether MS 110 lost the PCH during access state 2. This condition is satisfied if a T4 Qm time out occurred.
  • diagnostic message b of FIG. 17A (line 1712) is printed.
  • FIG. 11 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition bg j is made. This diagnosis occurs when an SCH message is received by MS 110 when it is in access state 3.
  • step 1102 it is inquired why MS 110 has gone to the system determination substate after getting the Base Station Ack Order message on the PCH.
  • the analysis tool transitions back to the system determination substate.
  • step 1106 MS 110 goes back to the system determination substate. As indicated in step 1106, diagnostic messages 2.b, 2.e, 8.e, 8.f, or 7.b of FIGs. 17A and 17B (lines 1722, 1725, 1785, 1786, or 1772) are printed, respectively.
  • step 1108 it is determined whether MS 110 received a Reorder Order message, a Registration Accepted Order message, or an
  • Intercept Order message from BS 102 on the PCH.
  • the analysis tool transitions back to the idle substate of state 1. If one of these messages was actually received in step 1108, then in step 1110 MS 110 goes to the idle substate of state 1.
  • diagnostic messages 2.c, 7.a, or 2.d of FIGs. 17A and 17B are printed.
  • step 1110 MS 110 is in the same condition as for diagnose b- , i.e., in the idle substate of state 1, where an SCH message has been received from BS 102. Therefore, control passes to step 1128, where the diagnose state transition for b ⁇ of FIG. 8 is repeated. If none of the messages of step 1108 are received, then control passes to step 1112. In step 1112, it is determined whether MS 110 did an idle handoff or whether MS 110 did not see any valid PCH messages for T4 Q seconds. Here, an attempt is made to determine why MS 110 bailed out of the PCH. If the condition in step 1112 is satisfied, then control passes to step
  • step 1114 it is determined whether the bail-out of the PCH occurred within T42 m seconds after MS 110 received the Base Station Ack Order message on the PCH message. If the condition in step 1114 is satisfied, i.e., a ⁇ 42m ⁇ me out d d not occur ' then control passes to step 1116. In step 1116, where it has already been determined that a T42 m time out did not occur, it is concluded that MS 110 lost the PCH in access state 3 and a T4 Qm time out occurred. The analysis tool transitions to the idle substate of state 1. As indicated in step 1116, diagnostic message l.b of FIG.
  • step 1114 If the condition in step 1114 is not satisfied, indicating that MS 110 bailed out of the PCH, but not within T42 m seconds after receiving a Base
  • step 1118 it is concluded that MS 110 was in access state 3, but did not receive a Channel Assignment message within T42 m seconds after the Base Station
  • Ack Order message on the PCH was received.
  • the analysis tool transitions to the idle substate of state 1.
  • diagnostic message 3.b of FIG. 17A (line 1732) is printed.
  • MS 110 is in the same condition as for a diagnose b ⁇ , i.e., in the idle substate of state 1, where an SCH message has been received from BS 102. Therefore, control passes to step 1128, where diagnose state transitions for b ⁇ of FIG. 8 are repeated. If in step 1112 an idle handoff did not occur and one or more valid
  • step 1120 it is desired to determine whether a 42 m time out occurred.
  • time stamps are used in order to determine this condition.
  • the value t_3 is the time stamp for when a
  • Base Station Ack Order message on the PCH is first received, i.e., the entry time of MS 110 into access state 3.
  • step 1118 it is determined that a T 2 m time out occurred. Namely, it is determined that a Channel Assignment message was not received within T42 m seconds after a Base Station Ack Order message on the PCH was received. Again, the analysis tool transitions to the idle substate of state 1, diagnostic message 3.b of FIG. 17A (line 1732) is printed, and control passes to step 1128, where diagnose state transitions for b ⁇ of
  • FIG. 8 are repeated.
  • step 1120 it is determined whether the value t_exit - t_p is between Tcn m seconds and
  • the value t_p is a time stamp of the last valid PCH message seen in the log file. Therefore, the value t_exit-t_p is the difference in time between when the last valid PCH message was seen in the log file and when the SCH message was seen in the log file (i.e., when MS 110 transitioned back to the system determination substate). Normally, when a Channel Assignment message is received, MS
  • MS 110 transitions to "jump to TCH" state 4, where MS 110 jumps to the TCH and begins maintaining imers. If Ng m valid null frames are received over the TCH from BS 102 within Tg Qm seconds, then MS 110 begins transmitting null frames to BS 102 in order to establish the reverse TCH. Subsequently, if MS 110 receives the Base Station Ack Order message on the TCH from BS 102 within ⁇ m seconds, then it jumps to state 5. It must be remembered that in step 1122, an SCH message has been received even though no T4 Qm time out or T42 m time out has occurred. Accordingly, the analysis tool determines that MS 110 was actually in jump to TCH state 4, and no Channel Assignment message was received because of an insufficient logging problem.
  • step 1122 If the condition in step 1122 is satisfied, then control passes to step
  • diagnostic message 3.a of FIG. 17A (line 1731) is printed.
  • step 1122 If the condition in step 1122 is not satisfied, it is assumed that the time between when the last valid PCH message was seen in the log file and when the SCH message was received is greater than T ⁇ seconds. Again, like in step 1126, it is determined that a Channel Assignment message was received but was not logged. Here, however, it is determined that the Base Station Ack Order message on the TCH did not occur within seconds after MS 110 jumped to the TCH. As indicated in step 1126, diagnostic message 3.c of FIG. 17A (line 1733) is printed. v. Diagnose e ⁇
  • FIG. 12 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition e ⁇ is made.
  • This diagnosis occurs when an Origination message, a Page Response message, or a Registration message access probe is transmitted from MS 110 to BS 102 over the ACH when MS 110 is in access state 3.
  • step 1202 it is inquired why MS 110 is starting a new access attempt after receiving the Base Station Ack Order message on the PCH message for the current access attempt. In other words, an attempt is made to determine why MS 110 is starting a new access attempt while awaiting a Channel Assignment message.
  • step 1204 If any one of these messages is received, meaning that the condition of step 1204 is satisfied, then control passes to step 1206.
  • step 1206 MS 110 ends the previous access attempt. A transition back to the idle substate of state 1 occurs.
  • diagnostic messages 2.c, 7.a, or 2.d of FIG. 17A and 17B are printed.
  • step 1204 If none of the messages of step 1204 is received by MS 110, then control passes to step 1208. In step 1208, it is determined whether either (1) MS 110 performed an idle hand-off, or (2) during the T4 2m timeout period
  • step 1208 If the condition in step 1208 is satisfied, then control passes to step
  • step 1210 it is determined that the PCH was lost in the access state 3 due to a valid T4 Qm time out.
  • the analysis tool transitions to the idle substate of state 1.
  • step 1212 it is determined that MS 110 failed to receive a Channel Assignment message within T42 m seconds after the Base Station
  • Ack Order message was received.
  • the analysis tool transitions to the idle substate of state 1.
  • diagnostic message 3.b of FIG. 17A (line 1732) is printed. vi. Diagnose e ⁇
  • FIG. 13 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition 6 2 is made. This diagnosis occurs when an Origination message, a Page Response message or a Registration message access probe is transmitted from MS 110 to BS 102 over the PCH when MS
  • step 1302 it is inquired why MS 110 is starting a new access attempt after receiving the Channel Assignment message for the current access attempt.
  • MS 110 transmits an Access Channel Order message to BS 102, rejecting the current Channel Assignment message.
  • step 1306 it is determined whether the Channel Assignment message was received ⁇ A 2m seconds after the Base Station Ack Order message on the PCH was received from BS 102. If this condition is satisfied, indicating that a T42 m timeout occurred, then control passes to step 1308.
  • step 1308 it is determined that the Channel Assignment message was received after a T42 m timeout occurred, meaning that the Channel
  • diagnostic message 3.b of FIG. 17A (line 1732) is printed. If the Channel Assignment message is not received 42 m seconds after the Base Station Ack Order message on the PCH is received, then control passes to step 1310. In step 1310, it is determined that MS 110 may have lost the PCH while in the access state, as determined by a T4 Q timeout. The analysis tool transitions back to the idle substate of state 1. y vii. Diagnose
  • FIG. 14 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition is made. This diagnosis occurs when an SCH message is received by MS 110 when it is in jump to TCH state 4. In step 1402, it is inquired why MS 110 has gone to system determination substate after receiving the Channel Assignment message for the current access attempt.
  • step 1404 it is determined whether MS 110 has transmitted an
  • step 1404 Access Channel Order message rejecting the Channel Assignment message. If the condition in step 1404 is not satisfied, control passes to step 1406.
  • step 1406 it is determined whether the value t_exit - t_p is between Tc Qm seconds and T[ ⁇ m seconds.
  • the value t_4 is the time stamp for when the Channel Assignment message is first received, i.e., the entry time of MS 110 into jump to TCH state 4.
  • the difference between t_exit and t_4 represents the time between when MS 110 entered jump to the TCH state 4 and the SCH message was received.
  • MS 110 received the Base Station Ack Order message on the TCH from BS 102 within Tc ⁇ m seconds, then MS 110 transitions to state 5 (the first Base
  • step 1406 If the condition in step 1406 is satisfied, then control passes to step 1406
  • step 1408 it is determined that a TCH initialization failure occurred, because N ⁇ m good frames were not seen in the log file within T5 Qm seconds after MS 110 jumped to the TCH.
  • diagnostic message 3.a of FIG. 17A (line 1731) is printed. If the condition in step 1406 is not satisfied, then control passes to step 1410.
  • step 1410 like in step 1408, it is determined that a TCH initialization failure occurred. In this step, however, the TCH initialization failure occurred because MS 110 did not receive a Base Station Ack Order message on the TCH before a seconds after MS 110 jumped to the TCH).
  • diagnostic message 3.c of FIG. 17A (line 1733) is printed.
  • step 1404 If MS 110 did transmit an Access Channel Order message rejecting the Channel Assignment message in step 1404, then control passes to step
  • step 1412 it is determined whether the Channel Assignment message was received T42 m seconds after the Base Station Ack Order message was received on the PCH.
  • step 1416 it is determined that MS 110 may have lost the PCH while in the access state, as determined by a T4 Qm timeout.
  • the analysis tool transitions back to the idle substate of state 1.
  • diagnostic message b of FIG. 17A (line 1712) is printed.
  • MS 110 is in the same condition as for diagnose b-.-,, i.e., in the idle substate of state 1, where an SCH message has been received from BS 102. Therefore, control passes to step 1420, where the diagnose state transition for b ⁇ of FIG. 8 is repeated.
  • step 1412 If the condition in step 1412 is not satisfied, then control passes to step 1418.
  • step 1418 it is determined that MS 110 did not receive a valid Channel Assignment message within T42 m seconds after it received the
  • FIG. 17A (line 1732) is printed.
  • step 1416 when MS 110 is in step 1418, it is in the idle substate of state 1 and has received an SCH message from BS 102. Accordingly, from step 1418, control passes to step 1420 and diagnose b jj is repeated. viii. Diagnose bci diagnose bg- j
  • FIG. 15 illustrates the flow chart used to make diagnostic decisions when the diagnose state transitions b ⁇ and b ⁇ are made. These diagnoses occur when an SCH message is received by MS 110 when it is in state 5 (the first Base Station Ack Order message on TCH state) or in state 6 (the TCH messaging state), respectively. In step 1502, it is inquired why the call was terminated through other than normal release mechanisms.
  • step 1504 it is determined whether MS 110 received either a Lock Until Power-Cycled Order message or an Analog Hand-Off Direction message.
  • MS 110 receives the Lock Until Power-Cycled Order message when BS 102 detects that MS 110 is expending unnecessary power, resulting in uncontrolled interference to the system.
  • An Analog Hand-Off Direction message can be received if MS 110 is a dual mode mobile station, where it can handle both CDMA and analog cellular services.
  • the Analog Hand-Off Direction message itself, indicates that MS 110 is to be handed-off from a CDMA system to an analog system. If either of the messages of step 1504 is received, then control passes to step 1506.
  • MS 110 transitions to the system determination substate, if a Lock Until Power-Cycled Order message was received, or alternatively MS 110 transitions to AMPS, if an Analog Hand-Off Direction message was received.
  • diagnostic messages 4.c or 8.d of FIG. 17A and 17B are printed.
  • step 1508 it is determined whether a T ⁇ m fade timeout occurred, by comparing the value t_exit-t_f with T ⁇ m .
  • t_exit is the time stamp for when MS 110 attempts to go to the system determination substate (i.e., when an SCH message is received).
  • t_f is the time stamp for when the last valid TCH message was received.
  • step 1510 the T ⁇ m timeout is taken to show that the call was dropped because of a fade timeout.
  • the fade timeout, or T ⁇ m timeout refers to the fade or loss of the forward TCH signal.
  • diagnostic message 4.a of FIG. 17B line 1741 is printed. If a Tc m timeout did not occur in step 1508, then control passes to step 1512.
  • step 1512 if the call is an incoming call, then it is determined whether a Tc2 m timeout occurred with no Alert With Information message received. This timeout is determined by comparing to the value t_exit-t_f. If the condition in step 1512 is satisfied, then control passes to step
  • step 1514 it is determined that the call was dropped (i.e., the TCH was lost) because of a waiting for order substate timeout. As indicated in step 1514, diagnostic message 4.b of FIG. 17B (line 1742) is printed.
  • step 1516 it is determined whether an N ⁇ m acknowledgment failure occurred.
  • N- ⁇ m acknowledgment failure occurs when MS 110 has transmitted a message on the forward TCH that requires an acknowledgment on the reverse TCH N- ⁇ in times, but has not received such acknowledgment. In other words, N- ⁇ acknowledgment indicates a poor reverse TCH connection.
  • diagnostic message 4.d of FIG. 17B (line 1744) is printed. ix. Diagnose b ⁇
  • FIG. 16 illustrates the flow chart used to make diagnostic decisions when the diagnose state transition b j ⁇ is made. This diagnosis occurs when an SCH message is received by MS 110 when it is in call end state 7.
  • step 1604 it is determined whether MS 110 has transmitted to BS
  • step 1604 determines whether a T ⁇ g m timeout has occurred. If the condition in step 1604 is satisfied, control passes to step 1606, where a release state timeout is determined to have occurred. As indicated in step 1606, diagnostic message 5.a of FIG. 17B (line 1751) is printed. If the condition in step 1604 is not satisfied, then control passes to step 1608. In step 1608, it is determined that MS 110 and BS 102 exchange Release Order messages. Next, in step 1610, it is determined that a normal call termination has occurred. However, there is a minor exception.
  • MS 110 sends the initial Release Order message to BS 102, which subsequently sends back a Release Order Ack (acknowledgment) message to MS 110.
  • BS 102 is the first to send a Release Order message, awaiting acknowledgment from MS 110, this may indicate possible confusion in the algorithms that are implemented by BS 102.
  • diagnostic message 6 of FIG. 17B (line 1760) is printed.
  • FIGs. 17A and 17B illustrate the diagnostic message histograms (referred to as "Pareto Analysis") that the analysis tool can output for cases.
  • the analysis tool displays histograms of different categories of cases that are diagnosed from the mobile log files.
  • the output contains (1) a list of different case categories, (2) the number of times a given case has occurred in all the input files, (3) a percentage distribution of the case categories, and (4) the number of times a given case has occurred individually in each log file.
  • FIG. 18 illustrates the format used by the analysis tool to output the trigger messages, which it has detected from the log files, into its case studies.
  • Sections 1810, 1820, 1830 and 1840 respectively show the formats for SCH messages, PCH messages, ACH messages and TCH messages.
  • each message format has a time stamp section 1802, a pilot PN and pilot Ec/Io information section 1804, a message flow direction section 1806 (which uses different types of arrows, lines, etc. to uniquely define the direction of the message and the channel the message is transmitted over), a channel section 1808 (which includes layer two information), and a message section 1809.
  • Section 1812 shows a sample SCH message output.
  • Time stamp 1813 shows when the SCH message was received by the mobile station, in hours (hh), minutes (mm), seconds (ss), and thousandths of a second (000).
  • Section 1814 shows the pilot PN and Ec/Io of the signal. This is searcher information regarding the pilot. The searcher is an entity in the mobile station that is constantly looking for new pilot signals.
  • Section 1815 shows that the message is transmitted over the SCH, in a direction from the base station (B) toward the mobile station (M).
  • Section 1816 shows that the channel over which the message is transmitted is an SCH (Sync Channel). This field also includes layer two information, which includes such well known parameters as whether the message is an acknowledgment, whether the message requires an acknowledgment, etc.
  • section 1817 shows that the message is an SCH (Sync Channel) message.
  • a CDMA mobile station employs a rake receiver design.
  • a rake receiver is a collection of multiple demodulator receiving units, called “fingers,” that allow the mobile to simultaneously lock onto multiple signal paths (called the multipath) for improved diversity reception.
  • the multipath multiple signal paths
  • the mobile station On the SCH, PCH and ACH, the mobile station is allowed to lock onto the multipath from only one base station that has the highest signal energy.
  • the messages on SCH, PCH and ACH are displayed with the base station pilot PN and Ec/Io in section 1814.
  • the mobile station can simultaneously demodulate signals from more than one base station (called “soft handoff”). The soft handoff is, therefore, the mechanism by which the mobile station improves the signal quality through diversity reception of multiple signal paths from several base stations.
  • a “hard handoff” the mobile station "breaks” the connection with the old base station to "make” a new connection with a new base station.
  • the mobile station On a soft handoff, on the other hand, the mobile station "makes” a connection with a new base station before it "breaks” the connection with the old base station.
  • soft handoff not only improves signal reception but also prevents a call from dropping.
  • section 1814 displays up to three pilots the mobile station is demodulating on the TCH.
  • Section 1844 shows a sample finger information for a sample TCH signal, with the three fingers pointing respectively to PN1, PN2 and PN3.
  • FIG. 19 illustrates case studies performed for the log files M1517068.906 and M0222430.161. At the end of each case study, there are diagnostic notes to describe whether the call ended normally or has failures.
  • section 1927 shows that case 2 is a normal call termination; section 1910 shows that case 1 indicates a PCH problem.
  • the notes indicating failures are the outputs of the diagnoses described above.
  • the note for case 1 indicates that the PCH was lost in the idle state, T3 Q timeout occurred, and provides the time stamp of the occurrence.
  • This note is the same as diagnostic message 3.c of FIG. 17A (line 1711), but also includes the time stamp for convenience.
  • the time stamps provided in the diagnostics at the end of each case are very valuable pointers into the mobile log files, if one wants to study the problem in a greater detail than that provided by the algorithm. Referring to FIG. 19, the case studies also illustrate the searcher information and finger information.
  • Section 1923 shows a Release Order transmitted over the forward TCH, with the fingers locked onto pilots 176, 168 and 172, respectively. Here, all three pilots are being locked onto by the fingers.
  • the analysis tool outputs additional observations to aid the systems engineer studying a cellular system. These outputs are listed in FIGs. 20A-
  • Neighbor list problems section 2000 illustrates neighbor list problems for the sample log file M1517068.906.
  • Different base stations are uniquely identified with a unique PN offset.
  • a mobile station keeps continuously searching for good pilots.
  • the base station provides a list of it's neighbors to the mobile station, thereby assisting the mobile station to quickly hand off to the strongest base station.
  • the Neighbor List message can have up to No pilots.
  • the choice of pilots to be included in the Neighbor List message becomes crucial for proper functioning of the mobile station.
  • Typical problems in the neighbor list design include (a) missing neighbors, where the base station does not provide a complete neighbor list, (b) non- symmetric neighbors, where a base station A lists PN B as its neighbor, but base station B does not list PN A as its neighbor.
  • Sections 2002 and 2004 show neighbor list problems that actually occurred during a case.
  • pilots PN 192 and PN 30 were determined to not be in each other's neighbor lists.
  • pilots PN 192 and PN 30 were determined to not be in each other's neighbor lists.
  • PN 174 and PN 354 were determined to not be symmetric neighbors, meaning that PN 174 is not in the neighbor list of PN 354, but PN 354 is in the neighbor list of PN 174.
  • Section 2006 shows non-symmetric neighbors which did not actually cause a problem. The analysis tool determines these latter pairs by cross-checking the neighbor lists at the end of its analyses.
  • N ⁇ m counts out if the mobile station keeps retransmitting reverse TCH messages N ⁇ m times without any acknowledgment response from the base station.
  • Section 2010 provides histograms for the number of times the mobile station retransmits on the reverse TCH before acknowledgment is received. This is shown for the first log file
  • Section 2012 shows the handoff distributions.
  • the cellular coverage area of each base station is divided into three sectors, each sector representing one third of the coverage area (i.e., a 120 degree area).
  • the mobile station is communicating with two sectors from two different base stations.
  • the mobile station is communicating with two different sectors of the same base stations.
  • Section 2012 shows hand-off distributions on a percentage basis for (1) a one-way handoff, (2) a two-way soft handoff (2W-SF), (3) a two-way softer handoff (2W-SR), (4) a three-way soft handoff (3W-SF), (5) a three-way soft-to- softer handoff (3W-SF-SR), (6) a three-way softer handoff (3W-SR), (7) a hard handoff, and (8) other handoffs (four-way, five-way, or six-way). Section 2012 shows these distributions for the first and second log files, both individually and combined. This distribution is helpful in getting an idea about the amount of resources the mobile station is using or to compute the performance of two different handoff algorithms.
  • Section 2014 shows the handoff setup time statistics.
  • the mobile station desires to make a handoff, it sends a Pilot Strength Measurement message to the base station, providing the strengths of the pilot signals it is receiving.
  • the base station sends back a Hand- Off Direction message, indicating the list of pilot signals the mobile station may be in handoff with.
  • the lag in time between when the mobile station sends the Pilot Strength Measurement message and the base station sends back the Hand-Off Direction message is the handoff setup time.
  • the following statistics are provided for the handoff setup times: (1) the mean (in seconds), (2) the standard deviation (in seconds), (3) the minimum handoff setup time (in seconds), (4) the maximum handoff setup time (in seconds), and the number of handoff setup times (i.e., the sample size). These statistics are provided for the log files, both individually and combined. This data gives an idea about the latency of the base station in granting a handoff that could lead to a call drop.
  • Section 2016 shows the call setup time statistics.
  • the lag in time between when the mobile station sends the access probes (Origination message, Page Response message or Registration message) and when the base station sends back the Base Station Ack Order message on the TCH is the call setup time.
  • the call setup time indicates how long it took to establish the call from the time the mobile station requested it and gives an idea about the latency of the base station in setting up the resources and sending a Channel Assignment message.
  • the following statistics are provided for the call setup times: (1) the mean (in seconds), (2) the standard deviation (in seconds), (3) the minimum call setup time (in seconds), (4) the maximum call setup time (in seconds), and the number of call setup times (i.e., the sample size). These statistics are provided for the log files, both individually and combined.
  • Section 2018 shows the pilot acquisition time statistics.
  • the mobile station is searching for a valid pilot signal.
  • this indicates that the pilot signal has been acquired, and the mobile station transitions to the SCH substate 306.
  • Section 2018 shows the following statistics. The statistics of the number of fingers that are locked to a single pilot when the mobile station is demodulating only one pilot (such as when it is in idle state or in the TCH in a one-way handoff) are provided in this table.
  • the mobile station logs show the finger information consisting of the PN, Ec/Io and PN position for all the fingers.
  • the finger which has maximum Ec/Io is chosen as the reference finger and any other finger is counted as the multipath of a given PN if: (a) its Ec/Io is within 10 dB of the maximum Ec/Io of the reference finger and (b) its position is at least one chip away from that of the reference finger.
  • the first condition helps in isolating a reasonably strong multipath that can contribute to the effective Ec/Io, while the second condition ensures that the finger counted as multipath is not demodulating the same path as that of the reference finger.
  • Section 2022 provides the number of "timing change substate” problems (i.e., when despite a valid pilot signal, the mobile station cannot jump properly to the PCH from the SCH).
  • the jump from the SCH to the PCH is also called the "jump to Hyperspace.”
  • Section 2024 provides all of the pilot signals demodulated by the mobile station. This list not only indicates the different PNs the mobile station has seen, but also gives an idea about the mobility of the mobile station in a log file. For example, if one sees as many as six pilots when the mobile station is stationary, then one could suspect a pilot pollution problem.
  • Section 2026 provides the histogram of the maximum number of access probes transmitted per call.
  • the format [A,B] is provided, where A is the number of probes per call, and B is the frequency of the occurrence of the number A.
  • Section 2028 shows the number of hard handoffs.
  • Section 2030 shows the number of analog handoffs (i.e., the number of handoffs to an AMPS system from a CDMA system).
  • the base station sends a new list of neighbors in a Neighbor List Update message, obtained by combining the neighbor lists of all the base stations with which the mobile station is in hand off.
  • the base station includes its own pilot PN along with the neighboring PNs in the Neighbor List Update message, which can be a potential cause for confusing the mobile station and can also constitute a standard violation.
  • Section 2032 indicates any such cases and gives the time-stamps of the Neighbor List Update Messages where such an incident occurred.
  • the invention may be implemented using hardware, software or a combination thereof and may be implemented in a computer system or other processing system.
  • the invention is directed toward a computer system capable of carrying out the functionality described herein.
  • An example computer system 2102 is shown in FIG. 21.
  • the computer system 2102 includes one or more processors, such as processor 2104.
  • the processor 2104 is connected to a communication bus 2106.
  • Various software embodiments are described in terms of this example computer system. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the invention using other computer systems and/or computer architectures.
  • Computer system 2102 also includes a main memory 2108, preferably random access memory (RAM), and can also include a secondary memory 2110.
  • the secondary memory 2110 can include, for example, a hard disk drive 2112 and/or a removable storage drive 2114, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc.
  • the removable storage drive 2114 reads from and/or writes to a removable storage unit 2118 in a well known manner.
  • Removable storage unit 2118 represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive 2114.
  • the removable storage unit 2118 includes a computer usable storage medium having stored therein computer software and/or data.
  • secondary memory 2110 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 2102.
  • Such means can include, for example, a removable storage unit 2122 and an interface 2120. Examples of such can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and other removable storage units 2122 and interfaces 2120 which allow software and data to be transferred from the removable storage unit 2118 to computer system 2102.
  • Computer system 2102 can also include a communications interface
  • Communications interface 2124 allows software and data to be transferred between computer system 2102 and external devices. Examples of communications interface 2124 can include a modem, a network interface (such as an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via communications interface 2124 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communications interface 2124. These signals 2126 are provided to communications interface via a channel 2128. This channel 2128 carries signals 2126 and can be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels.
  • Computer system 2102 can also includes a graphics pipeline 2130.
  • the graphics pipeline comprises the hardware and software that take input commands and produce therefrom data in the format of pixels.
  • the pixels are output to frame buffer 2132.
  • Frame buffer 2132 varies from a simple buffer capable of storing two-dimensional images, to a state-of-the-art device capable of displaying textured, three-dimensional, color images.
  • Scan-out device 2134 comprises rendering hardware that selectively reads the pixels from frame buffer 2132 and transmits the pixels to display 2136.
  • Display 2136 comprising for example a cathode ray tube (CRT), provides a physical display of the pixels.
  • the scan-out device 2134 and display 2136 comport in function with the sophistication of the frame buffer 2132.
  • computer program medium and “computer usable medium” are used to generally refer to media such as removable storage device 2118, a hard disk installed in hard disk drive 2112, and signals 626.
  • These computer program products are means for providing software to computer system 2102.
  • Computer programs also called computer control logic
  • Computer programs are stored in main memory and/or secondary memory 2110.
  • Computer programs can also be received via communications interface 2124.
  • Such computer programs when executed, enable the computer system 2102 to perform the features of the present invention as discussed herein.
  • the computer programs when executed, enable the processor 2104 to perform the features of the present invention. Accordingly, such computer programs represent controllers of the computer system 2102.
  • the software may be stored in a computer program product and loaded into computer system 2102 using removable storage drive 2114, hard drive 2112 or communications interface 2124.
  • the control logic when executed by the processor 2104, causes the processor 2104 to perform the functions of the invention as described herein.
  • the invention is implemented primarily in hardware using, for example, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).
  • the invention is implemented using a combination of both hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Cet outil d'analyse des performances permet d'analyser des messages, lesquels sont transmis par voie radio entre une station mobile témoin (110) et une ou plusieurs stations de base (102, 104) et sont enregistrés par un moniteur de diagnostic mobile (112) dans des fichiers-journaux mobiles. L'outil d'analyse visionne le fichier-journal contenant les messages, et en réponse à certains messages de déclenchement, effectue une transition entre des états différents. Une série de transitions d'état comprend un 'cas', défini comme une série de messages vus dans le fichier-journal et aboutissant à un événement critique. Cet outil peut fonctionner à la fois d'une manière assumant que chaque message a été parfaitement enregistré (par le moniteur de diagnostic mobile), et d'une manière robuste en prenant en compte les messages qui ont été transmis mais n'ont pas été enregistrés dans les fichiers-journaux. Cet outil étudie le comportement des stations mobiles (110) et des stations de base (102, 104), pour trouver des transitions d'état normales ou anormales. Dans le cas de transitions d'état normales, l'outil émule des fonctions normales de la station mobile (110), et dans le cas de transitions d'état anormales, il diagnostique des problèmes en intégrant des informations de fichiers-journaux, des standards de systèmes de communication et des systèmes d'ingénierie de la connaissance. Cet outil produit plusieurs sorties comprenant des études détaillées pour chaque cas.
PCT/US1998/022767 1997-10-30 1998-10-26 Systeme et procede d'analyse de fichiers-journaux mobiles WO1999023849A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU12816/99A AU1281699A (en) 1997-10-30 1998-10-26 System and method for analyzing mobile log files

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US96077897A 1997-10-30 1997-10-30
US08/960,778 1997-10-30

Publications (1)

Publication Number Publication Date
WO1999023849A1 true WO1999023849A1 (fr) 1999-05-14

Family

ID=25503612

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/022767 WO1999023849A1 (fr) 1997-10-30 1998-10-26 Systeme et procede d'analyse de fichiers-journaux mobiles

Country Status (3)

Country Link
AR (1) AR018516A1 (fr)
AU (1) AU1281699A (fr)
WO (1) WO1999023849A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1309214A1 (fr) * 2001-11-05 2003-05-07 Nokia Corporation Remise de données de tests de fonctionnement, d'auto test et de performance à un reseau mobile en reponse à un message de demande crypte
WO2004095866A1 (fr) * 2003-04-22 2004-11-04 Sagem Sa Systeme et procede de test d'un reseau de telephonie mobile
US7076481B2 (en) * 1998-03-31 2006-07-11 Bmc Software, Inc. Method and apparatus for logically reconstructing incomplete records
WO2006111000A1 (fr) * 2005-04-18 2006-10-26 Research In Motion Limited Systeme et procede permettant de tester des applications a composants sans fil
US7400692B2 (en) 2004-01-14 2008-07-15 Interdigital Technology Corporation Telescoping window based equalization
WO2008045866A3 (fr) * 2006-10-12 2008-10-09 Qualcomm Inc Procédés et appareil pour reconstituer un réseau en environnements contrôlés
US7437135B2 (en) 2003-10-30 2008-10-14 Interdigital Technology Corporation Joint channel equalizer interference canceller advanced receiver
EP2099252A3 (fr) * 2001-08-17 2009-12-02 Qualcomm Incorporated Procédé er appareil permettant une réduction du temps d'établissement d'une communication
EP2319212A4 (fr) * 2008-08-28 2016-05-11 Ericsson Telefon Ab L M Procédé de détection d'erreurs physiques en déterminant un taux de connexions libérées
CN113852983A (zh) * 2021-08-19 2021-12-28 荣耀终端有限公司 一种获取基带日志的方法及装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1993015569A1 (fr) * 1992-01-28 1993-08-05 Comarco, Incorporated Systeme de commande automatique pour telephones cellulaires

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1993015569A1 (fr) * 1992-01-28 1993-08-05 Comarco, Incorporated Systeme de commande automatique pour telephones cellulaires

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GLOGER M ET AL: "TYPE-APPROVAL MEASUREMENTS ON DECT FIXED PARTS (FP) AND PORTABLE PARTS (PP) TO TBR22", NEWS FROM RHODE & SCHWARZ, vol. 35, no. 148, 1995, pages 9 - 11, XP000645891 *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7076481B2 (en) * 1998-03-31 2006-07-11 Bmc Software, Inc. Method and apparatus for logically reconstructing incomplete records
US7986674B2 (en) 2001-08-17 2011-07-26 Qualcomm Incorporated Method and apparatus for call setup latency reduction
EP2099252A3 (fr) * 2001-08-17 2009-12-02 Qualcomm Incorporated Procédé er appareil permettant une réduction du temps d'établissement d'une communication
US8126469B2 (en) 2001-08-17 2012-02-28 Qualcomm Incorporated Method and apparatus for call setup latency reduction
EP2302977A1 (fr) * 2001-08-17 2011-03-30 Qualcomm Incorporated Procédé er appareil permettant une réduction du temps d'établissement d'une communication
US7894403B2 (en) 2001-08-17 2011-02-22 Qualcomm Incorporated Method and apparatus for call setup latency reduction
US7369846B2 (en) 2001-11-05 2008-05-06 Nokia Corporation Delivery of mobile station operational and self-performance test results to network in response to encrypted request message
EP1309214A1 (fr) * 2001-11-05 2003-05-07 Nokia Corporation Remise de données de tests de fonctionnement, d'auto test et de performance à un reseau mobile en reponse à un message de demande crypte
US8050670B2 (en) 2003-04-22 2011-11-01 Apple Inc. System and method for testing a mobile telephone network
WO2004095866A1 (fr) * 2003-04-22 2004-11-04 Sagem Sa Systeme et procede de test d'un reseau de telephonie mobile
US7437135B2 (en) 2003-10-30 2008-10-14 Interdigital Technology Corporation Joint channel equalizer interference canceller advanced receiver
US7400692B2 (en) 2004-01-14 2008-07-15 Interdigital Technology Corporation Telescoping window based equalization
US8001529B2 (en) 2005-04-18 2011-08-16 Research In Motion Limited System and method of testing wireless component applications
WO2006111000A1 (fr) * 2005-04-18 2006-10-26 Research In Motion Limited Systeme et procede permettant de tester des applications a composants sans fil
US7840382B2 (en) 2006-10-12 2010-11-23 Qualcomm Incorporated Methods and apparatus for network re-creation in controlled environments
WO2008045866A3 (fr) * 2006-10-12 2008-10-09 Qualcomm Inc Procédés et appareil pour reconstituer un réseau en environnements contrôlés
EP2319212A4 (fr) * 2008-08-28 2016-05-11 Ericsson Telefon Ab L M Procédé de détection d'erreurs physiques en déterminant un taux de connexions libérées
CN113852983A (zh) * 2021-08-19 2021-12-28 荣耀终端有限公司 一种获取基带日志的方法及装置

Also Published As

Publication number Publication date
AR018516A1 (es) 2001-11-28
AU1281699A (en) 1999-05-24

Similar Documents

Publication Publication Date Title
US6178164B1 (en) Method and apparatus for performing idle handoff in a multiple access communication system
US6654611B2 (en) Method and apparatus for performing idle handoff in a multiple access communication system
US9538404B2 (en) Apparatus and methods for product acceptance testing on a wireless device
JP2015156661A (ja) Ｓｏｎソリューションを使用するネットワーク最適化のための方法及び装置
RU2000131197A (ru) Способ и устройство синхронизации состояний базовой и мобильной станции в системе множественного доступа с кодовым разделением каналов
US20090005027A1 (en) Terminal Device, and In-zone Cell Checking Method and Cell Re-selection Method Thereof
WO1999023849A1 (fr) Systeme et procede d'analyse de fichiers-journaux mobiles
US6826718B1 (en) Method and apparatus for tracking call processing failure data in a radiotelephone system
CN1691825B (zh) 扇区切换检测方法
JP2003522448A (ja) 移動通信ネットワーク
US20060252379A1 (en) Data transmission method with lower probability of erroneous rejection of data
EP4150960B1 (fr) Journalisation d'informations relatives à une exécution de transfert intercellulaire conditionnel à événements multiples pour des réseaux sans fil
CN114845411B (zh) 基于干扰感知的自组网抗干扰方法及应用
Yeo et al. Measuring traffic on the wireless medium: Experience and pitfalls
CN100550713C (zh) 用于允许快速重复特性的方法与设备
EP2949145B1 (fr) Technique pour rapporter des mesures relatives aux tentatives d'accès aléatoire
EP0214333B1 (fr) Circuit de contrôle d'un canal utilisé dans une station relais d'un système de transmission de signaux radio numériques
CN102740277A (zh) 一种切换时终端测量上报的控制方法及系统
EP4472268A1 (fr) Procédé de transmission de données, terminal et dispositif côté réseau
JPH05500291A (ja) 受動回路網モニタ
EP1487143B1 (fr) Procédé pour améliorer l'efficacité d'une interface dans un réseau de communication
CN109617659A (zh) 一种数据盲重传方法
CN101518149B (zh) 移动通信系统、用户设备和通信结束时段缩短方法
CN113708861B (zh) 一种ue基带合并预测方法、系统、设备及存储介质
EP4510724A1 (fr) Procédé et appareil de positionnement, terminal et support de stockage lisible

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA