UE assistance information evaluation

Abstract

This document relates to methods, systems, and apparatus, related to digital wireless communications, and more particularly, to techniques related to evaluation of UE assistance information. In one example aspect, a method for data communication is disclosed. The method includes transmitting, by a network node, a first message including a set of configuration information to a terminal. The method also includes receiving, by the network node, a second message from the terminal, the second message including a set of reporting information based on the set of configuration information. The method further includes comparing, by the network node, the set of reporting information to a set of assistance information to determine whether the set of assistance information corresponds to the set of reporting information, the set of assistance information received from the terminal.

Description

TECHNICAL FIELD

[0001] This patent document generally relates to wireless communication. BACKGROUND

[0002] Mobile communication technology is leading the world to a more connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency, are also important to meet the needs of various communication scenarios. Various techniques are now discussed, including new ways to provide higher quality of service. SUMMARY

[0003] This document discloses methods, systems, and devices related to digital wireless communications, and more specifically, techniques related to UE assistance information evaluation.

[0004] In one example aspect, a method for data communication is disclosed. The method includes transmitting, by a network node, a first message comprising a set of configuration information to a terminal. The method also includes receiving, by the network node, a second message from the terminal, the second message comprising a set of reporting information based on the set of configuration information. The method further includes comparing, by the network node, the set of reporting information to a set of assistance information to determine whether the set of assistance information corresponds to the set of reporting information, the set of assistance information received from the terminal.

[0005] In one example aspect, a method for data communication is disclosed. The method includes transmitting, by a network node, a first message comprising a set of configuration information to a terminal. The method also includes receiving, by the network node, a second message from the terminal, the second message comprising a set of reporting information based on the set of configuration information. The method further includes obtaining, by the network node, a minimization of drive test (MDT) measurement based on the set of reporting information.

[0006] In another example aspect, a wireless communication device includes a processor. The processor is configured to implement a method described herein.

[0007] In yet another example aspect, the various techniques described herein can be embodied as processor-executable code and can be stored on a computer-readable program medium.

[0008] The details of one or more implementations are set forth in the accompanying attachments, drawings and description below. Other features will be apparent from a reading of the following detailed description and a review of the associated drawings. BRIEF DESCRIPTION OF DRAWINGS

[0009] Figure 1 For illustration of an example 5G network architecture;

[0010] Figure 2An example signaling flow for UE assistance information reporting is shown;

[0011] Figure 3 A signaling flow for evaluating UE assistance information according to a first example embodiment;

[0012] Figure 4 A signaling flow for evaluating UE assistance information according to a second example embodiment;

[0013] Figure 5 A signaling flow for evaluating UE assistance information according to a third example embodiment;

[0014] Figure 6 A signaling flow for evaluating UE assistance information according to a fourth example embodiment;

[0015] Figure 7 A signaling flow for evaluating UE assistance information according to a fifth example embodiment;

[0016] Figure 8 A signaling flow for evaluating UE assistance information according to a sixth example embodiment;

[0017] Figure 9 A signaling flow for evaluating UE assistance information according to a seventh example embodiment;

[0018] Figure 10 A block diagram of an example method for evaluating UE assistance information;

[0019] Figure 11 An example of a wireless communication system is shown in which techniques according to one or more embodiments of the technology can be applied;

[0020] Figure 12 A block diagram representation of a portion of a hardware platform. DETAILED DESCRIPTION

[0021] Section headings are used in this document for ease of understanding and do not limit the scope of embodiments to the sections into which they are described. Furthermore, although embodiments are described with reference to a 5G example, the disclosed technology can be applicable to wireless systems that utilize protocols other than 5G or 3GPP protocols.

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

[0023] Figure 1 An example 5G network architecture 100 is shown. As shown, a fifth generation (5G) network architecture can include a 5G core network (5GC) and a next generation radio access network (NG-RAN). The 5GC can include any of an Access Mobility Function (AMF), a Session Management Function (SMF), and a User Plane Function (UPF). The NG-RAN can include base stations with different radio access technologies (RATs), such as evolved 4G base stations (ng-eNBs), 5G base stations (gNBs). The NG-RAN base stations can be connected to the 5GC through an NG interface, and the NG-RAN base stations can be connected through an Xn interface. Figure 1

[0024] Figure 2 An example signaling procedure for user equipment (UE) assistance information reporting 200 is shown. The purpose of this procedure is for the UE to inform the network about assistance information for power saving or handling overheating, in-device coexistence (IDC) issues, etc. In Figure 2 , a network node 204 can send an RRC reconfiguration message 206 to a UE 202. The UE 202 can send UE assistance information 208 to the network node 204.

[0025] However, the UE can report the UE assistance information more aggressively, or vice versa under certain considerations. For example, the UE can report that its preference for the maximum number of secondary component carriers is 0 (i.e., disabling carrier aggregation) to achieve the ultra-long battery life advertised in the advertisement. As another example, the UE can report that its preference for the maximum number of secondary component carriers is the maximum number of secondary serving cells to achieve the ultra-high throughput performance advertised in the advertisement.

[0026] System overview

[0027] This embodiment can involve evaluation of the UE assistance information. This can assist the network to evaluate whether the UE assistance information reported from the UE is too aggressive or vice versa.

