WO2021109481A1

WO2021109481A1 - Logged minimization of driving test (mdt) configuration and on demand system information (si)

Info

Publication number: WO2021109481A1
Application number: PCT/CN2020/091554
Authority: WO
Inventors: Jianmin Fang; He Huang; Zhihong Qiu; Dapeng Li; Yuan Gao
Original assignee: Zte Corporation
Priority date: 2020-05-21
Filing date: 2020-05-21
Publication date: 2021-06-10
Also published as: CN115699850A

Abstract

The present application relates to methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to configuring of logged Minimization of Driving Test (MDT) configurations. In one exemplary aspect, a method for wireless communication is disclosed. The method includes receiving, by a first network node, a first message from a terminal, the first message including a status of a logged driving test minimization configuration. The method also includes determining, by the first network node, whether to select the terminal to send a new logged driving test minimization configuration according to the status of the logged driving test minimization configuration.

Description

LOGGED MINIMIZATION OF DRIVING TEST (MDT) CONFIGURATION AND ON DEMAND SYSTEM INFORMATION (SI)

TECHNICAL FIELD

This patent document is directed generally to wireless communications.

BACKGROUND

Mobile communication technologies are moving the world toward an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios. Various techniques, including new ways to provide higher quality of service, are being discussed.

SUMMARY

This document discloses methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to configuring of logged Minimization of Driving Test (MDT) configurations.

In one exemplary aspect, a method for wireless communication is disclosed. The method includes receiving, by a first network node, a first message from a terminal, the first message including a status of a logged driving test minimization configuration. The method also includes determining, by the first network node, whether to select the terminal to send a new logged driving test minimization configuration according to the status of the logged driving test minimization configuration.

In another exemplary aspect, a method for wireless communication is disclosed. The method includes receiving, by a terminal, a first message including a logged driving test minimization configuration that includes a priority of the logged driving test minimization configuration from a first network node. The method also includes performing, by the terminal, a logged driving test minimization measurement based on the logged driving test minimization configuration when the terminal is in an idle or inactive state.

In yet another exemplary aspect, a method for wireless communication is disclosed. The method includes receiving, by a first network node, a first message from a core network node, the first message including a first set of information for the logged driving test minimization configuration. The method also includes determining, by the first network node, whether to select or not select a terminal to send a new logged driving test minimization configuration based on the first set of information for the logged driving test minimization configuration.

In another exemplary aspect, a wireless communications apparatus comprising a processor is disclosed. The processor is configured to implement a method described herein.

In yet another exemplary aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

The details of one or more implementations are set forth in the accompanying attachments, the drawings, and the description below. Other features will be apparent from the description and drawings, and from the clauses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example 5G network architecture.

FIG. 2 illustrates an example signaling process for logged MDT configuration corresponding to a first example embodiment.

FIG. 3 illustrates an example signaling process for logged MDT configuration corresponding to a second example embodiment.

FIG. 4 illustrates an example signaling process for logged MDT configuration corresponding to a third example embodiment.

FIG. 5 illustrates an signaling process for logged MDT configuration corresponding to the fourth example embodiment.

FIG. 6 illustrates an signaling procedure for logged MDT configuration corresponding to a fifth example embodiment.

FIG. 7 illustrates an example signaling process for logged MDT configuration corresponding to a sixth example embodiment.

FIG. 8 illustrates an example signaling process for on demand other SI corresponding to an seventh example embodiment.

FIG. 9 is a block diagram of an example method for configuring of logged Minimization of Driving Test (MDT) configurations.

FIG. 10 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied.

FIG. 11 is a block diagram representation of a portion of a hardware platform.

DETAILED DESCRIPTION

The development of the new generation of wireless communication –5G New Radio (NR) communication –is a part of a continuous mobile broadband evolution process to meet the requirements of increasing network demand. NR will provide greater throughput to allow more users connected at the same time. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios.

FIG. 1 illustrates an example 5G network architecture 100. As shown in FIG. 1, a fifth generation (5G) network architecture may include a 5G core network (5GC) and a next generation radio access network (NG-RAN) .

The 5GC may include any of an Access Mobility Function (AMF) , a Session Management Function (SMF) , and a User Plane Function (UPF) . NG-RAN may include base stations with different radio access technologies (RATs) , such as an evolved 4G base station (ng-eNB) , a 5G base station (gNB) . The NG-RAN base station may be connected to the 5GC through the NG interface, and the NG-RAN base stations may be connected through the Xn interface. In many cases, the signaling based logged MDT and the management based logged MDT may be utilized.

Logged MDT configuration may be used to ensure that the logged MDT configuration with high priority will not be overwritten by another one. On demand other system information (SI) may be used to help to optimize the configuration parameters relative to on demand other SI.

