Power state and context based data logging

Abstract

Example embodiments of the present disclosure relate to power state information based data logging. According to example embodiments, a user equipment (UE) may be provided. The UE may be configured to send a power state information report comprising a battery level and screen state to a base station; receive a radio resource control (RRC) message comprising one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and set the logging frequency of the UE based on the one or more logging parameters.

Description

POWER STATE AND CONTEXT BASED DATA LOGGINGTECHNICAL FIELD

[0001] The present disclosure relates to power state and context based data logging.BACKGROUND

[0002] The information disclosed in this background section is only for the enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0003] In the related art, telecommunications networks may need a user equipment (UE) to send measurement reports and / or performance data in order for the network to be able to make adjustments to the operation of the UE. In this regard, the UE may perform logging in order to collect the necessary data to be sent to the network.

[0004] Power state information may include aspects of how much power is being consumed by the UE. For example, this may include screen time usage, battery status, and power drain rate. Context information may include the environment of the UE. For example, this may be based on sensors and contextual data, including the mobility status of the UE.SUMMARY

[0005] Related art systems may have significant battery drain and high power consumption when performing data logging in UEs. This may be problematic in scenarios where the UE is needed to log large amounts of data over an extended time period. Meanwhile, the related art doesnot consider the power state information or context-based information when configuring the logging frequency of the data logger in the UE.

[0006] Accordingly, there is a need for a more dynamic method of configuring data logging frequency which considers power state information and context information.

[0007] Example embodiments of the present disclosure provide a system, method, and device for power state and context based data logging. According to example embodiments, a user equipment (EE) may be provided. The UE may be configured to send a power state information report comprising a battery level and screen state to a base station; receive a radio resource control (RRC) message comprising one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and set the logging frequency of the UE based on the one or more logging parameters.

[0008] Based on the above example embodiments, example effects which may be achieved may include a robust framework for dynamic logging adjustments based on real-time network and UE conditions.

[0009] According to example embodiments, a method may be provide including: sending, by a user equipment (UE) a power state information report including a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message including one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.

[0010] According to example embodiments, a non-transitory computer-readable recording medium may be provided, having recorded thereon instructions executable to perform a method including: sending, by a user equipment (UE) a power state information report including a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message including one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.

[0011] Additional aspects will be set forth in part in the description that follows and, in part, will be apparent from the description, or may be realized by practice of the presented embodiments of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0013] FIG. 1 illustrates an example callflow diagram for configuring a UE’s logging frequency based on power state information, according to one or more example embodiments;

[0014] FIG. 2 illustrates an example callflow diagram for configuring a UE’s logging frequency based on context state information, according to one or more example embodiments;

[0015] FIG. 3 illustrates a block diagram of an example method for determining logging frequency based on power state information, according to one or more example embodiments;

[0016] FIG. 4 illustrates a block diagram of an example method for determining logging frequency based on context state information, according to one or more example embodiments;

[0017] FIG. 5 illustrates a block diagram of an example method for updating a UE”s logging frequency based on a power state information report, according to one or more example embodiments;

[0018] FIG. 6 illustrates a block diagram of an example method for updating a UE”s logging frequency based on context state information report, according to one or more example embodiments;

[0019] FIG. 7 illustrates a block diagram of an example device for implementing one or more example embodiments; and

[0020] FIG. 8 illustrates a block diagram of an example environment for implementing one or more example embodiments.DETAILED DESCRIPTION

[0021] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0022] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to the described implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0023] Even though particular combinations of features are disclosed in the claims and / or in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0024] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]”, “[A] and / or [B]”, or “at least one of [A] or [B]”, are to be understood as including only A, only B, or both A and B.

[0025] It shall be noted that, descriptions of example embodiments of the present disclosure may include terms and names defined in one or more standard organizations, such asthe 3rd Generation Partnership Project (3GPP) standard organization, the EuropeanTelecommunications Standards Institute (ETSI) standard organization, the Open Radio AccessNetwork (O-RAN) Alliance standard organization, and the like.

