Electronic device, and method for recording information related to cellular event of electronic device

Abstract

An electronic device according to one embodiment may comprise: at least one communication circuit; a communication processor operatively connected to the at least one communication circuit; an application processor operatively connected to the communication processor; and a memory. When a request to record cellular event (CE)-related information is received from the application processor, the communication processor can record the CE-related information on the basis of a CE policy received from a server. While recording the CE-related information, the communication processor can identify, on the basis of the CE policy, whether at least a part of the recorded CE-related information is predetermined information. If at least the part of the recorded CE-related information is predetermined information, the communication processor enables a category of the recorded CE-related information to be identified on the basis of the predetermined information.

Description

Method for recording information related to electronic devices and cellular events of electronic devices

[0001] The present disclosure relates to an electronic device and a method of operating the electronic device, and more specifically to a method of recording information related to a cellular event of the electronic device.

[0002] Cellular events may refer to events that occur while an electronic device communicates based on cellular communication. Cellular events may include events occurring in the protocol stack. For example, CE may include events occurring in the radio resource control (RRC) layer, the medium access control (MAC) layer, and / or the physical (PHY) layer. Cellular events may include events occurring in layers related to the protocol stack. Layers related to the protocol stack may include the radio resource management (RRM) layer. The information described above may be provided as related art for the purpose of aiding understanding of this document. None of the foregoing is to be claimed as prior art related to this document, nor is it to be used to determine prior art.

[0003] The core network operator can monitor cellular events (CEs) that occur while an electronic device uses cellular communication by using various information utilized in the core network. The core network can collect information related to events that occur while the electronic device uses cellular communication and provide it to the core network operator. The core network operator can manage the quality of communication provided by the core network based on the information collected by the core network. Information related to CEs utilized in the core network can be transmitted to the core network over the control plane. The electronic device may not be able to store MR, error reports, and / or MDT data transmitted to the core network via the UL-DCCH.

[0004] The technical problems to be solved in this document are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this invention belongs from the description below.

[0005] An electronic device according to one embodiment may include at least one communication circuit. The electronic device may include a communication processor operatively connected to the at least one communication circuit. The electronic device may include an application processor operatively connected to the communication processor. The electronic device may include a memory. When the communication processor receives a request to record information related to a cellular event (CE) from the application processor, it may record information related to the CE based on a CE policy received from a server. While recording information related to the CE, the communication processor may determine, based on the CE policy, whether at least some of the information related to the CE being recorded is predetermined information. If at least some of the information related to the CE being recorded is predetermined information, the communication processor may determine the category of the recorded information related to the CE based on the predetermined information.

[0006] According to one embodiment, a method of operation of an electronic device may include, upon receiving a request from an application processor to record information related to a cellular event (CE), an operation of recording said CE-related information on a communication processor based on a CE policy received from a server. While recording said CE-related information, the method of operation of the electronic device may include, based on said CE policy, an operation of checking whether at least some of the recorded CE-related information is predetermined information. If at least some of the recorded CE-related information is predetermined information, the method of operation of the electronic device may include an operation of checking the category of said recorded CE-related information based on said predetermined information.

[0007] Electronic devices can set different frequencies for reporting information related to CE of specific categories by setting different reporting cycles for information related to CE of each category. If information related to CE of a specific category is required among the CE-related information of the electronic device, the manufacturer of the electronic device can increase the frequency of recording information related to CE of a specific category by reducing the reporting cycle for CE-related information.

[0008] The electronic device can be configured so that the communication processor delivers the CE sequence stored in the buffer to the application processor only when the application processor is activated. The electronic device can prevent power consumption caused by activating the application processor every time a CE sequence is stored.

[0009] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0010] FIG. 1 is a block diagram of an exemplary electronic device capable of performing the operations described in this document.

[0011] FIG. 2 is a block diagram of an electronic device for supporting at least one network communication according to one embodiment.

[0012] FIG. 3 is a diagram illustrating the protocol stack structure of a legacy communication and / or 5G communication network according to one embodiment.

[0013] FIG. 4 is a diagram illustrating an electronic device and a core network according to one embodiment.

[0014] FIG. 5 is a drawing illustrating the components of the present invention according to one embodiment.

[0015] FIG. 6a is a block diagram of a communication processor according to one embodiment. FIG. 6b is a diagram illustrating a buffer of a communication processor according to one embodiment.

[0016] FIG. 7 is a block diagram of an application processor according to one embodiment.

[0017] FIG. 8 is a block diagram of a server according to one embodiment.

[0018] FIG. 9 is a flowchart of the operation of a communication processor, an application processor, and a server according to one embodiment.

[0019] FIG. 10 is a flowchart of the initial setup operation of an application processor according to one embodiment.

[0020] FIG. 11 is a diagram illustrating the state of a communication processor according to one embodiment.

[0021] FIG. 12 is a flowchart of the operation of a communication processor in an inactive state according to one embodiment.

[0022] FIGS. 13a and FIGS. 13b are flowcharts of the operation of a communication processor in an active state according to one embodiment.

[0023] FIG. 14 is a flowchart of the reporting operation of an application processor according to one embodiment.

[0024] FIG. 1 is a block diagram of an exemplary electronic device (100) capable of performing the operations described in this document.

[0025] Referring to FIG. 1, the electronic device (100) may be one of various forms of electronic devices, such as a notebook (190), smartphones (191) having various form factors (e.g., a bar-type smartphone (191-1), a foldable-type smartphone (191-2), or a sliderable (or rollable)-type smartphone (191-3)), a tablet (192), a cellular phone (not shown), and other similar computing devices (not shown). The components, their relationships, and their functions illustrated in FIG. 1 are illustrative only and are not intended to limit the implementations described or claimed herein. The electronic device (100) may be referred to as a mobile device, a user device, a multifunction device, a portable device, or a server.

[0026] The electronic device (100) may include components comprising at least one processor (110) (hereinafter referred to as processor (110)), at least one memory (120) (hereinafter referred to as memory (120)), at least one display (140) (hereinafter referred to as display (140)), at least one image sensor (150) (hereinafter referred to as image sensor (150)), at least one communication circuit (160) (hereinafter referred to as communication circuit (160)), and / or at least one sensor (170) (hereinafter referred to as sensor (170)). The components are merely exemplary. For example, the electronic device (100) may include other components (e.g., power management integrated circuitry (PMIC), audio processing circuit, antenna, rechargeable battery, or input / output interface). For example, some components may be omitted from the electronic device (100). For example, some components may be integrated into a single component.

[0027] The processor (110) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (110) may include at least one electrical circuit and may process instructions (or programs, data, etc.) stored in memory (120) individually or collectively in a distributed manner. The processor (110) may include a processor assembly comprising one or more processing circuits. The processor (110) may include any processing circuit that is operative to control the performance and operations of one or more components of the electronic device (100) (e.g., memory (120), display (140), image sensor (150), communication circuit (160), and / or sensor (170)). For example, the processor (110) (e.g., application processor (AP)) may be implemented as a system on chip (SoC) (e.g., a single chip or chipset). For example, the processor (110) may be implemented with a plurality of cores (or at least one core circuit), a plurality of chips, or a plurality of chipsets. For example, the processor (110) may include one or more processing circuits. For example, the processor (110) may include one or more processing circuits configured to perform the various functions of the present disclosure individually and / or collectively. As an example without limitation, at least a portion of the processor (110) may be included in a first chip of the electronic device (100), and at least another portion of the processor (110) may be included in a second chip of the electronic device (100) different from the first chip of the electronic device (100).

[0028] For example, the processor (110) may include a central processing unit (111), a graphics processing unit (112), a neural processing unit (113), an image signal processor (114), a display controller (115), a memory controller (116), a storage controller (117), a communication processor (118), and / or a sensor interface (119). These components of the processor (110) are merely exemplary. For example, the processor (110) may include other components. For example, some components of the processor (110) may be omitted from the processor (110). For example, some components of the processor (110) may be included as separate components of the electronic device (100) outside of the processor (110). For example, some components of the processor (110) (e.g., memory controller (116)) may be included in other components (e.g., at least part of memory (120), an interface (e.g. available for connection to at least one component of the electronic device (100)), a display (140) and / or an image sensor (150)).

[0029] The processor (110) may cause other components of the electronic device (100) to perform various operations by executing instructions stored in memory (120). The CPU (111) (or central processing circuit) may be configured to control the components of the processor (110) based on the execution of instructions stored in memory (120) (e.g., volatile memory (121) and / or non-volatile memory (122)). The GPU (112) (or graphics processing circuit) may be configured to execute parallel operations (e.g., rendering). The NPU (113) (or neural processing circuit, or AI (artificial intelligence) chip) may be configured to execute operations for an artificial intelligence model (e.g., convolution computation). An ISP (114) (or image signal processing circuit) may be configured to process a raw image acquired through an image sensor (150) into a format suitable for a component within the electronic device (100) or a component of the processor (110). A display controller (115) (or display control circuit, or DPU (display processing unit)) may be configured to process an image acquired from a CPU (111), GPU (112), ISP (114), or memory (120) (e.g., volatile memory (121)) into a format suitable for a display (140). A memory controller (116) (or memory control circuit) may be configured to control reading data from the volatile memory (121) and writing data to the volatile memory (121). A storage controller (117) (or storage control circuit) may be configured to control reading data from the non-volatile memory (122) and writing data to the non-volatile memory (122).The CP (118) (communication processing circuit) may be configured to process data obtained from a component of the processor (110) into a format suitable for transmitting to another electronic device via the communication circuit (160), or to process data obtained from another electronic device via the communication circuit (160) into a format suitable for processing by the component of the processor (110). For example, the communication circuit (160) may include one or more communication circuits. The sensor interface (119) (or sensing data processing circuit, sensor hub) may be configured to process data regarding the state of the electronic device (100) and / or the state around the electronic device (100), obtained through the sensor (170), into a format suitable for the component of the processor (110).

[0030] Memory (120) may include one or more storage media (or one or more storage devices). For example, memory (120) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, a permanent memory such as flash memory, read-only memory (ROM) (e.g., non-volatile memory (122)), a semi-permanent memory such as random access memory (RAM) (e.g., volatile memory (121)), any other suitable type of storage (or storage assembly), or any combination thereof. Memory (120) may include a cache memory, which is one or more different types of memory used to temporarily store data for a function or feature of the electronic device (100). As an example not limited to, the cache memory may be included within the processor (110). The memory (120) may be fixedly embedded within the electronic device (100) or incorporated into one or more suitable types of components (e.g., a SIM (subscriber identity module) card and / or an SD (secure digital) card) that can be repeatedly inserted into and removed from the electronic device (100).

[0031] For example, memory (120) may store one or more software applications, such as operating system (or system) software applications, firmware software applications, driver software applications, plugin (e.g., add-in, add-on, and / or applet) software applications, and / or any other suitable software applications. For example, the one or more software applications may include instructions executable by the processor (110). For example, memory (120) may store instructions that can be called by an application programming interface (API). For example, memory (120) may store instructions within a library.

[0032] FIG. 2 is a block diagram (200) of an electronic device (201) for supporting at least one network communication according to one embodiment. The electronic device (201) may include, for example, a portable device (e.g., a smartphone, a tablet, a portable multimedia device, a portable medical device, a camera, or a wearable device), a computer device, or a home appliance. The electronic device (201) according to the embodiments of this document is not limited to the aforementioned devices.

[0033] Referring to FIG. 2, the electronic device (201) may include a processor (220), a communication processor (260), a first RFIC (radio frequency integrated circuit) (222), a second RFIC (224), a third RFIC (226), an IFIC (intermediate frequency integrated circuit) (228), a first RFFE (radio frequency front end) (232), a second RFFE (234), a third RFFE (236), a phase converter (238), a plurality of antennas (248), a first antenna (242), a second antenna (244) and / or an antenna module (246).

[0034] The antenna module (246) may include a third RFIC (226) and / or a plurality of antennas (248). The third RFIC (226) may include a third RFFE (236) including a phase converter (238), but is not limited thereto. The third RFIC (226), the third RFFE (236), the phase converter (238), and / or the plurality of antennas (248) may be implemented to be included in or mounted on a separate module or substrate.

[0035] The processor (220) may be implemented, for example, as an application processor and may execute an application stored in the electronic device (201). The processor (220) and the communication processor (260) may transmit and / or receive data through an interface. The processor (220) may provide at least some of the data generated by the application to the communication processor (260). The communication processor (260) may provide at least some of the data received from a network (e.g., a first cellular network (292) and / or a second cellular network (294)) to the processor (220), and the processor (220) may use the received data for the execution of the application.

