Electronic device and method for analyzing its data

Abstract

This disclosure provides an electronic device and a method for analyzing the data of the electronic device. The data analysis method includes the steps of: providing a push notification message and information regarding the transmission time of the push notification message to at least one user terminal in response to a push notification request related to an application service; obtaining first data from at least one user terminal regarding the time required to receive the push notification message based on the transmission time; and providing the first data.

Description

Technical Field

[0001] The present disclosure relates to an electronic device and a data analysis method thereof for enabling analysis of the required time for push notifications related to application services provided to user terminals.

Background Art

[0002] A user who receives a push notification related to an application cannot confirm whether the reception of the push notification is delayed. As the time required to actually receive the push notification from the user's perspective becomes longer, it may cause inconvenience to users who use the application service. Therefore, there is a need for the application developer to explore a solution that can confirm the reception time of the push notification in real time.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The disclosed embodiment aims to provide an electronic device and a data analysis method thereof. More specifically, it aims to provide an electronic device and a data analysis method thereof for enabling an application developer to analyze the reception time of push notifications related to application services based on log data collected from user terminals.

[0004] The technical problems to be achieved by this embodiment are not limited to the above technical problems, and other technical problems can be analogized from the following embodiments.

Means for Solving the Problems

[0005] A data analysis method for an electronic device according to one embodiment may include the steps of: providing a push notification message and information regarding the transmission time of the push notification message to at least one user terminal in response to a push notification request related to an application service; obtaining first data regarding the time required to receive the push notification message based on the transmission time from at least one user terminal; and providing the first data.

[0006] A data analysis method for an electronic device according to one embodiment may include the steps of: generating second data relating to the representative reception time of a push notification message based on first data from at least one user terminal; and providing the second data.

[0007] In one embodiment, information regarding a push notification message and the transmission time of the push notification message may be provided to at least one user terminal in the form of a push notification payload.

[0008] In one embodiment, the first data includes user terminal identification information, push notification message identification information, and the time required to receive the push notification message, the time required to receive the message may be determined based on the time the push notification message is transmitted and the time the push notification message is received by the user terminal.

[0009] In one embodiment, the time required to receive a push notification message may be the time measured by the user's terminal.

[0010] In one embodiment, the application service includes services relating to e-commerce, and the services relating to e-commerce may include at least one of the following: services relating to the purchase of e-commerce items, services relating to the sale of e-commerce items, and services relating to the transportation of e-commerce items.

[0011] In one embodiment, the step of providing first data may include the step of displaying a dashboard containing the first data.

[0012] In one embodiment, the step of generating the second data may include a step of confirming information regarding the reception time of multiple push notification messages corresponding to a push notification message based on the first data of multiple user terminals; and a step of determining a representative reception time for a push notification message based on the information regarding the reception time of multiple messages.

[0013] A data analysis method for an electronic device according to one embodiment may further include the steps of: identifying data that exceeds a threshold based on first data; and providing a notification regarding the data that exceeds the threshold to a pre-set operator.

[0014] A data analysis method for an electronic device according to one embodiment may further include the steps of: identifying data that exceeds a threshold based on first data; and providing a notification to a user terminal corresponding to the data that exceeds the threshold.

[0015] In one embodiment, the threshold can be pre-set as a different value for each application service.

[0016] In one embodiment, the threshold can be pre-set as different values ​​for each application service and push notification message.

[0017] In one embodiment, a push notification message is a push notification message transmitted from an electronic device, via a messaging server, and provided to a user terminal, and the messaging server may be a server that transmits push notification messages to the user terminal via a path configured by information about the operating system corresponding to the user terminal.

[0018] In one embodiment, the first data may include user terminal identification information, push notification message identification information, a first time period from the time the push notification message is transmitted to the time the messaging server receives the push notification message, and a second time period from the time the push notification message is transmitted to the time the user terminal receives the push notification message.

[0019] A data analysis method for an electronic device according to one embodiment may include the steps of: providing a notification to a first worker when it is confirmed that the cause of the first data exceeding a threshold is a first time; and providing a notification to a second worker when it is confirmed that the cause of the threshold exceeding is not a first time.

[0020] In one embodiment, the first worker may be a worker who performs tasks related to application development, and the second worker may be a worker who performs tasks related to network communication between an electronic device and a user terminal.

[0021] A data analysis method for an electronic device according to one embodiment includes the steps of: confirming third data that satisfies a preset condition based on first data; and displaying a dashboard including the third data, wherein the preset condition may include at least one of a date condition, a user terminal identification information condition, and a push notification message identification information condition.

[0022] A non-temporary recording medium according to one embodiment may be a computer-readable non-temporary recording medium on which a program for embodying a method performed by an electronic device is recorded.

[0023] An electronic device according to an embodiment includes a memory and a processor. The processor provides at least one user terminal with a push notification message and information regarding the time point of transmission of the push notification message in response to a push notification request related to an application, obtains first data regarding the time required for receiving the push notification message by transmission of the push notification message of the electronic device from at least one user terminal, and can provide the first data.

[0024] Specific matters of the embodiment are included in the detailed description and the drawings.

Advantages of the Invention

[0025] In the case of the proposed embodiment, one or more of the following effects can be expected.

[0026] In the case of the embodiments of this specification, it is possible to monitor the time required until a push notification is transmitted from an electronic device and provided to a user terminal.

[0027] Also, in the case of the embodiments of this specification, when the time required for a specific push notification is greater than a threshold value, i.e., when the push notification is delayed, it is possible to provide a notification to an operator to grasp the cause of the delay.

[0028] The advantages of the invention are not limited to the advantages mentioned above, and other advantages not mentioned will be clearly understood by those skilled in the art from the description of the claims.

Brief Description of the Drawings

[0029] [Figure 1] Shows a system according to an embodiment.

[0030] [Figure 2] It is a diagram for explaining a process in which an electronic device according to an embodiment analyzes data.

[0031] [Figure 3] This is a diagram illustrating the process by which an electronic device according to one embodiment analyzes data.

[0032] [Figure 4] This shows the time point that forms the basis for measuring the duration of a push notification according to one embodiment.

[0033] [Figure 5] A flowchart of a data analysis method for an electronic device according to one embodiment is shown.

[0034] [Figure 6] The dashboard according to the first embodiment is shown.

[0035] [Figure 7] The dashboard according to the second embodiment is shown.

[0036] [Figure 8] The dashboard according to the third embodiment is shown.

[0037] [Figure 9] A dashboard according to the fourth embodiment is shown.

[0038] [Figure 10] A block diagram of an electronic device according to one embodiment is shown. [Modes for carrying out the invention]

[0039] The terminology used in the embodiments has been selected, to the extent possible, to be widely used and common terminology, taking into account the function described herein, although this may change depending on the intent of the articulators, case law, the emergence of new technologies, etc. In certain cases, the applicant has arbitrarily selected some terms, in which case their meaning will be described in detail in the relevant section of the description. Therefore, the terminology used in this disclosure must be defined not merely as a name of a term, but based on the meaning of that term and the overall content of this disclosure.

[0040] When a part of the specification "includes" a certain component, unless otherwise stated, this does not exclude other components, but rather means that it may further include other components.

