Electronic device and data analysis method thereof

Abstract

Provided is a data analysis method of an electronic device. The data analysis method may comprise the steps of: providing, to at least one user terminal, a push notification message and information about sending time of the push notification message according to a push notification request related to an application service; acquiring, from the at least one user terminal, first data pertaining to a time required to receive the push notification message based on the sending time; and providing the first data.

Description

Electronic device and method for analyzing data thereof

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

[0002] Users receiving application-related push notifications cannot determine whether their push notifications are delayed. This can lead to increased delays in receiving push notifications, potentially resulting in inconvenience for users of application services. Therefore, it's crucial for application developers to explore ways to monitor the time it takes to receive push notifications in real time.

[0003] The disclosed embodiments provide an electronic device and a data analysis method thereof. More specifically, the present invention provides an electronic device and a data analysis method thereof that enable application developers to analyze the reception time of push notifications related to an application's service based on log data collected from a user terminal.

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

[0005] A method for analyzing data of an electronic device according to one embodiment may include: providing a push notification message and information regarding a 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, from at least one user terminal, first data regarding a reception time of the push notification message based on the transmission time; and providing the first data.

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

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

[0008] According to one embodiment, the first data includes user terminal identification information, push notification message identification information, and a time required for receiving the push notification message, wherein the time required for receiving the push notification message can be determined based on a time when the push notification message is transmitted and a time when the user terminal receives the push notification message.

[0009] In one embodiment, the time required for receiving a push notification message may be a time measured by the user terminal.

[0010] According to one embodiment, the application service includes a service related to e-commerce, and the service related to e-commerce may include at least one of a service related to purchasing an e-commerce object, a service related to selling an e-commerce object, and a service related to transporting an e-commerce object.

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

[0012] According to one embodiment, the step of generating the second data may include: a step of checking information regarding the reception times of a plurality of push notification messages corresponding to the push notification message based on the first data of the plurality of user terminals; and a step of determining a representative reception time of the push notification message based on the information regarding the plurality of reception times.

[0013] A method for analyzing data of an electronic device according to one embodiment may further include a step of identifying data exceeding a threshold based on first data; and a step of providing a notification regarding data exceeding the threshold to a preset worker.

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

[0015] In one embodiment, the threshold may be preset to a different value for each application service.

[0016] In one embodiment, the threshold may be preset to different values ​​for each application service and each push notification message.

[0017] According to one embodiment, a push notification message is a push notification message transmitted from an electronic device, passes through a messaging server, and is provided to a user terminal, and the messaging server may be a server that transmits a push notification message to a user terminal through a path set according to information about an operating system corresponding to the user terminal.

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

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

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

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

[0022] A non-transitory recording medium according to one embodiment may be a computer-readable non-transitory recording medium having recorded thereon a program for implementing a method performed by an electronic device.

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

[0024] Specific details of the embodiments are included in the detailed description and drawings.

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

[0026] According to an embodiment of the present specification, the time required for a push notification to be transmitted from an electronic device and provided to a user terminal can be monitored.

[0027] Additionally, in accordance with the embodiments of the present specification, if the time required for a specific push notification is greater than a threshold value and the push notification is delayed, a notification is provided to the worker so that the cause of the delay can be identified.

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

[0029] Figure 1 illustrates a system according to one embodiment.

[0030] FIG. 2 is a diagram illustrating a process in which an electronic device analyzes data according to one embodiment.

[0031] FIG. 3 is a diagram illustrating a process in which an electronic device analyzes data according to one embodiment.

[0032] FIG. 4 illustrates a point in time that serves as the basis for measuring the time required for a push notification according to one embodiment.

[0033] FIG. 5 illustrates a flowchart of a data analysis method of an electronic device according to one embodiment.

[0034] Figure 6 illustrates a dashboard according to the first embodiment.

[0035] Figure 7 illustrates a dashboard according to a second embodiment.

[0036] Figure 8 illustrates a dashboard according to a third embodiment.

[0037] Figure 9 illustrates a dashboard according to the fourth embodiment.

[0038] Figure 10 illustrates a block diagram of an electronic device according to one embodiment.

[0039] The terms used in the examples have been selected from widely used, current terms, taking into account the functions of the present disclosure. However, these terms may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Furthermore, in certain cases, terms may be arbitrarily selected by the applicant, in which case their meanings will be described in detail in the relevant description. Therefore, the terms used in this disclosure should not be defined simply as names, but rather based on the meanings of the terms and the overall content of the present disclosure.

[0040] When a part of a specification is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0041] The expression "at least one of a, b, and c" 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 "terminal" mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal via a network. Here, the computer includes, for example, a notebook, desktop, laptop, etc. equipped with a web browser, and the portable terminal may include, for example, a wireless communication device that guarantees portability and mobility, and may include all types of handheld-based wireless communication devices such as communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, tablet PCs, etc.

[0043] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0044] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

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

[0046] Referring to FIG. 1, the system may include at least one of an electronic device (100), a first user terminal (120), a second user terminal (140), a third user terminal (160), and a network (180). Meanwhile, the system illustrated in FIG. 1 only illustrates components related to the present embodiment. Therefore, those skilled in the art will appreciate that, in addition to the components illustrated in FIG. 1, other general-purpose components may be included.

[0047] An electronic device (100) is a device that configures and provides various types of information. The electronic device (100) may provide the configured information as a web page or application screen, or may provide the information in a form that can be displayed as a web page or application screen on a receiving terminal.

[0048] According to one embodiment, the electronic device (100) may provide data to at least one user terminal, and may obtain 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) may provide a push notification message and information regarding a transmission time of the push notification message to at least one user terminal, obtain first data regarding a reception time of the push notification message based on the transmission time from the at least one user terminal, 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 the 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 the users can receive push notifications related to application services using their respective terminals and use the application services based on the received push notifications.