[0026] According to example embodiments, energy-efficient logging mechanisms may be introduced which may include optimizing logging activities, and providing a smart logging scheduler. The energy-efficient logging mechanism may optimize the frequency and duration of logging activities to minimize UE power consumption. This may utilize low-power states of the UE to schedule logging activities. The mechanism may perform logging during periods of low activity, or when the UE is in a state where power consumption is naturally lower, such as idle times or when the screen is off.

[0027] The smart logging scheduler may activate logging only during low power usage periods or when critical events occur. The smart logging schedule may continuously monitor the UE’s power consumption and network activity, and adjust logging activities accordingly. The smart logging scheduler may use a combination of predefined rules and real-time data to decide optimal times for logging. For example, it may be programmed to avoid logging during high power consumption activities such as video streaming or gaming, and prioritize logging during activities like reading or idle periods. Adaptive algorithms may also be used to learn the user’s behavior and network conditions, in order to further optimize logging schedules, thereby ensuring minimal impact on the UE’s battery life.

[0028] According to example embodiments, context-aware logging mechanisms may be introduced which consider the UE’s environment based on sensors and contextual data in order to optimize logging settings. For example, logging may be less frequency when the UE is stationary, and more frequent when it is moving, or when significant (critical) network events occur.

[0029] A context detection mechanism may be provided which defines context state information such as UE mobility, signal strength, battery level, and network congestion, which may influence logging parameters. It may specify how the UE will detect and report these contexts to the network. For example, accelerometers may be used to detect motion, GPS may be used to determine location, and network indicators may be used for determining congestion levels. These measurements may be included in a context state information report and sent to the network (e.g., the base station).

[0030] Example embodiments may define dynamic logging parameter adjustment mechanisms which specifies logging parameters that may be dynamically adjusted, such as logging frequency and data granularity. The range of these parameters may be predetermined, and the conditions for their adjustment may also be defined. For example, logging frequency may range from one log per second in high mobility to one log per minute when stationary.

[0031] Example embodiments may also define a signaling mechanism for the network to communicate logging parameter adjustments to the UE. For example, example embodiments may utilize an RRC reconfiguration message to update logging settings based on network instructions. Sensor integration may also be provided by specifying the sensors which are needed for context detection, and defining their integration with their logging system. Specifically, it may be specified how the sensor’s data is used to adjust logging parameters.

[0032] Based on the above example embodiments, example effects which may be achieved may include a robust framework for dynamic logging adjustments based on real-time network and UE conditions.

[0033] It is contemplated that features, advantages, and significances of example embodiments described hereinabove are merely a portion of the present disclosure, and are notintended to be exhaustive or to limit the scope of the present disclosure. Further descriptions of the features, components, configuration, operations, and implementations of the example embodiments of the present disclosure are provided in the following.

[0034] FIG. 1 illustrates an example callflow diagram for configuring a UE’s logging frequency based on power state information, according to one or more example embodiments.

[0035] The RRC message may be sent from base station 100 to user equipment (UE) 110. Base station 100 may be, for example, a node such as gNodeB or eNodeB (for 5G and LTE respectively).

[0036] At step 1, UE 110 may send a measurement report including power state information to base station 100. Power state information may include a battery level (e.g., a percentage between 0 to 100%), and a screen state information (e.g., on or off). The power state information may also include further information such as what type of activity is being performed on the UE (e.g., streaming video, gaming), and other parameters may also be added depending on the specific implementation, as determined by a person skilled in the art.

[0037] At step 2, base station 100 may determine the logging frequency and logging parameters based on power state information. For example, it may firstly determine based on the battery level of the UE from step 1 whether the power state is normal (e.g., the battery level is equal to or above a predetermined threshold value such as 50%), or low power (e.g., the battery level is below a predetermined threshold value such as 50%). Base station 100 may also take into account the screen state information, and what type of activity is being performed on the UE. A detailed example of how base station determines the logging frequency and logging parameters is exemplified in FIG. 3 below, nevertheless it should be appreciated that other methods, such as amachine learning based approach for determining the optimal logging parameters may be used based on historical UE behavior as input.

[0038] The logging parameters may include the logging frequency (which may specify either in numerical values of frequency, or an enumerated list with “high”, “medium”, and “low” settings), and a power state (e.g., normal or low power states).