[0028] ​The UE may report a first report information message to the network. The first report information message may include at least one of the following: average scheduling intervals for both downlink and uplink, average downlink scheduling interval, average uplink scheduling interval, number of physical downlink control channel (PDCCH) receptions per discontinuous reception (DRX) cycle or per configured time period, average percentage of active time in DRX cycles, number of consecutive DRX cycles with an active time percentage exceeding a configured threshold, number of DRX cycles with an active time percentage exceeding a configured threshold within a configured time period, the UE's current temperature, predicted hold-up time (after which the UE may have serious problems if the UE temperature does not decrease), severity of in-device coexistence (IDC) problems, interference measurements related to IDC problems, predicted throughput, predicted latency requirements, predicted time periods during which the UE will not send or receive data, and predicted latency requirements if user preferences are adopted by the network. The remaining battery life is measured; the predicted remaining battery life is calculated in the case where the user preference will not be adopted by the network; the predicted remaining battery life is calculated; the percentage of remaining battery life is calculated; the level of remaining battery life is calculated (e.g., high, medium, low; another example is index 1, 2, ... 10 representing 10%, 20%, ... 100%); the estimated full battery life is calculated after 100% recharge; the average recharge interval of the UE; the percentage of time the remaining battery life is below a configured threshold; UE capability information; UE category; UE type (e.g., ordinary UE, industrial sensor, video surveillance, wearable device); and the received signal strength indication for each cross-link interference (cross-link interference). The periodic measurement results and CLI-RSSI resource index of the Link Interference Received Signal Strength Indication (CLI-RSSI) resource, the periodic reference signal received power (RSRP) measurement results and SRS resource index of each sounding reference signal (SRS) resource, the event-triggered measurement results (e.g., the triggered event I1 (interference becomes higher than the threshold)) and CLI-RSSI resource index of each CLI-RSSI resource, and the event-triggered RSRP measurement results (e.g., the triggered event I1 (interference becomes higher than the threshold)) and SRS resource index of each SRS resource.

[0029] By comprehensively comparing the first report information, the network can evaluate the information and / or preferences included in the UE assistance information message received from the UE. Alternatively, the first report information can be used for minimization of driving test (MDT) purposes (i.e., the first report information is the result of MDT measurement or a portion thereof). Alternatively, the first report information can be used for self-optimizing network (SON) purposes.

[0030] The first report information may be included in existing UE assistance information messages, existing UE information response messages, existing measurement report messages, or new messages. The network may send the first configuration information to the UE, and the UE reports the first report information based on the received first configuration information.

[0031] The first configuration information may include at least one of the following: requesting to report information on the average scheduling interval of both downlink and uplink; requesting to report information on the average downlink scheduling interval; requesting to report information on the average uplink scheduling interval; requesting to report information on the number of PDCCH receptions per DRX cycle or per configuration period; a configuration period for calculating the number of PDCCH receptions per configuration period; requesting to report information on the average percentage of active time in a DRX cycle; requesting to report information on the number of consecutive DRX cycles with an active time percentage higher than a configuration threshold; and / or a configuration threshold for calculating the number of consecutive DRX cycles with an active time percentage higher than a configuration threshold.

[0032] The first configuration information may include at least one of the following: information requesting a report on the number of DRX cycles in which the percentage of active time exceeds a configuration threshold during a configuration period; a configuration threshold and configuration period for calculating the number of DRX cycles in which the percentage of active time exceeds a configuration threshold during a configuration period; information requesting a report on the current temperature of the UE; information requesting a report on the predicted hold-up time (after which the UE may have serious problems if the UE temperature does not decrease); information requesting a report on the severity of in-device coexistence (IDC) problems; a configuration threshold for calculating the severity of IDC problems; information requesting a report on interference measurement results related to IDC problems; information requesting a report on the predicted throughput; information requesting a report on the predicted latency requirement; information requesting a report on the predicted period during which the UE will not send or receive data; information requesting a report on the predicted remaining battery life if the UE preference will be network-adopted; and / or information requesting a report on the predicted remaining battery life if the UE preference will not be network-adopted.

[0033] The first configuration information may include at least one of the following: requesting information on remaining battery operating time, requesting information on the percentage of remaining battery operating time, requesting information on the level of remaining battery operating time, requesting information on the estimated full battery operating time after 100% recharge, requesting information on the average recharge interval of the UE, and / or requesting information on the percentage of time during which the remaining battery operating time is less than a threshold.

[0034] The first configuration information may include at least one of the following: a configuration threshold for calculating the percentage of time when the remaining battery operating time is less than a configuration threshold; information requesting to report UE capability information; information requesting to report UE category; information requesting to report UE type (e.g., ordinary UE, industrial sensor, video surveillance, wearable device); information requesting to report periodic measurement results and CLI-RSSI resource indexes based on CLI-RSSI resources; information requesting to report periodic reference signal received power (RSRP) measurement results and SRS resource indexes for each SRS resource; information requesting to report event-triggered measurement results (e.g., triggered event I1 (interference becomes higher than the threshold)) and CLI-RSSI resource indexes for each CLI-RSSI resource; information requesting to report event-triggered RSRP measurement results (e.g., triggered event I1 (interference becomes higher than the threshold)) and SRS resource indexes for each SRS resource; a configuration time period for reporting periodic measurement results for each CLI-RSSI resource or SRS resource; and / or a configuration threshold for reporting event-triggered measurement results for each CLI-RSSI resource or SRS resource.

[0035] The first configuration information may be included in an existing radio resource control (RRC) reconfiguration message, an existing log-based measurement configuration message, or a new message.

[0036] Example embodiment 1

[0037] Figure 3 This is a signaling flow 300 for evaluating UE auxiliary information according to a first example embodiment.