[0041] The expression “at least one of a, b, and c” as described throughout the specification may encompass “a alone,” “b alone,” “c alone,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”

[0042] The term "terminal" as used below can refer to a computer or portable terminal that can connect to a server or other terminals via a network. Here, a computer includes, for example, a laptop, desktop, or laptop computer equipped with a web browser, while a portable terminal is, for example, a wireless communication device that guarantees portability and mobility, and can include all kinds of handheld wireless communication devices such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, and tablet PCs.

[0043] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings, so that they can be easily implemented by those skilled in the art in which the present disclosure pertains. However, the present disclosure may be embodied in several different forms and is not limited to the embodiments described herein.

[0044] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0045] Figure 1 shows a system according to one embodiment.

[0046] Referring to Figure 1, the system may include at least one of the following: an electronic device 100, a first user terminal 120, a second user terminal 140, a third user terminal 160, and a network 180. On the other hand, the system shown in Figure 1 only shows the components relevant to this embodiment. Therefore, a person with ordinary skill in the art related to this embodiment will understand that other general components may be included in addition to those shown in Figure 1.

[0047] The electronic device 100 is a device that configures and provides diverse information. The electronic device 100 can provide the configured information on a web page or application screen, or in a form that can be displayed on a terminal on a web page or application screen.

[0048] According to one embodiment, the electronic device 100 can provide data to at least one user terminal and acquire and provide data from the user terminal. For example, in response to a push notification request related to an application service, the electronic device 100 can provide at least one user terminal with a push notification message and information regarding the transmission time of the push notification message, acquire first data from at least one user terminal regarding the time required to receive the push notification message based on the transmission time, and provide the first data.

[0049] The first user terminal 120, the second user terminal 140, and the third user terminal 160 are terminals used by each user, and users can access services provided by the network 180 using their respective terminals. For example, the electronic device 100 can provide push notifications related to application services via the network 180, and users can receive push notifications about application services using their respective terminals and use application services based on the push notifications they receive.

[0050] On the other hand, although not shown in Figure 1, the electronic device 100 may include a database. A database is a data structure embodied in a predetermined storage space, and functions such as saving, searching, deleting, editing, or adding data can be freely performed. For example, a database may include fields or components for handling functions such as saving, searching, deleting, editing, or adding data.

[0051] At least one of the first user terminal 120, the second user terminal 140, and the third user terminal 160 and the electronic device 100 can communicate with each other within the network 180. The network 180 is a comprehensive data communication network that includes local area networks (LANs), wide area networks (WANs), value-added networks (VANs), mobile radio communication networks, satellite communication networks, and combinations thereof, enabling the entities of each network configuration shown in Figure 1 to communicate smoothly with each other, and may include wired internet, wireless internet, and mobile wireless communication networks. Wireless communication may include, but is not limited to, Wi-Fi, Bluetooth®, Bluetooth Low Energy, Zigbee, WFD (Wi-Fi Direct), UWB (ultra-wideband), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), etc.

[0052] Figure 2 is a diagram illustrating the process by which the electronic device 100 analyzes data according to one embodiment.

[0053] In one embodiment, the electronic device 100 can provide a push notification message and information regarding the transmission time of the push notification message to at least one user terminal in response to a push notification request related to an application service. The push notification provided by the electronic device 100 is a push notification related to an application service, where the application service can mean a service provided through an application. In this case, the application may be an application that provides e-commerce services, and thus the application service may include e-commerce services. Services related to e-commerce may include, for example, at least one of services related to the purchase of e-commerce items, services related to order management for the sale of e-commerce items, and services related to the transportation of e-commerce items. Specifically, services related to the purchase of e-commerce items may include services related to orders and delivery requests, services related to the sale of e-commerce items may include services related to order management for the sale of e-commerce items, and services related to the transportation of e-commerce items may include services related to transportation accompanying the sale of e-commerce items. On the other hand, each of the services related to the purchase of e-commerce items, services related to order management for the sale of e-commerce items, and services related to the transportation of e-commerce items may be e-commerce services provided through different applications.

[0054] This allows e-commerce services provided through different applications to provide push notifications to at least one user terminal corresponding to the application providing the service. Here, "at least one user terminal corresponding to an application" can mean at least one user terminal among multiple applications that uses the application providing the service that requests push notifications. In other words, the user terminals to which each e-commerce service provided through different applications provides push notifications can be user terminals using different applications.

[0055] A push notification request associated with a single application service may include at least one push notification request. Specifically, a push notification request associated with a service related to the purchase of an e-commerce item may include a push notification request to a first user terminal 120, a push notification request associated with a service related to the sale of an e-commerce item may include a push notification request to a second user terminal 140, and a push notification request associated with a service related to the transportation of an e-commerce item may include a push notification request to a third user terminal 160. In this case, the first user terminal 120, the second user terminal 140, and the third user terminal 160 may be distinguished, for example, by the application to which the push notification is provided. That is, the first user terminal 120 may be the user terminal of at least one user (e.g., an orderer) using an application that provides services related to ordering and requesting delivery of goods, the second user terminal 140 may be the user terminal of at least one user (e.g., a seller or store) using an application that provides services related to order management for the sale of goods, and the third user terminal 160 may be the user terminal of at least one user (e.g., a delivery person) using an application that provides services related to the transportation of goods accompanying the sale of goods. In other words, each of the first user terminal 120, the second user terminal 140, and the third user terminal 160 may include at least one user terminal that uses an application providing the same type of service. For convenience, the provisions relating to the first user terminal 120, the second user terminal 140, and the third user terminal 160 may also apply hereafter.