[0039] At step 3, base station 100 may send an RRC reconfiguration message including the logging parameters to UE 110. As indicated above, this may include the logging frequency and the power state as part of an information element (IE) to communicate the logging adjustments necessary by the UE.

[0040] At step 4, UE 110 may set the logging frequency based on the logging parameters. For example, if the logging frequency was specified in terms of the enumerated list with values of “high”, “medium”, and “low”, the UE may set it based on comparing it with a look-up table of frequency values. According to embodiments, this may include a range of allowable frequency values based on the enumerated list.

[0041] At step 5, UE 110 may reattempt logging adjustment of step 4 if logging adjustment failed. This may be performed after a predetermined time period (e.g., 10s).

[0042] FIG. 2 illustrates an example callflow diagram for configuring a UE’s logging frequency based on context state information, according to one or more example embodiments.

[0043] The RRC message may be sent from base station 100 to user equipment (UE) 110. Base station 100 may be, for example, a node such as gNodeB or eNodeB (for 5G and LTE respectively).

[0044] At step 1, UE 110 may send a measurement report including context state information to base station 100. Context information may include information such as a mobilitystatus as an enumerated list with “stationary”, “low speed”, and “high speed” as possible values. This may be determined, for example, based on an accelerometer sensor used to determine motion and GPS for location. Context information may also include battery level as a percentage value. Network congestion information may also be provided in the context information report.

[0045] At step 2, base station 100 may determine the logging frequency and logging parameters based on context state information. Logging parameters may include logging frequency as either a numerical value or an enumerated list with “high”, medium” and “low” settings, similar to the case with FIG. 1. Logging parameters may also further include data granularity as an enumerated list with values such as “fine” or coarse”, nevertheless it should be appreciated that more detailed parameters such as specifying the exact data points / data values which should be recorded may also be specified.

[0046] As an example, logging frequency may increase during high mobility, and be reduced during low mobility or stationary periods (since measurements are unlikely to change). Similarly, data granularity may be adjusted to be increased (more fine) during high mobility, and be reduced (more coarse) during low mobility (since measurements are unlikely to change). An example method for determining the logging parameters is exemplified in FIG. 4 below, nevertheless it should be appreciated that other methods, such as a machine learning based approach for determining the optimal logging parameters may be used.

[0047] At step 3, base station 100 may send an RRC reconfiguration message including logging parameters to UE 110. As indicated above, this may include the logging frequency and the data granularity as part of an information element (IE) to communicate the logging adjustments necessary by the UE.

[0048] At step 4, UE 110 may set the logging frequency based on the logging parameters. For example, if the logging frequency was specified in terms of “high”, “medium”, and “low”, the UE may set it based on comparing it with a lookup table. Data granularity may be set in a similar manner.

[0049] At step 5, UE 110 may reattempt logging adjustment of step 4 if logging adjustment failed. This may be performed after a predetermined time period (e.g., 10s).

[0050] FIG. 3 illustrates a block diagram of an example method for determining logging frequency based on power state information, according to one or more example embodiments.

[0051] At operation S301, the network may determine if the power state is low and the screen state is off. If yes, the network may set the logging frequency parameter to “low” in operation S302. Otherwise, the method may proceed to operation S303.

[0052] At operation S303, the network may determine if the power state is normal and the screen state is on. If yes, the network may set the logging frequency parameter to “high” in operation S304. Otherwise, the network may default to setting the logging frequency parameter to “medium” in operation S3O5.

[0053] As mentioned above, it should be appreciated that the method exemplified in FIG. 3 is a possible arrangement of an algorithm for determining logging frequency, and other algorithms such as a machine learning approach are possible, as implemented by a person skilled in the art.

[0054] FIG. 4 illustrates a block diagram of an example method for determining logging frequency based on context state information, according to one or more example embodiments.

[0055] At operation S401, the network may determine if the mobility status is high speed.If yes, the network may set the logging frequency parameter to “high” in operation S402.Otherwise, the system may proceed to operation S403.

[0056] At operation S403, the network may determine if the mobility status is low speed. If yes, the network may set the logging frequency parameter to “medium” in operation S404. Otherwise, the network may default to setting the logging frequency parameter to “low” in operation S405.