[0050] Meanwhile, although not illustrated in FIG. 1, the electronic device (100) may include a database. A database is a data structure implemented in a predetermined storage space, in which functions such as storing, searching, deleting, editing, or adding data can be freely performed. For example, the database may include fields or components for processing functions such as storing, 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) includes a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and a combination thereof, and is a comprehensive data communication network that enables each network component illustrated in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and a mobile radio communication network. Wireless communication may include, but is not limited to, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, Zigbee, Wi-Fi Direct (WFD), ultra-wideband (UWB), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), etc., for example.

[0052] FIG. 2 is a drawing for explaining a process in which an electronic device (100) analyzes data according to one embodiment.

[0053] According to one embodiment, the electronic device (100) may provide a push notification message and information regarding the timing of transmission 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, and the application service may refer to a service provided through the application. In this case, the application may be an application that provides an e-commerce service, and thus, the application service may include an e-commerce service. The e-commerce service may include, for example, at least one of a service related to the purchase of an e-commerce object, a service related to order management for the sale of an e-commerce object, and a service related to the transportation of an e-commerce object. Specifically, the service related to the purchase of an e-commerce object may include a service related to an order and delivery request, the service related to the sale of an e-commerce object may include a service related to order management for the sale of an e-commerce object, and the service related to the transportation of an e-commerce object may include a service related to transportation accompanying the sale of an e-commerce object. Meanwhile, services related to purchasing e-commerce items, services related to order management for selling e-commerce items, and services related to transporting e-commerce items may each be e-commerce services provided through different applications.

[0054] Accordingly, e-commerce services provided through different applications can provide push notifications to at least one user terminal corresponding to the application providing the service. Here, the at least one user terminal corresponding to the application may refer to at least one user terminal using an application among multiple applications that provides the service requesting the push notification. In other words, the user terminals to which each e-commerce service provided through different applications provides push notifications may be user terminals using different applications.

[0055] A push notification request related to an application service may include at least one push notification request. Specifically, a push notification request related to a service related to purchasing an e-commerce object may include a push notification request to a first user terminal (120), a push notification request related to a service related to selling an e-commerce object may include a push notification request to a second user terminal (140), and a push notification request related to a service related to transporting an e-commerce object 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, according to the application for which the push notification is provided. That is, the first user terminal (120) may be a user terminal of at least one user (e.g., an orderer) using an application that provides a service related to ordering and delivery requests for products, the second user terminal (140) may be a user terminal of at least one user (e.g., a seller or a store) using an application that provides a service related to order management for product sales, and the third user terminal (160) may be a user terminal of at least one user (e.g., a delivery person) using an application that provides a service related to transportation accompanying product sales. In other words, the first user terminal (120), the second user terminal (140), and the third user terminal (160) may each include at least one user terminal that uses an application that provides the same type of service. For convenience, the contents regarding the first user terminal (120), the second user terminal (140), and the third user terminal (160) may be equally applied below.