[0056] As a more specific example, a push notification request related to an e-commerce purchase service may include a push notification request informing at least one first user terminal 120 that an order and delivery request for an e-commerce purchase service has been accepted based on input provided to the first user terminal 120 requesting the order and delivery of specific food and beverages from a specific store (for example, a user's action of tapping a button, banner, etc. on the application screen); a push notification request informing at least one first user terminal 120 that the order request has been accepted; and a push notification request informing at least one first user terminal 120 that delivery of the specific food and beverages in response to the order and delivery request has begun.

[0057] Push notification requests related to services for sales subject to e-commerce may include, for example, a push notification request to at least one second user terminal 140 to input whether or not to accept an order for a specific food item from a specific store and its delivery; a push notification request to inform the second user terminal 140 to input the expected delivery time for the food item; a push notification request to inform at least one second user terminal 140 that the delivery request has been accepted; and a push notification request to inform at least one second user terminal 140 to input the requested pickup time for the food item at the delivery departure point based on the acceptance of the delivery request.

[0058] Push notification requests related to services for the delivery of e-commerce transactions may include, for example, a push notification request informing at least one third-party user terminal 160 whether or not to accept a delivery request from a specific store's address to the delivery destination address, and a push notification request informing the third-party user terminal 160 of the time for the food and beverage pickup request at the delivery departure point for delivery.

[0059] In other words, in response to at least one push notification request related to one application service, the electronic device 100 can provide at least one user terminal corresponding to the push notification request with a push notification message corresponding to the push notification request and information regarding the transmission time of the push notification message. Furthermore, if there are at least one push notification request related to multiple application services, the electronic device 100 can provide at least one user terminal corresponding to each push notification request with a push notification message corresponding to each push notification request and information regarding the transmission time of the push notification message.

[0060] On the other hand, the transmission time of a push notification message may be the time when the application service transmits the push notification message to the user terminal. Information regarding the push notification message and the transmission time of the push notification message may be provided to at least one user terminal, for example, in the form of a push notification payload. Specifically, information regarding the transmission time of the push notification message may be provided to the user terminal by including it in a data field within the payload that transmits the data within that field without processing.

[0061] Next, the electronic device 100 can obtain first data from at least one user terminal regarding the time required to receive a push notification message based on the transmission time. The first data may include, for example, user terminal identification information, push notification message identification information, and the time required to receive the push notification message. The time required to receive the message may be determined, for example, based on the transmission time of the push notification message and the time when the user terminal receives the push notification message. The time required to receive the push notification message may be, for example, a time measured by the user terminal.

[0062] Next, the electronic device 100 can provide the first data. For example, the electronic device 100 can provide the first data by displaying a dashboard containing the first data. More specific embodiments of the electronic device 100 providing data by displaying a dashboard will be described in detail below with reference to Figures 6 to 9.

[0063] In one embodiment, the electronic device 100 can identify data that exceeds a threshold based on first data and provide a notification regarding the data that exceeds the threshold to a pre-configured worker. Here, the pre-configured worker may include a worker configured for at least one user terminal that uses an application that provides the same type of service. For example, the electronic device 100 can identify via a dashboard that data of at least one first user terminal 120 has a duration exceeding a threshold and provide a notification to a worker who is pre-configured to receive notifications regarding the duration of the first user terminal 120. A worker who is already configured to receive notifications regarding the duration of the first user terminal 120 may be, for example, a developer monitoring the service operation related to e-commerce orders and delivery requests among application services. The content of the notification provided to the worker may include, for example, information regarding an abnormal delay in the delivery of a specific push notification message related to e-commerce orders and delivery requests to a specific user terminal. Based on the notifications received, workers can identify specific devices that frequently experience delays in delivering push notification messages, identify the cause, and resolve issues such as user inconvenience caused by these delays.

[0064] On the other hand, thresholds can be pre-set as different values ​​for each application service, for example. Specifically, thresholds for at least one push notification message related to a service for purchasing e-commerce items, thresholds for at least one push notification message related to a service for selling e-commerce items, and thresholds for at least one push notification message related to a service for transporting e-commerce items can be pre-set as different values ​​from each other, taking into account the impact of delays in push notifications related to each service.

[0065] As a more specific example, delays in push notification messages, such as push notification messages informing the first user terminal 120 that an order and delivery request has been accepted by a service related to e-commerce purchases, and push notification messages informing the first user terminal 120 that an order request has been accepted, may cause the customer to mistakenly believe that it is impossible to accept their order and delivery request, or to perceive that the acceptance of their order is delayed due to a large number of orders and delivery requests. However, considering that the customer can order and request delivery of other products or from other stores, such delays in push notifications can be seen as causing only a relatively minor inconvenience to the user of the first user terminal 120's application services. In contrast, delays in push notification messages, such as those provided to the second user terminal 140 by services related to e-commerce sales, requesting input on whether to accept or reject an order for a specific food item from a specific store and delivery, and push notification messages informing that a delivery request has been accepted, can lead to problems such as orders being canceled before the store can even confirm the order and delivery requested by the customer, or delays in the acceptance or rejection of delivery requests, which could lead to delays in the preparation of the food item itself. In this case, delays in push notification messages can negatively impact the sales of the specific store, as well as reviews or ratings of that store. Therefore, the threshold for services related to e-commerce sales may be set even lower than the threshold for services related to e-commerce sales. That is, the threshold for each service may be set considering the impact of push notification delays related to each service. As a result, the thresholds for the first user terminal 120, the second user terminal 140, and the third user terminal 160 may be set to different values ​​considering the impact of push notification delays related to each service.The electronic device 100 can provide higher quality service to application users by monitoring the time required to receive push notifications, taking into account the impact of delays in push notifications for application services.

[0066] In other examples, thresholds may be pre-set as different values ​​for each application service and push notification message. Specifically, thresholds may be pre-set values ​​based on the importance of each of at least one push notification message requested by a single application service. For example, if an e-commerce delivery service requests a push notification message to a third user terminal 160 asking whether to accept a delivery request from a specific store address to the delivery destination address, and another push notification message informing the user of the time for a food and beverage pickup request at the delivery departure point for delivery, the thresholds for each notification message may differ from one another.

[0067] If there is a delay in providing a push notification message to the third user terminal 160 requesting input on whether to accept or reject a delivery request, problems may arise such as the delivery request being canceled or the request being rejected regardless of the delivery person's wishes, for example, by the delivery person being evaluated based on the number of food delivery services provided to customers from the store via the application over a month, or by the delivery person being required to provide a predetermined amount or number of delivery services per day. Therefore, it is important to distinguish between cases where a push notification was provided to the user's terminal but the delivery service could not be provided because the delivery request was not accepted, and cases where the delivery service could not be provided regardless of the user's wishes because the push notification message was delayed and was not displayed on the user's terminal, or immediately after it was displayed. On the other hand, if there is a delay in providing a push notification message to the third user terminal 160 informing it of the food pickup request time at the delivery departure point, it may lead to a delay in picking up the food at the delivery departure point by delaying confirmation of the food pickup request time. However, considering the cooking time of the food, the possibility of a delay in picking up the food is considered low. Therefore, the importance of a push notification message requesting confirmation of acceptance or rejection of a delivery request may be relatively higher than that of a push notification message informing the time of a food pickup request at the delivery origin. Even when requested by the same type of service, the threshold for a push notification message requesting confirmation of acceptance or rejection of a delivery request from a specific store's address to the delivery destination address may be set even lower than the threshold for a push notification message informing the time of a food pickup request, taking into account the importance of the push notification message.

[0068] In another example, the electronic device 100 can provide information regarding statistics on the time taken to receive push notification messages based on first data. Specifically, based on the time taken to receive multiple push notification messages, it can provide information such as the total number or percentage of data that is less than or equal to a preset value, and the total number or percentage of data that is greater than or equal to a preset value. The preset value may be, for example, a value entered by an operator for monitoring data related to push notifications. This allows the electronic device 100 to calculate and provide to the operator, for example, the percentage of data where the time taken to receive a push notification message for an input request to accept or reject a delivery provided to the third user terminal 160 is 30 seconds or less, and the percentage of data where the time taken is 1 minute or more. Furthermore, based on data regarding the time taken to receive multiple push notifications at a specific time, the electronic device 100 can also provide a notification to the operator if the total number or percentage of data where the time taken is 1 minute or more has increased compared to the previous day.

[0069] In one embodiment, the electronic device 100 can identify data that exceeds a threshold based on first data and provide a notification to the user terminal corresponding to the data that exceeds the threshold. For example, if the electronic device 100 confirms via a dashboard that the time required for Device ID 1 includes data that exceeds a threshold, and confirms that Device ID 1 is terminal 1 included in the first user terminal 120, it can provide a notification to terminal 1. The content of the notification provided to the user terminal may include, for example, information regarding an abnormal delay in the delivery of a particular push notification message. The threshold may be pre-set as different values ​​for each application service, for example. In another example, the threshold may be a value pre-set based on the relationship between the time required to receive a push notification message and the application service.

[0070] In Figure 2, Service 1(202), Service 2(204), and Service 3(206) refer to application services. As an example, only Service 1(202), Service 2(204), and Service 3(206) are shown in Figure 2, but depending on the embodiment, many more types of services may be included. Service 1(202) may refer to a service related to purchasing electronically, Service 2(204) may refer to a service related to selling electronically, and Service 3(206) may refer to a service related to transporting electronically. For convenience, the contents of Service 1(202), Service 2(204), and Service 3(206) may also be applied identically below. The electronic device 100 can provide push notifications to the user terminal, such as push notification requests related to Service 1(202), push notification requests related to Service 2(204), and push notification requests related to Service 3(206). Each of the push notification requests related to Service 1 (202), Service 2 (204), Service 3 (206), etc., could be, for example, a push notification request from each application service, and specifically, could be a call to each application service's Push Sending Service 210 for the transmission of push notifications. For example, in Figure 2, the application service's push notification request is shown as being generated within the electronic device 100, but depending on the embodiment, it could be a request generated by the application service from an external electronic device (e.g., a terminal, server, etc.) with which the electronic device 100 can communicate. The Push Sending Service 210 can transmit the push notification message and information regarding the transmission time of the push notification message in order to provide a push notification to the user terminal in response to the application service's push notification request.

[0071] If Service 1(202) calls Push Sending Service 210 to provide a push notification informing a specific customer that their order has been accepted, Push Sending Service 210 can transmit a push notification to the first user terminal 120 from which the order was requested, informing the customer that the order has been accepted. If Service 2(204) calls Push Sending Service 210 to provide a push notification informing the customer whether they accept or reject an order for a specific food item from a specific store and whether they accept or reject the delivery, Push Sending Service 210 can transmit a push notification to the second user terminal 140 corresponding to the specific store, informing the customer whether they accept or reject an order for a specific food item and whether they accept or reject the delivery. If Service 3(206) calls Push Sending Service 210 to provide a push notification informing the customer whether they accept or reject a delivery from a specific delivery person, Push Sending Service 210 can transmit a push notification to the third user terminal 160 corresponding to the specific delivery person, informing the customer whether they accept or reject the delivery. On the other hand, based on the input provided to the first user terminal 120 requesting an order and delivery of specific food and beverages from a specific store, Service 1(202) can call Push Sending Service 210 to provide a push notification to the first user terminal 120 informing it that the order has been accepted, and simultaneously or in parallel, Service 2(204) can transmit a push notification to the second user terminal 140 requesting input regarding acceptance or rejection of the order and delivery of the specific food and beverages.

[0072] The operation of the electronic device 100 to provide a push notification to at least one first user terminal 120 corresponding to a push notification request in response to at least one push notification request related to Service 1(202), the operation to provide a push notification to at least one second user terminal 140 corresponding to a push notification request in response to at least one push notification request related to Service 2(204), and the operation to provide a push notification to at least one third user terminal 160 corresponding to a push notification request in response to at least one push notification request related to Service 3(206) may be performed at different times depending on the push notification request time for each service, and may be performed simultaneously or in parallel.

[0073] At least one user terminal (at least one of the first user terminal 120, second user terminal 140, third user terminal 160, etc.) can receive push notification messages transmitted from the Push Sending Service 210, as well as information regarding the transmission time of the push notification messages. For example, at least one user terminal can receive the title of the push notification message, the content of the push notification message, and the push sending time, which is the transmission time of the push notification message. Here, the push sending time may be, for example, the time when the Push Sending Service 210 was called by at least one application service.<Title、Content、Push sending time> These can also be provided to the user's terminal in the form of a payload.

[0074] The code for the payload provided to the user terminal from Push Sending Service 210 may include a pushPayloads field containing data corresponding to variables such as token, phase, osType, device ID, title, and msg, and an extras field containing data corresponding to variables such as tracking ID and push sending time. The token included in the pushPayloads field is a variable sent to the messaging server, Counous410, as described in Figure 4 below, and may contain information about the platform corresponding to the user terminal. Phase and osType may both contain information about the user terminal, device ID contains identification information for the user terminal, title contains information about the title of the push notification message, and msg may contain information about the content of the push notification message, as shown in Content in Figure 2.

[0075] On the other hand, the tracking ID included in the extras field may be data containing information about entry points in a series of paths from the Push Sending Service 210 to a specific terminal in response to a push notification request. For example, when a push notification is provided to a second user terminal (140) in response to a push notification request from Service 2 (204), the tracking ID may include information about at least one entry point in a series of paths for providing the push notification, from the call to the Push Sending Service (210) by Service 2 (204) to the processing logic at the backend server end for generating a push notification informing the pickup request time for food and beverages at the delivery departure point by the call to Service 2, and to the transmission of the generated push notification to the second user terminal 140.

[0076] On the one hand, unlike other fields in the data in the form of the payload, all the data included in the extras field can be bypassed to the electronic device 100 via the user terminal. That is, the electronic device 100 can obtain, without any processing (e.g., the process of extracting only a part of the data), the data in the extras field as it is provided to the terminal among the data in the form of the payload provided to at least one user terminal by the Push sending Service 210. Thus, the Push sending time and the tracking ID included in the extras field can be obtained by the electronic device 100 as they are provided to the user terminal. The electronic device 100 can check information regarding the specific path through which each push notification is provided based on the tracking ID corresponding to the push notification obtained from the user terminal.

[0077] The electronic device 100 can obtain first data including the Device ID, which is the identification information of the user terminal, the message ID, which is the identification information of the push notification message, and the required time, which is the time required for receiving the push notification message, from at least one user terminal that has received the provision of the push notification. As described above, since the first user terminal 120, the second user terminal 140, and the third user terminal 160 can each include at least one user terminal, the Device ID can be, for example, the identification information of the user terminal that can identify each user terminal included in the first user terminal 120. The push notification message is a message with content corresponding to the push notification request, and since multiple push notification messages can be provided to one user terminal, it can be the identification information for identifying each push notification message. The obtained first data can include, for example, at least one of <Device ID, message ID 1, required time,...>, <Device ID, message ID 2, required time,...>, <Device ID, message ID 3, required time,...>.

[0078] When the time it takes for at least one user terminal to receive a push notification message is defined as the push receive time, the required time may be the difference between the push receive time and the push sending time measured by the user terminal (push receive time - push sending time). The first data may be, for example, log data acquired in real time via Lumberjack. Lumberjack can collect, process, and transmit log data. In Figure 2, Lumberjack is shown as a component included in the electronic device 100, but Figure 2 is just one example, and in other examples, Lumberjack may be included in the user terminal as a component other than the electronic device 100, or in an external device that can communicate with other electronic devices 100.

[0079] Next, the electronic device 100 can provide the first data, which is log data acquired in real time via Lumberjack, after Flink Streaming processing. Flink Streaming may include a process of converting the log data into a streaming data format by utilizing Flink. The electronic device 100 can, for example, display a dashboard 220 containing the first data that has gone through the Flink Streaming process. On the other hand, although Figure 2 shows that there is one Lumberjack acquiring the first data from the first user terminal 120, the second user terminal 140, etc., Lumberjack can exist for each user terminal. That is, Lumberjack can exist for each user terminal using an application that provides the same type of service. As a result, the first data acquired by the electronic device 100 from user terminals can be divided into, for example, first data acquired from at least one first user terminal 120, first data acquired from at least one second user terminal 140, and first data acquired from at least one third user terminal 160, and a separate dashboard containing each of these first data sets can also exist.

[0080] Figure 3 is a diagram illustrating the process by which an electronic device analyzes data according to one embodiment.

[0081] In one embodiment, the electronic device 100 can generate and provide second data relating to the representative reception time of a push notification message based on first data from at least one user terminal. Specifically, the electronic device 100 can acquire first data through the process described above in Figure 2, and can generate second data based on the acquired first data. For example, the electronic device 100 can check information regarding the reception times of multiple push notification messages corresponding to a push notification message based on first data from multiple user terminals, and can determine the representative reception time of a push notification message based on the information regarding the multiple reception times. The electronic device 100 can then store the second data, which includes the information regarding the representative reception time of the determined push notification message, in a database, and can display a dashboard containing the stored second data.

[0082] Referring to FIG. 3, the electronic device 100 can provide a push notification message and information regarding the transmission time of the push notification message to at least one user terminal (at least one of the first user terminal 120, the second user terminal 140, and the third user terminal 160) corresponding to the push notification in response to at least one push notification request of at least one application service (at least one of Service 1 (202), Service 2 (204), and Service 3 (206)). Then, the electronic device 100 can obtain first data including a Device ID, a Message ID, and a required time from at least one user terminal that has received the push notification. The first data can be log data collected in real time via Lumberjack. Descriptions of content overlapping with FIG. 2 are omitted. Then, the electronic device 100 can generate second data regarding the representative reception required time of the push notification message.

[0083] For example, when the first data that has gone through the Flink Streaming process is data corresponding to message ID 1 and includes a plurality of <Device ID, message ID 1, required time,...>, the plurality of required times corresponding to message ID 1 can be confirmed based on the first data, and a representative required time can be determined based on the plurality of required times. Then, the electronic device 100 can save second data including information (<message ID 1, representative required time>) regarding the representative required time determined for the push notification message corresponding to message ID 1 in the database 310, and can display a dashboard 220 including the saved second data.

[0084] In another example, when the first data is data corresponding to message ID 1 <Device ID, message ID 1, required time, …>, data corresponding to message ID 2 <Device ID, message ID 2, required time, …>, and data corresponding to message ID 3 <Device ID, message ID 3, required time, …>, the electronic device 100 checks the plurality of required times corresponding to message ID 1, the plurality of required times corresponding to message ID 2, and the plurality of required times corresponding to message ID 3 based on the first data, and based on each of the plurality of checked required times, a representative required time of push notification message 1 corresponding to message ID 1, a representative required time of push notification message 2 corresponding to message ID 2, and a representative required time of push notification message 3 corresponding to message ID 3. The electronic device 100 can generate second data (<message ID 1, representative required time>, <message ID 2, representative required time>, <message ID 3, representative required time>) including the representative required times. Next, the electronic device 100 can store the second data in the database 310 and display a dashboard 220 including the stored second data. By providing the second data regarding the representative reception required time of the push notification message by the electronic device 100, an operator such as an application developer can analyze what the specific push notification message with the longest required time is, etc., and can provide a more improved application service based on the analysis.

[0085] In one example, the representative reception time for a push notification message may be the reception time that falls within a predetermined percentile among several reception times sorted from smallest to largest. The predetermined percentiles could be, for example, the 95th percentile (meaning the response time in the top 5%), the 90th percentile (meaning the reception time in the top 10%), and the 50th percentile (meaning the reception time in the top 50%). Furthermore, in another example, the representative reception time for a push notification message may be the average of several reception times.

[0086] In one embodiment, the electronic device 100 can generate and provide second data relating to the representative reception time of push notification messages for each user terminal based on first data of multiple user terminals. For example, the electronic device 100 can check information regarding the reception time of multiple push notification messages corresponding to each Device ID based on the first data of multiple user terminals, and determine a representative reception time for each user terminal based on the information regarding the multiple reception times. The electronic device 100 can then store the second data, which includes the information regarding the representative reception time for each Device ID, in a database and display a dashboard 220 containing the stored second data. As described above, since the first data is based on multiple user terminals using an application that provides the same type of service, for example, based on the second data provided by the electronic device 100, an application developer can determine which of the multiple user terminals included in the first user terminal 120 that uses the order and delivery request service generally experience problems with push notification delivery delays.

[0087] Figure 4 shows the time point used as the basis for measuring the duration of a push notification, according to one embodiment.

[0088] In one embodiment, the electronic device 100 can provide a push notification message and information regarding the transmission time of the push notification message to at least one user terminal in response to a push notification request related to an application service, and can obtain and provide first data regarding the time required to receive the push notification message based on the transmission time from at least one user terminal. In this case, the push notification message is a push notification message transmitted from the electronic device 100, via a messaging server, and provided to the user terminal, and the messaging server may be a server that transmits the push notification message to the user terminal via a route configured by information regarding the operating system corresponding to the user terminal. The messaging server may be a third-party server that provides messaging services for transmitting push notification messages from the electronic device 100 to the user terminal. The messaging server used to provide push notification messages may include server devices that support a variety of services depending on the information regarding the user terminal. For example, different messaging servers (e.g., APNs (Apple Push Notification service) or FCM (Firebase Cloud Messaging)) may be used based on platform information corresponding to the user terminal (e.g., iOS or Android).

[0089] In one embodiment, the first data acquired by the electronic device 100 may include user terminal identification information, push notification message identification information, a first time period from the time of transmission of the push notification message to the time the messaging server receives the push notification message, and a second time period from the time of transmission of the push notification message to the time the user terminal receives the push notification message. The first time period may be, for example, the time from the time the electronic device 100 transmits the push notification message to the messaging server to the time the messaging server receives the push notification message. In another example, the first time period may be the time up to the time the electronic device 100 calls the messaging server. The second time period may be, for example, the time from the time the electronic device 100 transmits the push notification message to the messaging server to the time the messaging server confirms platform information corresponding to the user terminal and transmits the push notification message to the user terminal via the server corresponding to the platform information, thereby allowing the user terminal to receive the push notification message. This allows the electronic device 100 to display a dashboard including the first and second time periods. The above description may apply to any overlapping content.

[0090] In one embodiment, if the first data includes data exceeding a threshold, the electronic device 100 can provide a notification to the first worker if it confirms that the cause of the first data exceeding the threshold is the first time, and can provide a notification to the second worker if it confirms that the cause of the threshold exceeding is not the first time. Specifically, if the first data includes data exceeding a threshold, the electronic device 100 can compare the data relating to the first time with threshold 1 and confirm that the cause of the threshold exceeding is the first time if there is data that exceeds threshold 1, and confirm that the cause of the threshold exceeding is not the first time if there is no data that exceeds threshold 1. In another example, in order to confirm the cause of the threshold exceeding, the electronic device 100 can check whether the data relating to the second time corresponding to the data exceeding the threshold exceeds threshold 2, and at the same time whether the data relating to the first time corresponding to the data exceeding the threshold exceeds threshold 1. In the two examples described above, threshold 1 is the threshold for the first time, and threshold 2 is the threshold for the second time. Threshold 1 may be the sum of threshold 1 and a value obtained by adding an acceptable delay to the time normally required for message transmission from the messaging server to the user terminal. This allows the electronic device 100, having determined whether the cause of the threshold exceedance is the first time, to provide a notification to the worker corresponding to the cause of the threshold exceedance.

[0091] The first worker may be, for example, a worker who performs work related to application development, and the second worker may be, for example, a worker who performs work related to network communication between the electronic device 100 and the user terminal. That is, if the cause of the threshold exceedance is the first time, and there is a delay in the delivery of a push notification message from the server terminal to the messaging server, the electronic device 100 can provide a notification to the worker who performs work related to application development. The content of the notification may include, for example, information about an abnormal delay in the delivery of a specific push notification message related to e-commerce delivery services to a specific user terminal. On the other hand, if the cause of the threshold exceedance is not the first time, and there is a delay in the delivery of a push notification message from the messaging server to the user terminal, the electronic device 100 can provide a notification to the worker who performs work related to network communication between the electronic device 100 and the user terminal. In another example, the electronic device 100 may also provide a notification to the worker who performs work related to network communication between the messaging server and the user terminal. The content of the notification may include, for example, information about a delay in the delivery of a message to the user terminal due to a communication problem. As a result, the electronic device 100 not only provides notifications regarding delays in the delivery of push notifications, but also identifies the causes of the delays and provides notifications to the relevant personnel, thereby enabling a more rapid and accurate improvement of the push notification delay problem.

[0092] On the other hand, the thresholds on which notifications are provided can be pre-set as different values ​​for each application service, for example. In another example, the thresholds can be pre-set as different values ​​for each application service and push notification message.

[0093] Referring to Figure 4, the electronic device 100 transmits at least one push notification message to the Counos 410, which represents a messaging server, and the Counos 410 can transmit each push notification message to the corresponding user terminal based on platform information corresponding to the user terminal. Time A is a first time, which may be, for example, the time elapsed from the time the application service invokes the Push Sending Service 210 until the time the Counos 410 receives the push notification message, or in other examples, the time elapsed from the time the application service invokes the Push Sending Service 210 until the time the Push Sending Service 210 invokes the Counos 410. Time B is a second time, which may be, for example, the time elapsed from the time the application service invokes the Push Sending Service 210 until the time the push notification message is provided from the electronic device 100 to the user terminal via the Counos 410. When Counos410 transmits a push notification message and the transmission time of the push notification message to a user terminal, Counos410 can also transmit information regarding the time when the push notification message was received or when the Push Sending Service210 ​​called Counos410. As a result, the first data acquired by the electronic device 100 from the user terminal can include information regarding the required time A and required time B measured by the user terminal. The electronic device 100 can then display a dashboard including the required time A and required time B. A more specific embodiment of providing a notification to a first or second worker based on the dashboard will be described in detail below with reference to Figure 7.

[0094] Figure 5 shows a flowchart of a data analysis method for an electronic device according to one embodiment. The previously mentioned descriptions may apply to any overlapping content.

[0095] In stage S500, the electronic device 100 can provide at least one user terminal with a push notification message and information regarding the transmission time of the push notification message in response to a push notification request related to an application service.

[0096] In one embodiment, information regarding a push notification message and the transmission time of the push notification message may be provided to at least one user terminal in the form of a push notification payload.

[0097] In one embodiment, the application service includes services relating to e-commerce, and the services relating to e-commerce may include at least one of the following: services relating to the purchase of e-commerce items, services relating to the sale of e-commerce items, and services relating to the transportation of e-commerce items.

[0098] In step S520, the electronic device 100 can obtain first data from at least one user terminal regarding the time required to receive a push notification message based on the transmission time.

[0099] In one embodiment, the first data includes user terminal identification information, push notification message identification information, and the time required to receive the push notification message, the time required to receive the message may be determined based on the time the push notification message is transmitted and the time the push notification message is received by the user terminal.

[0100] In one embodiment, the time required to receive a push notification message can be measured by the user's terminal.

[0101] At stage S540, the electronic device 100 can provide the first data.

[0102] In one embodiment, the electronic device 100 can display a dashboard containing first data.

[0103] Figure 6 shows the dashboard 220 according to the first embodiment.

[0104] Referring to Figure 6, a graph showing the reception times for multiple push notification messages corresponding to Message ID 1 can be seen. The x-axis of the graph represents the Device ID, and the y-axis represents the reception time value. Specifically, the graph on Dashboard 220 shows the reception time for the push notification message corresponding to message ID 1, which was confirmed at 11:00 AM on January 1, 2024. In this way, the electronic device 100 can display Dashboard 220, which allows users to view multiple reception times for each push notification message at different times, based on first data acquired from at least one terminal. The operator can monitor the distribution of multiple reception times for push notification messages at specific times on specific dates via Dashboard 220 displayed by the electronic device 100.

[0105] On the other hand, 30 sec represents a pre-set threshold for Message ID 1. The electronic device 100 can, for example, identify a user terminal corresponding to Device ID 2 that has a required time value exceeding 30 sec (i.e., the delivery of the push notification message was delayed). If the user terminal is included in the first user terminal 120, the electronic device 100 can provide a notification regarding the delay in required time corresponding to Device ID 2 to an operator pre-configured to receive notifications regarding the first user terminal 120. The electronic device 100 can also provide a notification regarding the delay in push notifications to the identified user terminal corresponding to Device ID 2. In Figure 6, 30 sec set as the threshold is merely an example, and the threshold may vary depending on the embodiment.

[0106] Figure 7 shows the dashboard 220 according to the second embodiment.

[0107] Referring to Figure 7, graphs showing multiple durations A and multiple durations B for push notification messages corresponding to message ID 1 can be seen. The graphs on Dashboard 220 show the data for durations A and B for push notification messages corresponding to message ID 1, as confirmed at 11:00 AM on January 1, 2024, with the x-axis representing the Device ID and the y-axis representing the value of duration A or duration B. In this way, the electronic device 100 can display Dashboard 220, which allows users to view multiple durations A and B for each push notification message at different times, based on first data including durations A and B obtained from at least one terminal. The operator can monitor the distribution of multiple durations A and B for push notification messages at specific times on specific dates via Dashboard 220 displayed by the electronic device 100.

[0108] On the other hand, as can be seen through Figure 7, as mentioned above, each of the data for duration B has a larger value than each of the data for duration A, and the threshold for duration B, 40 seconds, is set to an even larger value than the threshold for duration A, 30 seconds. The threshold for duration B, 40 seconds, could be, for example, the sum of the threshold for duration A, 30 seconds, and 10 seconds, which is the value obtained by adding an acceptable delay to the time normally required for message transmission from Counos410 to the user terminal.

[0109] Referring to Figure 7, if the data displayed on the dashboard 220 includes data exceeding a threshold, the electronic device 100 can check Device ID 2 and Device ID 3, which are the identification information of user terminals that exceed the threshold of 40 seconds for required time B, and check the value of required time A corresponding to Device ID 2 and Device ID 3. At this time, if the electronic device 100 confirms that the required time A corresponding to Device ID 2 exceeds the threshold of 30 seconds for required time A, it can provide a notification to the worker performing the application development work, indicating that the cause of the threshold exceedance is required time A. On the other hand, if the electronic device 100 confirms that the required time A corresponding to Device ID 3 does not exceed the threshold of 30 seconds for required time A, it can provide a notification to at least one of the workers performing network communication work between the electronic device 100 and the user terminal, and the worker performing network communication work between the messaging server and the user terminal, indicating that the cause of the threshold exceedance is not required time A.

[0110] Figure 8 shows a dashboard according to the third embodiment.

[0111] Referring to Figure 8, a graph showing the representative reception time for message ID 1 can be seen. The x-axis of the graph represents time, and the y-axis represents the value of the representative reception time. In other words, the graph on the dashboard 220 shows the representative reception time for push notification messages corresponding to message ID 1, as confirmed by time from 10:00 AM on January 1, 2024. The p95 at the upper right corner of the graph indicates that the preset percentile is the 95th percentile. That is, via the dashboard 220, the electronic device 100 can continuously display the value of the representative reception time corresponding to the 95th percentile among multiple reception times for push notification messages corresponding to message ID 1, sorted from smallest to largest, every hour from 10:00 AM on January 1, 2024. The operator can monitor how the representative reception time for each push notification message on each day is distributed over time via the dashboard 220 displayed by the electronic device 100.

[0112] Similar to Figures 6 and 7, 30 sec represents a preset threshold. The electronic device 100 can, for example, provide a notification to a preset worker regarding the representative reception time of a push notification message corresponding to message ID 1 at 8 PM that falls within a time period having a representative reception time value exceeding 30 sec. The worker who receives the notification can set specific conditions to verify the representative reception time of the push notification message corresponding to message ID 1, and can verify the identification information of the user terminal corresponding to the representative reception time of the push notification message that exceeded the threshold via a dashboard 220 containing data that satisfies the set conditions. An embodiment in which the electronic device 100 displays data based on specific conditions will be described in more detail below with reference to Figure 9. The electronic device 100 can also verify the identification information of the user terminal corresponding to the representative reception time of a push notification message at 8 PM that has a representative reception time value exceeding 30 sec, and provide a notification to the verified user terminal.

[0113] Figure 9 shows the dashboard according to the fourth embodiment.

[0114] In one embodiment, the electronic device 100 can identify and provide third data that satisfies pre-set conditions based on first data. The electronic device 100 can provide the third data, for example, by displaying a dashboard containing the third data. Here, the pre-set conditions may include at least one of the following: conditions relating to a date, conditions relating to user terminal identification information, and conditions relating to push notification message identification information. The pre-set conditions may further include conditions relating to a time. The pre-set conditions may be determined, for example, by selection by an operator (e.g., an application developer) on a dashboard 220 provided by the electronic device 100, and may be used to extract data relating to a specific date and data relating to the time taken to receive a push notification message for a specific user. For example, based on the acquired first data, the electronic device 100 can identify and display the time taken to receive multiple push notification messages acquired on January 1, 2024. In yet another example, based on the first data, the electronic device 100 can identify and display the time taken to receive multiple push notification messages that satisfy the condition that user terminal identification information includes Device ID 1. This allows the operator to review the history of the time it takes to receive push notification messages on a user terminal corresponding to Device ID 1, or to review the tendency to request or receive specific push notifications. In another example, the electronic device 100 can, based on the first data, review and display the reception times for multiple push notification messages corresponding to message ID 1 that satisfy the condition that the identification information of the push notification message includes message ID 1.

[0115] Referring to Figure 9, if an operator intending to analyze the time it takes to receive a push notification for Message ID 1, provided on January 1, 2024, sets January 1, 2024, as a condition, the electronic device 100 can check multiple time reception data corresponding to the conditional date based on the first data and display a dashboard 220 that represents the multiple time receptions in graph form. By further setting the time from 2 PM to 4 PM as a condition, the operator can also check multiple time receptions between 2 PM and 4 PM among the multiple time receptions for push notification messages corresponding to message ID 1, provided on January 1, 2024, via the dashboard 220. Depending on the date and time conditions set by the operator, the dashboard 220 may include time receptions by Device ID between 2 PM and 4 PM on January 1, 2024, as shown in Figure 9. If the preset threshold is 30 seconds, the electronic device 100 can provide a preset notification to the operator regarding response times exceeding 30 seconds. Furthermore, the electronic device 100 can provide notifications to user terminals corresponding to Device ID 2 and Device ID N, which have a reception time exceeding 30 seconds.

[0116] On the other hand, in the example shown in Figure 8, the worker who received the notification sets the date condition to January 1, 2024, and the time condition to 7:30 PM to 8:30 PM, in order to confirm the identification information of the user terminal corresponding to the reception time of message ID 1 at 8:00 PM. This allows the worker to confirm multiple reception times between 7:30 PM and 8:30 PM, even among the multiple reception times of the push notification message corresponding to message ID 1 provided via the dashboard 220 on January 1, 2024. As a result, the electronic device 100 can display multiple reception times for each Device ID that satisfy the conditions set by the worker via the dashboard 220, as shown in Figure 8, and the worker can confirm the identification information of user terminals with response times exceeding 30 seconds. Through monitoring the dashboard 220, the worker can identify user terminals that frequently experience the inconvenience of delayed push notification delivery, identify the cause of the delay in push notification delivery, and resolve the delay problem.

[0117] Figure 10 shows a block diagram of an electronic device 100 according to one embodiment.

[0118] In one embodiment, the electronic device 100 may include a processor 1010 and a memory 1020. The electronic device 100 shown in Figure 10 only shows components relevant to this embodiment. Therefore, a person with ordinary skill in the art related to this embodiment will understand that other general-purpose components may be included in addition to those shown in Figure 10. Descriptions of content that overlaps with Figures 1 to 9 are omitted.

[0119] The electronic device 100 may further include a communication device. The communication device may include a transceiver, which is a device for wired / wireless communication and can communicate with an external electronic device. The external electronic device may be a terminal or a server. Communication technologies used by the transceiver include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), and Bluetooth. TM Possible technologies include RFID (Radio Frequency Identification), infrared communication (Infrared Data Association; IrDA), ZigBee, and NFC (Near Field Communication).