System Overview

The present embodiments can relate to configuring of logged Minimization of Driving Test (MDT) configurations. A minimization of drive tests (MDT) is a feature that can allow for operators to utilize user equipment to collect radio measurements and associated location information, in order to assess network performance while reducing the operational resources associated with traditional drive tests. However, in the increasingly complex wireless packet data networks, performance can be affected by many different factors and cannot easily be estimated by simple radio measurements. Therefore, MDT can be enhanced in order to provide a more complete view of network performance.

To ensure that the logged MDT configuration with high priority may not be overwritten by another logged MDT configuration, at least one of the following messages may be utilized. A first message can include an indication indicating a priority of logged MDT configuration can be sent from a RAN node to a UE. A second such message can include sending an indication indicating the status of logged MDT configuration from the UE.

Alternatively, a message can include an indication indicating whether an ongoing logged MDT configuration exists for UE and/or a remaining valid time for the existing ongoing logged MDT configuration being sent from a core network node (CN) or an indication indicating the priority of logged MDT configuration and/or a time duration for UE being sent to the CN.

In some embodiments, a RAN node can receive an indication indicating the status of logged MDT configuration from a UE. The RAN node may or may not select the UE to send a new logged MDT configuration according to the received indication indicating the status of logged MDT configuration. The RAN node can send an indication indicating the priority of logged MDT configuration to UE. The RAN node can receive an indication indicating the priority of logged MDT configuration from CN, or from OAM.

The indication indicating the status of logged MDT configuration can indicate that the UE has an ongoing logged MDT configuration and the configuration is not allowed to be overwritten, or it can indicate that the UE has an ongoing logged MDT configuration and the configuration is prioritized.

The indication indicating the priority of logged MDT configuration can indicate whether a logged MDT configuration can be overwritten by another logged MDT configuration, or indicates whether a logged MDT configuration is prioritized.

The indication indicating the priority of logged MDT configuration can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or is presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

The indication indicating the status of logged MDT configuration can be included in a RRCSetupComplete message or in a RRCResumeComplete message.

The indication indicating the priority of logged MDT configuration can be included in the LoggedMeasurementConfiguration message from RAN node to UE, and/or included in the TRACE START or INITIAL CONTEXT SETUP REQUEST message from CN to RAN node.

In some embodiments, a RAN node can receive a first information from CN including at least one of the following: an indication indicating whether an ongoing signaling based logged MDT configuration exists for UE and/or a remaining valid time for the existing ongoing signaling based logged MDT configuration and/or a priority (prioritized or normal) , an indication indicating whether an ongoing management based logged MDT configuration exists for UE and/or a remaining valid time for the existing ongoing management based logged MDT configuration and/or a priority, an indication indicating whether an ongoing logged MDT configuration exists for UE and/or a remaining valid time for the existing ongoing logged MDT configuration and/or a type (signaling based or management based) and/or a priority. The RAN node may or may not select the UE to send a new logged MDT configuration according to the first information received from CN.

A second set of information can be sent to CN including an indication indicating the priority of logged MDT configuration and/or a time duration for UE. The first information can be included in a logged MDT configuration check response message to reply a logged MDT configuration check request message, or included in the INITIAL CONTEXT SETUP REQUEST message, or included in the PATH SWITCH REQUEST ACKNOWLEDGE message. The second information can be included in the CELL TRAFFIC TRACE message.

The RAN node may not select the UE to send a management based logged MDT configuration, if the first information indicates that an ongoing signaling based logged MDT configuration exists, and if the priority of management based logged MDT configuration is lower or equal to the priority of signaling based logged MDT configuration.

The present embodiments may also relate to on demand other system information (SI) to optimize the configuration parameters relative to on demand other SI. In some embodiments, when on demand other SI failure occurs, the UE can log at least one of: the message type of on demand other SI request (e.g., Msg1, Msg3, or MsgA) , the requested SI messages, the requested SIBs, the number of modification periods the UE attempts to receive, the approach of on demand other SI request (e.g., associating to PRACH preamble and/or PRACH resource, sending RRCSystemInfoRequest message) if MsgA is used, the current configured value of modification period, the current configured value of SI-window, the SI messages failed to receive, the SIBs failed to receive, whether the on demand other SI response message (e.g. Msg2, Msg4, or MsgB) has been received, the current configured value of si-Periodicity of SI messages failed to receive.