[0056] As a more specific example, a push notification request related to a service related to purchasing e-commerce may include a push notification request for notifying at least one first user terminal (120) that an order and delivery request for a service related to purchasing e-commerce has been received based on an input (e.g., a user's action of pressing a button, banner, etc. on an application screen) provided to the first user terminal (120) requesting an order and delivery of a specific food from a specific store, a push notification request for notifying at least one first user terminal (120) that the order request has been accepted, a push notification request for notifying at least one first user terminal (120) that delivery of a specific food according to the order and delivery request has started, etc.

[0057] A push notification request related to a service regarding sales of an e-commerce target may include, for example, a push notification request requesting at least one second user terminal (140) to input whether to accept a specific food order and delivery from a specific store, a push notification request notifying the second user terminal (140) to input an expected delivery time of the food, a push notification request notifying at least one second user terminal (140) that a delivery request has been accepted, a push notification request notifying at least one second user terminal (140) to input a requested food pickup time from a delivery departure point based on acceptance of the delivery request, etc.

[0058] Push notification requests related to services related to transportation of e-commerce may include, for example, a push notification request informing at least one third user terminal (160) to enter whether to accept a delivery request from an address of a specific store to an address of a delivery destination, a push notification request informing a third user terminal (160) of a food pickup request time from a delivery departure point for delivery, etc.

[0059] That is, in response to at least one push notification request related to one application service, the electronic device (100) may provide a push notification message corresponding to the push notification request and information regarding the transmission time of the push notification message to at least one user terminal corresponding to the push notification request. In addition, when there is at least one push notification request related to multiple application services, the electronic device (100) may provide a push notification message corresponding to each push notification request and information regarding the transmission time of the push notification message to at least one user terminal corresponding to the push notification request.

[0060] Meanwhile, the time of transmission of a push notification message may be the time at which the application service transmits the push notification message to the user terminal. The push notification message and information regarding the time of transmission 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, the information regarding the time of transmission of the push notification message may be provided to the user terminal by being included in a data field within the payload, where the data within the field is transmitted as is without processing.

[0061] Next, the electronic device (100) may obtain first data regarding the reception time of a push notification message based on the transmission time from at least one user terminal. The first data may include, for example, user terminal identification information, push notification message identification information, and the reception time of the push notification message. The reception time may be determined based on, for example, the transmission time of the push notification message and the time at which the user terminal receives the push notification message. The reception time may be the time from the transmission time of the push notification message to the time at which the user terminal receives the push notification message. The reception time of 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 including the first data. A more specific embodiment in which the electronic device (100) provides data by displaying a dashboard will be described in detail with reference to FIGS. 6 to 9 below.

[0063] According to one embodiment, the electronic device (100) may identify data exceeding a threshold based on first data and provide a notification regarding the data exceeding the threshold to a preset worker. Here, the preset worker may include a worker set for at least one user terminal using an application that provides the same type of service. For example, the electronic device (100) may identify through a dashboard that the time required for at least one first user terminal (120) includes data exceeding the threshold, and provide a notification regarding the time required for the first user terminal (120) to a preset worker. The preset worker to receive a notification regarding the time required for the first user terminal (120) may be, for example, a developer who monitors service operations regarding orders and delivery requests for e-commerce objects among application services. The content of the notification provided to the worker may include, for example, information regarding an abnormal delay in providing a specific push notification message regarding a service regarding orders and delivery requests for e-commerce objects to a specific user terminal. Based on the notifications provided, the operator can identify specific terminals that frequently experience delays in delivering push notification messages, and by identifying the cause, resolve issues such as user inconvenience caused by delays in delivering push notification messages.

[0064] Meanwhile, thresholds may be preset to different values ​​for each application service, for example. Specifically, the thresholds for at least one push notification message related to a service related to purchasing an e-commerce object, the thresholds for at least one push notification message related to a service related to selling an e-commerce object, and the thresholds for at least one push notification message related to a service related to transporting an e-commerce object may be preset to different values, taking into account the impact of push notification delays associated with each service.

[0065] As a more specific example, a delay in push notification messages, such as a push notification message notifying that an order and delivery request has been received and a push notification message notifying that an order request has been accepted, provided to a first user terminal (120) by a service related to purchases of e-commerce objects, may cause the orderer to misunderstand that the order and delivery request cannot be accepted, or may cause the orderer to perceive that the acceptance of the order is delayed due to a large number of order and delivery requests. However, considering that the orderer may request to order and deliver other products or other stores, such a delay in push notifications may be viewed as causing only a relatively minor inconvenience to users of the first user terminal (120) in using the application service. In contrast, delays in push notification messages, such as push notification messages requesting input of whether to accept an order and delivery of a specific food from a specific store and push notification messages notifying that a delivery request has been accepted, provided to a second user terminal (140) by a service related to sales of e-commerce objects, may lead to problems such as orders being canceled before the store confirms the order and delivery requested by the customer, or food cooking itself being delayed due to a delay in accepting a delivery request. In this case, the delay in push notification messages may negatively affect sales of a specific store, reviews or ratings of a specific store, etc. Therefore, the threshold corresponding to a service related to sales of e-commerce objects may be set lower than the threshold corresponding to a service related to sales of e-commerce objects. In other words, the threshold corresponding to each service may be set in consideration of the impact of the push notification delay associated with each service. Accordingly, the threshold corresponding to the first user terminal (120), the threshold corresponding to the second user terminal (140), and the threshold corresponding to the third user terminal (160) may be set to different values ​​in consideration of the influence of push notification delay associated with each service.The electronic device (100) will be able to provide higher quality service to users of the application by monitoring the time required to receive push notifications while taking into account the influence of the delay in push notifications of the application service.

[0066] In another example, the threshold value may be preset to a different value for each application service and push notification message. Specifically, the threshold value may be a preset value based on the importance of each of at least one push notification message requested by an application service. For example, if an e-commerce delivery service requests a third user terminal (160) to provide a push notification message requesting whether to accept a delivery request from a specific store address to a delivery destination address and a push notification message informing the user of the requested food pickup time at the delivery origin for delivery, the threshold values ​​for each push notification message may be different.

[0067] If the push notification message requesting the user to enter whether or not to accept a delivery request to a third-party user terminal (160) is delayed, problems may arise, such as the delivery person being evaluated based on the number of food delivery services provided from the store to the customer through the application in a month, or the delivery person having to provide delivery services for a preset amount or number of times per day having the delivery request canceled or the request rejected without the user's consent. Accordingly, it is highly necessary to distinguish between the case where the delivery request is not accepted despite the push notification being provided to the user's terminal and the case where the delivery service is not provided regardless of the user's consent before or immediately after the push notification message is displayed on the user's terminal. On the other hand, if the push notification message notifying the food pickup request time from the delivery departure point to the third-party user terminal (160) is delayed, there is a possibility that the food pickup at the delivery departure point may be delayed due to the delayed confirmation of the food pickup request time. However, considering the food cooking time, the possibility of a delay in food pickup appears to be low. Therefore, the importance of a push notification message requesting input on whether to accept a delivery request may be relatively higher than that of a push notification message informing the user of the requested food pickup time from the delivery origin. Even when requested by the same type of service, considering the importance of push notification messages, the threshold for a push notification message requesting input on whether to accept a delivery request from a specific store address to the delivery destination address may be set lower than the threshold for a push notification message informing the user of the requested food pickup time.

[0068] In another example, the electronic device (100) may provide statistical information regarding the reception time of a push notification message based on the first data. Specifically, based on the reception times of multiple push notification messages, the electronic device may provide information such as the total number or percentage of data that is less than or equal to a preset value, the total number or percentage of data that is greater than or equal to a preset value, etc. The preset value may be, for example, a value input by a worker for monitoring data regarding push notifications. Accordingly, the electronic device (100) may calculate and provide to the worker the percentage of data that is less than or equal to 30 seconds, the percentage of data that is greater than or equal to 1 minute, etc. of a push notification message requesting input of whether or not to accept delivery provided to a third user terminal (160), for example. Furthermore, the electronic device (100) may also provide a notification to the worker if the total number or percentage of data that is greater than or equal to 1 minute increases compared to the previous day based on the data regarding the reception times of multiple push notification messages at a specific time.

[0069] According to one embodiment, the electronic device (100) may identify data exceeding a threshold based on first data, and provide a notification to a user terminal corresponding to the data exceeding the threshold. For example, if the electronic device (100) confirms through the dashboard that the time required for Device ID 1 includes data exceeding the threshold, and confirms that Device ID 1 is Terminal 1 included in the first user terminal (120), the electronic device (100) may provide a notification to Terminal 1. The content of the notification provided to the user terminal may include, for example, content regarding the occurrence of an abnormal delay in the provision of a specific push notification message. The threshold may be preset to a different value for each application service, for example. In another example, the threshold may be a preset value based on the relationship between the time required to receive a push notification message and the service of the application.

[0070] In Fig. 2, Service 1 (202), Service 2 (204), and Service 3 (206) represent application services. As an example, only Service 1 (202), Service 2 (204), and Service 3 (206) are illustrated in Fig. 2, but more types of services may be included depending on the embodiment. Service 1 (202) may refer to a service related to purchasing an e-commerce object, Service 2 (204) may refer to a service related to selling an e-commerce object, and Service 3 (206) may refer to a service related to transporting an e-commerce object. For convenience, the contents of Service 1 (202), Service 2 (204), and Service 3 (206) may be equally applied below. The electronic device (100) may provide a push notification to the user terminal in response to a push notification request related to Service 1 (202), a push notification request related to Service 2 (204), a push notification request related to Service 3 (206), etc. Each push notification request related to Service 1 (202), Service 2 (204), Service 3 (206), etc. may be, for example, a push notification request by each application service, and specifically, may be a call to the Push Sending Service (210) of each application service for sending a push notification. As an example, in FIG. 2, the push notification request of the application service is illustrated as being generated within the electronic device (100), but according to an embodiment, it may be a request generated by the application service from an external electronic device (e.g., a terminal, a server, etc.) with which the electronic device (100) can communicate. The Push Sending Service (210) may transmit a 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 according to the push notification request of the application service.

[0071] If Service 1 (202) calls Push Sending Service (210) to provide a push notification notifying that an order from a specific orderer has been received, for example, Push Sending Service (210) can transmit a push notification notifying that an order has been received to the first user terminal (120) from which the order was requested. If Service 2 (204) calls Push Sending Service (210) to provide a push notification requesting input of whether to accept an order and delivery of a specific food from a specific store, for example, Push Sending Service (210) can transmit a push notification requesting input of whether to accept an order and delivery of a specific food to the second user terminal (140) corresponding to the specific store. If Service 3 (206) calls Push Sending Service (210) to provide a push notification requesting input of whether to accept delivery from a specific delivery person, for example, Push Sending Service (210) can transmit a push notification requesting input of whether to accept delivery to a third user terminal (160) corresponding to the specific delivery person. Meanwhile, based on an input requesting order and delivery of a specific food from a specific store provided to the first user terminal (120), Service 1 (202) can call Push Sending Service (210) to provide a push notification notifying that an order has been received to the first user terminal (120), and simultaneously or in parallel, Service 2 (204) can transmit a push notification requesting input of whether to accept order and delivery of a specific food to the second user terminal (140).

[0072] The operation of the electronic device (100) providing a push notification to at least one first user terminal (120) corresponding to the push notification request in response to at least one push notification request related to Service 1 (202), the operation of providing a push notification to at least one second user terminal (140) corresponding to the push notification request in response to at least one push notification request related to Service 2 (204), and the operation of providing a push notification to at least one third user terminal (160) corresponding to the push notification request in response to at least one push notification request related to Service 3 (206) may be performed at different times according to the push notification request times of 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), the second user terminal (140), the third user terminal (160), etc.) can receive a push notification message transmitted from the Push Sending Service (210) and information regarding the transmission time of the push notification message. For example, at least one user terminal can receive the Title which is the title of the push notification message, the Content which is the content of the push notification message, the Push sending time which is the transmission time of the push notification message, etc. Here, the Push sending time may be, for example, the time at which the Push Sending Service (210) is called by at least one application service.<Title, Content, Push sending time> The back can be provided to the user terminal in the form of a payload.