[0120] The processor 1010 can control the overall operation of the electronic device 100 and process data and signals. The processor 1010 may consist of at least one hardware unit. The processor 1010 can also operate through one or more software modules generated by executing program code stored in memory 1020. Because the processor 1010 can include memory, it can execute program code stored in memory to control the overall operation of the electronic device 100 and process data and signals.

[0121] The processor 1010 can be embodied in a computer or similar device through hardware, software, or a combination thereof. Hardware-wise, the processor 1010 can be embodied in the form of an electronic circuit that processes electrical signals and performs control functions, and software-wise, it can be embodied in the form of a program that drives the hardware-wise processor 1010. On the other hand, unless otherwise specified in the above description, the operation of the electronic device can be interpreted as being controlled by the processor 1010. That is, when a module embodied in a system for analyzing the aforementioned data is executed, the module can be interpreted as controlling the processor 1010 to perform the aforementioned operation of the electronic device.

[0122] For example, the processor 1010 can provide at least one user terminal with information regarding a push notification message and the transmission time of the push notification message, in response to a push notification request related to an application service, via the communication unit. The processor 1010 can also obtain first data regarding the time required to receive the push notification message based on the transmission time from at least one user terminal, and can provide the obtained first data. For example, the processor 1010 can display a dashboard including the first data via a display included in the electronic device 100 or a separate display connected to the electronic device 100.