[0057] As mentioned above, it should be appreciated that the method exemplified in FIG.4 is a possible arrangement of an algorithm for determining logging frequency, and other algorithms such as a machine learning approach are possible, as implemented by a person skilled in the art. Further, the method illustrated in FIG. 4 may be modified to also include settings for the data granularity.

[0058] FIG. 5 illustrates a block diagram of an example method 500 for updating a UE”s logging frequency based on a power state information report, according to one or more example embodiments.

[0059] At operation S501 , the UE may send a power state information report to base station. The power state information report may include a battery level and screen state value.

[0060] At operation S502, the UE may receive an RRC message including logging parameters from the base station. The logging parameters may include a logging frequency and power state, and the logging frequency may have been configured by the base station based on the power state information report. Specifically, if the power state is low and the screen state is off, the logging frequency may be set to low. If the power state is normal and the screen state is on,then the logging frequency may be set to high. Otherwise, the power state may default to be medium.

[0061] At operation S503, the UE may adjust / set the logging frequency of the UE based on logging parameters. If logging frequency of the UE fails, then the UE may be configured to reattempt setting the logging frequency of the UE after a predetermined period of time.

[0062] FIG. 6 illustrates a block diagram of an example method 600 for updating a UE”s logging frequency based on context state information report, according to one or more example embodiments.

[0063] At operation S601, the UE may send a context state information report to base station. The context information report may include a mobility status and battery level (which may have been obtained based on sensors of the UE).

[0064] At operation S602, the UE may receive an RRC message including logging parameters from the base station. The logging parameters may include a logging frequency and data granularity. Of mobility status is high, the logging frequency may be high. If the mobility status is low, logging frequency may be medium. Otherwise, it may be assumed mobility status is stationary and logging frequency may be set to low.

[0065] At operation S603, the UE may adjust / set the logging frequency of the UE based on logging parameters. It should be appreciated that adjustments of the data granularity is also possible in a similar manner. If logging frequency of the UE fails, then the UE may be configured to reattempt setting the logging frequency of the UE after a predetermined period of time.

[0066] Based on the above example embodiments, example effects which may be achieved may include a robust framework for dynamic logging adjustments based on real-time network and UE conditions.

[0067] FIG. 7 illustrates a block diagram of an example device 700 for implementing one or more example embodiments. As shown in FIG. 7, the device 700 includes processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, and a bus 770.

[0068] The processor 710, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 710 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 710 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0069] Memory 720 includes a non-transitory computer readable medium. Memory 720 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 710. The memory 720 comprises machine-readable instructions which are executable by the processor 710. These machine-readable instructions when executed by the processor 710 cause the processor 710 to perform one or more method steps of an embodiment described above.

[0070] Storage component 730 stores information and / or software related to the operation and use of the device 700. For example, storage component 730 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0071] Input component 740 is configured to receive information, such as user input. For example, the input component 740 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 740 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0072] Output component 750 is configured to provide output information from the device 700. For example, the output component 750 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0073] Communication interface 760 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 760 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 700 and other devices. In other words, the standard of the communication interface 760 is not limited.

[0074] The bus 770 acts as an interconnect between the processor 710, the memory 720, the storage component 730, the input component 740, the output component 750, and the communication interface 760 of the device 700. The bus 770 may include a wired interconnection or a wireless interconnection.

[0075] The number and arrangement of components shown in FIG. 7 are provided as an example. In practice, device 700 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 7. Additionally, or alternatively, a set of components (e.g., one or more components) of device 700 may perform one or more functions described as being performed by another set of components of device 700.Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 700 in communication with one another.

[0076] Example embodiments of the present disclosure may be implemented in any suitable type of environment. In the following, an example environment (in which the example embodiments may be implemented) is described.

[0077] FIG. 8 illustrates a block diagram of an example environment 800 for implementing in which systems and / or method, described herein, may be implemented. The implementation environment 800 includes a UE (User equipment) 810, a service environment 820, and a network 830. The service environment 820 include one or more sub-environments 821. To illustrate this, FIG. 8 shows, for convenience, examples of a 1st sub-environment 821-1, a 2nd sub-environment 821-2, and an N-th sub-environment 821-N (where N is any natural number).