[0036] Depending on the implementation, the communication processor (260) may be implemented as a single chip (or single package) with the processor (220), but this is exemplary and may also be implemented as independent hardware. If the communication processor (260) is implemented as a chip (or package), the chip (or package) may include a storage device (e.g., memory) in which protocol information for communication with legacy networks (e.g., LTE (long term evolution) protocol information), protocol information for communication with 5G networks (e.g., NR (new radio) protocol information), and / or protocol information for communication with communication networks beyond 5G (e.g., 6G networks) is stored. For example, the communication processor (260) may utilize multiple protocol stacks to perform MR-DC (multiple radio access technology-dual connectivity) or dual SIM (subscriber identification module) services. The communication processor (260) may support the establishment of a communication channel in a band to be used for wireless communication with the first cellular network (292), and legacy network communication through the established communication channel. According to various embodiments, the first cellular network (292) may be a legacy network including a second-generation (2G), 3G, 4G, and / or LTE network. The communication processor (260) may support a designated band among the bands to be used for wireless communication with the second cellular network (294) (e.g., FR (frequency range) 1 (e.g., 410 MHz (megahertz) to 7.125 GHz (gigahertz), but without limitation) (or, sub 6), and / or FR2 (e.g., 24.It may support the establishment of a communication channel corresponding to 25GHz to 71GHz (but not limited thereto) (or, above 6)) and 5G network communication through the established communication channel. The second cellular network (294) may be, for example, a 5G network, but is not limited thereto. For example, the second cellular network (294) may be a communication network beyond 5G (e.g., a 6G network). The communication processor (260) may operate based on information (or instructions) associated with an LTE protocol stack (e.g., E-UTRA (evolved UMTS (universal mobile telecommunication system) terrestrial radio access network), EPC (evolved packet core), and / or EPS (evolved packet system), but not limited thereto) stored in an internal memory (or accessible memory). The communication processor (260) may operate based on information (or instructions) associated with a 5G (e.g., NR, 5GC (5th generation core), and / or 5GS (5th generation system), but without limitation) protocol stack stored in built-in memory (or accessible memory). The communication processor (260) may generate a baseband signal based on data from the processor (220), for example. The communication processor (260) may provide data processed from a baseband signal received from the first RFIC (222), the second RFIC (224), and / or IFIC (228) to the processor (220). The electronic device (201) may also perform communication based on dual connectivity.For example, the electronic device (201) can perform communication using an LTE network and a 5G network based on a heterogeneous radio access technology (RAT), for example, ENDC (E-UTRA NR dual connectivity). For example, the electronic device (201) (for example, a communication processor (260)) may perform dual connectivity communication based on FR1 and FR2 of NR, which is a single RAT. Meanwhile, there is no limitation on the type of dual connectivity, and depending on the type of dual connectivity, at least some of the components described above may be implemented so as not to be included in the electronic device (201).

[0037] The first RFIC (222) can convert a baseband signal generated by the communication processor (260) into a radio frequency (RF) signal of a first frequency band (e.g., about 700 MHz to about 3 GHz) during transmission. During reception, the first RFFE (232) can receive an RF signal of the first frequency band through the first antenna (242), preprocess the received RF signal, and provide it to the first RFIC (222). The first RFIC (222) can convert the preprocessed RF signal into a baseband signal so that it can be processed by the communication processor (260).

[0038] The second RFIC (224) can convert a baseband signal generated by the communication processor (260) into an RF signal of the second frequency band (e.g., FR 1 (e.g., a frequency band of about 7.125 GHz or less)) when transmitting. The second RFFE (234) can receive an RF signal of the second frequency band through an antenna (e.g., the second antenna (244)) when receiving, preprocess the received RF signal, and provide it to the second RFIC (224). The second RFIC (224) can convert the preprocessed RF signal of the second frequency band into a baseband signal so that it can be processed by the communication processor (260). The first RFIC (222) and the second RFIC (224) may be implemented as two or more independent chips (or multiple packages) or as a single chip (or a single package). The first RFIC (222), the second RFIC (224), the first RFFE (232), and / or the second RFFE (234) may include a plurality of PAs (power amplifiers), LNAs (low noise amplifiers), filters, multiplexers, and / or switches to support a plurality of RF paths (e.g., RF transmission paths and / or RF reception paths).

[0039] The third RFIC (226) can convert a baseband signal generated by the communication processor (260) into an RF signal of the third frequency band (e.g., FR 2 (e.g., a frequency band of about 24.25 GHz or higher)) upon transmission. The third RFFE (236) can receive the RF signal of the third frequency band through an antenna (e.g., a plurality of antennas (248)) upon reception and preprocess the received RF signal. The third RFIC (226) and / or IFIC (228) can convert the preprocessed RF signal of the third frequency band into a baseband signal so that it can be processed by the communication processor (260). According to one embodiment, the third RFFE (236) may be formed as part of the third RFIC (226). In various embodiments, the third RFIC (226) may transmit and / or receive signals with the communication processor (260). For example, when communication based on dual connectivity of FR1 and FR2 is performed, the second RFIC (224) and the second RFFE (234) may be used for processing signals in the FR1 band, and the third RFIC (226) and IFIC (228) may be used for processing signals in the FR2 band, but there are no limitations.

[0040] According to one embodiment, the electronic device (201) may include an IFIC (228) separately from or at least as part of the third RFIC (226). For example, the IFIC (228) may convert a baseband signal generated by the communication processor (260) into an RF signal (hereinafter referred to as an IF signal) in an intermediate frequency band (e.g., about 9 GHz to about 11 GHz) and then transmit the IF signal to the third RFIC (226). The third RFIC (226) may convert the IF signal into an RF signal in a third frequency band. Upon reception, the third RFIC (226) may receive the RF signal in the third frequency band through an antenna (e.g., a plurality of antennas (248)), convert the received RF signal into an IF signal, and provide it to the IFIC (228). The IFIC (228) can convert the IF signal into a baseband signal so that the communication processor (260) can process it. In various embodiments, the IFIC (228) may transmit and / or receive signals to and from the communication processor (260). The RFICs (222, 224, 226) and / or the IFIC (226) may include at least one mixer (e.g., a mixer that performs frequency up conversion and / or a mixer that performs frequency down conversion).

[0041] A plurality of antennas (248) may be formed into an antenna array comprising a plurality of antenna elements that can be used for beamforming. In this case, the third RFIC (226) may include, for example, a plurality of phase shifters (238) corresponding to the plurality of antenna elements as part of the third RFFE (236). The plurality of phase shifters (238) may, at transmission, convert the phase of each RF signal of the third frequency band to be transmitted to the outside of the electronic device (201) (e.g., a base station of a 5G network) through an antenna element corresponding to each of the plurality of phase shifters (238). At reception, the plurality of phase shifters (238) may convert the phase of the RF signal of the third frequency band received from the outside to the same or substantially the same phase through an antenna element corresponding to each of the plurality of phase shifters (238). According to an embodiment, the electronic device (201) may include a plurality of antenna modules (246). The electronic device (2101) may select and use some of the plurality of antenna modules (246) or may use all of the plurality of antenna modules (246).

[0042] FIG. 3 is a diagram illustrating the protocol stack structure of a network (100) of legacy communication and / or 5G communication according to one embodiment.

[0043] Referring to FIG. 3, a network (101) according to an illustrated embodiment may include an electronic device (100), a legacy network (392), a 5G network (394), and a server (108).

[0044] The electronic device (100) may include an Internet protocol (312), a first communication protocol stack (314), and a second communication protocol stack (316). The electronic device (100) may communicate with a server (108) via a legacy network (392) and / or a 5G network (394).

[0045] According to one embodiment, an electronic device (100) can perform internet communication associated with a server (108) using an internet protocol (312) (e.g., TCP, UDP, IP). The internet protocol (312) can be executed, for example, on a main processor included in the electronic device (100) (e.g., the main processor (121) of FIG. 1).

[0046] According to another embodiment, the electronic device (100) can wirelessly communicate with a legacy network (392) using a first communication protocol stack (314). According to yet another embodiment, the electronic device (100) can wirelessly communicate with a 5G network (394) using a second communication protocol stack (316). The first communication protocol stack (314) and the second communication protocol stack (316) may be executed, for example, in one or more communication processors included in the electronic device (100) (e.g., the wireless communication module (192) of FIG. 1).

[0047] The server (108) may include an Internet Protocol (322). The server (108) may transmit and receive data related to the Internet Protocol (322) to and from an electronic device (100) via a legacy network (392) and / or a 5G network (394). According to one embodiment, the server (108) may include a cloud computing server located outside the legacy network (392) or the 5G network (394). In another embodiment, the server (108) may include an edge computing server (or a Mobile Edge Computing (MEC) server) located inside at least one of the legacy network or the 5G network (394).

[0048] The legacy network (392) may include an LTE base station (340) and an EPC (342). The LTE base station (340) may include an LTE communication protocol stack (344). The EPC (342) may include a legacy NAS protocol (346). The legacy network (392) may perform LTE wireless communication with an electronic device (100) using the LTE communication protocol stack (344) and the legacy NAS protocol (346).

[0049] The above 5G network (394) may include an NR base station (350) and a 5GC (352). The NR base station (350) may include an NR communication protocol stack (354). The 5GC (352) may include a 5G NAS protocol (356). The 5G network (394) may perform NR wireless communication with an electronic device (100) using the NR communication protocol stack (354) and the 5G NAS protocol (356).

[0050] According to one embodiment, the first communication protocol stack (314), the second communication protocol stack (316), the LTE communication protocol stack (344), and the NR communication protocol stack (354) may include a control plane protocol for transmitting and receiving control messages and a user plane protocol for transmitting and receiving user data. The control messages may include, for example, messages related to at least one of security control, bearer setup, authentication, registration, or mobility management. The user data may include, for example, data other than the control messages.

[0051] According to one embodiment, the control plane protocol and the user plane protocol may include PHY (physical), MAC (medium access control), RLC (radio link control), or PDCP (packet data convergence protocol) layers. The PHY layer may, for example, channel code and modulate data received from an upper layer (e.g., a MAC layer) and transmit it over a wireless channel, and demodulate and decode data received through the wireless channel and transmit it to the upper layer. The PHY layer included in the second communication protocol stack (316) and the NR communication protocol stack (354) may further perform operations related to beam forming. The MAC layer may, for example, logically / physically map data to a wireless channel to be transmitted and received, and perform a HARQ (hybrid automatic repeat request) for error correction. The RLC layer may, for example, concatenate, segmentate, or reassemble data, and perform data ordering, reordering, or duplicate checking. The PDCP layer can perform operations related to ciphering and data integrity of control data and user data, for example. The second communication protocol stack (316) and the NR communication protocol stack (354) may further include a service data adaptation protocol (SDAP). The SDAP can manage wireless bearer allocation based on the Quality of Service (QoS) of user data, for example.

[0052] According to various embodiments, the control plane protocol may include a radio resource control (RRC) layer and a non-access stratum (NAS) layer. The RRC layer may process control data related to, for example, radio bearer setup, paging, or mobility management. The NAS may process control messages related to, for example, authentication, registration, and mobility management.

[0053] FIG. 4 is a diagram illustrating an electronic device and a core network according to one embodiment.

[0054] An electronic device (400) (e.g., the electronic device (100) of FIG. 1, the electronic device (201) of FIG. 2, the electronic device (100) of FIG. 3) can communicate wirelessly with a core network (410). The core network (410) can perform an operation to prevent a deterioration in the quality of communication while the electronic device (400) is moving.

[0055] The core network operator can monitor events occurring while the electronic device (400) uses cellular communication by using various information used in the core network (410). The core network (410) can collect information related to events occurring while the electronic device (400) uses cellular communication and provide it to the core network operator. The core network operator can manage the quality of communication provided by the core network (410) based on the information collected by the core network (410).

[0056] The core network (410) can obtain information related to a cellural event (CE) that occurs while the electronic device (400) is using cellular communication by utilizing an access and mobility function (AMF) included in the core network (410). For example, the core network (410) can receive a measurement report (MR) from the electronic device (400). For example, the core network (410) can obtain an error report transmitted from an uplink dedicated control channel (UL-DCCH) or obtain MDT data from an electronic device (400) that supports a minimization of drive test (MDT) function.

[0057] The electronic device may not be able to store information related to CE used in the core network. Information related to CE used in the core network may be transmitted to the core network (410) on the control plane. The electronic device may not be able to store MR, error reports, and / or MDT data transmitted to the core network (410) via the UL-DCCH.

[0058] Information related to CE used in the core network may be restricted in its use by the manufacturer of the electronic device. Information related to CE used in the core network may take the form of short-time interval data during communication between the electronic device and the base station. For example, MR or error reports may consist of data related to communication at a specific moment. Even if the electronic device acquires information related to CE used in the core network, such information may not be continuous data intended for monitoring CE occurring during cellular communication or for training an artificial intelligence model.

[0059] The electronic device (400) of the present disclosure can record information related to CE that occurs while the electronic device (400) performs cellular communication and transmit it to a server on a user plane. In the drawings below, the operation of the electronic device (400) recording information related to cellular events required by the manufacturer of the electronic device and transmitting it to a server will be described.

[0060] FIG. 5 is a drawing illustrating the components of the present invention according to one embodiment.

[0061] An electronic device (e.g., the electronic device (100) of FIG. 1, the electronic device (201) of FIG. 2, the electronic device (100) of FIG. 3, and the electronic device (400) of FIG. 4) may include a communication processor (e.g., the CP (118) of FIG. 1, the communication processor (260) of FIG. 2)) and / or an application processor (e.g., the processor (110) of FIG. 1, the processor (220) of FIG. 2). The electronic device (400) may communicate with a server (530).

[0062] The communication processor (510) can write information related to a cellular event (CE) to a buffer of a recording module included in the communication processor (510) upon a request from the application processor (520).

[0063] CE may refer to an event that occurs while the electronic device (400) communicates based on cellular communication. CE may include events that occur in the protocol stack. For example, CE may include events that occur in the radio resource control (RRC) layer, the medium access control (MAC) layer, and / or the PHY (physical) layer. CE may include events that occur in layers associated with the protocol stack (e.g., measurement (MR) events obtained from the radio resource management (RRM) layer). Layers associated with the protocol stack may include the RRM layer.