[0123] Memory 1020 can store various types of information. Memory 1020 can store data temporarily or semi-permanently. For example, the memory 1020 of the electronic device 100 may store an operating system (OS) for driving the electronic device 100, data for hosting a website, and data related to a program or application for generating Braille (e.g., a web application). Also, as mentioned above, memory 1020 can store modules in the form of computer code.

[0124] Examples of memory 1020 include hard disk drives (HDDs), solid state drives (SSDs), flash memory, read-only memory (ROMs), and random access memory (RAMs). Such memory 1020s can be supplied as internal or removable modules.

[0125] In summary, diverse embodiments can be realized through diverse means. For example, diverse embodiments can be realized through hardware, firmware, software, or a combination thereof.

[0126] In the case of hardware implementation, the various embodiments of the method can be implemented by one or more ASICs (application-specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, and the like.

[0127] In the case of implementation by firmware or software, the methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described above. For example, software code may be stored in memory and driven by a processor. The memory may be located inside or outside the processor and can send and receive data to and from the processor by various already known means.

[0128] The electronic device according to the above embodiment may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with external devices, and user interface devices such as a touch panel, keys, and buttons. A method embodied in a software module or algorithm may be stored on a computer-readable recording medium as computer-readable code or program instructions executable on the processor. Here, computer-readable recording media include magnetic recording media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD (Digital Versatile Disc)). Computer-readable recording media may be distributed across a network of computer systems, and computer-readable code may be stored and executed in a distributed manner. The medium may be computer-readable, stored in memory, and executed by the processor.