[0038] At 306, UE 302 may report first reporting information to network 304. The first reporting information includes at least one of the following: average scheduling interval for both downlink and uplink, average downlink scheduling interval, average uplink scheduling interval, number of Physical Downlink Control Channel (PDCCH) receptions per discontinuous reception (DRX) cycle or per configured time period, average percentage of active time in DRX cycles, number of consecutive DRX cycles with an active time percentage exceeding a configured threshold, number of DRX cycles with an active time percentage exceeding a configured threshold within a configured time period, current temperature of the UE, predicted hold-up time (after which the UE may have serious problems if the UE temperature does not decrease), severity of in-device coexistence (IDC) problems, interference measurements related to IDC problems, predicted throughput, predicted latency requirements, predicted time period during which the UE will not transmit or receive data, predicted remaining battery life if the user preference will be adopted by the network, predicted remaining battery life if the user preference will not be adopted by the network, remaining battery life, remaining battery Percentage of operating time, level of remaining battery operating time (e.g., high, medium, low; another example index 1, 2, ... 10 represents 10%, 20%, ... 100%), estimated full battery operating time after 100% recharge, average recharge interval of the UE, percentage of time the remaining battery operating time is below a configured threshold, UE capability information, UE category, UE type (e.g., general UE, industrial sensor, video surveillance, wearable device), periodic measurements and CLI-RSSI resource index for each Cross-Link Interference Received Signal Strength Indication (CLI-RSSI) resource, periodic measurements and SRS resource index for each Sounding Reference Signal (SRS) resource, event-triggered measurements (e.g., triggered event I1 (interference becomes above the threshold)) and CLI-RSSI resource index for each CLI-RSSI resource, and / or event-triggered measurements (e.g., triggered event I1 (interference becomes above the threshold)) and SRS resource index for each SRS resource.

[0039] The first report information may be included in existing UE assistance information messages, existing UE information response messages, existing measurement report messages, or new messages.

[0040] At 308, using a comprehensive comparison of the first reported information, network 304 can assess the information and / or preferences included in the UE assistance information message received from the UE. For example, it can assess whether the information and / or preferences included in the UE assistance information are too positive or too negative.

[0041] Example embodiment 2

[0042] Figure 4 This is a signaling flow 400 for evaluating UE auxiliary information according to a second example embodiment.

[0043] At 406, network 404 may send first configuration information to UE 402. The first configuration information may include at least one of the following: requesting information on the average scheduling interval of both downlink and uplink; requesting information on the average downlink scheduling interval; requesting information on the average uplink scheduling interval; requesting information on the number of PDCCH receptions per DRX cycle or per configuration period; a configuration period for calculating the number of PDCCH receptions per configuration period; requesting information on the average percentage of active time in a DRX cycle; and / or requesting information on the number of consecutive DRX cycles in which the percentage of active events is higher than a configuration threshold.

[0044] The first configuration information may include at least one of the following: a configuration period for calculating the number of consecutive DRX cycles with an activity time percentage higher than a configuration threshold; information requesting a report on the number of DRX cycles with an activity time percentage higher than a configuration threshold within the configuration period; a configuration threshold and configuration period for calculating the number of DRX cycles with an activity time percentage higher than a configuration threshold within the configuration period; information requesting a report on the current temperature of the UE; information requesting a report on the predicted hold time (after which the UE may have a serious problem if the UE temperature does not decrease); information requesting a report on the severity of in-device coexistence (IDC) problems; and / or a configuration threshold for calculating the severity of IDC problems.

[0045] The first configuration information may include at least one of the following: requesting information on interference measurement results related to IDC issues, requesting information on predicted throughput, requesting information on predicted latency requirements, requesting information on predicted time periods during which the UE will not send or receive data, requesting information on predicted remaining battery life if the UE preference will be used by the network, requesting information on predicted remaining battery life if the UE preference will not be used by the network, requesting information on remaining battery life, requesting information on a percentage of remaining battery life, and / or requesting information on the level of remaining battery life.

[0046] The first configuration information may include at least one of the following: requesting information on the estimated full battery operating time after 100% recharge, requesting information on the average recharge interval of the UE, requesting information on the percentage of time the remaining battery operating time is less than a threshold, a configuration threshold for calculating the percentage of time the remaining battery operating time is less than a configured threshold, requesting information on UE capability information, requesting information on UE category, requesting information on UE type (e.g., ordinary UE, industrial sensor, video surveillance, wearable device), and / or requesting information on periodic measurement results and CLI-RSSI resource indexes for each CLI-RSSI resource.

[0047] The first configuration information may include at least one of the following: information requesting the reporting of periodic measurement results and SRS resource indexes for each SRS resource; information requesting the reporting of event-triggered measurement results (e.g., triggered event I1 (interference becomes higher than a threshold)) and CLI-RSSI resource indexes for each CLI-RSSI resource; information requesting the reporting of event-triggered measurement results (e.g., triggered event I1 (interference becomes higher than a threshold)) and SRS resource indexes for each SRS resource; a configured time period for reporting periodic measurement results for each CLI-RSSI resource or SRS resource; and / or a configured threshold for reporting event-triggered measurement results for each CLI-RSSI resource or SRS resource.

[0048] The first configuration information may be included in an existing Radio Resource Control (RRC) reconfiguration message, an existing log-based measurement configuration message, or a new message.

[0049] At 408, UE 402 can report first report information to network 404 based on the received first configuration information.

[0050] Example embodiment 3

[0051] Figure 5 This is a signaling procedure 500 for evaluating UE auxiliary information according to a third example embodiment.

[0052] In 506, UE 502 can report power saving preferences via UE Auxiliary Information Message.

[0053] At 508, network 504 sends the first configuration information to UE502 via a Radio Resource Control (RRC) reconfiguration message.

[0054] The first configuration information may include at least one of the following: information requesting a report of the percentage of remaining battery operating time, information requesting a report of the estimated full battery operating time after a 100% recharge, information requesting a report of the UE's average recharge interval, information requesting a report of the percentage of time the remaining battery operating time is less than a threshold, and / or a configuration threshold (e.g., 20%) used to calculate the percentage of time the remaining battery operating time is less than a configured threshold.