When on demand other SI succeeds and some condition matches (e.g., the number of SI-windows the UE attempts to receive is larger than a configured value or pre-set value) , the UE can log at least one of: the message type of on demand other SI request (e.g., Msg1, Msg3, or MsgA) , the requested SI messages, the requested SIBs, the number of modification periods the UE attempts to receive, the approach of on demand other SI request (e.g., associating to PRACH preamble and/or PRACH resource, sending RRCSystemInfoRequest message) if MsgA is used, the current configured value of modification period, the current configured value of SI-window, the number of SI-windows the UE attempts to receive.

The UE can log logging information of on demand other SI when on demand other SI failure occurs and/or when on demand other SI succeeds and some condition matches, UE can also report the logging information of on demand other SI to RAN node.

The UE can receive configuration information for on demand other SI event triggered logging from RAN node, the configuration information can indicate that the UE can log the information of on demand other SI in case some event occurs.

The UE can send an availability indication to RAN node to indicate the availability of logging information of on demand other SI. The availability indication can be included in the RRCSetupComplete message, the RRCResumeComplete message, the RRCReconfigurationComplete message, or the RRCReestablishmentComplete message.

The RAN node can send a request indication for logging information of on demand other SI to UE, the request indication is carried in the UEInformationRequest message.

The UE can send the logging information of on demand other SI to RAN node, the logging information of on demand other SI can be carried in the UEInformationResponse message.

The RAN node can send the received logging information of on demand other SI to another RAN node, if the received logging information is for another RAN node.

Example Embodiment 1

FIG. 2 illustrates an example signaling process 200 for logged MDT configuration corresponding to a first example embodiment.

In step 212, the CN 202 can send a signaling based logged MDT configuration to a RAN node 204 (RAN node1 204) serving a UE. The configuration can include an indication indicating the priority of logged MDT configuration. For example, the indication indicates whether a logged MDT configuration can be overwritten by another logged MDT configuration, or the indication indicates whether a logged MDT configuration is prioritized. As another example, the indication can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or the indication can be presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

In step 214, the RAN node 204 can send the signaling based logged MDT configuration to the UE 208. The configuration can include the indication indicating whether the logged MDT configuration can be overwritten by another logged MDT configuration.

In step 216, the UE 208 can go to an idle state and starts the logged MDT measurement according to the received logged MDT configuration.

In step 218, the UE 208 can move to a new RAN node 206 (RAN node2 206) and goes to a connected state. If the UE has an ongoing logged MDT configuration and the configuration is indicated that it is not allowed to be overwritten, to include an indication indicating the status of logged MDT configuration in the RRCSetupComplete message to indicate that the UE has an ongoing logged MDT configuration and the configuration may not be allowed to be overwritten.

In step 220, the OAM 210 can send a management based logged MDT configuration to the new RAN node.

In step 222, the new RAN node 206 may not select the UE to send the management based logged MDT configuration, if an indication indicating the status of logged MDT configuration has received from the UE to indicate that the UE has an ongoing logged MDT configuration and the configuration is not allowed to be overwritten.

Example Embodiment 2

FIG. 3 illustrates an example signaling process 300 for logged MDT configuration corresponding to a second example embodiment.

In step 312, the OAM 310 can send a management based logged MDT configuration to a RAN node 304 (RAN node1 304) .

In step 314, the RAN node 304 can select one or more UE and sends the management based logged MDT configuration to the selected UE. The configuration can include an indication indicating the priority of logged MDT configuration. For example, the indication indicates whether a logged MDT configuration can be overwritten by another logged MDT configuration, or the indication indicates whether a logged MDT configuration is prioritized. As another example, the indication can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or the indication can be presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

In step 316, the UE 308 can go to an idle state and starts the logged MDT measurement according to the received logged MDT configuration.

In step 318, the UE 308 can move to a new RAN node (RAN node2 306) and goes to connected state. If the UE has an ongoing logged MDT configuration and the configuration is indicated that it is not allowed to be overwritten, the configuration can include an indication indicating the status of logged MDT configuration in the RRCSetupComplete message to indicate that the UE has an ongoing logged MDT configuration and the configuration is not allowed to be overwritten.

In step 320, the OAM 310 can send another management based logged MDT configuration to the new RAN node serving the UE.