[0129] This embodiment may be represented as a functional block configuration and various processing stages. Such functional blocks may be embodied in various numbers of hardware and / or software configurations that perform specific functions. For example, the embodiment may employ an integrated circuit configuration such as memory, processing, logic, look-up tables, etc., which can perform various functions under the control of one or more microprocessors or other control devices. Just as the components may be executed by software programming or software elements, this embodiment includes various algorithms embodied in combinations of data structures, processes, routines, or other programming configurations, which may be embodied in programming or scripting languages ​​such as C, C++, Java, assembler, etc. Functional aspects may be embodied in algorithms executed on one or more processors. Furthermore, this embodiment may employ prior art for electronic environment configuration, signal processing, and / or data processing, etc. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The terms may also include the meaning of a series of software processes (routines) in conjunction with a processor, etc.

[0130] The embodiments described above are merely examples, and other embodiments may be embodied within the scope of the claims described later.

Claims

1. A method for analyzing data from electronic devices, A step of providing at least one user terminal with a push notification message and information regarding the transmission time of the push notification message in response to a push notification request related to an application service, A step of obtaining first data relating to the time required to receive the push notification message based on the transmission time from at least one user terminal, A data analysis method comprising the step of providing the first data.

2. A step of generating second data relating to the representative reception time of the push notification message based on first data from at least one user terminal, The data analysis method according to claim 1, further comprising the step of providing the second data.