[0055] At 510, UE 502 may report first report information to network 504 via a measurement report message based on the received first configuration information. The first report information may include at least one of the following: the percentage of remaining battery operating time, the estimated full battery operating time after 100% recharge, the average recharge interval of the UE, and / or the percentage of time during which the remaining battery operating time is less than a configured threshold.

[0056] At 512, using the comprehensive comparison of the received first report information, network 504 can evaluate the received preference regarding power saving. For example, the network may consider the preference regarding power saving to be too aggressive; because the first report information indicates that the UE can have a long remaining battery life, can be recharged frequently, and rarely has less than 20% remaining battery life. The network may not adopt the preference regarding power saving from the UE, or may adopt an alternative approach regarding power saving.

[0057] Example embodiment 4

[0058] Figure 6 This is a signaling flow 600 for evaluating UE assistance information according to a fourth example embodiment. At 606, UE 602 can change its preference to leave the RRC_CONNECTED state via a UE assistance information message report.

[0059] At 608, network 604 may send first configuration information to the UE via a Radio Resource Control (RRC) reconfiguration message. The first configuration information may include at least one of the following: information requesting a report of a predicted period of time during which the UE will not send or receive data, information requesting a report of the percentage of remaining battery operating time, and / or information requesting a report of the estimated full battery operating time after 100% recharge.

[0060] At 610, UE 602 may report first report information to the network via a UE auxiliary information message based on the received first configuration information. The first report information may include at least one of the following: a predicted period of time during which the UE will not send or receive data, the percentage of remaining battery operating time, and the estimated full battery operating time after 100% recharge.

[0061] At 612, using the comprehensive comparison of the received first report information, network 604 can evaluate the received preference for transitioning out of the RRC_CONNECTED state. For example, the network may consider the preference for transitioning out of the RRC_CONNECTED state to be too aggressive; because the first report information indicates that the UE may have a long remaining battery life and the predicted period during which the UE will not send or receive data is short. The network may not adopt the preference for transitioning out of the RRC_CONNECTED state from the UE.

[0062] Example embodiment 5

[0063] Figure 7 This is a signaling flow 700 for evaluating UE auxiliary information according to a fifth example embodiment. At 706, network 702 can send first configuration information to the UE via a log-based measurement configuration message; the first configuration information may include at least one of the following: information requesting a report of the percentage of remaining battery operating time, information requesting a report of the estimated full battery operating time after 100% recharge, information requesting a report of the UE's average recharge interval, information requesting a report of the percentage of time the remaining battery operating time is less than a threshold, and / or a configuration threshold (e.g., 20%) for calculating the percentage of time the remaining battery operating time is less than a configured threshold.

[0064] At 708, UE 702 may send an indication of the availability of first report information to the network, which is included in the RRCResumeComplete message, RRCReestablishmentComplete message, RRCReconfigurationComplete message, or RRCSetupComplete message.

[0065] At 710, network 704 can send a request instruction for the first report information to UE 702 via a UE information request message.

[0066] In 712, UE 702 may report first reporting information to the network via a UE information response message based on a UE information request message. The first reporting information may include at least one of the following: the percentage of remaining battery operating time, the estimated full battery operating time after 100% recharge, the UE's average recharge interval, and / or the percentage of time during which the remaining battery operating time is less than a configured threshold.

[0067] In 714, UE 702 can report power saving preferences via UE Auxiliary Information Message.

[0068] At 716, by comprehensively comparing the received first report information, network 704 can evaluate the received preference regarding power saving. For example, the network may consider the preference regarding power saving to be too aggressive; because the first report information indicates that the UE can have a long remaining battery life, can be recharged frequently, and rarely has less than 20% remaining battery life. The network may not adopt the preference regarding power saving from the UE, or may adopt a more moderate approach to power saving.

[0069] Example embodiment 6

[0070] Figure 8 This is a signaling flow 800 for evaluating UE auxiliary information according to a sixth example embodiment.

[0071] At 806, network 804 may send first configuration information to the UE via a Radio Resource Control (RRC) reconfiguration message. The first configuration information may include at least one of the following: information requesting a report of a preference to switch away from the RRC_CONNECTED state, information requesting a report of the duration for which the UE predicts it will not receive or transmit data in the future, information requesting a report of the percentage of remaining battery operating time, and / or information requesting a report of the estimated full battery operating time after 100% recharging.

[0072] At 808, UE 802 may report first report information to the network via UE auxiliary information message based on the received first configuration information. The first report information may include at least one of the following: preference to switch out of the RRC_CONNECTED state, the duration for which the UE predicts it will not receive or transmit data in the future, the percentage of remaining battery operating time, and / or the estimated full battery operating time after 100% recharge.

[0073] At 810, using the comprehensive comparison of the received first report information, network 804 can evaluate the received preference for transitioning out of the RRC_CONNECTED state. For example, the network may consider the preference for transitioning out of the RRC_CONNECTED state to be too aggressive; because the first report information indicates that the UE may have a long remaining battery life and the UE predicts that the duration for which it will not receive or transmit data in the future is short. The network may not adopt the preference for transitioning out of the RRC_CONNECTED state from the UE.

[0074] Example embodiment 7

[0075] Figure 9 The signaling flow 900 according to the seventh example embodiment is used to minimize drive tests or self-optimizing networks.