In step 322, the new RAN node (RAN node2 306 may not select the UE to send the new management based logged MDT configuration. If an indication indicating the status of logged MDT configuration has received from the UE to indicate that the UE has an ongoing logged MDT configuration and the configuration may not be allowed to be overwritten.

Example Embodiment 3

FIG. 4 illustrates an example signaling process 400 for logged MDT configuration corresponding to a third example embodiment.

In step 412, the OAM 410 can send a management based logged MDT configuration to a RAN node (RAN node1 404) .

In step 414, the RAN node 404 can select one or more UE and sends the management based logged MDT configuration to the selected UE. The configuration can include an indication indicating the priority of logged MDT configuration. For example, the indication indicates whether a logged MDT configuration can be overwritten by another logged MDT configuration, or the indication indicates whether a logged MDT configuration is prioritized. As another example, the indication can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or the indication can be presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

In step 416, the UE 408 can go into an inactive state and start the logged MDT measurement according to the received logged MDT configuration.

In step 418, the UE 408 can move to a new RAN node (RAN node2 406) and goes to a connected state. If the UE has an ongoing logged MDT configuration and the configuration is indicated that it is prioritized, the configuration can include an indication indicating the status of logged MDT configuration in the RRCResumeComplete message to indicate that the UE has an ongoing logged MDT configuration and the configuration is prioritized.

In step 420, the CN 402 can send a signaling based logged MDT configuration to the new RAN node 406 serving the UE. The configuration can include an indication indicating the priority of logged MDT configuration. For example, the indication indicates whether a logged MDT configuration can be overwritten by another logged MDT configuration, or the indication indicates whether a logged MDT configuration is prioritized. As another example, the indication can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or the indication can be presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

In some embodiments, in step 422, the new RAN node 406 may not select the UE to send the signaling based logged MDT configuration, if an indication indicating the status of logged MDT configuration has received from the UE to indicate that the UE has an ongoing logged MDT configuration and the configuration is prioritized, and the indication indicating the priority of logged MDT configuration in the received signaling based logged MDT configuration is absent.

In some embodiments, in step 422, the new RAN node may select the UE to send the signaling based logged MDT configuration, if an indication indicating the status of logged MDT configuration has received from the UE to indicate that the UE has an ongoing logged MDT configuration and the configuration is prioritized, and the indication indicating the priority of logged MDT configuration in the received signaling based logged MDT configuration is present.

Example Embodiment 4

FIG. 5 illustrates an signaling process 500 for logged MDT configuration corresponding to the fourth example embodiment.

In step 512, the CN 5020 can send an signaling based logged MDT configuration to a RAN node (RAN node1 504) serving a UE.

In step 514, the RAN node can send the signaling based logged MDT configuration to the UE.

In step 516, the UE 508 can go to an idle state and start the logged MDT measurement according to the received logged MDT configuration.

In step 518, the UE 508 can move to a new RAN node (RAN node2) and goes to connected state. The UE 508 can send the RRCSetupComplete message to the new RAN node 506.

In step 520, the OAM 510 can send a management based logged MDT configuration to the new RAN node.

In step 522, the new RAN node 506 can send a logged MDT configuration check request message to CN including UE NGAP ID.

In step 524, the CN 502 can send a logged MDT configuration check response message to the new RAN node including at least one of an indication indicating whether an ongoing signaling based logged MDT configuration exists for the UE, a remaining valid time for the existing ongoing signaling based logged MDT configuration.

In step 526, the new RAN node may not select the UE to send the management based logged MDT configuration, if an indication has received from CN indicating that the UE has an ongoing signaling based logged MDT configuration.

In step 528, the OAM 510 can send another management based logged MDT configuration to the new RAN node.

In step 530, the new RAN node 506 may not select the UE to send the new management based logged MDT configuration, if the UE has an ongoing signaling based logged MDT configuration according to the remaining valid time for the existing ongoing signaling based logged MDT configuration in the recently received logged MDT configuration check response message from CN.

Example Embodiment 5

FIG. 6 illustrates an signaling procedure 600 for logged MDT configuration corresponding to a fifth example embodiment. In step 612, the CN 602 can send a signaling based logged MDT configuration to a RAN node (RAN node1 604) serving a UE 608.

In step 614, the RAN node can send the signaling based logged MDT configuration to the UE.

In step 616, the UE 608 can go to idle state and starts the logged MDT measurement according to the received logged MDT configuration.

In step 618, the UE 608 can move to a new RAN node (RAN node2 606) and goes to connected state. The UE can send the RRCSetupComplete message to the new RAN node.

In step 620, the CN 602 can send at least one of an indication indicating whether an ongoing signaling based logged MDT configuration exists for the UE, a remaining valid time for the existing ongoing signaling based logged MDT configuration to the new RAN node, included in the INITIAL CONTEXT SETUP REQUEST message.

In step 622, the OAM 610 can send a management based logged MDT configuration to the new RAN node.

In step 624, the new RAN node 606 may not select the UE to send the management based logged MDT configuration, if the UE has an ongoing signaling based logged MDT configuration according to the received remaining valid time for the existing ongoing signaling based logged MDT configuration.

Example Embodiment 6

FIG. 7 illustrates an example signaling process 700 for logged MDT configuration corresponding to a sixth example embodiment. In step 712, the OAM 710 can send a management based logged MDT configuration to a RAN node (RAN node1 704) . The configuration can include an indication indicating the priority of logged MDT configuration. For example, the indication indicates whether a logged MDT configuration can be overwritten by another logged MDT configuration, or the indication indicates whether a logged MDT configuration is prioritized. As another example, the indication can be presented as an optional IE with one value of ‘not allowed’ and absence of the indication means ‘allowed, ’ or the indication can be presented as an optional IE with one value of ‘prioritized’ and absence of the indication means ‘normal. ’

In step 714, the RAN node can select one or more UE and sends the management based logged MDT configuration to the selected UE.

In step 716, the RAN node can send to CN 702 at least one of an indication indicating the priority of logged MDT configuration, a time duration for the UE in the CELL TRAFFIC TRACE message.

In step 718, the UE 708 can go to inactive state and starts the logged MDT measurement according to the received logged MDT configuration.

In step 720, the UE 708 can move to a new RAN node (RAN node2 706) and goes to connected state. The UE can send the RRCResumeComplete message to the new RAN node.

In step 722, the new RAN node can send the PATH SWITCH REQUEST message to CN.

In step 724, the CN 702 can send at least one of an indication indicating whether an ongoing management based logged MDT configuration exists for the UE and a remaining valid time for the existing ongoing management based logged MDT configuration to the new RAN node, which can be included in the PATH SWITCH REQUEST ACKNOWLEDGE message.

In step 726, when CN wants to send an signaling based logged MDT configuration to a RAN node serving a UE, it may take the indication indicating the priority of logged MDT configuration and/or the time duration for the UE received in the CELL TRAFFIC TRACE message into account. For example, if the indication indicating the priority of logged MDT configuration received in the CELL TRAFFIC TRACE message is ‘prioritized’ and the logged MDT configuration is ongoing according to the received time duration, and the signaling based logged MDT configuration is a ‘normal’ one, then the signaling based logged MDT configuration for the UE may not be sent.

In step 728, the OAM 710 may send a management based logged MDT configuration to the new RAN node.

In step 730, the new RAN node may not select the UE to send the management based logged MDT configuration, if an ongoing management based logged MDT configuration exists for the UE, according to the received indication indicating whether an ongoing management based logged MDT configuration exists for the UE, remaining valid time for the existing ongoing management based logged MDT configuration, included in the PATH SWITCH REQUEST ACKNOWLEDGE message from CN.

Example Embodiment 6A

When a RAN node receives a management based logged MDT configuration including a time duration from an OAM node, and the RAN node may not send the logged MDT configuration to a UE immediately duo to the UE is not in connected state, the RAN node can save the logged MDT configuration. When the UE goes to connected state, and if the logged MDT configuration is still valid according to the time duration and the time point the logged MDT configuration is received from OAM, the RAN node can send the management based logged MDT configuration to the UE and set the time duration to the remaining valid time.

Example Embodiment 6B

When a RAN node receives a signaling based logged MDT configuration including a time duration from CN for a UE, and the RAN node may not send the logged MDT configuration to the UE immediately duo to the UE is not in connected state, the RAN node can save the logged MDT configuration. When the UE goes to connected state, and if the logged MDT configuration is still valid according to the time duration and the time point the logged MDT configuration is received from CN, the RAN node can send the signaling based logged MDT configuration to the UE and set the time duration to the remaining valid time.

Example Embodiment 6C

When a RAN node receives a signaling based logged MDT configuration including a time duration from CN for a UE, and the RAN node may not send the logged MDT configuration to the UE immediately duo to the UE is not in connected state, the RAN node can save the logged MDT configuration. When the UE goes to connected state to a new RAN node, and if the new RAN node sends a RETRIEVE UE CONTEXT REQUEST message to the old RAN node, and if the logged MDT configuration is still valid according to the time duration and the time point the logged MDT configuration is received from CN, the old RAN node can send the signaling based logged MDT configuration to the new RAN node and set the time duration to the remaining valid time, included in the RETRIEVE UE CONTEXT RESPONSE message.

Example Embodiment 6D

If the remaining valid time in any of example embodiments 6A-6C is not one of pre-set values, for example, the pre-set values are 10, 20, 40, 60, 90 and 120 minutes, the remaining valid time can be 66, to set the time duration to the nearest one of pre-set values (i.e. 60) or the next upper one of pre-set values (i.e. 90) .

Example Embodiment 6E

The remaining valid time in the example embodiment 6A can be calculated as the time duration minus the time past from the time point the logged MDT configuration received from OAM to the moment the logged MDT configuration sending to the UE. The remaining valid time in the example embodiment 6B can be calculated as the time duration minus the time past from the time point the logged MDT configuration received from CN to the moment the logged MDT configuration sending to the UE. The remaining valid time in the example embodiment 6C can be calculated as the time duration minus the time past from the time point the logged MDT configuration received from CN to the moment the logged MDT configuration sending to the new RAN node.

Example Embodiment 7

FIG. 8 illustrates an example signaling process 800 for on demand other SI corresponding to an seventh example embodiment. In step 808, the RAN node1 804 can send a configuration information for on demand other SI event triggered logging to a UE 802.

In step 810, the UE 802 can go to idle or inactive state and starts the on demand other SI event triggered logging according to the received configuration information.

When on demand other SI failure occurs, the UE can log at least one of: the message type of on demand other SI request (e.g. Msg1, Msg3, or MsgA) , the requested SI messages, the requested SIBs, the number of modification periods the UE attempts to receive, the approach of on demand other SI request (e.g. associating to PRACH preamble and/or PRACH resource, sending RRCSystemInfoRequest message) if MsgA is used, the current configured value of modification period, the current configured value of SI-window, the SI messages failed to receive, the SIBs failed to receive, whether the on demand other SI response message (e.g. Msg2, Msg4, or MsgB) has been received, the current configured value of si-Periodicity of SI messages failed to receive.

When on demand other SI succeeds and some condition matches (e.g., the number of SI-windows the UE attempts to receive is larger then a configured value or pre-set value) , the UE can log at least one of: the message type of on demand other SI request (e.g. Msg1, Msg3, or MsgA) , the requested SI messages, the requested SIBs, the number of modification periods the UE attempts to receive, the approach of on demand other SI request (e.g. associating to PRACH preamble and/or PRACH resource, sending RRCSystemInfoRequest message) if MsgA is used, the current configured value of modification period, the current configured value of SI-window, the number of SI-windows the UE attempts to receive.

In step 812, the UE 802 can go to connected state in RAN node2 806 (RAN node2 and RAN node1 maybe the same RAN node) . The UE sends a availability indication to the RAN node2 to indicate the availability of logging information of on demand other SI, in the RRCSetupComplete message or RRCResumeComplete message.

In step 814, the RAN node2 806 can send the UEInformationRequest message to the UE 802, carrying a request indication for logging information of on demand other SI.

In step 816, the UE 802 can send the UEInformationResponse message to the RAN node2, carrying the logging information of on demand other SI.

In step 818, the RAN node2 806 can send the received logging information of on demand other SI to the RAN node1, if RAN node2 and RAN node1 is not the same and the received logging information is for RAN node1.

FIG. 9 is a block diagram of an example method 900 for configuring of logged Minimization of Driving Test (MDT) configurations. The method can include receiving, by a first network node, a first message from a terminal, the first message including a status of a logged driving test minimization configuration (block 902) . The method can also include determining, by the first network node, whether to select the terminal to send a new logged driving test minimization configuration according to the status of the logged driving test minimization configuration (block 904) .

In some embodiments, the terminal is configured to receive a second message from a second network node, the second message including a priority of the logged driving test minimization configuration.

In some embodiments, the second network node is configured to receive the priority of the logged driving test minimization configuration in a third message from a core network node or a management network node.

In some embodiments, the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged minimization of driving test (MDT) configuration and the ongoing MDT configuration is not allowed to be overwritten.

In some embodiments, the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged MDT configuration and the ongoing logged MDT configuration is prioritized.

In some embodiments, the priority of the logged driving test minimization configuration indicates that the logged driving test minimization configuration is not allowed to be overwritten by another logged driving test minimization configuration or the priority of the logged driving test minimization configuration indicates that the logged driving test minimization configuration is prioritized.

In some embodiments, the priority of the logged driving test minimization configuration is presented as an information element (IE) that includes a value of not allowed, wherein an absence of the IE includes a value of allowed.

In some embodiments, the priority of the logged driving test minimization configuration is presented as an IE that includes a value of prioritized, wherein an absence of the IE includes a value of normal.

In some embodiments, the first message is any of a RRCSetupComplete message or a RRCResumeComplete message.

In some embodiments, the second message is a LoggedMeasurementConfiguration message from the second network node to the terminal.

In some embodiments, the third message is any of a trace start message from the core network node to the second network node, and an initial context setup request message from the core network node to the second network node.

In another embodiment, a method for wireless communication can include receiving, by a terminal, a first message including a logged driving test minimization configuration that includes a priority of the logged driving test minimization configuration from a first network node; and performing, by the terminal, a logged driving test minimization measurement based on the logged driving test minimization configuration when the terminal is in an idle or inactive state.

In some embodiments, the method includes transmitting, by the terminal, a second message to a second network node that includes a status of the logged driving test minimization configuration.

In some embodiments, the second network node is configured to determine whether to select or not select the terminal to send a new logged driving test minimization configuration based on the status of the logged driving test minimization configuration.

In some embodiments, the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged driving test minimization configuration and the logged driving test minimization configuration is not allowed to be overwritten.

In some embodiments, the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged driving test minimization configuration and the logged driving test minimization configuration is prioritized.

In some embodiments, the first message is a LoggedMeasurementConfiguration message.

In some embodiments, the second message is any of a RRCSetupComplete message or a RRCResumeComplete message.

In another embodiment, a method for wireless communication can include receiving, by a first network node, a first message from a core network node, the first message including a first set of information for the logged driving test minimization configuration; and determining, by the first network node, whether to select or not select a terminal to send a new logged driving test minimization configuration based on the first set of information for the logged driving test minimization configuration.

In some embodiments, the first set of information includes any of: an indication of whether an ongoing logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing logged driving test minimization configuration, a type of the ongoing the logged driving test minimization configuration that includes any of a signaling-based type or a management-based type, and a priority of the ongoing logged driving test minimization configuration.

In some embodiments, the first set of information includes any of: an indication of whether an ongoing signaling-based logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing signaling-based logged driving test minimization configuration, and/or a priority of the ongoing signaling-based logged driving test minimization configuration.

In some embodiments, the first information includes any of: an indication of whether an ongoing management-based logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing management-based logged driving test minimization configuration, and/or a priority of the ongoing management-based logged driving test minimization configuration.

In some embodiments, a second network node is configured to send a second message to a core network node, the second message including any of a priority of the logged driving test minimization configuration and/or a time duration for the terminal.

In some embodiments, the first message is any of: a logged minimization of driving test (MDT) configuration check response message, an initial context setup request message, and/or a path switch request acknowledge message.

In some embodiments, the second message is a cell traffic trace message.

In some embodiments, the first network node will not select the terminal to send the new logged driving test minimization configuration due to the first message indicating that an ongoing signaling-based logged driving test minimization configuration exists.

In some embodiments, the first network node will not select the terminal to send the new logged driving test minimization configuration in a case that a priority for a management-based logged driving test minimization configuration is lower than or equal to a priority of an ongoing signaling-based logged driving test minimization configuration.

In some embodiments, the method includes sending, by the first network node, a logged driving test minimization configuration check request message to a core network node; and receiving, by the first network node, a logged driving test minimization configuration check response message from the core network node.

Example Wireless System

FIG. 10 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied. A wireless communication system 1000 can include one or more base stations (BSs) 1005a, 1005b, one or more wireless devices or

terminals

1010a, 1010b, 1010c, 1010d, and a core network 1025. A base station 1005a, 1005b can provide wireless service to

wireless devices

1010a, 1010b, 1010c and 1010d in one or more wireless sectors. In some implementations, a base station 1005a, 1005b includes directional antennas to produce two or more directional beams to provide wireless coverage in different sectors. The base station may implement functionalities of a scheduling cell or a candidate cell, as described in the present document.

The core network 1025 can communicate with one or more base stations 1005a, 1005b. The core network 1025 provides connectivity with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to the subscribed

wireless devices

1010a, 1010b, 1010c, and 1010d. A first base station 1005a can provide wireless service based on a first radio access technology, whereas a second base station 1005b can provide wireless service based on a second radio access technology. The base stations 1005a and 1005b may be co-located or may be separately installed in the field according to the deployment scenario. The

wireless devices

1010a, 1010b, 1010c, and 1010d can support multiple different radio access technologies.

In some implementations, a wireless communication system can include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that could be used to connect to different wireless networks.

FIG. 11 is a block diagram representation of a portion of a hardware platform. A hardware platform 1105 such as a network node or a base station or a terminal or a wireless device (or UE) can include processor electronics 1110 such as a microprocessor that implements one or more of the techniques presented in this document. The hardware platform 1105 can include transceiver electronics 1115 to send and/or receive wired or wireless signals over one or more communication interfaces such as antenna 1120 or a wireline interface. The hardware platform 1105 can implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 1105 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 1110 can include at least a portion of the transceiver electronics 1115. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the hardware platform 1105.

Conclusion

From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.

The disclosed and other embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document) , in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code) . A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit) .

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub combination or variation of a sub combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few implementations and examples are described, and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.