[0064] Events occurring in the RRC layer may include events occurring between the core network (e.g., the core network (410) of FIG. 4) and the communication processor (510). For example, events occurring in the RRC layer may include connection setup, connection resume, handover (HO), connection re-establishment, and connection release.

[0065] Events occurring at the MAC layer may include events occurring between the base station and the communication processor (510). For example, events occurring at the MAC layer may include events related to random access control (RACH).

[0066] Events occurring at the PHY layer may include uplink transmission power (UL Tx power), path loss, channel quality indicator (CQI), rank indicator (RI), modulation and coding scheme (MCS), and block error rate (BLER).

[0067] The communication processor (510) can record information related to CE based on the CE policy. The application processor (520) can receive the CE policy from the server (530). The application processor (520) can store the CE policy in the buffer of the application processor (520). The application processor (520) can transmit the CE policy to the communication processor (510).

[0068] A CE policy may include rules for recording information related to CE.

[0069] For example, a CE policy may include some of the rules in [Table 1]. Field names in [Table 1] may refer to the names of the rules. Types in [Table 1] may refer to the data types of the rules. Default values ​​in [Table 1] may refer to the default values ​​set as rules in the CE policy when no value is set as a rule. Some of the default values ​​in [Table 1] (e.g., supportRat, supportCE, target CE) may be arbitrarily set default values ​​and are subject to change. Units in [Table 1] may refer to the units of values ​​indicated by the rules. [Table 1] is for illustrative purposes only, and it should be understood that the rules included in a CE policy may consist of rules different from those in [Table 1].

[0070] 필드 네임기본 값단위특징policyId--32 bit pseudo-reandom seednextPolicyUpdate--Next policy update date, 32 bit UTC valuereportInterval24hour(To AP(어플리케이션 프로세서(520))) the time interval which a device has to wait till next report after latest onesizeOfMemory10-(To AP) the maximum number of report elements which can be storedsupportRat0xC1-(To CP(통신 프로세서(510))) Bitmap0x01:LTE, 0x02:WCDMA, 0x04:GSM, 0x8:CDMA1x, 0x10:TDSCDMA, 0x20:WIFI, 0x40:NR(LTE W / ENDC), 0x80:NR_SA(NR5G Stand Alone)reportIntervalNormal7200min(To CP) report interval for normal eventsreportIntervalChange4320min(To CP) report interval for cell change eventsreportIntervalFailure1440min(To CP) report interval for failure eventsrecordInterval60min(To CP) record interval within report intervalsupportCE0x7FFFFFF-(To CP) event to record in buffer (Bitmap)0x1: CLOCK_UPDATE, 0x2: PLMN_CHANGE,0x4: MEAS_PFREQ_L3, 0x8: MEAS_SFREQ_L3, 0x10: MEAS_IFREQ_L3, 0x20: MEAS_CELL_L3,0x40: MEAS_PFREQ_L1, 0x80: MEAS_SFREQ_L1, 0x100: MEAS_IFREQ_L1,0x200: MEAS_CELL_L1,0x400: HANDOVER_TRIGGER, 0x800: HANDOVER_RESULT,0x1000: LINK_FAILURE,0x2000: UL_PWR,0x4000: RRC_SETUP_REQ, 0x8000: RRC_SETUP_RESULT,0x10000: RRC_RESUME_REQ, 0x20000: RRC_RESUME_RESULT,0x40000: RRC_REEST_REQ, 0x80000: RRC_REEST_RESULT, 0x100000: RRC_RELEASE,0x200000: SCG_ADD_TRIGGER, 0x400000: SCG_ADD_RESULT, 0x800000: SCG_RELEASE,0x1000000: RACH_RESULT,0x2000000: RRC_MEAS_RPT_CFG, 0x4000000: RRC_MEAS_RPT_CELL,targetCE0x7F0F-(To CP) event to use for report booking (Bitmap)0x1: NORMAL_MEAS_L3, 0x2: NORMAL_MEAS_L1,0x4: CHANGE_HANDOVER_SUCCESS,0x8: CHANGE_RRC_SETUP, 0x10: CHANGE_RRC_RESUME, 0x20: CHANGE_RRC_REEST,0x40: CHANGE_RACH,0x80: CHANGE_RRC_MEAS_REPORT,0x100: FAILURE_HOF, 0x200: FAILURE_RLF, 0x400: FAILURE_MCGF, 0x800: FAILURE_SCGF,0x1000: FAILURE_RRC_SETUP, 0x2000: FAILURE_RRC_RESUME, 0x4000: FAILURE_RRC_REEST,0x8000: FAILURE_RACH,freezeDelay5sec(To CP) time gap between report booking and buffer freezereportLength30sec(To CP) maximum time length of report,