[0078] The UE 810 is connected to the network 830, and the network 830 is connected to the service environment 820. The connections may be wired, wireless, or a combination of both wired and wireless. The UE 810 and the service environment 820 are connected via the network 830.

[0079] The UE 810 is a device that communicates with the service environment 820. The UE 810 receives information from the service environment 820 and / or sends information to the service environment 820. Also, the UE 810 may generate and / or store information to be transmitted, as necessary. Also, the UE 810 may store and / or process information that is received, as necessary.

[0080] The example of FIG. 8 refers to the “UE”. However, it should be understood by those skilled in the art that general terms such as “user device,” “terminal,” “terminal device,”“communication device,” and “communication terminal” can be used interchangeably with the term “UE.”

[0081] For example, the UE 810 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device.

[0082] The service environment 820 is an environment that communicates with the UE 810 to provide one or more services. The service environment 820 receives information from the UE 810 and / or sends information to the UE 810. Also, the service environment 820 may generate and / or store information to be transmitted, as necessary. Also, the service environment 820 may store and / or process information that is received, as necessary. For example, the service environment 820 may provide computing resources as one of the services. It should be noted that the service is not limited to being provided to the UE; it may also be provided to devices other than the UE. For example, based on communication from the UE, the service may perform processes such as anomaly detection or traffic analysis and notify the results to a predetermined destination.

[0083] The example FIG. 8 refers to the “service environment”. The term "service environment" is used to refer to the broader context within which services operate. For example, cloud environments, platforms, computing systems, network systems, and cloud systems generally represent the environments in which services are conducted, and these are included within the "service environment." However, the "service environment" is not limited to these examples. Additionally, the specific types of environments within the "service environment" are not restricted.For instance, cloud environments and cloud systems can be categorized as private cloud, public cloud, hybrid cloud, or multi-cloud, all of which are included within the "service environment."

[0084] The one or more services provided by the service environment 820 is not specifically limited and can be adjusted according to the embodiments. For example, the services may include a service that provides information to the UE 810, a service that stores information from the UE 810, or a service that performs processing based on information from the UE 810 and returns the results of the processing.

[0085] In an embodiment, the Service Environments 820 may also provide computing resources as the service. The computing resources can be hardware resources and / or software resources. For example, applications, processors, memory, and storage can be included in the provided computing resources. Each computing resource can communicate with other computing resources via wired connections, wireless connections, or a combination of wired and wireless connections.

[0086] The provided computing resources can be actual resources (also referred to as physical resources) and / or virtual resources. Furthermore, means of virtualization for virtual resources can be selected as appropriate. That is, in this disclosure, the use of adjectives such as "Virtual" or "Virtualized" to describe names does not imply that they are virtualized by a specific means of virtualization. For example, “virtual machine” refers to software that operates like an actual computer, realized through means of virtualization, and it is not intended to exclude those realized by specific means of virtualization such as Hypervisors or Containers. Conversely, when means of virtualization such as Hypervisors or containers are mentioned in this disclosure, it is merely cited as a general method of implementation. It should also be interpreted that embodimentsimplemented with other virtualization means are also disclosed. Also, the services may also be provided using resources virtualized by different means.

[0087] The service environment 820 includes one or more devices, such as servers and network devices, which provide services or perform processes. The placement of these devices within the service environment 820 can be determined as appropriate. Additionally, if the service environment 820 includes one or more sub-environments 821, the placement of devices can be determined based on predetermined policies for each sub-environment 821. For example, devices related to the first service may be placed in the 1st sub-environment 821-1, and devices related to the second service may be placed in the 2nd sub -environment 821-2. In another example, devices expected to have a higher load than a predetermined threshold may be placed in the 1st subenvironment 821-1, while devices expected to have a lower load than the predetermined threshold may be placed in the 2nd sub-environment 821-2. In this way, specific devices can be placed in specific sub -environments 821. Conversely, each sub-environment 821 can be specialized for a particular purpose.