[0076] In 906, UE 902 can report first report information to the network for the purpose of minimizing drive test (MDT) (i.e., the first report information is the MDT measurement result or a part thereof) or for the purpose of self-optimizing network (SON). The first report information may include at least one of the following: UE capability information, UE category, UE type (e.g., general UE, industrial sensor, video surveillance, wearable device), periodic measurement results and CLI-RSSI resource index for each Cross-Link Interference Received Signal Strength Indication (CLI-RSSI) resource, periodic reference signal received power (RSRP) measurement results and SRS resource index for each Sounding Reference Signal (SRS) resource, event-triggered measurement results (e.g., triggered event I1 (interference becomes higher than the threshold)) and CLI-RSSI resource index for each CLI-RSSI resource, event-triggered RSRP measurement results (e.g., triggered event I1 (interference becomes higher than the threshold)) and SRS resource index for each SRS resource, and a preamble group indication indicating whether preamble group A or preamble group B was used (this indication may be for each random access RA procedure or for each RA attempt within each RA procedure). This indication may be a one-bit indication, where a value of "0" indicates preamble group A and a value of "1" indicates preamble group B, or vice versa. Alternatively, the indication can be enumerated from group A or group B. Alternatively, the indication can be the presence of group B, i.e., the appearance of the indication refers to preamble group B, and the absence of the indication refers to preamble group A, or an indication of whether the PUSCH configuration is used for the physical uplink shared channel PUSCH group of preamble group A or preamble group B (this indication can be for each RA process or for each RA attempt within each RA process).

[0077] This indication can be a one-bit indication, where a value of "0" indicates the PUSCH configuration for preamble group A, and a value of "1" indicates the PUSCH configuration for preamble group B, or vice versa. Alternatively, the indication can be an enumeration of either group A or group B. Alternatively, the indication can be the presence of group B, meaning its presence indicates the PUSCH configuration for preamble group B, and its absence indicates the PUSCH configuration for preamble group A. Alternatively, this indication can be derived from the preamble group indication (if the preamble group indication uses preamble group A, then the PUSCH configuration for preamble group A is used; otherwise, the PUSCH configuration for preamble group B is used), the number of preambles transmitted for each cell in a 4-step RA (or type 1 RA), the number of preambles transmitted for each beam in each cell in a 4-step RA (or type 1 RA), the number of preambles transmitted for each cell in a 2-step RA (or type 2 RA), the number of preambles transmitted for each beam in each cell in a 2-step RA (or type 2 RA), and / or MsgA PUSCH information used to specify the PUSCH resource allocation for MsgA in a 2-step RA.

[0078] The MsgA PUSCH information may include at least one of the following: nID, the offset of the lowest PUSCH timing in the frequency domain relative to PRB0 (frequencyStartMsgA-PUSCH), the value of the hopping bits indicating the frequency offset for the second hopping (msgAHoppingBits), the intra-slot hopping for each PUSCH timing (msgAIntraSlotFrequencyHopping), the combination of the start symbol and length of the TDRA table and the PUSCH mapping type (msgA-PUSCH-TimeDomainAllocation), the single time offset relative to the start of each PRACH slot (msgA-PUSCH-TimeDomainOffse) (counted as the number of slots), and msgA in one time unit. The number of frequency domain multiplexed PUSCH timings (nrofMsgA-PO-FDM), the number of time domain PUSCH timings in each slot (nrofMsgA-PO-PerSlot), the number of PRBs for each PUSCH timing (nrofPRBs-PerMsgA-PO), the number of slots including one or more PUSCH timings (nrofSlotsMsgA-PUSCH), and / or an index giving the combination of start symbol, length, and mapping type as the start and length indicator for the first msgA PUSCH timing (startSymbolAndLengthMsgA-PO).

[0079] The first report information may be included in existing UE information response messages, existing measurement report messages, or new messages.

[0080] At 908, network 904 can process MDT measurement results. For example, the network can aggregate MDT measurement results for each UE category based on the receiving UE category. As another example, the network can better reduce cross-link interference based on CLI-RSSI and / or SRS-RSRP measurement results from the first reporting information of the MDT measurement results.

[0081] Example embodiment 8

[0082] Network nodes may calculate at least one of the following: the number of received random access preambles for each cell in 4-step access, the number of received random access preambles for each cell in 2-step access, the number of received random access preambles for each synchronization signal and physical broadcast channel block (SSB) in each cell in 4-step access, the number of received random access preambles for each SSB in each cell in 2-step access, the number of recovery requests received per cell, and / or the number of recovery requests received per RAN notification area; and send the calculation results to the trace collection entity (TCE).

[0083] Example embodiment 9

[0084] Network nodes may receive configuration information from core network nodes or OAM (operation and maintenance) nodes; the configuration information may include at least one of the following: requesting reports on the number of received random access preambles for each cell in 4-step access, requesting reports on the number of received random access preambles for each cell in 2-step access, requesting reports on the number of received random access preambles for each SSB in each cell in 4-step access, requesting reports on the number of received random access preambles for each SSB in each cell in 2-step access, requesting reports on the number of received connection recovery requests for each cell, and / or requesting reports on the number of received connection recovery requests for each RAN notification area; and perform calculations based on the configuration information.

[0085] Example embodiment 10

[0086] Network nodes can send measurement results to another network node (e.g., TCE). Measurement results can be used for MDT and / or SON purposes. Measurement results may include UE auxiliary information and / or updated UE auxiliary information received from the terminal and sent to the terminal. UE auxiliary information may include at least one of the following: a delay budget report of expected increment / decrement in the DRX cycle length of the bearer connection mode, overheating auxiliary information, IDC auxiliary information, preferences for DRX parameters regarding power saving, preferences for the maximum convergence bandwidth regarding power saving, preferences for the maximum number of auxiliary component carriers regarding power saving, preferences for the maximum number of MIMO (Multiple-Input Multiple-Output) layers regarding power saving, preferences for the minimum scheduling offset for cross-slot scheduling regarding power saving, auxiliary information for transitioning out of the RRC_CONNECTED state (in cases where the UE is not expected to send or receive data in the near future), a UE capability ID identifying the terminal's category, type, or model (which may be a vendor ID used to identify the terminal's vendor), and / or configuration authorization auxiliary information regarding NR-side downlink communication.