[0074] The code for the payload provided to the user terminal in the Push sending service (210) may include a pushPayloads field including data corresponding to variables such as token, phase, osType, device ID, title, and msg, and an extras field including data corresponding to variables such as tracking ID and Push sending time. The token included in the pushPayloads field is a variable sent to Counous (410), which is a messaging server to be described in FIG. 4 below, and may include information about a platform corresponding to the user terminal, and both Phase and osType may include information about the user terminal, the device ID may include user terminal identification information, the title may include information about the title of the push notification message, and the msg may include information about the content of the push notification message, such as Content of FIG. 2.

[0075] Meanwhile, the tracking ID included in the extras field may be data including information about an entry point within a series of paths from the Push Sending Service (210) to the provision of a push notification 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 of Service 2 (204), the tracking ID may include information about at least one entry point within a series of paths for providing a push notification, from the call to the Push Sending Service (210) of Service 2 (204) to the processing logic on the backend server side for generating a push notification notifying the food pickup request time from the delivery departure point in response to the call of Service 2, and to the transmission of the generated push notification to the second user terminal (140).

[0076] Meanwhile, unlike other fields in the payload-type data, all 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 the data in the extras field among the payload-type data provided to at least one user terminal by the Push sending service (210) as provided to the terminal without processing (e.g., processing to extract only a part of the data). Accordingly, the Push sending time and tracking ID included in the extras field can be obtained by the electronic device (100) as provided to the user terminal. The electronic device (100) can check information about the unique path through which each push notification was provided based on the tracking ID corresponding to the push notification obtained from the user terminal.

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

[0078] When the time at which at least one user terminal receives a push notification message is called the Push receive time, the required time may be the difference between the Push receive time measured by the user terminal and the Push sending time (Push receive time - Push sending time). The first data may be, for example, log data acquired in real time through Lumberjack. Lumberjack may collect, process, and transmit log data. Although Lumberjack is illustrated as a component included in the electronic device (100) in FIG. 2, FIG. 2 is only an example, and in other examples, Lumberjack may be included in the user terminal as a component other than the electronic device (100) or may be included 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 through Lumberjack, after processing it with Flink Streaming. Flink Streaming can include a process of converting the log data into a streaming data format by processing it using Flink. The electronic device (100) can display, for example, a dashboard (220) including the first data that has gone through the Flink Streaming process. Meanwhile, although FIG. 2 illustrates that there is only one Lumberjack acquiring the first data from each of the first user terminal (120) and the second user terminal (140), Lumberjack can exist for each user terminal. That is, Lumberjack can exist for each user terminal that uses an application that provides the same type of service. Accordingly, the first data acquired by the electronic device (100) from the user terminal may 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 dashboard including each of the first data may also exist separately.

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

