UE-based MDT measuring and reporting in a cellular radio access network
AssigneeTelefonaktiebolaget LM Ericsson (publ)
InventorAndreas Olsson
Life of this patent
Estimating the term…
Loading patent…
AssigneeTelefonaktiebolaget LM Ericsson (publ)
InventorAndreas Olsson
Estimating the term…
In one embodiment, if a UE is performing minimizing drive test (MDT) measurements and a radio link failure (RLF) occurs, the UE may add MDT measurement information to an RLF message to the network. In effect, the UE “piggy-backs” MDT information in the RLF report, and in so doing, provides greater flexibility to UEs reporting MDT information and more robust reporting. In another embodiment, the UE detects that no allowed reporting channel to report MDT measurement information exists, stores the MDT information, and after detecting that allowed reporting channel exists, initiates establishment of a radio link with the radio communications network during which the UE informs the network using an availability indicator that the UE has stored unreported MDT measurement information to be reported to the radio communications network.
A method for a user equipment (UE) to report measurement information to a radio communications network, the UE performing the steps comprising:
A method for a network node in a radio communications network, comprising:
Apparatus for a user equipment (UE) to report measurement information to a radio communications network, the apparatus comprising:
Apparatus for a network node in a radio communications network, comprising:
Apparatus for a user equipment (UE) to report measurement information to a radio communications network, the apparatus comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
No references of this kind are recorded.
Connection setup: management of setup rejection or failure
Supervisory, monitoring or testing arrangements: scheduling measurement reports ; Arrangements for measurement reports
Wireless communication networks
About 4 years 7 months of term left · ends 2 Jun 2031 (estimated)
The technical field relates to radio communications, and more particularly, to UE-based minimizing drive time (MDT) measuring and reporting in a cellular radio access network.
FIG. 1 shows a radio or wireless communications system 1 where wireless terminals 2 (also known as mobile stations and/or user equipment units (UEs)) communicate via a radio access network (RAN) to one or more core networks (shown as a cloud 3). In a cellular communications system, the radio access network (RAN) covers a geographical area which is divided into cell areas, with each cell area being served by a base station, e.g., a radio base station (RBS), which in some networks may also be called a “NodeB” (UMTS) or “eNodeB” (LTE). A cell is a geographical area where radio coverage is provided by the radio base station equipment at a base station site. Each cell is identified by an identity within the local radio area, which is broadcast in the cell. The base stations communicate over the air interface operating on radio frequencies with the user equipment units (UE) within range of the base stations.
In some versions of a radio access network, several base stations are typically connected (e.g., by landlines or microwave) to a controller node (such as a radio network controller (RNC) or a base station controller (BSC)) which supervises and coordinates various activities of the plural base stations connected thereto. The radio network controllers are typically connected to one or more core networks.
FIG. 1 illustrates a non-limiting example of a wireless communications system;
FIG. 2 illustrates a non-limiting example of a wireless LTE communications system;
FIG. 3 is a flowchart diagram illustrating non-limiting example procedures for UE-based MDT measuring and reporting in a cellular radio access network when radio communication is temporarily disrupted between a UE and the RAN and re-connected by a radio connection reestablishment procedure;
In the following description, for purposes of explanation and non-limitation, specific details are set forth, such as particular nodes, functional entities, techniques, protocols, standards, etc. in order to provide an understanding of the described technology. It will be apparent to one skilled in the art that other embodiments may be practiced apart from the specific details disclosed below. In other instances, detailed descriptions of well-known methods, devices, techniques, etc. are omitted so as not to obscure the description with unnecessary detail. Individual function blocks are shown in the figures. Those skilled in the art will appreciate that the functions of those blocks may be implemented using individual hardware circuits, using software programs and data in conjunction with a suitably programmed microprocessor or general purpose computer, using applications specific integrated circuitry (ASIC), and/or using one or more digital signal processors (DSPs). The software program instructions and data may be stored on computer-readable storage medium and when the instructions are executed by a computer or other suitable processor control, the computer or processor performs the functions.
Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudocode, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller” may be provided through the use of hardware such as circuit hardware and/or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and/or computer-implemented, and thus machine-implemented.