[0087] The information elements of UE auxiliary information (which need to be sent to another network along with the measurement results) can be configured or specified through the core network node or OAM node.

[0088] Example embodiment 11

[0089] The terminal may send measurement results to the network node. The measurement results may be used for MDT and / or SON purposes. The measurement results may include UE auxiliary information and / or updated UE auxiliary information reported to the network node and received from the network node. UE auxiliary information may include at least one of the following: a delay budget report of expected increment / decrement in the DRX cycle length of the bearer connection mode, overheating auxiliary information, IDC auxiliary information, preferences for DRX parameters regarding power saving, preferences for the maximum aggregation bandwidth regarding power saving, preferences for the maximum number of auxiliary component carriers regarding power saving, preferences for the maximum number of MIMO (Multiple-Input Multiple-Output) layers regarding power saving, preferences for the minimum scheduling offset for cross-slot scheduling regarding power saving, auxiliary information for transitioning out of the RRC_CONNECTED state (in cases where the UE is not expected to send or receive data in the near future), a UE capability ID identifying the terminal's category, type, or model (which may be a vendor ID used to identify the terminal's vendor), and / or configuration authorization auxiliary information regarding NR-side downlink communication.

[0090] The information elements of UE auxiliary information (which may need to be sent to the network node along with the measurement results) can be configured or specified through the network node.

[0091] Example embodiment 12

[0092] A network node may transmit measurement results to another network node (e.g., TCE) based on UE assistance information received from the terminal and / or updated UE assistance information sent to the terminal. The measurement results may include indications that the measurement result is invalid or that the network node does not transmit the measurement results to the other network node. UE assistance information may include at least one of the following: a delay budget report for expected increments / decrements in the DRX cycle length of the bearer connection mode; overheating assistance information; IDC assistance information; preferences for power-saving DRX parameters; preferences for maximum convergence bandwidth for power saving; preferences for the maximum number of power-saving secondary component carriers; preferences for the maximum number of power-saving MIMO (Multiple-Input Multiple-Output) layers; preferences for minimum scheduling offsets for power-saving cross-slot scheduling; assistance information for transitioning out of the RRC_CONNECTED state (when the UE is not expected to transmit or receive data in the near future); a UE capability ID identifying the terminal's category, type, or model (this UE capability ID may be a vendor ID used to identify the terminal's vendor); and / or configuration authorization assistance regarding NR-side downlink communication.

[0093] The information elements of UE auxiliary information can be configured or specified by the core network node or the OAM node; these information elements may be regarded as used to determine whether to send the measurement result to another network node, the measurement result including an indication that the measurement result is invalid or that the network node does not send the measurement result to another network node.

[0094] Example embodiment 13

[0095] The terminal may send measurement results to the network node based on UE assistance information reported to the network node and / or updated UE assistance information received from the network node. The measurement results may include indications that the measurement results are invalid or that the terminal has not sent the measurement results to the network node. UE assistance information may include at least one of the following: a delay budget report for expected increment / decrement in the DRX cycle length of the bearer connection mode; overheating assistance information; IDC assistance information; preferences for power-saving DRX parameters; preferences for maximum convergence bandwidth for power saving; preferences for the maximum number of power-saving secondary component carriers; preferences for the maximum number of power-saving MIMO (Multiple-Input Multiple-Output) layers; preferences for minimum scheduling offset for power-saving cross-slot scheduling; assistance information for transitioning out of the RRC_CONNECTED state (in cases where the UE is not expected to send or receive data in the near future); a UE capability ID identifying the terminal's category, type, or model (this UE capability ID may be a vendor ID used to identify the terminal's vendor); and / or configuration authorization assistance regarding NR-side downlink communication. Measurement results may be used for MDT and / or SON purposes.

[0096] The information elements of UE auxiliary information can be configured or specified by the network node; these information elements can be regarded as being used to determine whether to send the measurement result to the network node, the measurement result including indications that the measurement result may be invalid or that the terminal did not send the measurement result to the network node.

[0097] Figure 10 This is a block diagram of an example method 1000 for evaluating UE assistance information. The method may include: a network node sending a first message including a set of configuration information to a terminal (block 1002). The first message may include an RRC reconfiguration message, for example, such as... Figure 5 , Figure 6 or Figure 8 The subject of discussion.

[0098] The method may further include: receiving a second message from a terminal by a network node, the second message including a set of reporting information based on the set of configuration information (block 1004). The second message may include a first reporting information message (such as...). Figure 4 (as described) or measurement reports (e.g., relative to) Figure 5 (As described).

[0099] The method may further include: a network node comparing the set of reported information with a set of auxiliary information to determine whether the set of auxiliary information corresponds to the set of reported information, the set of auxiliary information being received from the terminal (block 1006). The method may include evaluating the set of reported information, for example, relative to... Figures 5 to 8 As described.

[0100] In another embodiment, the method for wireless communication may include: a network node transmitting a first message including a set of configuration information to a terminal. The method may further include: the network node receiving a second message from the terminal, the second message including a set of reporting information based on the set of configuration information. The method may further include: the network node obtaining a minimized drive test (MDT) measurement based on the set of reporting information.

[0101] In some embodiments, the set of auxiliary information is received before or after the second message.

[0102] In some embodiments, the set of auxiliary information is included in the second message.