3. The data analysis method according to claim 1, wherein the push notification message and information regarding the transmission time of the push notification message are provided to the at least one user terminal in the form of a push notification payload.

4. The first data is, This includes user terminal identification information, push notification message identification information, and the time required to receive the push notification message. The data analysis method according to claim 1, wherein the reception time is determined based on the time of transmission of the push notification message and the time when the user terminal receives the push notification message.

5. The data analysis method according to claim 1, wherein the time required to receive the push notification message is the time measured by the user's terminal.

6. The aforementioned application service includes services related to electronic commerce, The aforementioned electronic commerce service is The data analysis method according to claim 1, comprising at least one of the following: a service relating to the purchase of electronic commerce items, a service relating to the sale of electronic commerce items, and a service relating to the transportation of electronic commerce items.

7. The step of providing the first data is, The data analysis method according to claim 1, further comprising the step of displaying a dashboard containing the first data.

8. The step of generating the second data is: A step of confirming information regarding the time required to receive multiple push notification messages corresponding to the push notification message, based on first data from multiple user terminals, The data analysis method according to claim 2, comprising the step of determining a representative reception time for the push notification message based on the information relating to the plurality of reception times.

9. A step of confirming data that exceeds a threshold based on the first data, The process further includes the step of providing a pre-configured worker with a notification regarding data that exceeds the threshold, The data analysis method according to claim 1.