Claims

A method for wireless communication, comprising:

receiving, by a first network node, a first message from a terminal, the first message including a status of a logged driving test minimization configuration; and

determining, by the first network node, whether to select the terminal to send a new logged driving test minimization configuration according to the status of the logged driving test minimization configuration.
The method of claim 1, wherein the terminal is configured to receive a second message from a second network node, the second message including a priority of the logged driving test minimization configuration.
The method of claim 2, wherein, the second network node is configured to receive the priority of the logged driving test minimization configuration in a third message from a core network node or a management network node.
The method of claim 1, wherein the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged minimization of driving test (MDT) configuration and the ongoing MDT configuration is not allowed to be overwritten.
The method of claim 1, wherein the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged MDT configuration and the ongoing logged MDT configuration is prioritized.
The method of any of claims 2 and 3, wherein the priority of the logged driving test minimization configuration indicates that the logged driving test minimization configuration is not allowed to be overwritten by another logged driving test minimization configuration or the priority of the logged driving test minimization configuration indicates that the logged driving test minimization configuration is prioritized.
The method of claim 6, wherein the priority of the logged driving test minimization configuration is presented as an information element (IE) that includes a value of not allowed, wherein an absence of the IE includes a value of allowed.
The method of claim 6, wherein the priority of the logged driving test minimization configuration is presented as an IE that includes a value of prioritized, wherein an absence of the IE includes a value of normal.
The method of claim 1, wherein the first message is any of a RRCSetupComplete message or a RRCResumeComplete message.
The method of claim 2, wherein the second message is a LoggedMeasurementConfiguration message from the second network node to the terminal.
The method of claim 3, wherein the third message is any of a trace start message from the core network node to the second network node, and an initial context setup request message from the core network node to the second network node.
A method for wireless communication, comprising:

receiving, by a terminal, a first message including a logged driving test minimization configuration that includes a priority of the logged driving test minimization configuration from a first network node; and

performing, by the terminal, a logged driving test minimization measurement based on the logged driving test minimization configuration when the terminal is in an idle or inactive state.
The method of claim 12, further comprising:

transmitting, by the terminal, a second message to a second network node that includes a status of the logged driving test minimization configuration.
The method of claim 13, wherein the second network node is configured to determine whether to select or not select the terminal to send a new logged driving test minimization configuration based on the status of the logged driving test minimization configuration.
The method of claim 13, wherein the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged driving test minimization configuration and the logged driving test minimization configuration is not allowed to be overwritten.
The method of claim 13, wherein the status of the logged driving test minimization configuration indicates that the terminal has an ongoing logged driving test minimization configuration and the logged driving test minimization configuration is prioritized.
The method of claim 12, wherein the first message is a LoggedMeasurementConfiguration message.
The method of claim 13, wherein the second message is any of a RRCSetupComplete message or a RRCResumeComplete message.
A method for wireless communication, comprising:

receiving, by a first network node, a first message from a core network node, the first message including a first set of information for the logged driving test minimization configuration; and

determining, by the first network node, whether to select or not select a terminal to send a new logged driving test minimization configuration based on the first set of information for the logged driving test minimization configuration.
The method of claim 19, wherein the first set of information includes any of: an indication of whether an ongoing logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing logged driving test minimization configuration, a type of the ongoing the logged driving test minimization configuration that includes any of a signaling-based type or a management-based type, and a priority of the ongoing logged driving test minimization configuration.
The method of claim 19, wherein the first set of information includes any of: an indication of whether an ongoing signaling-based logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing signaling-based logged driving test minimization configuration, and/or a priority of the ongoing signaling-based logged driving test minimization configuration.
The method of claim 19, wherein the first information includes any of: an indication of whether an ongoing management-based logged driving test minimization configuration exists for the terminal, a remaining valid time for an existing ongoing management-based logged driving test minimization configuration, and/or a priority of the ongoing management-based logged driving test minimization configuration.
The method of claim 19, wherein a second network node is configured to send a second message to a core network node, the second message including any of a priority of the logged driving test minimization configuration and/or a time duration for the terminal.
The method of claim 19, wherein the first message is any of: a logged minimization of driving test (MDT) configuration check response message, an initial context setup request message, and/or a path switch request acknowledge message.
The method of claim 23, wherein the second message is a cell traffic trace message.
The method of claim 19, wherein the first network node will not select the terminal to send the new logged driving test minimization configuration due to the first message indicating that an ongoing signaling-based logged driving test minimization configuration exists.
The method of claim 19, wherein the first network node will not select the terminal to send the new logged driving test minimization configuration in a case that a priority for a management-based logged driving test minimization configuration is lower than or equal to a priority of an ongoing signaling-based logged driving test minimization configuration.
The method of claim 19, further comprising:

sending, by the first network node, a logged driving test minimization configuration check request message to a core network node; and

receiving, by the first network node, a logged driving test minimization configuration check response message from the core network node.
An apparatus for wireless communication comprising a processor that is configured to carry out the method of any of claims 1 to 28.
A non-transitory computer readable medium having code stored thereon, the code when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 28.