[0103] In some embodiments, the group of reported information includes at least one of the following: the average scheduling interval for both downlink and uplink transmissions, the average downlink scheduling interval, the average uplink scheduling interval, the number of physical downlink control channel (PDCCH) receptions per discontinuous reception (DRX) cycle or per configuration period, the average percentage of active time in a DRX cycle, the number of consecutive DRX cycles with an active time percentage higher than a configuration threshold, and / or the number of DRX cycles with an active time percentage higher than a configuration threshold within a configuration period.

[0104] In some embodiments, the group of reported information includes at least one of the following: the terminal's current temperature, predicted hold time, severity of in-device coexistence (IDC), interference measurements related to the IDC, predicted throughput, predicted latency requirements, and / or the duration for which the terminal predicts it will not receive or transmit data in the future.

[0105] In some embodiments, the group of reported information includes at least one of the following: predicted remaining battery operating time when the parameter will be adopted by the network, predicted remaining battery operating time when the parameter will not be adopted by the network, remaining battery operating time, percentage of remaining battery operating time, level of remaining battery operating time, estimated full battery operating time after full recharge, average recharge interval of the terminal, and / or percentage of time when the remaining battery operating time is less than a configured threshold.

[0106] In some embodiments, the group of reported information includes at least one of the following: terminal capability information, terminal category, terminal type, periodic measurement results and CLI-RSSI resource index for each cross-link interference received signal strength indicator CLI-RSSI resource, periodic reference signal received power RSRP measurement results and SRS resource index for each sounding reference signal SRS resource, event-triggered measurement results and CLI-RSSI resource index for each CLI-RSSI resource, and / or event-triggered RSRP measurement results and SRS resource index for each SRS resource.

[0107] In some embodiments, the group of reported information is included in any of the UE assistance information message, UE information response message, and / or measurement report message.

[0108] In some embodiments, the set of configuration information includes any of the following: requesting reports of information including the average scheduling interval of both downlink and uplink transmissions, requesting reports of information on the average downlink scheduling interval, requesting reports of information on the average uplink scheduling interval, requesting reports of information on the number of PDCCH receptions per DRX cycle or per configuration period, and / or a configuration period for calculating the number of PDCCH receptions per configuration period.

[0109] In some embodiments, the set of configuration information includes any of the following: information requesting a report on the average percentage of active time in a DRX cycle, information requesting a report on the number of consecutive DRX cycles with an active time percentage higher than a configuration threshold, a configuration threshold for calculating the number of consecutive DRX cycles with an active time percentage higher than a configuration threshold, information requesting a report on the number of DRX cycles with an active time percentage higher than a configuration threshold within a configuration time period, and / or a configuration threshold and a configuration time period for calculating the number of DRX cycles with an active time percentage higher than a configuration threshold within a configuration time period.

[0110] In some embodiments, the set of configuration information includes any of the following: information requesting a report on the current temperature of the terminal, information requesting a report on the predicted hold time, information requesting a report on the severity of in-device coexistence (IDC), a configuration threshold for calculating the severity of the IDC, and / or information requesting a report on interference measurement results related to the IDC.

[0111] In some embodiments, the set of configuration information includes any of the following: information requesting a report on predicted throughput, information requesting a report on predicted latency requirements, and / or information requesting a report on the duration for which the terminal will not receive or send data in the future.

[0112] In some embodiments, the set of configuration information includes any of the following: requesting information on the predicted remaining battery operating time when the terminal's preferences will be adopted by the network node; requesting information on the predicted remaining battery operating time when the terminal's preferences will not be adopted by the network node; requesting information on the remaining battery operating time; requesting information on the percentage of remaining battery operating time; requesting information on the level of remaining battery operating time; requesting information on the estimated full battery operating time after a full recharge; and / or requesting information on the terminal's average recharge interval.

[0113] In some embodiments, the set of configuration information includes any of the following: information requesting a report of the percentage of time the remaining battery operating time is less than a threshold, a configuration threshold for calculating the percentage of time the remaining battery operating time is less than a configured threshold, information requesting a report of terminal capability information, information requesting a report of terminal category, and / or information requesting a report of terminal type.

[0114] In some embodiments, the set of configuration information includes any one of the following: information requesting the reporting of periodic measurement results and CLI-RSSI resource indexes for each CLI-RSSI resource; information requesting the reporting of periodic reference signal received power (RSRP) measurement results and SRS resource indexes for each SRS resource; information requesting the reporting of event-triggered measurement results and CLI-RSSI resource indexes for each CLI-RSSI resource; information requesting the reporting of event-triggered RSRP measurement results and SRS resource indexes for each SRS resource; a configured time period for reporting periodic measurement results for each CLI-RSSI resource or SRS resource; and / or a configured threshold for reporting event-triggered measurement results for each CLI-RSSI resource or SRS resource.

[0115] In some embodiments, the first message includes either a Radio Resource Control (RRC) reconfiguration message or a log-based measurement configuration message.

[0116] In some embodiments, the third message includes a UE assistance information message.

[0117] Example wireless system

[0118] Figure 11An example of a wireless communication system is illustrated, in which techniques according to one or more embodiments of the present invention can be applied. The wireless communication system 1100 may include one or more base stations (BS) 1105a, 1105b, one or more wireless devices or terminals 1110a, 1110b, 1110c, 1110d, and a core network 1125. Base stations 1105a, 1105b may provide wireless services to wireless devices 1110a, 1110b, 1110c, and 1110d in one or more wireless sectors. In some embodiments, base stations 1105a, 1105b include directional antennas to generate two or more directional beams to provide wireless coverage for different sectors. The base stations may implement the functions of a scheduling unit or candidate unit, as described in this document.

