Method of MDT information logging and reporting

• US 20120106356A1
• Filed: 11/02/2011
• Published: 05/03/2012
• Est. Priority Date: 11/03/2010
• Status: Active Grant

• Current Assignee: HFI Innovation, Inc. (MediaTek, Inc.)
• Original Assignee: MediaTek, Inc.
• Inventors: Chen, Yih-Shen, Hsu, Chia-Chun, Roberts, Michael, Johansson, Per Johan Mikael
• Granted Patent: US 10,595,221 B2
• Time in Patent Office: Days
• US Class Current: 370/241.1
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 52/14 Separate analysis of uplink or downlink

Abstract

A method of MDT information logging and problem event reporting is provided. The method supports provisioning of reference events to enable correlation of system time and the problem occurrence. In one embodiment, a problem event report includes time information directly or indirectly related to a reference event. A method of handling battery condition is also provided. The method supports autonomously suspending or resuming OAM activities in MDT based on predefined battery condition. In one embodiment, a testable battery condition handling is designed for MDT logging.

Claims

1. A method, comprising:

detecting a reference event by a user device (UE) in a wireless network;

detecting a problem event by the UE;

logging the problem event and thereby generating a problem event report based on the detected reference event; and

sending the problem event report to a network device, wherein the problem event report provides time information of the problem event that is related to an occurrence of the reference event.

2. The method of claim 1, wherein the problem event is taking from the group consisting of a radio link failure (RLF), a handover (HO) failure, a random access channel (RACH) failure, an initial connection setup failure, a cell reselection failure, and a UE entering an out-of-service state.

3. The method of claim 1, wherein the reference event is a request of the problem event report.

4. The method of claim 3, wherein the time information contains a duration between the request of the problem event report and the problem event.

5. The method of claim 1, wherein the reference event is a successful connecting of the UE to a base station before the problem event occurred.

6. The method of claim 5, wherein the time information contains a duration between the successful connecting of the UE to a base station and the problem event.

7. The method of claim 1, wherein the reference event is the UE being served by a different radio access technology (RAT) or by a different public land mobile network (PLMN).

8. The method of claim 7, wherein the time information contains a delayed report indicator.

9. A method, comprising:

detecting one or more problem events by a user device (UE) in a wireless network;

starting a deadline timer associated with the problem events;

logging the problem events into a problem event report; and

determining whether to discard or keep the logged problem events in the problem event report based on a status of the deadline timer.

10. The method of claim 9, wherein the problem event is taking from the group consisting of a radio link failure (RLF), a handover (HO) failure, a random access channel (RACH) failure, an initial connection setup failure, a cell reselection failure, and a UE entering an out-of-service state.

11. The method of claim 9, wherein the deadline timer is expired, and wherein the UE discards the problem events logged at the expiration of the deadline timer.

12. The method of claim 9, wherein the deadline timer is expired, and wherein the UE is configured to discard or keep the problem events logged before the expiration of the deadline timer.

13. A method, comprising:

monitoring a condition on a battery of a user device (UE) in a wireless network;

detecting a low battery condition of the UE;

taking an autonomously suspending action on Operations, Administration, and Maintenance (OAM) activities when detecting the low battery condition; and

taking an autonomously resuming action on OAM activities when the UE exits the low battery condition.

14. The method of claim 13, wherein the low battery condition being the UE not using unlimited power source, a remaining battery life being smaller than a threshold duration, or a remaining battery life reaching a percentage of a normal battery life when fully charged.

15. The method of claim 14, wherein the normal battery life is based on battery life in stand-by mode.

16. The method of claim 13, wherein when the UE is in the low battery condition, and wherein the UE keeps a configuration related to the OAM activities while suspending the OAM activities.

17. The method of claim 13, wherein when the UE is in the low battery condition, and wherein the UE keeps a configuration timer running whiling suspending the OAM activities.

18. The method of claim 17, wherein the configuration timer is a Minimization of Driver Tests (MDT) logging duration timer.

19. The method of claim 13, further comprising:

obtaining a configuration for the autonomously suspending action, wherein the UE does not autonomously suspend the OAM activities when the configuration indicates taking no autonomous action.

20. The method of 13, further comprising:

logging information of said autonomous suspending action or said autonomous resuming action in a log.

21. The method of 13, further comprising:

storing an existing OAM activity log in a persistent memory when the UE is in the low battery condition.

22. The method of 13, wherein the said OAM activities is at least one of logging information for network operation purposes, MDT logging, applying certain device configurations related to the said logging, performing measurements and measurement evaluation for the said logging such as radio measurements or positioning measurements.