[0081] According to one embodiment, the electronic device (100) may generate second data regarding a representative reception time of a push notification message based on first data of at least one user terminal, and provide the second data. Specifically, the electronic device (100) may acquire the first data through a process as described above with reference to FIG. 2, and generate the second data based on the acquired first data. For example, the electronic device (100) may check information regarding the reception times of a plurality of push notification messages corresponding to a push notification message based on the first data of a plurality of user terminals, and determine a representative reception time of the push notification message based on the information regarding the plurality of reception times. Subsequently, the electronic device (100) may store second data including information regarding the representative reception times of the determined push notification messages in a database, and display a dashboard including the stored second data.

[0082] Referring to FIG. 3, the electronic device (100) may provide a push notification message and information about 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)). Subsequently, the electronic device (100) may 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 may be log data collected in real time through Lumberjack. Description of the same content as in FIG. 2 will be omitted. Subsequently, the electronic device (100) may generate second data about a representative required reception time of the push notification message.

[0083] For example, the first data that went through the Flink Streaming process is data corresponding to message ID 1.<Device ID, message ID 1, 소요 시간, ...> When including multiple times, multiple 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 multiple required times. Then, the electronic device (100) can receive information about the determined representative required time for the push notification message corresponding to message ID 1 (<message ID 1, 대표 소요 시간> ) can be stored in a database (310), and a dashboard (220) including the stored second data can be displayed.

[0084] In another example, the first data is the data corresponding to message ID 1.<Device ID, message ID 1, 소요 시간, ...> , data corresponding to message ID 2<Device ID, message ID 2, 소요 시간, ...> , and data corresponding to message ID 3<Device ID, message ID 3, 소요 시간, ...> When including, the electronic device (100) checks a plurality of required times corresponding to message ID 1, a plurality of required times corresponding to message ID 2, and a plurality of required times corresponding to message ID 3 based on the first data, and, based on each of the checked plurality of required times, checks 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, including second data (<message ID 1, 대표 소요 시간> ,<message ID 2, 대표 소요 시간> ,<message ID 3, 대표 소요 시간> ) can be generated. Subsequently, 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 time of the push notification message by the electronic device (100), a worker such as an application developer can analyze which specific push notification message takes the longest time, and provide a more improved application service based on the analysis.

[0085] In one example, the representative reception time of a push notification message may be a reception time corresponding to a preset percentile among multiple reception times sorted from smallest to largest. The preset percentile may be, for example, the 95th percentile (representing a response time corresponding to the top 5%), the 90th percentile (representing a reception time corresponding to the top 10%), or the 50th percentile (representing a reception time corresponding to the top 50%). In another example, the representative reception time of a push notification message may be an average of multiple reception times.

[0086] According to one embodiment, the electronic device (100) may generate second data regarding a representative reception time of push notification messages for each user terminal based on first data of a plurality of user terminals, and provide the generated second data. For example, the electronic device (100) may check information regarding the reception time of a plurality of push notification messages corresponding to each Device ID based on the first data of the plurality of user terminals, and determine a representative reception time for each user terminal based on the information regarding the plurality of reception times. Subsequently, the electronic device (100) may store the second data including the information regarding the representative reception time for each determined Device ID in a database, and may display a dashboard (220) including the stored second data. As described above, since the first data is data based on a plurality of user terminals using an application that provides the same type of service, for example, an application developer may determine which of the plurality of user terminals included in the first user terminal (120) using the ordering and delivery request service generally experiences a delay in providing push notifications based on the second data provided by the electronic device (100).

[0087] FIG. 4 illustrates a point in time that serves as the basis for measuring the time required for a push notification according to one embodiment.

[0088] According to one embodiment, the electronic device (100) may 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, obtain first data regarding the time required to receive the push notification message based on the transmission time from the at least one user terminal, and provide the first data. In this case, the push notification message is a push notification message transmitted from the electronic device (100) and provided to the user terminal via a messaging server, and the messaging server may be a server that transmits the push notification message to the user terminal via a path set according to information regarding an operating system corresponding to the user terminal. The messaging server may be a third-party server that provides a messaging service for transmitting the push notification message from the electronic device (100) to the user terminal. The messaging server used to provide the push notification message may include a server device corresponding to various services according to 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] According to 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 from the time of transmitting the push notification message to the time at which the messaging server receives the push notification message, and a second time from the time of transmitting the push notification message to the time at which the user terminal receives the push notification message. The first time may be, for example, the time from the time at which the push notification message is transmitted to the messaging server of the electronic device (100) to the time at which the messaging server receives the push notification message. In another example, the first time may be the time from the time at which the electronic device (100) calls the messaging server. The second time may be, for example, the time from the time at which the push notification message is transmitted to the messaging server of the electronic device (100) to the time at which the user terminal receives the push notification message by the messaging server confirming platform information corresponding to the user terminal and transmitting the push notification message to the user terminal through a server corresponding to the platform information. Accordingly, the electronic device (100) may display a dashboard including the first time and the second time. The above description may apply to overlapping content.

[0090] According to one embodiment, when the first data includes data exceeding a threshold, the electronic device (100) may provide a notification to a first worker if it determines that the cause of the first data exceeding the threshold is the first time, and may provide a notification to a second worker if it determines that the cause of the threshold exceeding is not the first time. Specifically, when the first data includes data exceeding the threshold, the electronic device (100) may compare data regarding the first time with threshold value 1, and if data exceeding threshold value 1 is present, it may determine that the cause of the threshold exceeding is the first time, and if data exceeding threshold value 1 is not present, it may determine that the cause of the threshold exceeding is not the first time. In another example, the electronic device (100) may determine whether data regarding the second time corresponding to the data exceeding the threshold exceeds threshold value 2 and data regarding the first time corresponding to the data exceeding the threshold exceeds threshold value 1 in order to determine the cause of the threshold exceeding. In the two examples described above, threshold 1 is a threshold for the first time period, and threshold 2 is a threshold for the second time period, which may be a value that is the sum of threshold 1 and a value that adds an allowable amount of delay to the time that it normally takes for the messaging server to transmit a message to the user terminal. Accordingly, the electronic device (100) that determines whether the cause of the threshold exceedance is the first time period can provide a notification to the operator corresponding to the cause of the threshold exceedance.