[0088] In an embodiment, all processes executed in a single service may run within a single service environment, or in multiple service environments. Multiple processes executed in a single service could be provided by different service environments.

[0089] The network 830 is a network that exchanges information between the UE 810 and the service environment 820. The network 830 includes one or more wired and / or wireless networks.

[0090] For example, the network 830 may include a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc ), a public land mobile network (PLMN), alocal area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, a non-terrestrial network (NTN), and / or a combination of these or other types of networks.

[0091] The network 830 can be a part of a network. For example, in a 5G network that includes a RAN, a transport network, and a core network, the network 830 can be at least one of the RAN, the transport network, or the core network. For example, the service environment 820 could be in the core network, in which case the network 830 could correspond to a network that is a combination of a RAN and a transport network and is part of the 5G network.

[0092] The number and arrangement of devices and networks shown in FIG. 8 are provided as an example. It should be understood that any changes that may be implemented by those skilled in the art, such as the addition or rearrangement of well-known devices or networks at the time of implementation, are included in this disclosure.Various Aspects of Embodiments

[0093] It is contemplated that the example embodiments described hereinabove with reference to FIG. 1 to FIG. 8 are merely examples of possible embodiments of the present disclosure, and are not intended to limit or restrict the scope of the present disclosure.

[0094] Specifically, the foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0095] Some embodiments may relate to a device (e.g., node, etc.), a system, a method, and / or a computer-readable medium at any possible technical detail level of integration. Further,one or more of the above components described above may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non- transitory storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out operations.

[0096] The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), electrically erasable programmable read-only memory (EEPROM), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0097] Computer-readable program instructions described herein can be downloaded to respective computing / processing devices from a computer-readable storage medium or to anexternal computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing / processing device.

[0098] Computer-readable program code / instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages.

[0099] The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

[0100] These computer-readable program instructions may be provided to a processor of a general -purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer- readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks.

[0101] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0102] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer- readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method,computer system, and computer-readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0103] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to the implementations. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0104] In view of the above, various further respective aspects and features of embodiments of the present disclosure may be defined by the following items:Item [1]: A user equipment (UE) configured to: send a power state information report including a battery level and screen state to a base station; receive a radio resource control (RRC) message including one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the powerstate information report; and set the logging frequency of the UE based on the one or more logging parameters.Item [2]: The UE according to Item [1], wherein if the power state is low and the screen state is off, the logging frequency is set to be low.Item [3]: The UE according to any one of Items [l]-[2], wherein if the power state is normal and the screen state is on, the logging frequency is set to high.Item [4]: The UE according to any one of Items [l]-[3], wherein the one or more logging parameters further comprise a data granularity, wherein the UE is further configured to: send a context information report including a mobility status and battery level to the base station, wherein the logging frequency is based in part on the context information report.Item [5]: The UE according to Item [4], wherein if the mobility status is high, the logging frequency is set to high.Item [6]: The UE according to Item [4], wherein if the mobility status is low, the logging frequency is set to medium.Item [7]: The UE according to any one of Items [l]-[6], wherein if setting the logging frequency of the UE fails, the UE is configured to reattempt setting the logging frequency of the UE after a predetermined period of time.Item [8]: A method including: sending, by a user equipment (UE) a power state information report including a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message including one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.Item [9]: The method according to Item [8], wherein if the power state is low and the screen state is off, the logging frequency is set to be low.Item

[0010] : The method according to any one of Items [8]-[9], wherein if the power state is normal and the screen state is on, the logging frequency is set to high.Item

[0011] : The method according to any one of Items [8]-

[0010] , wherein the one or more logging parameters further comprise a data granularity, the method further includes: sending, by the UE, a context information report including a mobility status and battery level to the base station, wherein the logging frequency is based in part on the context information report.Item

[0012] : The method according to Item

[0011] , wherein if the mobility status is high, the logging frequency is set to high.Item

[0013] : The method according to Item

[0012] , wherein if the mobility status is low, the logging frequency is set to medium.Item

[0014] : The method according to any one of Items [8]-

[0013] , wherein if setting the logging frequency of the UE fails, the UE is configured to reattempt setting the logging frequency of the UE after a predetermined period of time.Item