10. A step of confirming data that exceeds a threshold based on the first data, The data analysis method according to claim 1, further comprising the step of providing a notification to a user terminal corresponding to data that exceeds the threshold.

11. The data analysis method according to claim 9, wherein the threshold is set in advance as a different value for each application service.

12. The data analysis method according to claim 9, wherein the threshold is set in advance as a different value for each application service and each push notification message.

13. The aforementioned push notification message is: This is a push notification message transmitted from the aforementioned electronic device, via a messaging server, and provided to the user terminal. The data analysis method according to claim 1, wherein the messaging server is a server that transmits the push notification message to the user terminal via a route configured by information about the operating system corresponding to the user terminal.

14. The first data is, The data analysis method according to claim 13, comprising user terminal identification information, push notification message identification information, a first time period from the time of transmission of the push notification message to the time the messaging server receives the push notification message, and a second time period from the time of transmission of the push notification message to the time the user terminal receives the push notification message.

15. If the first data includes data that exceeds a threshold, When it is confirmed that the cause of the first data exceeding the threshold is the first time, a step is provided to the first worker; The data analysis method according to claim 14, further comprising the step of providing a notification to a second worker when it is confirmed that the cause of exceeding the threshold is not the first time.

16. The aforementioned first worker is a worker who performs work related to the development of the aforementioned application, The data analysis method according to claim 15, wherein the second worker is a worker who performs work related to network communication between an electronic device and a user terminal.

17. A step of confirming a third data that satisfies pre-set conditions based on the first data, The third step of providing the data is further included, The aforementioned pre-set conditions are: The data analysis method according to claim 1, comprising at least one of the following: a condition relating to the date, a condition relating to the identification information of the user terminal, and a condition relating to the identification information of the push notification message.

18. A computer-readable non-temporary recording medium that stores a program for causing a computer to perform the method according to claim 1.

19. An electronic device, Memory and A processor is included, and the processor is In response to a push notification request related to the application, the system provides at least one user terminal with a push notification message and information regarding the transmission time of the push notification message. From at least one user terminal, first data relating to the time required to receive the push notification message transmitted by the electronic device is obtained, and An electronic device that provides the aforementioned first data.

Images