[0071] A CE policy includes rules specifying the frequency for updating the CE policy (e.g., nextPolicyUpdate in [Table 1]), information representing the CE policy (e.g., policyID in [Table 1]), rules specifying the frequency at which the application processor reports CE sequences to the server (e.g., reportInterval in [Table 1]), rules specifying the maximum capacity of CE sequences stored in the application processor (e.g., sizeOfMemory in [Table 1]), rules specifying the frequency for reporting information related to CEs for each of multiple categories (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure in [Table 1]), rules specifying the maximum time for which the communication processor records information related to CEs (e.g., recordInterval in [Table 1]), rules specifying the information related to CEs that the communication processor records (e.g., supportCE in [Table 1]), rules specifying the network method among multiple network methods that records information related to CEs (e.g., supportRat in [Table 1]), and rules specifying predetermined information configured to be included in the CE sequence (e.g., [Table It may include [targetCE] of [1], a rule indicating a specified time for the communication processor to record information related to the CE after recording predetermined information (e.g., freezeDelay in [Table 1]), and / or a rule indicating the length of the CE sequence transmitted to the server (e.g., reportLength in [Table 1]). According to one embodiment, the application processor (520) may receive an updated CE policy from the server (530) at each CE policy update cycle based on a rule indicating a CE policy update cycle (e.g., nextPolicyUpdate in [Table 1]). According to one embodiment, the application processor (520) may report information representing the CE policy (e.g., policyID in [Table 1]) to the server (530).The server (530) may transmit an updated CE policy to the application processor (520) based on information representing the CE policy reported by the application processor (520) (e.g., policyID in [Table 1]). The electronic device (400) of the present disclosure may update the CE policy based on at least one of a rule indicating a cycle for updating the CE policy (e.g., nextPolicyUpdate in [Table 1]) or information representing the CE policy (e.g., policyID in [Table 1]).

[0072] According to one embodiment, the application processor (520) may transmit at least one CE sequence stored in the application processor's buffer to the server (530) at each period in which the application processor reports a CE sequence to the server, based on a rule (e.g., reportInterval of [Table 1]) that indicates the period in which the application processor reports a CE sequence to the server included in the CE policy.

[0073] According to one embodiment, a communication processor (510) may start recording information related to CE in response to the elapsed of at least one of the periods for reporting information related to CE, based on a rule (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure of [Table 1]) that indicates the period for reporting information related to CE for each of the plurality of categories. When at least one of the periods for reporting information related to CE has elapsed, the communication processor (510) may determine to collect the CE sequence of the category for which the period has elapsed.

[0074] According to one embodiment, the communication processor (510) may stop recording information related to CE if, based on a rule (e.g., recordInterval of [Table 1]) indicating a maximum time for recording information related to CE, the information related to CE, which is a predetermined piece of information related to CE, is not recorded during the maximum time for recording information related to CE.

[0075] According to one embodiment, the communication processor (510) can record information related to the CE of a specific network method based on a rule (e.g., supportRat of [Table 1]) indicating at least one network method among a plurality of network methods that is the target for recording information related to the CE.

[0076] According to one embodiment, the communication processor (510) can determine whether some of the information related to the CE being recorded is predetermined information based on a rule (e.g., targetCE of [Table 1]) that indicates predetermined information set to be included in the CE sequence. The predetermined information may refer to information among the information related to the CE recorded by the communication processor (510) that is necessary for the manufacturer of the electronic device (400) to monitor events occurring while using cellular communication. The predetermined information may be set differently for each CE policy, and the communication processor (510) can determine whether the information related to the CE is predetermined information based on the CE policy received from the application.

[0077] According to one embodiment, the communication processor (510) may stop recording information related to CE after a specified time has elapsed, based on a rule (e.g., freezeDelay of [Table 1]) that indicates a specified time for the communication processor to record information related to CE after recording information related to CE.

[0078] According to one embodiment, the communication processor (510) may determine a set of some of the information related to the recorded CE to be transmitted to the server as the CE sequence to be transmitted to the server based on a rule (e.g., reportLength in [Table 1]) indicating the length of the CE sequence to be transmitted to the server. For example, the CE sequence may be generated based on a set of information related to the CE with a length indicated by reportLength from the information related to the last recorded CE.

[0079] A CE sequence may refer to a set of some of the information related to CE recorded by the communication processor (510). For example, the communication processor (510) may stop recording information related to CE after a specified time has elapsed following recording predetermined information, and determine a set of some of the recorded information related to CE as the CE sequence to be transmitted to the server.

[0080] A CE sequence may include predetermined information according to a rule (e.g., targetCE in [Table 1]) that indicates the predetermined information set to be included in the CE sequence. The communication processor (510) may stop recording information related to CE after recording information related to CE for a specified time (e.g., the specified time indicated by freezeDelay in [Table 1]) after recording the predetermined information. The communication processor (510) may not stop recording information related to CE until the predetermined information is recorded. However, the communication processor (510) may stop recording information related to CE if the information related to CE, which is the predetermined information, is not recorded during the maximum time for recording information related to CE.

[0081] The communication processor (510) can determine, while recording information related to the CE, whether some of the information related to the CE being recorded is predetermined information set to be included in the CE sequence. If some of the information related to the CE being recorded is predetermined information corresponding to the CE policy, the communication processor (510) can determine the category of some of the information related to the CE that is predetermined information. The communication processor (510) can determine the identified category as the category of the CE sequence.

[0082] The categories may include a first category related to the quality of the signal or the state of the network, a second category related to a change in communication between the network and the electronic device (400), and / or a third category related to a failure in communication between the network and the electronic device (400). The first category may be a category of predetermined information that is an L1 measurement or an L3 measurement. An L1 measurement may refer to information that measures the strength and / or quality of the signal, and an L3 measurement may refer to information that measures the connection status and / or network performance. The second category may be a category of predetermined information that is one of a handover success (HO success), setup success, resume success, or reestablishment success. The third category may be a predetermined category of information that is one of a handover failure (HO failure), radio link failure (RLF), master cell group failure (MCGF), secondary cell group failure (SCGF), setup failure, resume failure, or reestablishment failure.

[0083] CE can occur at time intervals of several seconds to several hundred milliseconds. The communication processor (510) can record information related to CE for managing mobility for several seconds. However, the storage capacity of the communication processor (510) may be smaller than that of the application processor (520). The application processor (520) may require a method to efficiently utilize the storage capacity. The communication processor (510) of the present disclosure can record information related to CE using the structure shown in [Table 2]. The communication processor (510) can efficiently manage the storage capacity of the communication processor (510) by storing some of the repetitive information.

[0084] A CE sequence may be composed of multiple structures. For example, a CE sequence may include some of the structures included in [Table 2]. In [Table 2], union refers to a structure that is a set of information that may be included in information related to CE, and table refers to a structure that is a set of information that may be included in a CE sequence.

[0085] Classification Structure Features union Composed of a union of structures: clockT ~ rrc clockT utcQ: Records whenever an update occurs, utcQ: quantized value of utc_ms by 1024, i.e., (utc_ms >> 10) plmn TPMN: Records upon change, composed of MCC (Mobile Country Code) and MNC (Mobile Network Code) measP freq L3 TPM Cell: Records when an L3 (Layer-3) measurement for FCN occurs, composed of RAT, GCI, FCN, and numCells measS freq L3 TPM Cell: Records when an L3 measurement for FCN occurs, composed of RAT, FCN, and numCells measIf freq L3 T: Records when an L3 measurement corresponding to inter-frequency occurs, composed of RAT, FCN, and numCells measCell L3 TL: Records per cell when a L3 measurement occurs, including PCI, RSRP, RSRQ, RSSI, Composed of SINR, ssbIdx, etc. measPfreqL1TPCell Record when L1 (Layer-1) measurement for FCN occurs, composed of RAT, GCI, FCN, numCells measSfreqL1TSCell Record when L1 measurement for FCN occurs, composed of RAT, FCN, numCells measIfreqL1TRecord when L1 measurement corresponding to Inter-frequency occurs, composed of RAT, FCN, numCells measCellL1TL1 Record per cell when measurement occurs, composed of PCI, RSRP, RSRQ, RSSI, SINR, ssbIdx, etc. handoverTriggerTHO Occurs when a command is received, composed of RAT, PCI, FCN for source cell and target cell handoverResultTHO Occurs upon completion,Composed of RAT, PCI, FCN, and result values ​​for the source cell and target cell linkFailureT: When a failure event is detected at the terminal, composed of RAT, failure type, PCI, FCN, and cause ulPwrTUL: Composed of transmit power, RAT, ccIdx, channel, and power values rrcSetupReqTRRC: When a setup request occurs, composed of RAT, PCI, FCN, and cause rrcSetupResultTRRC: When setup is completed or fails, composed of RAT, PCI, FCN, and result rrcResumeReqTRRC: When a resume request occurs, composed of RAT, PCI, FCN, and cause rrcResumeResultTRRC: When resume is completed or fails, composed of RAT, PCI, FCN, and result rrcReEstReqTRRC: When a reestablishment request occurs, composed of RAT, cause, and the PCI and FCN of the source and target cells rrcReEstResultTRRC: When reestablishment is completed or fails, composed of RAT, result, and the PCI and FCN of the source and target cells rrcReleaseTRRC: When a release is received, composed of RAT, Consisting of PCI, FCN, redirectRat, and redirectFcn scgAddTriggerTRRC: When adding an SCG due to reconfiguration scgAddResultTSCG: When additional configuration is completed or fails scgReleaseTSCG: When receiving a release-related message scgReleaseTSCG: When completing or failing a TRAC ResultTRACHThe meas that triggered the report and the report condition rrcMeasRptCellTMR, the report value per cell reporting when an event occurs table1 cellularEventNtf chipset ~ version structure composed of chipset 0: QCOM, 1: SLSI, 2: MTK timestamp UTC timestamp of the last sample (UTC (ms) of the last sample) mccMCCmncMNCsegSetIdsegment set IDsegIdxindex of segment, 0~isSegEndIndicate whether current segment is the last cellularEventInfoceDataT union structure version Cellular Event format version to distinguish change in structures or values table2 cellularEventInfoTtic ~ ceData structure composed of tic (utc_ms >> 2) & 0xFF, 4ms unit ceType enum value corresponding to the data structure type that the ceDataT union can have ceDataceDataT union structure,

[0086] According to one embodiment, the CE sequence may be in the form of cellularEventNtf of table 1 of [Table 2]. The communication processor (510) may record cellularEventNtf, which is a structure composed of chipset, timestamp, mcc, mnc, segSetId, segIdx, isSegEnd, cellularEventInfo, and version included in table 1, based on table 1 included in [Table 2]. The communication processor (510) may include data that is commonly included in information related to a plurality of CEs in a separate structure of the CE sequence (e.g., chipset, timestamp, mcc, mnc, segSetId, segIdx, isSegEnd, cellularEventInfo, version), and may not include it in a structure corresponding to information related to a plurality of CEs included in the CE sequence (e.g., cellularEventInfo). The communication processor (510) may record information that may be duplicated in information related to a plurality of CEs in a separate structure. The communication processor (510) can stably manage the storage capacity of the recording module included in the communication processor (510) while continuously storing information related to CE. According to one embodiment, information related to CE may include information related to time. The communication processor (510) can record some of the information related to time of the information related to CE. The communication processor (510) can record the remaining part of the information related to time only when the remaining part changes. For example, the communication processor (510) can distinguish between upper and lower time-related information based on the basic unit of the information related to time. The communication processor (510) can record the lower basic unit for every piece of information related to CE. The communication processor (510) can record the upper basic unit only when the upper basic unit changes.According to one example, if the UTC (in milliseconds) is 1725237551123 (e.g., 0x191B02BE013) and the base unit is 4 milliseconds, the UTC can be represented as 431309387780 (e.g., 1725237551123 divided by 4 milliseconds). The UTC (e.g., 431309387780) can be represented in hexadecimal (e.g., 0x646C0AF804). The communication processor (510) can separate the UTC represented in hexadecimal into an upper base unit (e.g., 0x646C0AF8, [Table 2] clockT) and a lower base unit (e.g., 0x04, [Table 2] tic). The communication processor (510) records a lower basic unit (e.g., [Table 2] tic) for every piece of information related to CE, and records a higher basic unit only when the higher basic unit (e.g., [Table 2] clockT) changes.

[0087] According to one embodiment, the communication processor (510) can record specific information of information related to CE (e.g., a public land mobile network, PLMN) only when the specific information changes.

[0088] According to one embodiment, a communication processor (510) may record measurement information related to a cell of information related to CE by classifying it into a PCell (primary cell), a SCell (secondary cell), and / or an inter-frequency cell. The measurement information related to the cell may include information measured in a plurality of cells for a specific frequency channel number (FCN). The FCNs of the plurality of cells may be the same. If the FCNs of the plurality of cells are the same, the communication processor (510) may not record the FCN for each of the plurality of cells, but may record it only once for each type of cell. The communication processor may record the same FCN once for each structure classified into a PCell (primary cell), a SCell (secondary cell), and / or an inter-frequency cell. Therefore, measurement information related to PCell (primary cell), SCell (secondary cell), and / or inter-frequency cell can all be configured to include some common information (e.g., RAT, FCN) of PCell, SCell, and inter-frequency cell.

[0089] According to one embodiment, the communication processor (510) may record some of the measurement information of the PCell (e.g., global cell identity (GCI)) related to the CE only when it changes. For example, the communication processor (510) may record information related to the conditions of a commonly applied measurement (or report) only once. By reducing the number of times some of the measurement information of the PCell (e.g., GCI) is recorded, the communication processor (510) may prevent additional overhead that occurs while the communication processor is operating (e.g., recording).

[0090] The communication processor (510) can transmit the recorded CE sequence to the application processor (520).

[0091] The application processor (520) can report (or transmit) the CE sequence received from the communication processor (510) to the server (530).

[0092] A communication processor (510) according to one embodiment can record only some of the redundant information according to [Table 2]. Even if the communication processor (510) has a smaller storage capacity than the application processor (520), it can reliably record information related to CE by recording only some of the redundant information.

[0093] FIG. 6a is a block diagram of a communication processor according to one embodiment.

[0094] According to one embodiment, the communication processor (510) may include a protocol stack (640), a layer associated with the protocol stack, a receiving module (630), a writing module (620), and / or a controller (610). The writing module (620) may include at least one buffer. The protocol stack (640) may include an RRC layer (650), a MAC layer (660), and / or a PHY layer (670). The layer associated with the protocol stack may include an RRM layer (680).

[0095] According to one embodiment, the controller (610) may receive a request to record information related to CE and / or a CE policy from the application processor (520). When the controller (610) receives a request to record information related to CE and / or a CE policy from the application processor (520), it may check whether the application processor (520) is activated.

[0096] According to one embodiment, the controller (610) can detect that the application processor (520) is activated. For example, the communication processor (510) can detect that the application processor (520) is activated when the display of the electronic device (400) (e.g., the display (140) of FIG. 1) is activated for a specified period of time. When the application processor (520) is activated, the display (140) can be activated. The controller (610) can detect that the application processor (520) is activated by confirming that the display (140) is activated.

[0097] According to one embodiment, the controller (610) may wait for a specified time when the application processor (520) is deactivated. The controller (610) may check whether the application processor (520) is activated after waiting for the specified time. The controller (610) may repeat the action of waiting for a specified time until the application processor (520) is activated and the action of checking whether the application processor (520) is activated.

[0098] According to one embodiment, the controller (610) may request the application processor (520) to activate the application processor (520) if the application processor (520) is disabled for a period exceeding a specific time. The controller (610) may repeat the action of waiting for a specified time and the action of checking whether the application processor (520) is activated until the specific time is exceeded, and may activate the application processor (520) if the specific time is exceeded. Information indicating the specific time may be included in the CE policy.

[0099] According to one embodiment, the controller (610) can check whether a CE sequence is stored in a buffer of the communication processor. The controller (610) can check whether a CE sequence is stored in a buffer included in the writing module (620) of the communication processor. If there is a written CE sequence, the communication processor (510) can be configured to write information related to the CE after transmitting the written CE sequence to the application processor (520).

[0100] According to one embodiment, the controller (610) can transfer the CE sequence to the application processor (520) when the CE sequence is stored in the buffer.

[0101] According to one embodiment, the controller (610) can check whether at least one of the periods for reporting information related to CE has elapsed. If at least one of the periods for reporting information related to CE has not elapsed, the controller (610) can wait for a specified time. The period for reporting information related to CE can be set for each category of information related to CE. For example, a period for reporting information related to CE can be set for each of the following: a first category corresponding to predetermined information related to signal quality or network status, a second category corresponding to predetermined information related to changes in communication between the network and the electronic device, or a third category corresponding to predetermined information related to failure of communication between the network and the electronic device. According to one example, the period for reporting information related to CE in the third category can be set to be shorter than the period for reporting information related to CE in the second category. The period for reporting information related to CE in the second category can be set to be shorter than the period for reporting information related to CE in the first category. The electronic device can set different frequencies for reporting information related to CE of a specific category by setting different reporting cycles for information related to CE of each category. When information related to CE of a specific category is required among the CE-related information of the electronic device, the server can increase the frequency of recording information related to CE of a specific category by the electronic device by reducing the reporting cycle for CE-related information.

[0102] According to one embodiment, the CE policy may include rules that indicate the reporting period for information related to the CE of each of the plurality of categories (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure of [Table 1]). A communication processor may determine whether the reporting period for information related to the CE has elapsed since the time when the last CE sequence was transmitted to the server, based on the rules that indicate the reporting period for information related to the CE of each of the plurality of categories (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure of [Table 1]).

[0103] The controller (610) may register a CE to the receiving module (630) when at least one of the cycles for reporting information related to the CE has elapsed. The operation of registering a CE to the receiving module (630) may refer to an operation of setting the receiving module (630) to receive information related to the CE. For example, the controller (610) may transmit a registration command to the receiving module (630) when at least one of the cycles for reporting information related to the CE has elapsed. By transmitting a registration command to the receiving module (630), the controller (610) may enable the receiving module (630) to obtain information related to the CE from the layer where the CE occurred (e.g., RRC layer, MAC layer, PHY layer, RRM layer). The state of the communication processor may be switched from an inactive state to an active state in response to the registration of the CE to the receiving module (630).

[0104] According to one embodiment, the receiving module (630) may transmit information related to the CE to the recording module (620) when the CE is registered. The receiving module (630) may transmit information related to the CE to the recording module (620) based on a first method (e.g., an event-driven method) or a second method (e.g., an adaptive polling method). For example, the receiving module (630) may transmit information related to the CE to the recording module (620) based on either the first method or the second method, depending on the layer where the CE occurs (e.g., an RRC layer, a MAC layer, a PHY layer, an RRM layer) and / or the characteristics of the information related to the CE (e.g., the occurrence period). For example, the receiving module (630) may receive information related to the CE from a layer included in the protocol stack (640) (or a layer related to the protocol stack) based on the first method. The first method may refer to a method of receiving information related to the CE from the layer where the CE occurred whenever the CE occurs. The receiving module (630) may request a layer included in the stack (or a layer associated with the protocol stack) to transmit information related to the CE to the receiving module (630) when the CE is registered. A layer included in the protocol stack (640) (or a layer associated with the protocol stack) may transmit information related to the CE to the receiving module (630) when the CE occurs. According to one example, the receiving module (630) may receive information related to the CE from the RRC layer (650), the MAC layer (660), and / or the RRM layer (680) based on the first method.

[0105] According to one embodiment, the receiving module (630) may receive CE-related information that occurs in seconds among CE-related information based on the first method. For example, the receiving module (630) may receive RRC messages based on the first method. RRC messages may include RRC reconfiguration, RRC reestablishment, and / or RRC release. RRC reconfiguration may refer to a message instructing to change the settings of a currently connected RRC connection. For example, changing the settings of a currently connected RRC connection may include connection setup and / or connection resume handover. RRC reestablishment may refer to a message instructing to restore the connection when the RRC connection between the network and the electronic device is temporarily disconnected. RRC release may refer to a message instructing to terminate the RRC connection between the network and the electronic device.

[0106] The receiving module (630) can receive information related to CE from a layer included in the protocol stack (640) based on the second method. The second method may refer to a method of receiving (or reading) information related to CE from the layer where the CE occurred at a fixed interval from the time a specific event occurs until the specific event ends. The receiving module (630) can check whether a specific event has occurred in the protocol stack (640) based on information related to CE that is recorded when a CE is registered (e.g., information related to CE received according to the first method). If a specific event has occurred in the protocol stack (640), the receiving module (630) can receive (or read) information related to CE from a layer included in the protocol stack (640) at a fixed interval. The receiving module (630) can stop receiving information related to CE when the specific event ends. The specific event may include an event where a communication processor is connected to a network (e.g., RRC connected). For example, the receiving module (630) can receive (or read) information related to CE from the PHY layer based on the second method when the communication processor is connected to the network. The receiving module (630) can receive (or read) information related to CE from the PHY layer at a set period and transmit it to the writing module (620). The receiving module (630) can stop the operation of receiving information related to CE from the PHY layer (670) as the communication processor is connected to the network and then the connection to the network is interrupted (e.g., RRC idle) or transitions to a state preparing for connection to the network (e.g., RRC inactive).

[0107] According to one embodiment, the receiving module (630) can read information related to CE occurring in milliseconds based on a second method. Among the information related to CE, information related to the channel quality indicator (CQI), rank indicator (RI), modulation and coding scheme (MCS), block error rate (BLER), and / or uplink transmission power (UL Tx power) may be information occurring in milliseconds. The electronic device (400) may experience a problem of slowed operation speed (e.g., sluggish issue) or a problem of interrupted operation (e.g., crash) when the receiving module (630) receives information occurring in milliseconds using the first method. The receiving module (630) can read information related to CE by using a method of receiving (or reading) information related to CE from the layer where CE occurred (e.g., RRC layer) at fixed intervals from the time a specific event occurs (e.g., RRC setup request) until the time a specific event ends (e.g., release) so as not to cause a problem (e.g., sluggish issue, crash) in the operation of the electronic device (400). For example, the receiving module (630) can read information related to CQI, RI, MCS BLER, and UL Tx power based on the second method.

[0108] The recording module (620) can record information related to CE received from the receiving module (630) into a buffer included in the recording module (620).

[0109] The controller (610) can check whether the period for recording information related to CE, which is predetermined information of the third category, and reporting information related to CE of the third category has elapsed. If the period for recording information related to CE, which is predetermined information of the third category, and reporting information related to CE of the third category has elapsed, the controller (610) can determine to collect the CE sequence of the third category.

[0110] The controller (610) can check whether information related to CE, which is predetermined information of the third category, has not been recorded or whether the period for reporting information related to CE of the third category has not elapsed, and whether information related to CE, which is predetermined information of the second category, has been recorded and whether the period for reporting information related to CE of the second category has elapsed.

[0111] The controller (610) can determine to collect the CE sequence of the second category when information related to CE, which is predetermined information of the second category, is recorded and a period for reporting information related to CE of the second category has elapsed.

[0112] The controller (610) can check whether information related to CE, which is predetermined information of the second category, has not been recorded or whether the period for reporting information related to CE of the second category has not elapsed, and whether information related to CE, which is predetermined information of the first category, has been recorded and whether the period for reporting information related to CE of the first category has elapsed.

[0113] The controller (610) can determine to collect the CE sequence of the first category when information related to CE, which is predetermined information of the first category, is recorded and a period for reporting information related to CE of the first category has elapsed.

[0114] When the controller (610) determines to collect a CE sequence, it may record information related to CE for a specified time from the time when the CE sequence collection is determined (or the time when information related to CE, which is predetermined information, is recorded). The controller (610) may check the specified time based on the CE policy. The CE policy may include a rule (e.g., freezeDelay in [Table 1]) that indicates the specified time for the communication processor to record information related to CE after recording the predetermined information. According to one example, the rule (e.g., freezeDelay in [Table 1]) that indicates the specified time for the communication processor to record information related to CE after recording the predetermined information may include information indicating the specified time for each of a plurality of categories (e.g., first category, second category, third category). When the communication processor determines to collect a CE sequence of the third category (or second category, first category), it may check whether the specified time for the third category (or second category, first category) has elapsed.

[0115] The controller (610) may stop recording information related to CE, freeze the buffer, and unregister CE of the receiving module (630) when a specified time has elapsed. The operations of stopping recording information related to CE, freezing the buffer, and / or unregistering CE of the receiving module (630) may be performed in parallel or sequentially.

[0116] A CE sequence may include predetermined information (e.g., predetermined information indicated by the targetCE of [Table 1]). The electronic device of the present disclosure may use a circular buffer so that the CE sequence includes the predetermined information. According to one example, a recording module (620) may record a specific CE (e.g., HO (handover)) sequence. When recording a specific CE (e.g., HO) sequence, the recording module (620) needs to record information related to the CE between the time when the specific CE (e.g., HO) started (e.g., when the HO command was received) and the time when the specific CE (e.g., HO) ended (e.g., when the HO result was obtained). The recording module (620) may use a circular buffer to store information from before the specific CE (e.g., HO) started until the time when the specific CE (e.g., HO) ended. For example, the recording module (620) can record information related to CE in the circular buffer from before a specific CE (e.g., HO) starts, and can continue to record information related to CE even after the specific CE (e.g., HO) ends until the controller (610) stops recording information related to CE. The circular buffer can store information from before the specific CE (e.g., HO) starts until the point when the specific CE (e.g., HO) ends.

[0117] FIG. 6b is a diagram illustrating a buffer of a communication processor according to one embodiment.

[0118] According to one embodiment, the communication processor (510) may include a recording module (620). The recording module (620) may include at least one buffer. The buffer included in the recording module (620) may be a circular buffer. The circular buffer can delete the oldest data and store new data when storing new data in a situation where storage capacity is insufficient. It should be understood that the buffers described below are identical buffers, except that the information related to CE stored varies depending on the recording operation of the communication processor. The start (begin) indicated in each buffer may represent the information stored first among the information stored in each buffer. The end (begin) indicated in each buffer may represent the information stored last among the information stored in each buffer.

[0119] According to one embodiment, the buffer (621) may not store information related to CE before the recording operation is performed.

[0120] According to one embodiment, the buffer (622) is a circular buffer in a state where it does not store predetermined information set to be included in the CE sequence (e.g., predetermined information indicated by the targetCE of [Table 1]). As the communication processor (510) begins writing information related to the CE, the buffer (622) can sequentially store information related to the CE (e.g., information from the begin to the end of the buffer (622)). The communication processor (510) can store information related to the CE in the buffer (622) until the predetermined information set to be included in the CE sequence (e.g., predetermined information indicated by the targetCE of [Table 1]) is stored in the buffer (622). Thus, the buffer (622) can store additional information related to the CE even after storing information related to the CE (e.g., information stored sequentially from the begin to the end of the buffer (622).

[0121] According to one embodiment, if the buffer (623) stores additional information related to CE after storing information related to CE (e.g., information stored sequentially from begin to end of the buffer (622)), the storage capacity may be insufficient. If the buffer (623) stores new information when the storage capacity is insufficient, it may delete the oldest information and store the new information. Thus, the buffer (623) can store sequential information from the first stored information (begin) to the last stored information (end).

[0122] According to one embodiment, the buffer (623) may store predetermined information (610) that is set to be included in the CE sequence. The communication processor (510) may store additional information related to CE even after storing the last stored information (end) because, based on a rule (e.g., freezeDelay of [Table 1]) that indicates a specified time for the communication processor (510) to record information related to CE after recording the predetermined information (610), the communication processor (510) records information related to CE for a specified time after recording the predetermined information (610).

[0123] According to one embodiment, the buffer (624) may store information related to CE that occurs for a specified time after recording the predetermined information (610). The communication processor (510) may stop recording information related to CE after recording the predetermined information (610) for a specified time (e.g., the specified time indicated by freezeDelay in [Table 1]). When the communication processor (510) stops recording information related to CE, it may freeze the buffer. Information related to CE stored in the frozen buffer (e.g., information stored sequentially from begin to end of the buffer (624)) may be referred to as a CE sequence. According to one example, the communication processor (510) may exclude information related to CE that exceeds a specified length from the CE sequence based on a rule indicating the length of the CE sequence transmitted to the server (e.g., reportLength in [Table 1]). The communication processor (510) can determine a CE sequence of information related to CE of a predetermined length, starting from the information related to the last recorded CE.

[0124] The electronic device (400) may record information related to CE in a circular buffer before recording the predetermined information (610), and may also record information related to CE for a specified time (e.g., the specified time indicated by freezeDelay in [Table 1]) after recording the predetermined information (610). The electronic device may obtain a CE sequence containing the predetermined information (610).

[0125] Additionally, the electronic device (400) can record information related to CE while deleting old information using a circular buffer. Thus, the CE sequence can be recorded while stably managing the storage capacity of the buffer. However, it should be understood that the electronic device of the present disclosure is not required to use a circular buffer to record the CE sequence.

[0126] According to one embodiment, the communication processor (510) may stop recording information related to CE if, based on a rule (e.g., recordInterval of [Table 1]) indicating a maximum time for recording information related to CE, the information related to CE, which is predetermined information, is not recorded during the maximum time for recording information related to CE. The buffers (621, 622, 623, 624) illustrated in FIG. 6b may not further store information related to CE if the communication processor (510) stops recording information related to CE.

[0127] According to one embodiment, the recording module may include a plurality of buffers. For example, the recording module may include two buffers. When a CE sequence is recorded (or stored) in one of the two buffers, the recording module may record information related to the CE in the other of the two buffers. While recording information related to the CE in the other of the two buffers, if the period for reporting the CE sequence (e.g., a period based on the reportInterval of [Table 1]) arrives, the recording module may record information related to the CE in the other of the two buffers and report the already recorded CE sequence to the server.

[0128] FIG. 7 is a block diagram of an application processor according to one embodiment.

[0129] According to one embodiment, the controller (710) can confirm whether the electronic device (400) is activated or whether the user's consent to recording CE-related information changes.

[0130] Activation of the electronic device (400) may refer to the electronic device (400) switching from an inactive state to an active state. The controller (710) may detect that the electronic device (400) switches from an inactive state to an active state.

[0131] The controller (710) may receive user input indicating consent or non-consent to recording information related to CE. When the controller (710) receives user input indicating consent or non-consent to recording information related to CE, it may check whether the user's consent to recording information related to CE has changed. When the controller (710) first receives user input indicating consent or non-consent to recording information related to CE, it may check that the user's consent to recording information related to CE has changed.

[0132] The controller (710) may receive user input indicating whether consent is given to recording information related to CE occurring during the execution of the specific software when the specific software is first executed, if the specific software is installed on the electronic device (400). For example, the controller (710) may receive user input indicating whether consent is given to recording information related to CE occurring in the specific application when the specific application is first executed, if the specific application is first set up.

[0133] The controller (710) can determine whether the user consents to recording information related to CE. The controller (710) can determine whether the user consents to recording information related to CE based on the user's existing consent when the electronic device (400) is activated while the user's existing consent to recording information related to CE is maintained.

[0134] If the user does not agree to record information related to CE, the controller (710) may request the communication processor not to record information related to CE. If the user agrees to record information related to CE, the controller (710) may request the communication processor to record information related to CE.

[0135] The controller (710) can check whether the CE policy has expired. The controller (710) can determine that the CE policy has expired if there is no CE policy stored in the buffer (720) of the application processor or if the validity period of the CE policy stored in the buffer (720) has expired. According to one embodiment, if the CE policy has expired, the controller (710) can receive an updated CE policy from the server (530). The updated CE policy may be a CE policy whose validity period has not expired.

[0136] The controller (710) can transmit the CE policy to the communication processor. If the CE policy has not expired, the controller (710) can transmit the CE policy stored in the buffer (720) of the application processor to the communication processor. If the CE policy has expired, the controller (710) can transmit the updated CE policy received from the server (530) to the communication processor.

[0137] When the communication processor receives a CE policy from the controller (710), it can record information related to the CE. The communication processor can transmit a CE sequence, which is a set of information related to the CE, to the application processor.

[0138] The controller (710) can receive a CE sequence from a communication processor. The communication processor can transmit the CE sequence to the controller (710). When the application processor is activated, the communication processor can transmit the CE sequence stored in a buffer included in the communication processor to the controller (710).

[0139] The controller (710) can accumulate CE sequences in the buffer (720) of the application processor. The communication processor can transfer the CE sequences stored in the buffer of the communication processor to the controller (710) whenever the application processor is activated. The controller (710) can store multiple CE sequences in the buffer (720) of the application processor. The controller (710) can store CE sequences in the buffer (720) of the application processor whenever it receives a CE sequence from the communication processor. The controller (710) can limit the capacity of CE sequences accumulated based on a rule (e.g., sizeOfMemory in [Table 1]) that indicates the maximum capacity of CE sequences stored in the application processor (520).

[0140] The controller (710) can store information acquired by the application processor in the application processor's buffer (720) along with the CE sequence. For example, the controller (710) can tag the information acquired by the application processor in the CE sequence. The information acquired by the application processor may include at least one of information related to the electronic device (400) (e.g., model name, binary version (or software version) of the electronic device (400)) and / or information indicating a CE policy. The information indicating a CE policy may refer to information for identifying the CE policy used by the communication processor while recording (or generating) the CE sequence.

[0141] The controller (710) can check whether the reporting period has elapsed. The reporting period may be determined based on the CE policy. According to one embodiment, the controller (710) may be configured to report at least one CE sequence stored in the buffer (720) of the application processor to the server (530) at each period in which the controller (710) reports a CE sequence to the server (530), based on a rule (e.g., reportInterval of [Table 1]) that indicates the period in which the controller (710) reports a CE sequence to the server (530) included in the CE policy.

[0142] The controller (710) can accumulate CE sequences until the reporting cycle has elapsed, if the reporting cycle has not elapsed. If the reporting cycle has elapsed, the controller (710) can check whether the electronic device (400) is connected to Wi-Fi.

[0143] The controller (710) can determine whether the user has agreed to use cellular network-based communication when the electronic device (400) is not connected to Wi-Fi. Using cellular network-based communication may include transmitting a CE sequence to the server using cellular network-based communication.

[0144] The controller (710) can check whether the user has agreed to report errors, and whether the user has agreed to report errors, if the user has not agreed to use cellular network-based communication, and the CE sequence associated with the error is stored in the buffer (720).

[0145] The controller (710) can accumulate CE sequences until the reporting cycle has elapsed if the CE sequence associated with the error is not stored in the buffer (720) or if the user does not agree to report the error.

[0146] The controller (710) may report at least one CE sequence to the server (530). The controller (710) may report to the server (530) a CE sequence bundle that is at least part of at least one CE sequence accumulated in the buffer (720) of the application processor. The controller (710) may delete at least part of the reported CE sequence from the buffer (720) of the application processor.

[0147] The controller (710) can report at least one CE sequence to the server (530) when the electronic device (400) is connected to Wi-Fi, the user agrees to use communication based on a cellular network, or when a CE sequence related to an error is stored in the buffer (720) and the user agrees to report the error.

[0148] The controller (710) can report at least one CE sequence to the server (530) based on Wi-Fi when the electronic device (400) is connected to Wi-Fi. Since the electronic device (400) reports a CE sequence based on Wi-Fi when connected to Wi-Fi, it can prevent the user from unintentionally using communication based on a cellular network.

[0149] The controller (710) can report a CE sequence using cellular network-based communication if the user has agreed to use cellular network-based communication even if the electronic device (400) is not connected to Wi-Fi. The electronic device (400) can report a CE sequence to the server (530) even when Wi-Fi is not connected. If the user has agreed to use cellular network-based communication, the electronic device (400) can prevent the user from unintentionally using cellular network-based communication by using cellular network-based communication.

[0150] The controller (710) may report the CE sequence related to the error using cellular network-based communication even if the user does not consent to using cellular network-based communication, provided that the CE sequence related to the error is stored in the buffer (720) and the user consents to reporting the error. The electronic device (400) may report the CE sequence related to the error to the server (530) in certain situations, even if the user does not consent to using cellular network-based communication.

[0151] FIG. 8 is a block diagram of a server according to one embodiment.

[0152] The server (530) may include a database and / or a controller (810). The server (530) may additionally include at least one component for communicating with the electronic device (400). The database may store at least one CE policy.

[0153] When the server controller (810) receives a CE policy request from the application processor (520), it may determine (or generate) a CE policy to be transmitted to the electronic device (400) based on information related to the electronic device (400) (e.g., model name, binary version (or software version) of the electronic device (400)) and / or a public land mobile network (PLMN). The electronic device (400) may perform on / off control, RAT control, parameter optimization, and / or record information related to CE using the CE policy generated by the controller (810). The CE policy generated by the controller (810) may include some of the contents of [Table 1].

[0154] The server controller (810) may receive information obtained by the application processor (520) from the application processor (520) (e.g., information related to the electronic device (400) (e.g., model name, binary version (or software version) of the electronic device (400)) and / or information indicating a CE policy). When the application processor (520) transmits a CE sequence bundle to the server (530), it may transmit the information indicating the CE policy together.

[0155] The controller (810) can determine whether the CE policy stored in the application processor (520) has expired based on information indicating the CE policy. For example, if the CE policy stored in the application processor (520) has expired, the controller (810) can receive an updated CE policy from the database (820).

[0156] The controller (810) can determine whether the cycle for updating the CE policy has arrived based on a rule indicating the cycle for updating the CE policy (e.g., nextPolicyUpdate in [Table 1]). For example, the controller (810) can receive information from the application processor (520) indicating that the cycle for updating the CE policy has arrived. When the controller (810) receives information from the application processor (520) indicating that the cycle for updating the CE policy has arrived, the controller (810) can receive the updated CE policy from the database (820).

[0157] According to one embodiment, the application processor (520) may receive an updated CE policy from the server (530) at each CE policy update cycle based on a rule indicating a CE policy update cycle (e.g., nextPolicyUpdate in [Table 1]). According to one embodiment, the application processor (520) may report information indicating a CE policy (e.g., policyID in [Table 1]) to the server (530). The controller (810) may transmit the updated CE policy to the application processor (520) based on the information indicating a CE policy (e.g., policyID in [Table 1]) received from the application processor (520). The electronic device (400) of the present disclosure may update a CE policy based on at least one of a rule indicating a CE policy update cycle (e.g., nextPolicyUpdate in [Table 1]) or information indicating a CE policy (e.g., policyID in [Table 1]).

[0158] FIG. 9 is a flowchart of the operation of a communication processor, an application processor, and a server according to one embodiment.

[0159] According to one embodiment, the communication processor (510) may perform operations (910, 920, 930, 940) related to initialization during step 901. However, some of the operations related to initialization may be omitted, and the order of some of the operations may be changed.

[0160] According to one embodiment, the application processor (520) may request the communication processor (510) to record information related to CE in operation 910.

[0161] CE may refer to events that occur while the electronic device (400) communicates based on cellular communication. CE may include events that occur in the protocol stack. For example, CE may include events that occur in the layer, MAC layer, and / or PHY layer. CE may include events that occur in the layer associated with the protocol stack. The layer associated with the protocol stack may include the RRM layer. Events that occur in the RRC layer may include events that occur between the core network (e.g., the core network (410) of FIG. 4) and the communication processor. For example, events that occur in the RRC layer may include connection setup, connection resume, handover (HO), connection re-establishment, and connection release. Events that occur in the MAC layer may include events that occur between the base station and the communication processor. For example, events that occur in the MAC layer may include events related to RACH. Events occurring in the PHY layer may include events related to UL Tx power, path loss, CQI, RI, MCS, and BLER.

[0162] According to one embodiment, the application processor (520) can confirm whether the user's consent to confirming that the electronic device is activated or recording CE-related information has changed.

[0163] The application processor (520) can check whether the user consents to recording CE-related information when the electronic device is activated or when the user's consent to recording CE-related information changes. If the user consents to recording CE-related information, the application processor (520) can request the communication processor (510) to record CE-related information.

[0164] According to one embodiment, the application processor (520) may request a CE policy from the server (530) in operation 920.

[0165] For example, the application processor (520) may request an updated CE policy from the server (530) when the cycle for updating the CE policy arrives, based on a rule (e.g., nextPolicyUpdate in [Table 1]) that indicates the cycle for updating the CE policy.

[0166] According to one embodiment, the server (530) may transmit the updated CE policy to the application processor (520) in operation 930. According to one example, if the cycle for updating the CE policy has not arrived, operations 920 and 930 may be omitted.

[0167] According to one embodiment, the application processor (520) may transmit an updated CE policy to the communication processor (510) in operation 940. According to one example, if the cycle for updating the CE policy has not arrived, the application processor (520) may transmit an existing CE policy stored in the buffer of the application processor (520), rather than the updated CE policy, to the communication processor (510).

[0168] A CE policy includes a rule specifying the cycle for updating the CE policy (e.g., nextPolicyUpdate in [Table 1]), information representing the CE policy (e.g., policyID in [Table 1]), a rule specifying the cycle for the application processor to report CE sequences to the server (e.g., reportInterval in [Table 1]), a rule specifying the maximum capacity of CE sequences stored in the application processor (e.g., sizeOfMemory in [Table 1]), a rule specifying the cycle for reporting information related to CEs for each of multiple categories (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure in [Table 1]), a rule specifying the maximum time for the communication processor to record information related to CEs (e.g., recordInterval in [Table 1]), a rule specifying the network method among multiple network methods that is the target for recording information related to CEs (e.g., supportRat in [Table 1]), a rule specifying the predetermined information configured to be included in the CE sequence (e.g., targetCE in [Table 1]), and a rule specifying the designated time for the communication processor to record information related to CEs after the predetermined information has been recorded. It may include a rule (e.g., freezeDelay in [Table 1]) and / or a rule indicating the length of the CE sequence sent to the server (e.g., reportLength in [Table 1]).

[0169] According to one embodiment, the communication processor (510) may perform an operation related to recording during step 902. The details of how the communication processor (510) performs the recording operation will be described in FIGS. 11, FIGS. 12, FIGS. 13a, and FIGS. 13b.

[0170] According to one embodiment, step 902 may include an operation of recording a CE sequence according to a rule (e.g., supportCE in [Table 1]) that indicates information related to the CE that is a recording target of the communication processor included in the CE policy.

[0171] According to one embodiment, the communication processor (510) may perform operations related to reporting (950, 960, 970, 980) during step 903. However, some of the operations related to reporting may be omitted, and some of the operations may be changed.

[0172] According to one embodiment, the communication processor (510) can transmit a CE sequence to the application processor (520) in operation 950.

[0173] When the application processor (520) is activated, the communication processor (510) can transmit the CE sequence stored in the buffer of the communication processor (510) to the application processor (520). The application processor (520) can report at least one CE sequence stored in the buffer of the application processor (520) to the server (530) at each period in which the application processor (520) reports the CE sequence to the server (530), based on a rule (e.g., reportInterval of [Table 1]) that indicates the period in which the application processor (520) reports the CE sequence to the server (530) included in the CE policy.

[0174] According to one embodiment, the application processor (520) can transmit at least one CE sequence to the server (530) in operation 960.

[0175] The server (530) can receive information obtained by the application processor (520) from the application processor (520). For example, the server (530) can receive information indicating a CE policy from the application processor (520). When the application processor (520) transmits a CE sequence bundle to the server (530), it can transmit the information indicating the CE policy together with it. Based on the information indicating the CE policy, the server (530) can check whether the CE policy stored in the application has expired.

[0176] According to one embodiment, the server (530) may transmit an updated CE policy to the application processor (520) in operation 970. However, if the CE policy stored in the application processor (520) has not expired, operation 970 may be omitted.

[0177] According to one embodiment, the application processor (520) may transmit the updated CE policy to the communication processor (510) in operation 980. However, if the CE policy stored in the application processor (520) has not expired, operation 980 may be omitted.

[0178] FIG. 10 is a flowchart of the initial setup operation of an application processor according to one embodiment.

[0179] According to one embodiment, an application processor (e.g., the application processor (520) of FIG. 5) can confirm, in operation 1010, that an electronic device (e.g., the electronic device (400) of FIG. 4) is activated or that the user's consent to recording information related to CE is changed.

[0180] Activating the electronic device (400) may refer to the electronic device (400) transitioning from an inactive state to an active state. The application processor (520) may detect that the electronic device (400) transitions from an inactive state to an active state.

[0181] According to one embodiment, the application processor (520) may receive user input indicating consent or non-consent to recording information related to CE. When the application processor (520) receives user input indicating consent or non-consent to recording information related to CE, it may check whether the user's consent to recording information related to CE has changed. A change in the user's consent to recording information related to CE may include the consent or non-consent being set by the initial user input indicating consent or non-consent to recording information related to CE. The user's consent to recording information related to CE may be set for each software.

[0182] According to one embodiment, the application processor (520) may receive user input indicating consent to record information related to CE occurring during the execution of the specific software when the specific software is first executed, when the specific software is installed on the electronic device (400). For example, the application processor (520) may receive user input indicating consent to record information related to CE occurring in the specific application when the specific application is first executed, when the specific application is installed.

[0183] According to one embodiment, the application processor (520) can determine whether the user agrees to record information related to CE in operation 1015.

[0184] According to one embodiment, the application processor (520) can determine whether the user consents to recording information related to CE based on the user's existing consent when the electronic device (400) is activated while the user's existing consent to recording information related to CE is maintained.

[0185] According to one embodiment, the application processor (520) may request the communication processor (510) not to record information related to CE if, in operation 1016, the user does not agree to record information related to CE.

[0186] In operation 1020, if the user agrees to record information related to CE, the application processor (520) may request the communication processor (510) to record information related to CE.

[0187] The communication processor (510) can perform a recording operation of information related to CE when requested to record information related to CE. The recording operation of information related to CE by the communication processor (510) will be described in FIGS. 11, FIGS. 12, FIGS. 13a, and FIGS. 13b.

[0188] According to one embodiment, the application processor (520) can check whether the CE policy has expired in operation 1025.

[0189] The application processor (520) can determine that the CE policy has expired if there is no CE policy stored in the buffer (720) of the application processor (520) or if the validity period of the CE policy stored in the buffer has expired.

[0190] According to one embodiment, the application processor (520) may receive an updated CE policy from the server when the CE policy has expired in operation 1030. The updated CE policy may refer to a CE policy whose validity period has not expired.

[0191] According to one embodiment, the application processor (520) can transmit a CE policy to the communication processor (510) in operation 1040. If the CE policy has not expired, the application processor (520) can transmit the CE policy stored in the buffer (720) of the application processor (520) to the communication processor (510). If the CE policy has expired, the application processor (520) can transmit an updated CE policy received from the server to the communication processor (510).

[0192] FIG. 11 is a diagram illustrating the state of a communication processor according to one embodiment.

[0193] The communication processor (e.g., the communication processor (510) of FIG. 5) may be in any one of the following states when the electronic device is activated: off state (1103), activated state (1102), or deactivated state (1101).

[0194] The communication processor (510) can be set to an off state (1103) in response to the electronic device (400) being activated in an inactive state (1101).

[0195] The transition (1110) from the off state (1103) to the disabled state (1101) may occur according to the initial setup step of FIG. 10. The application processor (520) obtains user consent for recording information related to CE 40

[0196] In response to the inbox, a request for recording of information related to CE can be made to the communication processor (510), and a CE policy can be transmitted to the communication processor (510). When the communication processor (510) receives the request for recording of information related to CE and receives the CE policy, it can be switched from an off state (1103) to an inactive state (1101).

[0197] Transition (1120) from an inactive state (1101) to an off state (1103) and transition (1121) from an active state (1102) to an off state (1103) may occur depending on the user's non-consent to recording information related to CE.

[0198] The transition (1140) from the disabled state (1101) to the enabled state (1102) may occur as CE is registered in the receiving module of the communication processor (510). For example, it may occur according to the operation of the communication processor (510) described in FIG. 12.

[0199] The transition (1130) from the active state (1102) to the inactive state (1101) may occur as CE is deregistered from the receiving module of the communication processor (510). For example, it may occur according to the operation of the communication processor (510) described in FIGS. 13a and FIGS. 13b.

[0200] FIG. 12 is a flowchart of the operation of a communication processor (510) in a deactivated state according to one embodiment.

[0201] As the communication processor (510) performs the operation of FIG. 12, the state of the communication processor (510) can be transitioned from an inactive state to an active state.

[0202] A communication processor (510) according to one embodiment can detect that an application processor (520) is activated in operation 1210.

[0203] According to one embodiment, when the application processor (520) is activated, the display may be activated. The communication processor (510) may detect that the application processor (520) is activated by confirming that the display is activated. For example, the communication processor (510) may detect that the application processor (520) is activated when the display of the electronic device (400) is activated for a specified period of time.

[0204] The communication processor (510) may wait for a specified time when the application processor (520) is disabled. The communication processor (510) may check whether the application processor (520) is enabled after waiting for the specified time. The communication processor (510) may repeat the action of waiting for a specified time until the application processor (520) is enabled and the action of checking whether the application processor (520) is enabled.

[0205] The communication processor (510) may request the application processor (520) to activate the application processor (520) if the application processor (520) is disabled for a period exceeding a specific time. The communication processor (510) may repeat the action of waiting for a specified time and the action of checking whether the application processor (520) is activated until the specific time is exceeded, and may activate the application processor (520) when the specific time is exceeded. Information indicating the specific time may be included in the CE policy.

[0206] According to one embodiment, the communication processor (510) can check whether a CE sequence is stored in the buffer in operation 1215.

[0207] The communication processor (510) can check whether the CE sequence recorded by the communication processor (510) is stored in a buffer included in the recording module of the communication processor (510). If there is a recorded CE sequence, the communication processor (510) can be configured to record information related to the CE after transmitting the recorded CE sequence to the application processor (520).

[0208] A CE sequence may consist of information related to CE recorded by a communication processor (510). A CE sequence may include information related to CE according to a rule (e.g., targetCE in [Table 1]) that indicates information related to CE that is set to be included in the CE sequence. After recording the information related to CE, the communication processor (510) may stop recording information related to CE after recording information related to CE for a specified time (e.g., the specified time indicated by freezeDelay in [Table 1]). When the communication processor (510) stops recording information related to CE, it may freeze the buffer. Information related to CE stored in the frozen buffer may be referred to as a CE sequence. According to one example, the communication processor (510) may exclude information related to CE that exceeds a specified length from the CE sequence based on a rule (e.g., reportLength in [Table 1]) that indicates the length of the CE sequence transmitted to the server. The communication processor (510) can determine a CE sequence of information related to CE of a predetermined length, starting from the information related to the last recorded CE.

[0209] According to one embodiment, the communication processor (510) can transmit the CE sequence to the application processor (520) when the CE sequence is stored in the buffer in operation 1216.

[0210] The communication processor (510) may include a recording module. The recording module may include at least one buffer. The buffer included in the recording module may be a circular buffer. The circular buffer can delete the oldest data and store new data when storing new data in a situation where storage capacity is insufficient.

[0211] A communication processor (510) according to one embodiment can check whether at least one of the cycles reporting information related to CE has elapsed in operation 1225.

[0212] The communication processor (510) may wait for a specified time if at least one of the cycles reporting information related to CE has not elapsed. After waiting for the specified time, the communication processor (510) may check whether the application processor (520) is activated in operation 1210.

[0213] The reporting period for information related to CE can be set for each category of information related to CE. For example, a reporting period for information related to CE can be set for each of the following: a first category corresponding to predetermined information related to signal quality or network status, a second category corresponding to predetermined information related to changes in communication between the network and the electronic device (400), or a third category corresponding to predetermined information related to failure of communication between the network and the electronic device (400).

[0214] According to one embodiment, the CE policy may include rules (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure of [Table 1]) that indicate the period for reporting information related to the CE of each of the plurality of categories. The communication processor (510) can determine whether the period for reporting information related to the CE has elapsed since the time when the last CE sequence was transmitted to the server, based on the rules (e.g., reportIntervalNormal, reportIntervalChange, reportIntervalFailure of [Table 1]) that indicate the period for reporting information related to the CE.

[0215] According to one embodiment, the communication processor (510) can register the CE to the receiving module in operation 1230 when at least one of the cycles for reporting information related to the CE has elapsed.

[0216] The operation of registering CE to the receiving module may refer to the operation of setting the receiving module to receive information related to CE. The state of the communication processor (510) may be switched to an active state in response to registering CE to the receiving module.

[0217] FIGS. 13a and FIGS. 13b are flowcharts of the operation of a communication processor in an active state according to one embodiment.

[0218] As the communication processor (510) performs the operations of FIG. 13a and FIG. 13b, the state of the communication processor (510) can be transitioned from an active state to an inactive state.

[0219] According to one embodiment, the communication processor (510) can record information related to CE in operation 1310.

[0220] According to one embodiment, the communication processor (510) can check whether, in operation 1315, information related to CE, which is predetermined information of the third category, is recorded and whether the period of the third category has elapsed. The period of the third category may refer to a period for reporting information related to CE of the third category included in the CE policy.

[0221] According to one embodiment, the communication processor (510) may determine to collect the CE sequence of the third category in operation 1325 when information related to CE of the third category, which is predetermined information of the third category, is recorded and a period for reporting information related to CE of the third category has elapsed.

[0222] According to one embodiment, the communication processor (510) can check in operation 1316 whether information related to CE, which is predetermined information of the third category, has been recorded and whether the period of reporting information related to CE of the third category has elapsed, in case information related to CE, which is predetermined information of the second category, has been recorded and the period of the second category has elapsed. The period of the second category may refer to the period of reporting information related to CE of the second category included in the CE policy.

[0223] According to one embodiment, the communication processor (510) may determine to collect the CE sequence of the second category in operation 1326 when information related to CE, which is predetermined information of the second category, is recorded and a period for reporting information related to CE of the second category has elapsed.

[0224] According to one embodiment, the communication processor (510) can check in operation 1317 whether information related to CE, which is predetermined information of the second category, has been recorded and whether the period of reporting information related to CE of the second category has elapsed, in case information related to CE, which is predetermined information of the first category, has not been recorded or the period of reporting information related to CE of the second category has not elapsed. The period of the first category may refer to the period of reporting information related to CE of the first category included in the CE policy.

[0225] According to one embodiment, the communication processor (510) may determine to collect the CE sequence of the first category in operation 1327 when information related to CE, which is predetermined information of the first category, is recorded and a period for reporting information related to CE of the first category has elapsed.

[0226] The electronic device (400) can determine whether information related to CE, which is predetermined information of the third category, has not been recorded or whether the period for reporting information related to CE of the third category has not elapsed, and whether information related to CE, which is predetermined information of the second category, has been recorded and whether the period for the second category has elapsed. The electronic device (400) can determine whether information related to CE, which is predetermined information of the second category, has not been recorded or whether the period for reporting information related to CE of the second category has not elapsed, and whether information related to CE, which is predetermined information of the first category, has been recorded and whether the period for the first category has elapsed. The electronic device (400) can determine whether to determine whether to collect the CE sequence of the second category if it cannot determine the collection of the CE sequence of the third category, and determine whether to determine the collection of the CE sequence of the first category if it cannot determine the collection of the CE sequence of the second category, thereby determining to collect the CE sequence of a specific category (e.g., the third category or the second category) preferentially.

[0227] According to one embodiment, the communication processor (510) can check whether the specified time of the third category has elapsed in operation 1335. According to one embodiment, the communication processor (510) can check whether the specified time of the second category has elapsed in operation 1336. According to one embodiment, the communication processor (510) can check whether the specified time of the first category has elapsed in operation 1337.

[0228] When the communication processor (510) determines to collect a CE sequence, it may record information related to CE for a specified time from the time when the CE sequence collection is determined (or the time when information related to CE, which is predetermined information, is recorded). The communication processor (510) may determine a specified time (e.g., a specified time in the third category, a specified time in the second category, a specified time in the first category) based on a CE policy. The CE policy may include a rule (e.g., freezeDelay in [Table 1]) that indicates a specified time for the communication processor (510) to record information related to CE after recording the predetermined information.

[0229] According to one example, a rule (e.g., freezeDelay in [Table 1]) that indicates a specified time for a communication processor (510) to record information related to CE after recording predetermined information may include information indicating a specified time for each of a plurality of categories (e.g., first category, second category, third category). When the communication processor (510) determines to collect a CE sequence of the third category (or second category, first category), it may check whether the specified time of the third category (or second category, first category) has elapsed.

[0230] According to one embodiment, the communication processor (510) may record information related to CE in operation 1338 until the specified time of the third category has elapsed, if the specified time of the third category has not elapsed in operation 1335. The communication processor (510) may perform operations after operation 1335 after operation 1338.

[0231] According to one embodiment, if the specified time of the second category has not elapsed in operation 1336, the communication processor (510) may record information related to CE in operation 1338 until the specified time of the second category has elapsed. The communication processor (510) may perform operations after operation 1336 after operation 1338.

[0232] The communication processor (510) may record information related to CE in operation 1338 until the specified time of the first category has elapsed, if the specified time of the first category has not elapsed in operation 1337. The communication processor (510) may perform operations after operation 1337 after operation 1338.

[0233] According to one embodiment, the communication processor (510) may, when a specified time has elapsed, stop recording information related to CE, freeze the buffer, and unregister the CE of the receiving module in operation 1340. The operation of stopping recording information related to CE, the operation of freezing the buffer, and / or the operation of unregistering the CE of the receiving module may be performed in parallel or sequentially.

[0234] The reporting period for information related to CE of the present disclosure may be set for each category of information related to CE. For example, a reporting period for information related to CE may be set for each of the following: a first category corresponding to predetermined information related to signal quality or network status, a second category corresponding to predetermined information related to changes in communication between the network and the electronic device (400), or a third category corresponding to predetermined information related to failure of communication between the network and the electronic device (400). According to one example, the reporting period for information related to CE of the third category may be set shorter than the reporting period for information related to CE of the second category. The reporting period for information related to CE of the second category may be set shorter than the reporting period for information related to CE of the first category. By setting the reporting period for information related to CE of each category differently, the electronic device (400) may set the frequency of reporting information related to CE of a specific category differently. When information related to a specific category of CE is required among the information related to CE of the electronic device (400), the server (430) can increase the frequency of recording information related to a specific category of CE by the electronic device (400) by reducing the frequency of reporting information related to CE.

[0235] FIG. 14 is a flowchart of the reporting operation of an application processor according to one embodiment.

[0236] According to one embodiment, an application processor (e.g., the application processor (520) of FIG. 5) may receive a CE sequence from a communication processor (e.g., the communication processor (510) of FIG. 5) in operation 1410.

[0237] The communication processor (510) can transmit a CE sequence to the application processor (520). When the application processor (520) is activated, the communication processor (510) can transmit the CE sequence stored in the buffer included in the communication processor (510) to the application processor (520).

[0238] According to one embodiment, the application processor (520) can accumulate a CE sequence in the buffer of the application processor (520) in operation 1420.

[0239] The communication processor (510) can transfer a CE sequence stored in the buffer of the communication processor (510) to the application processor (520) whenever the application processor (520) is activated. The application processor (520) can store multiple CE sequences. The application processor (520) can store a CE sequence in the buffer of the application processor (520) whenever it receives a CE sequence from the communication processor (510). The application processor (520) can limit the capacity of CE sequences accumulated based on a rule (e.g., sizeOfMemory in [Table 1]) that indicates the maximum capacity of CE sequences stored in the application processor (520).

[0240] The electronic device (400) can be configured so that the communication processor (510) transmits the CE sequence stored in the buffer to the application processor (520) only when the application processor (520) is activated. The electronic device (400) can prevent power consumption caused by activating the application processor (520) whenever the CE sequence is stored.

[0241] The application processor (520) may store the information acquired by the application processor (520) in the buffer of the application processor (520) along with the CE sequence. For example, the application processor (520) may tag the information acquired by the application processor (520) in the CE sequence. The information acquired by the application processor (520) may include at least one of information related to the electronic device (400) (e.g., model name, binary version (or software version) of the electronic device (400)) and / or information indicating a CE policy. The information indicating a CE policy may refer to information for identifying the CE policy used by the communication processor (510) while recording the CE sequence.

[0242] According to one embodiment, the application processor (520) can check whether the reporting cycle has elapsed in operation 1425.

[0243] The reporting period may be determined based on the CE policy. According to one embodiment, the application processor (520) may be configured to report at least one CE sequence stored in the buffer of the application processor (520) to the server (530) at each period in which the application processor (520) reports a CE sequence to the server (530), based on a rule (e.g., reportInterval of [Table 1]) that indicates the period in which the application processor (520) reports a CE sequence to the server (530) included in the CE policy.

[0244] According to one embodiment, the application processor (520) can accumulate CE sequences in operation 1438 until the reporting cycle has elapsed, if the reporting cycle has not elapsed.

[0245] According to one embodiment, the application processor (520) can check whether the electronic device (400) is connected to Wi-Fi in operation 1435 when the reporting cycle has elapsed.

[0246] According to one embodiment, the application processor (520) can determine whether the user has agreed to use cellular network-based communication in operation 1436 when the electronic device (400) is not connected to Wi-Fi.

[0247] According to one embodiment, if the user has not agreed to use communication based on a cellular network, the application processor (520) can check in operation 1437 whether the CE sequence associated with the error is stored in a buffer and whether the user has agreed to report the error.

[0248] According to one embodiment, the application processor (520) may accumulate CE sequences until the reporting cycle elapses in operation 1438, if the CE sequence associated with the error is not stored in the buffer or the user does not agree to report the error.

[0249] According to one embodiment, the application processor (520) may report at least one CE sequence to the server (530) in operation 1440. The application processor (520) may report a CE sequence bundle, which is at least part of at least one CE sequence accumulated in the buffer of the application processor (520), to the server (530). The application processor (520) may delete at least part of the reported CE sequence from the buffer of the application processor (520).

[0250] The application processor (520) can report at least one CE sequence to the server (530) when the electronic device (400) is connected to Wi-Fi, the user agrees to use communication based on a cellular network, or when a CE sequence related to an error is stored in a buffer and the user agrees to report the error.

[0251] The application processor (520) can report at least one CE sequence to the server (530) based on Wi-Fi when the electronic device (400) is connected to Wi-Fi. Since the electronic device (400) reports a CE sequence based on Wi-Fi when Wi-Fi is connected, it can prevent the user from unintentionally using communication based on a cellular network.

[0252] According to one embodiment, the application processor (520) may report a CE sequence using cellular network-based communication if the user has agreed to use cellular network-based communication even if the electronic device (400) is not connected to Wi-Fi. The electronic device (400) may report a CE sequence to the server (530) even when Wi-Fi is not connected. If the user has agreed to use cellular network-based communication, the electronic device (400) may prevent the user from unintentionally using cellular network-based communication by using cellular network-based communication.

[0253] The application processor (520) may report the CE sequence using cellular network-based communication even if the user does not consent to using cellular network-based communication, provided that the CE sequence related to the error is stored in a buffer and the user consents to reporting the error. The electronic device (400) may report the CE sequence related to the error to the server (530) in certain situations, even if the user does not consent to using cellular network-based communication.

[0254] The server (530) may receive information obtained by the application processor (520) from the application processor (520) (e.g., information related to the electronic device (400) (e.g., model name, binary version (or software version) of the electronic device (400)) and / or information indicating a CE policy). For example, the server (530) may receive information indicating a CE policy from the application processor (520). When the application processor (520) transmits a CE sequence bundle to the server (530), it may transmit the information indicating a CE policy together with it.

[0255] The server (530) can determine whether the CE policy stored in the application has expired based on information indicating the CE policy. If the CE policy stored in the application processor (520) has expired, the server (530) can transmit the updated CE policy to the application processor (520).

[0256] The application processor (520) can transmit the updated CE policy received from the server (530) to the communication processor (510). The communication processor (510) can use the updated CE policy to record information related to CE.

[0257] An electronic device according to one embodiment may include at least one communication circuit. The electronic device may include a communication processor operatively connected to the at least one communication circuit. The electronic device may include an application processor operatively connected to the communication processor. The electronic device may include a memory. When the communication processor receives a request to record information related to a cellular event (CE) from the application processor, it may start recording information related to the CE based on a CE policy received from a server. Based on the CE policy, the communication processor may determine whether at least some of the information related to the CE to be recorded is predetermined information. If at least some of the information related to the CE to be recorded is predetermined information, the communication processor may determine the category of the recorded information related to the CE based on the predetermined information.

[0258] In an electronic device according to one embodiment, the communication processor may determine whether a period for reporting information related to the CE of the identified category has elapsed among a plurality of periods for reporting information related to the CE, starting from the point in time when at least some of the information related to the CE has been recorded. If the period for reporting information related to the CE of the identified category has elapsed, the communication processor may stop recording the information related to the CE after a specified time has elapsed. The communication processor may generate a cellular event (CE) sequence, which is a set of information related to the CE recorded up to the point of cessation. The communication processor may transmit the generated CE sequence to the application processor.

[0259] In an electronic device according to one embodiment, the communication processor can transmit the CE sequence to the application processor when it confirms that the application processor is activated.

[0260] In an electronic device according to one embodiment, the application processor,

[0261] At least one CE sequence received from the communication processor can be transmitted to a server. When the application processor transmits at least one CE sequence received from the communication processor to a server, it may transmit to the server information related to the electronic device and / or information indicating the CE policy used by the communication processor while generating the CE sequence.

[0262] In an electronic device according to one embodiment, the application processor can transmit at least one CE sequence received from the communication processor to the server when it confirms that the electronic device is connected to Wi-Fi or confirms that the user consents to transmitting the CE sequence to the server using communication based on a cellular network.

[0263] In an electronic device according to one embodiment, the application processor may update the CE policy based on information representing the CE policy and / or a period for updating the CE policy. The application processor may transmit the updated CE policy to the communication processor.

[0264] In an electronic device according to one embodiment, the information related to the CE may include at least one of information exchanged with a network through a radio resource control (RRC) layer, information exchanged with a base station through a medium-access control (MAC) layer, information verified through a physical (PHY) layer, and / or information verified through a layer for controlling the electronic device.

[0265] In an electronic device according to one embodiment, the communication processor may identify the recorded information related to CE as a first category if at least part of the information related to CE is predetermined information related to the quality of a signal or the state of a network. The communication processor may identify the recorded information related to CE as a second category if at least part of the information related to CE is predetermined information related to a change in communication between the network and the electronic device. The communication processor may identify the category of the recorded information related to CE as a third category if at least part of the information related to CE is predetermined information related to a failure in communication between the network and the electronic device.

[0266] In an electronic device according to one embodiment, the period for reporting information related to a CE of the third category may be set shorter than the period for reporting information related to a CE of the second category. The period for reporting information related to a CE of the second category may be set shorter than the period for reporting information related to a CE of the first category.

[0267] In an electronic device according to one embodiment, the application processor may transmit a request to record information related to a cellular event (CE) to the communication processor when the user has consented to recording information related to a cellular event (CE) that occurs while performing cellular communication.

[0268] In an electronic device according to one embodiment, the CE policy may include a rule for recording information related to CE.

[0269] In an electronic device according to one embodiment, the communication processor may record information related to the CE when at least one of a plurality of cycles for reporting information related to the CE has elapsed.

[0270] According to one embodiment, a method of operation of an electronic device may include, upon receiving a request to record information related to a cellular event (CE) from an application processor, an operation of starting to record said CE-related information based on a CE policy received from a server. Based on said CE policy, the method may include an operation of checking whether at least some of the information related to the CE to be recorded is predetermined information. If at least some of the information related to the CE to be recorded is predetermined information, the method of operation of the electronic device may include an operation of checking the category of said recorded information related to the CE based on said predetermined information.

[0271] According to one embodiment, a method of operation of an electronic device may include an operation of checking whether a period for reporting information related to the CE of the identified category has elapsed among a plurality of periods for reporting information related to the CE from the time when at least some of the information related to the CE is recorded. If the period for reporting information related to the CE of the identified category has elapsed, the method of operation of the electronic device may include an operation of stopping the recording of information related to the CE after a specified time has elapsed. The method of operation of the electronic device may include an operation of generating a cellular event (CE) sequence, which is a set of information related to the CE recorded up to the time of cessation. The method of operation of the electronic device may include an operation of transmitting the generated CE sequence from a communication processor to an application processor.

[0272] According to one embodiment, the method of operating the electronic device may include the operation of transmitting the CE sequence from the communication processor to the application processor when it is confirmed that the application processor is activated.

[0273] According to one embodiment, the method of operation of the electronic device may include the operation of transmitting at least one CE sequence received from the communication processor to a server. When transmitting at least one CE sequence received from the communication processor to a server, the method of operation of the electronic device may include the operation of transmitting to a server at least one of information related to the electronic device and / or information indicating a CE policy used by the communication processor while generating the CE sequence.

[0274] According to one embodiment, the method of operation of the electronic device may include the operation of transmitting at least one CE sequence received from the communication processor to the server when the electronic device is confirmed to be connected to Wi-Fi or when the user is confirmed to consent to transmitting a CE sequence to the server using communication based on a cellular network.

[0275] According to one embodiment, the method of operation of the electronic device may include an operation of updating the CE policy based on information representing the CE policy and / or a period for updating the CE policy. The method of operation of the electronic device may include an operation of transmitting the updated CE policy to the communication processor.

[0276] According to one embodiment, the information related to the CE may include at least one of information exchanged with a network through a radio resource control (RRC) layer, information exchanged with a base station through a medium-access control (MAC) layer, information verified through a physical (PHY) layer, and / or information verified through a layer for controlling the electronic device.

[0277] According to one embodiment, the method of operating the electronic device may include an operation of identifying the recorded information related to the CE as a first category when at least part of the information related to the CE is predetermined information related to the quality of a signal or the state of a network. The method of operating the electronic device may include an operation of identifying the recorded information related to the CE as a second category when at least part of the information related to the CE is predetermined information related to a change in communication between the network and the electronic device. The method of operating the electronic device may include an operation of identifying the category of the recorded information related to the CE as a third category when at least part of the information related to the CE is predetermined information related to a failure in communication between the network and the electronic device.

[0278] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0279] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any possible combination of items listed together in the corresponding phrase. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0280] As used in this document, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be a component formed as a whole, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0281] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., memory (120) of FIG. 1) that is readable by a machine (e.g., electronic device (100)). For example, a processor (e.g., processor (110)) of the machine (e.g., electronic device (100)) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' merely means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0282] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0283] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the components of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to the integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In an electronic device, At least one communication circuit; A communication processor operatively connected to the above-mentioned at least one communication circuit; An application processor operatively connected to the above communication processor; and Includes memory, The above communication processor is, When a request to record information related to a cellular event (CE) is received from the above application processor, recording of the information related to the CE is started based on the CE policy received from the server, and Based on the above CE policy, verify whether at least some of the recorded CE-related information is predetermined information, and An electronic device for identifying the category of information related to the recorded CE based on the predetermined information, where at least some of the information related to the recorded CE is predetermined information.