[0015] : A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method including: sending, by a user equipment (UE) a power state information report including a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message including one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.Item

[0016] : The non-transitory computer-readable recording medium according to Item

[0015] , wherein if the power state is low and the screen state is off, the logging frequency is set to be low.Item

[0017] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0016] , wherein if the power state is normal and the screen state is on, the logging frequency is set to high.Item

[0018] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0017] , wherein the one or more logging parameters further comprise a data granularity, the method further includes: sending, by the UE, a context information report including a mobilitystatus and battery level to the base station, wherein the logging frequency is based in part on the context information report.Item

[0019] : The non-transitory computer-readable recording medium according to Item

[0018] , wherein if the mobility status is high, the logging frequency is set to high.Item

[0020] : The non-transitory computer-readable recording medium according to Item

[0018] , wherein if the mobility status is low, the logging frequency is set to medium.It will be apparent that within the scope of the appended clauses, the present disclosures may be practiced otherwise than as specifically described herein.

Claims

What is claimed is:

1. A user equipment (UE) configured to: send a power state information report comprising a battery level and screen state to a base station; receive a radio resource control (RRC) message comprising one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and set the logging frequency of the UE based on the one or more logging parameters.

2. The UE as claimed in claim 1, wherein if the power state is low and the screen state is off, the logging frequency is set to be low.

3. The UE as claimed in claim 1, wherein if the power state is normal and the screen state is on, the logging frequency is set to high.

4. The UE as claimed in claim 1, wherein the one or more logging parameters further comprise a data granularity, wherein the UE is further configured to: send a context information report comprising a mobility status and battery level to the base station, wherein the logging frequency is based in part on the context information report.

5. The UE as claimed in claim 4, wherein if the mobility status is high, the logging frequency is set to high.

6. The UE as claimed in claim 4, wherein if the mobility status is low, the logging frequency is set to medium.

7. The UE as claimed in claim 1, wherein if setting the logging frequency of the UE fails, the UE is configured to reattempt setting the logging frequency of the UE after a predetermined period of time.

8. A method comprising: sending, by a user equipment (UE) a power state information report comprising a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message comprising one or more logging parameters including a logging frequency and power state from the base station, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.

9. The method as claimed in claim 8, wherein if the power state is low and the screen state is off, the logging frequency is set to be low.

10. The method as claimed in claim 8, wherein if the power state is normal and the screen state is on, the logging frequency is set to high.

11. The method as claimed in claim 8, wherein the one or more logging parameters further comprise a data granularity, the method further comprises: sending, by the UE, a context information report comprising a mobility status and battery level to the base station, wherein the logging frequency is based in part on the context information report.

12. The method as claimed in claim 11, wherein if the mobility status is high, the logging frequency is set to high.

13. The method as claimed in claim 11, wherein if the mobility status is low, the logging frequency is set to medium.

14. The method as claimed in claim 8, wherein if setting the logging frequency of the UE fails, the UE is configured to reattempt setting the logging frequency of the UE after a predetermined period of time.

15. A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method comprising: sending, by a user equipment (UE) a power state information report comprising a battery level and screen state to a base station; receiving, by the UE, a radio resource control (RRC) message comprising one or more logging parameters including a logging frequency and power state from the basestation, wherein the logging frequency is configured by the base station based on the power state information report; and setting, by the UE, the logging frequency of the UE based on the one or more logging parameters.

16. The non-transitory computer-readable recording medium as claimed in claim 15, wherein if the power state is low and the screen state is off, the logging frequency is set to be low.

17. The non-transitory computer-readable recording medium as claimed in claim 15, wherein if the power state is normal and the screen state is on, the logging frequency is set to high.

18. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the one or more logging parameters further comprise a data granularity, the method further comprises: sending, by the UE, a context information report comprising a mobility status and battery level to the base station, wherein the logging frequency is based in part on the context information report.

19. The non-transitory computer-readable recording medium as claimed in claim 18, wherein if the mobility status is high, the logging frequency is set to high.

20. The non-transitory computer-readable recording medium as claimed in claim 18, wherein if the mobility status is low, the logging frequency is set to medium.

Images