[0091] The first worker may be, for example, a worker performing work related to application development, and the second worker may be, for example, a worker performing 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 providing a push notification message from the server to the messaging server, the electronic device (100) may provide a notification to the worker performing work related to application development. The content of the notification may include, for example, information about an abnormal delay in providing a specific push notification message related to an e-commerce delivery service 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 providing a push notification message from the messaging server to the user terminal, the electronic device (100) may provide a notification to the worker performing 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 performing work related to network communication between the messaging server and the user terminal. The content of the notification may include, for example, information indicating a delay in delivering a message to the user terminal due to a communication issue. Accordingly, the electronic device (100) not only provides a notification regarding a delay in delivering a push notification, but also identifies the cause of the delay and notifies the relevant worker, thereby enabling a more rapid and accurate resolution of the problem of delayed push notification delivery.

[0092] Meanwhile, the threshold that serves as the basis for notification provision may be preset to a different value for each application service, for example. In another example, the threshold may be preset to a different value for each application service and push notification message.

[0093] Referring to FIG. 4, the electronic device (100) may transmit at least one push notification message to Counos (410), which represents a messaging server, and Counos (410) may transmit the push notification message to a user terminal corresponding to each push notification message based on platform information corresponding to the user terminal. The time required A may be a first time, for example, the time required from the time the application service calls the Push Sending Service (210) to the time the Counos (410) receives the push notification message, and in another example, the time required from the time the application service calls the Push Sending Service (210) to the time the Push Sending Service (210) calls Counos (410). The time required B may be a second time, for example, the time required from the time the application service calls the Push Sending Service (210) to the time the push notification message is provided to the user terminal from the electronic device (100) via Counos (410). When transmitting a push notification message and the transmission time of the push notification message from Counos (410) to a user terminal, Counos (410) may also transmit information regarding the time at which the push notification message was received or the time at which the Push Sending Service (210) called Counos (410). Accordingly, the first data acquired by the electronic device (100) from the user terminal may include information regarding the required time A and the required time B measured by the user terminal. Subsequently, the electronic device (100) may display a dashboard including the required time A and the required time B. A more specific embodiment of providing a notification to a first worker or a second worker based on the dashboard will be described in detail with reference to FIG. 7 below.

[0094] Figure 5 illustrates a flowchart of a data analysis method for an electronic device according to one embodiment. The above description may apply to overlapping content.

[0095] In step S500, the electronic device (100) can provide a push notification message and information about the timing of transmission of the push notification message to at least one user terminal in response to a push notification request related to an application service.

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

[0097] According to one embodiment, the application service includes a service related to e-commerce, and the service related to e-commerce may include at least one of a service related to purchasing an e-commerce object, a service related to selling an e-commerce object, and a service related to transporting an e-commerce object.

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

[0099] According to one embodiment, the first data includes user terminal identification information, push notification message identification information, and a time required for receiving the push notification message, and the time required for receiving the push notification message can be determined based on a time point at which the push notification message is transmitted and a time point at which the user terminal receives the push notification message.

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

[0101] At step S540, the electronic device (100) can provide first data.

[0102] According to one embodiment, the electronic device (100) may display a dashboard including first data.

[0103] Figure 6 illustrates a dashboard (220) according to the first embodiment.

[0104] Referring to FIG. 6, a graph regarding the reception times of multiple push notification messages corresponding to Message ID 1 can be confirmed. The x-axis of the graph represents the Device ID, and the y-axis represents the value of the reception time. Specifically, the graph of the dashboard (220) represents the reception time of the push notification message corresponding to message ID 1 confirmed at 11:00 AM on January 1, 2024. In this way, the electronic device (100) can display the dashboard (220) that can confirm the multiple reception times for each push notification message by time based on the first data acquired from at least one terminal. The worker can monitor the distribution of the reception times of multiple push notification messages by specific time on a specific date through the dashboard (220) displayed by the electronic device (100).

[0105] Meanwhile, 30 sec represents a preset threshold value for message ID 1. The electronic device (100) can, for example, identify a user terminal corresponding to Device ID 2 having a time value exceeding 30 sec (i.e., delayed provision of a push notification message). Next, when the user terminal is included in the first user terminal (120), the electronic device (100) can provide a notification to a worker preset to receive a notification regarding the first user terminal (120) regarding the delay in the time required corresponding to Device ID 2. In addition, the electronic device (100) can provide a notification regarding the delay in the push notification to the user terminal corresponding to the identified Device ID 2. 30 sec set as a threshold value in FIG. 6 is only an example, and the threshold value may vary depending on the embodiment.

[0106] Figure 7 illustrates a dashboard (220) according to the second embodiment.

[0107] Referring to FIG. 7, a graph regarding multiple time periods A and a graph regarding multiple time periods B of a push notification message corresponding to Message ID 1 can be confirmed. The graph of the dashboard (220) represents data regarding time periods A and B of the push notification message corresponding to message ID 1 confirmed at 11:00 AM on January 1, 2024, respectively, and the x-axis represents the Device ID, and the y-axis represents the value of time periods A or B. In this way, the electronic device (100) can display the dashboard (220) that can confirm each of the multiple time periods A and B of the push notification message by time based on the first data including the time periods A and B acquired from at least one terminal. The operator can monitor the distribution of each of the multiple time periods A and B of the push notification message by time period on a specific date through the dashboard (220) displayed by the electronic device (100).

[0108] Meanwhile, through Fig. 7, as described above, it can be confirmed that each data of the time required B has a larger value than each data of the time required A, and that the threshold value of the time required B, 40 sec, is set to a larger value than the threshold value of the time required A, 30 sec. The threshold value of the time required B, 40 sec, may be, for example, the value obtained by adding 10 sec, which is the allowable amount of delay added to the time normally required for message transmission from Counos (410) to the user terminal, to the threshold value of the time required A, 30 sec.