2. In claim 1, the communication processor, Check whether the period for reporting information related to the CE of the identified category has elapsed among the plurality of periods for reporting information related to the CE, from the time when at least some of the information related to the CE was recorded, and If the reporting cycle for information related to the CE of the above-identified category has elapsed, the recording of information related to the said CE is stopped after a specified period of time has elapsed, and Generate a cellular event (CE) sequence, which is a set of information related to the above CE recorded up to the point of interruption, and An electronic device that transmits the generated CE sequence to the application processor.

3. In Clause 2, the communication processor, An electronic device that transmits the CE sequence to the application processor when it is confirmed that the application processor is activated.

4. In claim 2, the application processor, Transmit at least one CE sequence received from the above communication processor to a server, and An electronic device that, when transmitting at least one CE sequence received from the communication processor to a server, transmits to the server information related to the electronic device and / or information indicating the CE policy used by the communication processor while generating the CE sequence.

5. In claim 4, the application processor, An electronic device that transmits at least one CE sequence received from the communication processor to the server when it is confirmed that the electronic device is connected to Wi-Fi or when it is confirmed that the user consents to transmitting the CE sequence to the server using communication based on a cellular network.

6. In claim 5, the application processor, Based on information representing the above CE policy and / or the cycle for updating the CE policy, the above CE policy is updated, and An electronic device that transmits the above-mentioned updated CE policy to the above-mentioned communication processor.