[0119] The core network 1125 can communicate with one or more base stations 1105a, 1105b. The core network 1125 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 wireless devices 1110a, 1110b, 1110c, and 1110d that have subscribed to services. The first base station 1105a can provide wireless services based on a first wireless access technology, while the second base station 1105b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 1105a and 1105b can be co-located or installed separately in the field. Wireless devices 1110a, 1110b, 1110c, and 1110d can support multiple different wireless access technologies.

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

[0121] Figure 12This is a block diagram representation of a hardware platform. Hardware platform 1205 (such as a network node, base station, terminal, or wireless device (or UE)) may include processor electronics 1210, such as a microprocessor, which implements one or more of the technologies proposed in this document. Hardware platform 1205 may include transceiver electronics 1215 for transmitting and / or receiving wired or wireless signals via one or more communication interfaces (such as antenna 1220) or wired interfaces. Hardware platform 1205 may implement other communication interfaces with defined protocols for transmitting and receiving data. Hardware platform 1205 may include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some embodiments, processor electronics 1210 may include at least a portion of transceiver electronics 1215. In some embodiments, at least some of the disclosed technologies, modules, or functions are implemented via hardware platform 1205.

[0122] Conclusion

[0123] The disclosed and other embodiments, modules, and functional operations described in this document may be implemented in digital electronic circuits, or in computer software, firmware, or hardware (including the structures disclosed in this document and their structural equivalents), or combinations thereof. The disclosed and other embodiments may 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 a data processing apparatus or for controlling the operation of a data processing apparatus. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material composition affecting machine-readable propagation signals, or combinations thereof. The term "data processing apparatus" covers all devices, apparatuses, and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program under consideration, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, or combinations thereof. The propagated signal is an artificially generated signal, such as an electrical, optical, or electromagnetic signal generated by a machine, which is used to encode information for output to a suitable receiver device.

[0124] Computer programs (also known as programs, software, software applications, scripts, or code) can be written in any form of programming language, including compiled or interpreted languages; and they can be deployed in any form, including as standalone programs, or as modules, components, subroutines, or other units suitable for a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored as a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document); stored in a single file dedicated to the program in question; or stored in multiple coordinating files (e.g., a file storing one or more modules, subroutines, or portions of code). Computer programs can be deployed to execute on one or more computers located at a single point or distributed across multiple points and interconnected via a communication network.

[0125] The processes and logic flows described in this document can be executed by one or more programmable processors, which execute one or more computer programs to perform functions by manipulating input data and generating output. Processes and logic flows can also be executed by dedicated logic circuitry, and the device can also be implemented as dedicated logic circuitry, such as FPGA (field programmable gate array) or ASIC (application-specific integrated circuit).

[0126] Processors suitable for executing computer programs include, for example, both general-purpose and special-purpose microprocessors, and one or more processors of any kind of digital computer. Generally, a processor receives instructions and data from read-only memory or random access memory, or both. The basic components of a computer are a processor (for executing instructions) and one or more memory devices (for storing instructions and data). Generally, a computer will also include data, or be operatively coupled to receive data from or transfer data to one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks. However, a computer does not necessarily need to 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, such as 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-ROMs and DVD-ROMs. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0127] While this patent document includes numerous details, these details should not be construed as limiting the scope of any invention or claimable content, but rather as descriptions of features that may be specific to particular embodiments of a particular invention. In the context of an independent embodiment, certain features described in this patent document may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, while features may be described above as functioning in certain combinations or even initially claimed in this manner, in some cases, one or more features of the claimed combination may be removed from that combination, and the claimed combination may involve sub-combinations or variations thereof.

[0128] Similarly, although operations are described in a specific order in the accompanying drawings, this should not be construed as requiring such materials to be performed in the specific order shown or in sequential order, or that all shown operations should be performed to achieve the desired result. Furthermore, the separation of various system components in the embodiments described in this patent document should not be construed as requiring such separation in all embodiments.

[0129] Only a few implementation methods and examples have been described, and other implementation methods, improvements and variations may be made based on what is described and shown in this patent document.

Claims

1. A method for wireless communication, comprising: The terminal reports its power-saving preferences to the network node; The network node sends the first configuration information to the terminal; The terminal reports first report information to the network node based on the received first configuration information; The network node uses the received first report information to evaluate the received power saving preference; The first report information includes at least one of the following: the level of remaining battery operating time, the estimated total battery operating time after a full charge, the average recharge interval of the terminal, and / or the percentage of time during which the remaining battery operating time is less than a configured threshold. The network nodes' preferences for evaluating the power savings include: When the first report information indicates that the remaining battery life of the terminal exceeds a threshold, the frequency of recharging exceeds a threshold, and the working time with remaining battery power below the threshold is less than the threshold, then it is determined that the power saving preference is too aggressive. If the power-saving preference is determined to be too aggressive, the network node will not adopt the power-saving preference from the terminal, or will adopt an alternative power-saving preference.

2. The method according to claim 1, wherein, The power-saving preference is reported via UE Assist Information, the first report information being included in the measurement report message, and the first configuration information being sent via Radio Resource Control (RRC) reconfiguration message.

3. The method of claim 1, wherein the first configuration information includes any one of the following: information requesting a report of the percentage of time during which the remaining battery operating time is less than a threshold, and the configuration threshold for calculating the percentage of time during which the remaining battery operating time is less than a configuration threshold.

4. A device for wireless communication, the device comprising a processor configured to perform the method according to any one of claims 1 to 3.

5. A non-transitory computer-readable medium having code stored thereon, said code causing the processor to perform the method according to any one of claims 1 to 3 when executed by a processor.

Images