[0109] Referring to FIG. 7, when the data indicated by the dashboard (220) includes data exceeding a threshold value, the electronic device (100) can check the user terminal identification information Device ID 2 and Device ID 3 that exceed the threshold value of the time required B of 40 seconds, and check the value of the time required A corresponding to each of Device ID 2 and Device ID 3. At this time, the electronic device (100) that confirms that the time required A corresponding to Device ID 2 exceeds the threshold value of the time required A of 30 seconds, can provide a notification to a worker performing work related to application development, as the cause of exceeding the threshold value is the time required A. Meanwhile, the electronic device (100) that confirms that the time required A corresponding to Device ID 3 does not exceed the threshold value of the time required A of 30 seconds, can provide a notification to at least one worker among a worker performing work related to network communication between the electronic device (100) and the user terminal and a worker performing work related to network communication between the messaging server and the user terminal, as the cause of exceeding the threshold value is not the time required A.

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

[0111] Referring to FIG. 8, a graph regarding the representative reception time of message ID 1 can be confirmed. The x-axis of the graph represents time, and the y-axis represents the value of the representative reception time. That is, the graph of the dashboard (220) represents the representative reception time of the push notification message corresponding to message ID 1 confirmed over time from 10:00 AM on January 1, 2024. p95 on the upper right of the graph indicates that the preset percentile is the 95th percentile. That is, through the dashboard (220), the electronic device (100) can continuously display the value of the representative reception time corresponding to the 95th percentile among the multiple reception times of the push notification messages corresponding to message ID 1 sorted in order from the smallest value to the largest value every hour from 10:00 AM on January 1, 2024. The worker can monitor the distribution of the representative reception time of each push notification message by date over time through the dashboard (220) displayed by the electronic device (100).

[0112] As with FIGS. 6 and 7, 30 seconds represents a preset threshold. The electronic device (100) may provide a notification to a preset worker regarding the representative reception time of a push notification message corresponding to message ID 1 at 8:00 PM, which is included in a time zone having a representative reception time value exceeding 30 seconds, for example. The worker who receives the notification may set a specific condition to check the representative reception time of the push notification message corresponding to message ID 1, and may check user terminal identification information corresponding to the representative reception time of the push notification message exceeding the threshold through a dashboard (220) including data satisfying the set condition. An embodiment in which the electronic device (100) displays data according to a specific condition will be described in more detail with reference to FIG. 9 below. In addition, the electronic device (100) may check user terminal identification information corresponding to the representative reception time of a push notification message at 8:00 PM, which has a representative reception time value exceeding 30 seconds, and provide a notification to the identified user terminal.

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

[0114] According to one embodiment, the electronic device (100) may identify third data that satisfies a preset condition based on the first data and provide the third data. The electronic device (100) may provide the third data, for example, by displaying a dashboard including the third data. Here, the preset condition may include at least one of a condition regarding a date, a condition regarding identification information of a user terminal, and a condition regarding identification information of a push notification message. In addition, the preset condition may further include a condition regarding time. The preset condition may be determined, for example, by a selection by an operator (e.g., an application developer) on the dashboard (220) provided by the electronic device (100), and may be used to extract data regarding a specific date and data regarding the time required to receive a push notification message by a specific user. For example, the electronic device (100) may identify and display a plurality of reception times for push notification messages acquired on January 1, 2024, based on the acquired first data. In another example, the electronic device (100) can check and display, based on the first data, the reception times of a plurality of push notification messages that satisfy the condition that the identification information of the user terminal includes Device ID 1. Accordingly, the operator can check the history of the reception times of the push notification messages of the user terminal corresponding to Device ID 1, or the tendency to request a specific push notification or the tendency to receive a push notification. In another example, the electronic device (100) can check and display, based on the first data, the reception times of a plurality of 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 FIG. 9, if January 1, 2024 is set as a condition by a worker who wants to analyze the time required for receiving push notifications of Message ID 1 provided on January 1, 2024, the electronic device (100) can check multiple pieces of reception time information corresponding to the date that serves as the condition based on the first data and display a dashboard (220) that expresses the multiple reception times in a graph form. In addition, by setting the time from 2:00 PM to 4:00 PM as a condition, the worker can check multiple reception times between 2:00 PM and 4:00 PM among the multiple reception times of push notification messages corresponding to Message ID 1 provided on January 1, 2024 through the dashboard (220). Depending on the date and time conditions set by the worker, the dashboard (220) can include the reception times for each Device ID between 2:00 PM and 4:00 PM on January 1, 2024, as shown in FIG. 9. When the preset threshold is 30 seconds, the electronic device (100) can provide a notification to a preset worker regarding a response time exceeding 30 seconds. In addition, the electronic device (100) can provide a notification to a user terminal corresponding to Device ID 2 and a user terminal corresponding to Device ID N, which have a reception time exceeding 30 seconds.

[0116] Meanwhile, in the example described above in FIG. 8, the worker who received the notification sets the date condition to January 1, 2024, and additionally sets the time condition to from 7:30 PM to 8:30 PM, in order to check the user terminal identification information corresponding to the reception time of message ID 1 at 8:00 PM, so that among the multiple reception times of push notification messages corresponding to message ID 1 provided on January 1, 2024, the worker can check the multiple reception times between 7:30 PM and 8:30 PM through the dashboard (220). Accordingly, the electronic device (100) can display the reception times for each of the multiple Device IDs that satisfy the conditions set by the worker, as shown in FIG. 8, through the dashboard (220), and the worker can check the user terminal identification information having a response time exceeding 30 seconds. By monitoring the dashboard (220), the operator can identify user terminals that frequently experience inconvenience due to delayed push notification delivery, and can resolve the delay problem by identifying the cause of the delay in push notification delivery.

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

[0118] The electronic device (100) may include a processor (1010) and a memory (1020), according to one embodiment. The electronic device (100) illustrated in FIG. 10 only illustrates components related to the present embodiment. Therefore, those skilled in the art will understand that, in addition to the components illustrated in FIG. 10, other general-purpose components may be included. Descriptions of content overlapping with FIGS. 1 to 9 will be omitted.

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