7. In Paragraph 1, the information related to the CE above is, An electronic device comprising at least one of information exchanged with a network through a radio resource control (RRC) layer, information exchanged with a base station through a medium-access control (MAC) layer, information verified through a physical (PHY) layer, and / or information verified through a layer for controlling the electronic device.

8. In claim 1, the communication processor, If at least some of the information related to the above CE is predetermined information related to the signal quality or network status, the recorded information related to the CE is identified as a first category, and If at least some of the information related to the above CE is predetermined information related to a change in communication between the network and the electronic device, the recorded information related to the CE is identified as a second category, and An electronic device that identifies the category of the recorded information related to CE as a third category when at least some of the information related to the CE is predetermined information related to the failure of communication between the network and the electronic device.

9. In paragraph 8, the reporting period for information related to CE of Category 3 is set shorter than the reporting period for information related to CE of Category 2, and The reporting cycle for information related to Category 2 CE is, An electronic device set to a shorter reporting cycle than the information related to Category 1 CE.

10. In claim 1, the application processor, An electronic device that transmits a request to record information related to a cellular event (CE) to a communication processor when the user has consented to recording information related to a cellular event (CE) occurring during cellular communication.

11. An electronic device according to claim 1, wherein the CE policy includes rules for recording information related to CE.

12. In claim 1, the communication processor, An electronic device that records information related to the CE when at least one of a plurality of cycles reporting information related to the CE has elapsed.

13. In a method of operating an electronic device, When a request to record information related to a cellular event (CE) is received from an application processor, an operation to start recording the information related to the CE based on a CE policy received from a server; Based on the above CE policy, an operation to determine whether at least some of the information related to the CE being recorded is predetermined information; and A method of operation of an electronic device comprising, when at least some of the information related to the CE recorded above is predetermined information, an operation of identifying the category of the information related to the CE recorded above based on the predetermined information.

14. In claim 13, the method of operating the electronic device is, An operation to check whether a period for reporting information related to the CE of the identified category has elapsed among a plurality of periods for reporting information related to the CE, from the point in time when at least some of the information related to the CE is recorded; If the reporting cycle for information related to the CE of the above-identified category has elapsed, the operation of stopping the recording of information related to the CE after a specified time has elapsed; The operation of generating a cellular event (CE) sequence, which is a set of information related to the CE recorded up to the point of interruption; and A method of operation of an electronic device comprising the operation of transmitting the generated CE sequence from a communication processor to an application processor.

15. In paragraph 14, the method of operating the electronic device is, A method of operation of an electronic device comprising the operation of transmitting the CE sequence from the communication processor to the application processor when it is confirmed that the application processor is activated.

Images