[0120] The processor (1010) can control the overall operation of the electronic device (100) and process data and signals. The processor (1010) can be composed of at least one hardware unit. In addition, the processor (1010) can operate by one or more software modules generated by executing program codes stored in the memory (1020). The processor (1010) can include a memory, and the processor (1010) can control the overall operation of the electronic device (100) and process data and signals by executing program codes stored in the memory.

[0121] The processor (1010) may be implemented as a computer or similar device based on hardware, software, or a combination thereof. In terms of hardware, the processor (1010) may be implemented in the form of an electronic circuit that processes electrical signals to perform control functions, and in terms of software, the processor (1010) may be implemented in the form of a program that drives the hardware processor (1010). Meanwhile, unless otherwise specified in the above description, the operation of the electronic device may be interpreted as being performed under the control of the processor (1010). That is, when modules implemented in the system for analyzing the above-described data are executed, the modules may be interpreted as controlling the processor (1010) to perform the above-described operations of the electronic device.

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

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

[0124] Examples of memory (1020) may include a hard disk drive (HDD), a solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. Such memory (1020) may be provided as a built-in type or a detachable type.

[0125] In summary, the various embodiments may be implemented through various means. For example, the various embodiments may be implemented through hardware, firmware, software, or a combination thereof.

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

[0127] When implemented via 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 executed by a processor. The memory may be located within or outside the processor and may exchange data with the processor via various known means.

[0128] The electronic device according to the above-described embodiments may include a processor, a memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a user interface device such as a touch panel, a key, a button, etc. The methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on the processor. Here, the computer-readable recording medium includes a magnetic storage medium (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and an optical reading medium (e.g., CD-ROM, DVD: Digital Versatile Disc)). The computer-readable recording medium may be distributed to computer systems connected to a network, so that the computer-readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

[0129] The present embodiment may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various hardware and / or software configurations that perform specific functions. For example, the embodiment may employ direct circuit configurations such as memory, processing, logic, look-up tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Similarly, the present embodiment may be implemented in a programming or scripting language such as C, C++, Java, assembler, etc., including various algorithms implemented as a combination of data structures, processes, routines, or other programming configurations. Functional aspects may be implemented as algorithms that execute on one or more processors. Furthermore, the present embodiment may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "composition" can be used broadly and are not limited to mechanical or physical structures. These terms can also encompass a series of software routines, such as those associated with a processor.

[0130] The above-described embodiments are merely examples, and other embodiments may be implemented within the scope of the claims set forth below.

Claims

1. In a method for analyzing data of an electronic device, A step 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; A step of 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 A data analysis method comprising a step of providing the first data.

2. In paragraph 1, A step of generating second data regarding a representative reception time of the push notification message based on first data of at least one user terminal; and A data analysis method further comprising a step of providing the second data.

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

4. In paragraph 1, The above first data is, Includes user terminal identification information, push notification message identification information, and the time required to receive the push notification message. A data analysis method wherein the above reception time is determined based on the time at which the push notification message is transmitted and the time at which the user terminal receives the push notification message.

5. In paragraph 1, A data analysis method wherein the time required to receive the above push notification message is the time measured by the user terminal.

6. In paragraph 1, The above application service includes services related to e-commerce, The above e-commerce services are: A data analysis method comprising at least one of a service related to purchasing an e-commerce object, a service related to selling an e-commerce object, and a service related to transporting an e-commerce object.

7. In paragraph 1, The step of providing the above first data is: A data analysis method comprising the step of displaying a dashboard including the first data.

8. In paragraph 2, The step of generating the above second data is: A step of checking information regarding the reception time of a plurality of push notification messages corresponding to the push notification message based on first data of a plurality of user terminals; and A data analysis method comprising a step of determining a representative reception time of the push notification message based on information about the plurality of reception times.

9. In paragraph 1, A step of checking data exceeding a threshold value based on the first data; and Further comprising the step of providing a notification to a preset worker regarding data exceeding the threshold, Data analysis methods.

10. In paragraph 1, A step of checking data exceeding a threshold value based on the first data; and A data analysis method further comprising the step of providing a notification to a user terminal corresponding to data exceeding the above threshold.

11. In paragraph 9, A data analysis method in which the above threshold value is preset to a different value for each application service.

12. In paragraph 9, A data analysis method wherein the above threshold value is preset to a different value for each application service and each push notification message.

13. In paragraph 1, The above push notification message is, A push notification message transmitted from the electronic device and provided to the user terminal via a messaging server, A data analysis method, wherein the above messaging server is a server that transmits the push notification message to the user terminal through a path set according to information about the operating system corresponding to the user terminal.

14. In paragraph 13, The above first data is, A data analysis method comprising user terminal identification information, push notification message identification information, a first time from the time of transmission of the push notification message to the time at which the messaging server receives the push notification message, and a second time from the time of transmission of the push notification message to the time at which the user terminal receives the push notification message.

15. In paragraph 14, If the above first data includes data exceeding the threshold value, If it is confirmed that the cause of the first data exceeding the threshold is the first time, a step of providing a notification to the first worker; and A data analysis method further comprising the step of providing a notification to a second worker when it is confirmed that the cause of exceeding the threshold value is not the first time.

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

17. In paragraph 1, A step of confirming third data that satisfies a preset condition based on the first data; and Further comprising a step of providing the third data, The above-mentioned conditions are: A data analysis method comprising at least one of a condition regarding a date, a condition regarding identification information of a user terminal, and a condition regarding identification information of a push notification message.

18. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method of paragraph 1 on a computer.

19. As an electronic device, memory; and A processor is included, wherein the processor comprises: In response to a push notification request related to an application, providing a push notification message and information about the timing of transmission of the push notification message to at least one user terminal, Obtaining first data regarding the time required to receive the push notification message according to the transmission of the push notification message by the electronic device from at least one user terminal, and An electronic device providing the first data.

Images