WO2019146996A1 - Method for network state identification and electronic device therefor - Google Patents

Abstract

An electronic device according to various embodiments of the present invention can include a method comprising the steps of: identifying the state of a transport protocol; determining a communication state of the electronic device on the basis of the state of the transport protocol; and changing a network on the basis of the communication state. Other embodiments are also possible.

Description

METHOD FOR IDENTIFICATION OF NETWORK STATE

Various embodiments of the present invention are directed to an apparatus and method for network status identification in an electronic device.

Recently, in order to cope with the exponential increase of smartphone users with the introduction of smart phones, efforts are being made to provide optimal network services to users. For example, optimal network services can provide a seamless Internet experience for users, regardless of Wi-Fi or cellular network, by selecting the most optimized network for the user to access the Internet. have. In order to provide an optimal network service to a user, methods of measuring a user's network environment and selecting a network so that a user can use smooth network services are being discussed. For example, the electronic device can analyze the state of a transport layer protocol represented by a transmission control protocol (TCP), thereby providing an optimal network environment for a user.

Various embodiments of the present invention provide a method and an electronic device for network status identification of an electronic device.

According to various embodiments of the present invention, a method of operating an electronic device includes the steps of: identifying a state of a transport protocol; determining a communication state of the electronic device based on the state of the transmission protocol; And changing the network based on the communication state.

According to various embodiments of the present invention, an electronic device includes a communication module, at least one processor, a memory operably coupled to the at least one processor, , Identify a state of a transport protocol, determine a communication state of the electronic device based on the state of the transmission protocol, and store instructions that cause the network to change based on the communication state.

The electronic device and its method of operation according to various embodiments can identify network conditions more efficiently than existing methods by identifying network conditions using a transport protocol.

1 shows a block diagram of an electronic device in a network environment in accordance with various embodiments of the present invention.

2A illustrates a block diagram 200 of an electronic device according to various embodiments of the present invention.

Figure 2B illustrates a block diagram 240 of a wireless communication module, a power management module, and an antenna module of an electronic device according to various embodiments of the present invention.

Figure 3 shows a flow diagram 300 of an electronic device according to various embodiments of the present invention.

FIG. 4 illustrates a flow diagram 400 of an electronic device for identifying a transmission protocol state to determine a communication state in accordance with various embodiments of the present invention.

FIG. 5 illustrates a sequence diagram 500 for transmitting data using a transmission control protocol (TCP) protocol in accordance with various embodiments of the present invention.

6 illustrates an example 600 of an interface of an electronic device displayed in an electronic device when the communication status according to various embodiments of the present invention is in a block state.

Figure 7A shows a flowchart 710 illustrating a red flag accumulation in accordance with various embodiments of the present invention.

Figure 7B shows a flowchart 720 illustrating a red flag accumulation in accordance with various embodiments of the present invention.

Figure 8 illustrates a flowchart 800 for determining a good state in accordance with various embodiments of the present invention.

Figure 9 illustrates a flowchart 900 for determining a poor state in accordance with various embodiments of the present invention.

Figure 10 illustrates a flowchart 1000 for determining a blocked state in accordance with various embodiments of the present invention.

11 illustrates a flowchart 1100 for determining a sluggish state in accordance with various embodiments of the present invention.

12 illustrates a flowchart 1200 for identifying a communication state and modifying a network in accordance with various embodiments of the present invention.

13 shows a flow diagram 1300 of an electronic device for monitoring the status of a transport layer protocol in accordance with various embodiments of the present invention.

14 illustrates an example 1400 interface of an electronic device for monitoring the status of a transport layer protocol in accordance with various embodiments of the present invention.

15A illustrates an example 1500 of an interface of an electronic device to be displayed on an electronic device when the communication state is in a block state according to various embodiments of the present invention.

15B shows an example 1510 of an interface of an electronic device displayed on an electronic device when the communication state is in a good state according to various embodiments of the present invention.

FIG. 16 illustrates a sequence diagram 1600 illustrating a state change of a transport protocol socket in accordance with various embodiments of the present invention.

Figure 17 illustrates a flow diagram 1700 of an electronic device that determines a backhaul failure based on at least one of a state of a transport protocol and a count of a transport protocol in accordance with various embodiments of the present invention.

18 shows an example 1800 of an interface of an electronic device that represents a backhaul failure in accordance with various embodiments of the present invention.

19 illustrates a flow diagram 1900 of an electronic device that determines a backhaul failure based on a total count of connection and a connection establishment count in accordance with various embodiments of the present invention.

Figure 20 shows a graph 2000 illustrating an example of determining a backhaul failure based on a total count of transmission protocols and a connection establishment count in accordance with various embodiments of the present invention.

21 shows a flow diagram 2100 of an electronic device for determining a backhaul failure based on a retransmission state of a transmission protocol according to various embodiments of the present invention.

22A illustrates a graph 2200 illustrating an example of determining a backhaul failure based on the retransmission state of a transmission protocol in accordance with various embodiments of the present invention.

Figure 22B shows a sequence diagram 2250 illustrating an example of determining a backhaul failure based on the retransmission state of a transport protocol in accordance with various embodiments of the present invention.

23 shows a flow diagram 2300 of an electronic device for determining a backhaul failure based on a reception error of a transmission protocol according to various embodiments of the present invention.

24A illustrates a graph 2400 illustrating an example of determining a backhaul failure based on a reception error of a transmission protocol in accordance with various embodiments of the present invention.

24B illustrates a sequence diagram 2450 illustrating an example of determining a backhaul failure based on a reception error of a transmission protocol in accordance with various embodiments of the present invention.

25 shows a flow diagram 2500 of an electronic device for indicating a backhaul failure and a network change indicator in accordance with various embodiments of the present invention.

26 illustrates an example interface 2600 of an electronic device for indicating a network change indicator in a backhaul failure according to various embodiments of the present invention.

FIG. 27 illustrates an example interface 2700 of an electronic device that indicates a change to another access point (AP) upon a backhaul failure in accordance with various embodiments of the present invention.

28 illustrates an example of an interface 2800 of an electronic device that optionally presents a network change indicator upon backhaul failure according to various embodiments of the present invention.

29 shows a flow diagram 2900 of an electronic device sharing a backhaul failure with other electronic devices in accordance with various embodiments of the present invention.

30A illustrates an example 3010 of sharing a backhaul failure with another electronic device connected to the same AP upon a backhaul failure according to various embodiments of the present invention.

Figure 30B illustrates an example 3020 of sharing a backhaul failure with another electronic device connected to the same AP upon a backhaul failure according to various embodiments of the present invention.

31 shows a flow diagram 3100 of an electronic device that stores and provides information related to backhaul failures in accordance with various embodiments of the present invention.

32 shows a flow diagram 3200 of an electronic device for checking backhaul failures and performing control over backhaul failures in accordance with various embodiments of the present invention.

33 shows a flow diagram 330 of an electronic device illustrating an implementation for examining a backhaul condition in accordance with various embodiments of the present invention.

34 illustrates a flow diagram 3400 of an electronic device for obtaining a threshold according to various embodiments of the present invention.

35 shows a flow diagram 3500 of an electronic device for obtaining a received signal strength indication (RSSI) threshold according to various embodiments of the present invention.

36 shows a flow diagram 3600 of an electronic device for checking a new connection establishment state and a time waiting state in accordance with various embodiments of the present invention.

Figure 37 shows a flow diagram 3700 of an electronic device for inspecting in-segment and out-segment errors in accordance with various embodiments of the present invention.

38 shows a flow diagram 3800 of an electronic device for inspecting a retransmission segment in accordance with various embodiments of the present invention.

Figure 39 shows a flow diagram 3900 of an electronic device for checking the state of a backhaul in accordance with various embodiments of the present invention.

Hereinafter, various embodiments of the present document will be described with reference to the accompanying drawings.

1 is a block diagram of an electronic device 101 in a network environment 100, in accordance with various embodiments. 1, an electronic device 101 in a network environment 100 communicates with an electronic device 102 via a first network 198 (e.g., a short-range wireless communication network) (E. G., A < / RTI > remote wireless communication network). According to one embodiment, the electronic device 101 is capable of communicating with the electronic device 104 through the server 108. According to one embodiment, the electronic device 101 includes a processor 120, a memory 130, an input device 150, an audio output device 155, a display device 160, an audio module 170, a sensor module 176, an interface 177, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a subscriber identity module 196, ). In some embodiments, at least one (e.g., display 160 or camera module 180) of these components may be omitted from the electronic device 101, or one or more other components may be added. In some embodiments, some of these components may be implemented as a single integrated circuit. For example, a sensor module 176 (e.g., a fingerprint sensor, an iris sensor, or a light sensor) may be implemented embedded in the display device 160 (e.g., a display)

Processor 120 executes at least one other component (e.g., hardware or software component) of electronic device 101 connected to processor 120 by executing software (e.g., program 140) And can perform various data processing or arithmetic operations. According to one embodiment, as part of a data processing or computation, the processor 120 may provide instructions or data received from other components (e.g., sensor module 176 or communication module 190) Process the instructions or data stored in the volatile memory 132, and store the resulting data in the non-volatile memory 134. According to one embodiment, the processor 120 includes a main processor 121 (e.g., a central processing unit or application processor), and a secondary processor 123 (e.g., a graphics processing unit, an image signal processor , A sensor hub processor, or a communications processor). Additionally or alternatively, the coprocessor 123 may use less power than the main processor 121, or it may be set to be specific to the specified function. The coprocessor 123 may be implemented separately from, or as part of, the main processor 121.

 The coprocessor 123 may be configured to execute on behalf of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, At least one component (e.g., display device 160, sensor module 176, or communication module 190) of the components of electronic device 101, along with main processor 121, Lt; RTI ID = 0.0 > and / or < / RTI > According to one embodiment, the coprocessor 123 (e.g., an image signal processor or communications processor) may be implemented as part of a functionally related other component (e.g., camera module 180 or communication module 190) have.

Memory 130 may store various data used by at least one component (e.g., processor 120 or sensor module 176) of electronic device 101. The data may include, for example, input data or output data for software (e.g., program 140) and instructions related thereto. The memory 130 may include a volatile memory 132 or a non-volatile memory 134.

The program 140 may be stored as software in the memory 130 and may include, for example, an operating system 142, middleware 144,

The input device 150 may receive commands or data to be used for components (e.g., processor 120) of the electronic device 101 from the outside (e.g., a user) of the electronic device 101. The input device 150 may include, for example, a microphone, a mouse, or a keyboard.

The sound output device 155 can output the sound signal to the outside of the electronic device 101. [ The sound output device 155 may include, for example, a speaker or a receiver. Speakers can be used for general purposes, such as multimedia playback or record playback, and receivers can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker, or as part thereof.

Display device 160 may visually provide information to an external (e.g., user) of electronic device 101. Display device 160 may include, for example, a display, a hologram device, or a projector and control circuitry for controlling the device. According to one embodiment, the display device 160 may comprise a touch circuitry configured to sense a touch, or a sensor circuit (e.g., a pressure sensor) configured to measure the force generated by the touch have.

The audio module 170 may convert the sound into an electrical signal or vice versa. According to one embodiment, the audio module 170 is configured to acquire sound through the input device 150, or to output audio to the audio output device 155, or to an external electronic device (e.g., Electronic device 102) (e.g., a speaker or headphone)).

The sensor module 176 senses the operating state (e.g., power or temperature) of the electronic device 101 or an external environmental condition (e.g., a user state) and generates an electrical signal or data value corresponding to the sensed condition can do. According to one embodiment, the sensor module 176 may be, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, A temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 177 may support one or more designated protocols that may be used by the electronic device 101 to connect directly or wirelessly with an external electronic device (e.g., the electronic device 102). According to one embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 may be physically connected to an external electronic device (e.g., the electronic device 102). According to one embodiment, connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module 179 may convert electrical signals into mechanical stimuli (e.g., vibrations or movements) or electrical stimuli that the user may perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 can capture a still image and a moving image. According to one embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 can manage the power supplied to the electronic device 101. [ According to one embodiment, the power management module 388 may be implemented as at least a portion of, for example, a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101. According to one embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

The communication module 190 may be a direct (e.g., wired) communication channel between the electronic device 101 and an external electronic device (e.g., an electronic device 102, an electronic device 104, or a server 108) Establishment, and communication through the established communication channel. Communication module 190 may include one or more communication processors that operate independently of processor 120 (e.g., an application processor) and that support direct (e.g., wired) or wireless communication. According to one embodiment, the communication module 190 may include a wireless communication module 192 (e.g., a cellular communication module, a short range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 : A local area network (LAN) communication module, or a power line communication module). A corresponding one of these communication modules may be a first network 198 (e.g., a short range communication network such as Bluetooth, WiFi direct or IrDA (infrared data association)) or a second network 199 (e.g. a cellular network, (E.g., a telecommunications network, such as a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into one component (e.g., a single chip) or a plurality of components (e.g., a plurality of chips) that are separate from each other. The wireless communication module 192 may be configured to communicate with the subscriber identity module 196 in a communication network such as the first network 198 or the second network 199 using subscriber information (e.g., International Mobile Subscriber Identity (IMSI) The electronic device 101 can be confirmed and authenticated.

The antenna module 197 can transmit signals or power to the outside (e.g., an external electronic device) or receive it from the outside. An antenna module, according to one embodiment, may be formed of a conductor or a conductive pattern, and in some embodiments may further include other components (e.g., RFIC) in addition to the conductor or conductive pattern. In accordance with one embodiment, the antenna module 197 may include one or more antennas, from which at least one (e.g., one or more) antennas suitable for a communication scheme used in a communication network, such as the first network 198 or the second network 199, May be selected, for example, by the communication module 190. A signal or power may be transmitted or received between the communication module 190 and the external electronic device via the selected at least one antenna.

At least some of the components are connected to each other via a communication method (e.g., bus, general purpose input and output, SPI, or mobile industry processor interface (MIPI) For example, commands or data).

 According to one embodiment, the command or data may be transmitted or received between the electronic device 101 and the external electronic device 104 via the server 108 connected to the second network 199. Each of the electronic devices 102 and 104 may be the same or a different kind of device as the electronic device 101. [ According to one embodiment, all or a portion of the operations performed on the electronic device 101 may be performed on one or more external devices of the external electronic devices 102, 104, or 108. For example, in the event that the electronic device 101 has to perform some function or service automatically, or in response to a request from the user or another device, the electronic device 101 may, instead of executing the function or service itself Or in addition, to one or more external electronic devices to perform the function or at least part of the service. One or more external electronic devices that have received the request may execute at least a portion of the requested function or service, or an additional function or service associated with the request, and deliver the result of the execution to the electronic device 101. The electronic device 101 may process the result as it is or in addition to provide it as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, or client-server computing technology may be used.

2A illustrates a block diagram 200 of an electronic device according to various embodiments of the present invention. For example, the electronic device may include all or a portion of the electronic device 101 shown in FIG.

2A, the electronic device 101 may include one or more processors (e.g., an AP) In various embodiments, the processor 120 may include a transport protocol state identification unit 210, a communication state determination unit 220, and a network change unit 230. However, the present invention is not limited thereto, and some components may be omitted. According to an embodiment of the present invention, the transmission protocol state identifying unit 210, the communication state determining unit 220, and the network changing unit 230 may be implemented as separate hardware or software modules outside the processor 120 Lt; / RTI >

The transport protocol status identifying unit 210 can identify the status of the transport protocol to determine the communication status of the electronic device. In various embodiments of the invention, the transport protocol may comprise a transmission control protocol (TCP). TCP provides connection-oriented communication. In connection-oriented communication, communication can be performed after preparation for communication with a communication partner is started before data communication is started. TCP can indicate various socket states during this connection process, and the electronic device can identify dynamically changing TCP socket states.

In various embodiments, the communication state determination unit 220 can determine the communication state of the electronic device based on the identified TCP socket state. For example, the communication state may include states such as data transmission and reception signal strength of an electronic device, block by a network firewall, and the like. In various embodiments, a predefined table may be stored in the memory 130 to determine the communication state according to the TCP socket state. In various embodiments, the communication state may include a poor state, a good state, a blocked state, and a sluggish state. In various embodiments, the communication state may mean Internet service quality. For example, if the user can smoothly use an application that requires the Internet, the processor 120 may determine that the Internet service quality is good and determine the communication state to be good. If the user can not use an application that requires the Internet smoothly, the processor 120 may determine that the quality of the internet service is bad and determine that the communication state is insufficient.

In various embodiments, the network changing unit 230 may change the network to which the electronic device is connected based on the determined communication state. For example, when the communication state of the electronic device is in the block state, the WiFi network environment is good but is blocked by the firewall, so that the network change unit 230 can perform the network change from the WiFi to the cellular network. As another example, in some countries, even in a cellular network environment, the right to use certain apps may be blocked by the firewall. Therefore, the network changing unit 230 can notify the user of this block state, and can perform the network change to the Wi-Fi in the cellular network.

In various embodiments, the processor 120 can perform a network change by detecting the state of a socket of a transport layer protocol, since a network quality measure alone can not detect that a particular application is blocked by a firewall. For example, the transport layer protocol may include user datagram protocol (UDP) and TCP. Of these, TCP is a protocol that controls the transmission of information in a network. It allows a series of octets to be exchanged stably, sequentially, and error-free between a local area network, an intranet, a computer connected to the Internet, or a program running on a smart phone. The above-described socket may be an endpoint connecting communication between a plurality of entities performing communication. Because all applications use sockets to send and receive data, application applications that interact with other electronic devices can create a socket pattern. In various embodiments of the present invention, the processor 120 may use a socket pattern to detect the communication state of the electronic device. The communication state may include a user experience of a user using the electronic device. For example, the user experience may include states such as data transmission and reception signal strength of electronic devices, block by network firewall, and the like. In various embodiments, the processor 120 may identify the state of the TCP socket and determine the state of communication based on the state of the identified TCP socket. After the communication state is determined, the processor 120 may change the network based on the determined communication state. For example, you can change from Wi-Fi to a cellular network.

In various embodiments, the electronic device 101 may include a communication module 190, a processor 120, and a memory 130 operatively coupled to the processor 120. The memory 130, when executed, causes the processor 120 to identify the state of the transport protocol, determine the communication state of the electronic device 101 based on the state of the identified transport protocol, Based on the communication state of the device 101. [0040] In one embodiment, the state of the transport protocol may include the state of the TCP socket of the application running in the electronic device 101. [ In one embodiment, the communication state of the electronic device 101 may be determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state.

In one embodiment, the instructions stored in the memory 130 of the electronic device 101 cause at least one processor 101 to detect a TCP socket for connection establishment, Identifies whether or not the sum of the transmission data packet and the reception data packet of the application executed in the electronic device 101 is larger than the threshold value and identifies whether or not the TCP socket state is in the connection release waiting state and the time The state of the TCP socket is changed from the connection setting request state to the connection setting state and the sum of the transmission data packet and the reception data packet is larger than the threshold value, When the release standby state and the time standby state are identified, the communication state of the electronic device 101 is determined to be in a good state You can lock it.

The instructions stored in the memory 130 of the electronic device 101 allow the processor 120 to identify whether the communication state of the electronic device 101 is in a good state and to provide a TCP socket Identifies whether the state of the TCP socket is a connection establishment request state, identifies whether the number of transmission data packets of the application executed in the electronic device 101 is larger than the number of reception data packets, If the TCP socket for connection setting is detected, the connection setting request status is identified, and the number of transmission data packets is larger than the number of received data packets, the communication status of the electronic device 101 is set to the insufficient status Can be determined.

In one embodiment, the instructions stored in memory 130 of electronic device 101 cause processor 120 to detect a TCP socket that performs retransmission and send a transmission data packet < RTI ID = 0.0 > And identifies whether the number of received data packets is less than a threshold and whether the link speed, SNR (signal) and received signal strength indication (RSSI) of the electronic device 101 are greater than a threshold, If the TCP socket performing the retransmission is concealed and the number of transmit data packets and receive data packets is less than the threshold and the link speed, SNR and RSSI are greater than the threshold, the communication state of the electronic device 101 is determined to be in the block state can do. In one embodiment, the block state may include a state in which an application running on the electronic device 101 is blocked by a network firewall.

In one embodiment, the instructions stored in memory 130 of electronic device 101 cause processor 120 to detect a TCP socket for connection establishment and determine whether the state of the TCP socket is a new connection establishment request state Identifies whether or not the sum of the transmission data packet and the reception data packet of the application executed in the electronic device 101 is smaller than a threshold value, a TCP socket for connection establishment is detected, a new connection establishment request state is identified , And when the sum of the transmission data packet and the reception data packet is smaller than the threshold value, the communication state of the electronic device 101 can be determined as the sluggish state.

2B is a block diagram 200 of a wireless communication module 192, a power management module 188, and an antenna module 197 of the electronic device 101, according to various embodiments. 2, the wireless communication module 192 may include an MST communication module 250 or an NFC communication module 260, and the power management module 188 may include a wireless charging module 270. Referring to FIG. In this case, the antenna module 297 is connected to the MST antenna 297-1 connected to the MST communication module 250, the NFC antenna 297-3 connected to the NFC communication module 260, and the wireless charging module 270 And a plurality of antennas including a wireless charging antenna 297-5. For convenience of description, elements overlapping with those in Fig. 1 are omitted or briefly described.

The MST communication module 250 receives a signal including payment information such as control information or card information from the processor 120 and generates a magnetic signal corresponding to the received signal through the MST antenna 297-1 And then transmit the generated magnetic signal to an external electronic device 102 (e.g., POS device). In order to generate the magnetic signal, according to one embodiment, the MST communication module 250 includes a switching module (not shown) including one or more switches connected to the MST antenna 297-1 To change the direction of the voltage or current supplied to the MST antenna 297-1 according to the received signal. The change in the direction of the voltage or current makes it possible to change the direction of the magnetic signal (e.g., magnetic field) transmitted through the MST antenna 297-1 accordingly. When a magnetic signal in a direction changing direction is detected by an external electronic device 102, a magnetic card corresponding to the received signal (e.g., card information) is read by the card reader of the electronic device 102 swiped) effects (eg, waveforms) similar to those that occur. According to one embodiment, the payment related information and control signals received in the form of the magnetic signals at the electronic device 102 may be transmitted to the external server 108 (e.g., ). ≪ / RTI >

The NFC communication module 260 acquires a signal containing the payment information such as control information or card information from the processor 120 and transmits the obtained signal to the external electronic device 102 via the NFC antenna 297-3. As shown in FIG. According to one embodiment, the NFC communication module 260 can receive such signals sent from an external electronic device 102 via an NFC antenna 297-3.

The wireless charging module 270 wirelessly transmits power to an external electronic device 102 (e.g., a mobile phone or a wearable device) via a wireless charging antenna 297-5, or to an external electronic device 102 : Wireless charging device). The wireless charging module 270 may support one or more of various wireless charging schemes including, for example, magnetic resonance or magnetic induction.

According to one embodiment, some of the MST antenna 297-1, the NFC antenna 297-3, or the wireless charging antenna 297-5 may share at least a portion of the radiating part with each other. For example, the radiating portion of the MST antenna 297-1 can be used as the radiating portion of the NFC antenna 297-3 or the wireless charging antenna 297-5, and vice versa. In this case, the antenna module 297 may be coupled to the wireless communication module 192 (e.g., the MST communication module 250 or the NFC communication module 260) or the power management module 188 (e.g., the wireless charging module 270) (Not shown) configured to selectively connect (e.g., close) or disconnect (e.g., open) at least a portion of the antennas 297-1, 297-3, have. For example, when the electronic device 101 uses the wireless charging function, the NFC communication module 260 or the wireless charging module 270 may control the switching circuit so that the NFC antenna 297-3 and the wireless charging antenna 297-5 may be temporarily disconnected from the NFC antenna 297-3 and connected to the wireless charging antenna 297-5.

According to one embodiment, at least one function of MST communication module 250, NFC communication module 260, or wireless charging module 270 may be controlled by an external processor (e.g., processor 120) . According to one embodiment, the designated functions (e.g., payment functions) of the MST communication module 250 or the NFC communication module 260 may be performed in a trusted execution environment (TEE). A trusted execution environment (TEE) according to various embodiments may be implemented in the memory 130 for use in performing functions (e.g., financial transactions, or personal information related functions) that require a relatively high level of security, An execution environment in which at least some designated areas are allocated can be formed. In this case, access to the designated area may be limitedly allowed, for example, depending on the subject accessing thereto or the application executing in the trusted execution environment.

1) may include a communication module (e.g., communication module 190 of FIG. 1), at least one processor (e.g., processor 120 of FIG. 1 (E.g., memory 130 of FIG. 1) operatively coupled to the at least one processor, and the memory 130, when executed, causes the at least one processor 120 to transmit May identify the state of the transport protocol, determine the communication state of the electronic device 101 based on the state of the transmission protocol, and store instructions to change the network based on the communication state.

In various embodiments, the state of the transport protocol may include a state of a transmission control protocol (TCP) socket of an application executing in the electronic device.

In various embodiments, the communication state may be determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state.

In various embodiments, the instructions cause the at least one processor to detect a TCP socket for connection establishment, identify whether the state of the TCP socket changes from a connection establishment request state to a connection establishment state, Identifying whether a sum of a transmission data packet and a reception data packet of an application executed in an electronic device is larger than a threshold value, identifying whether the state of the TCP socket is a connection release waiting state and a time waiting state, A TCP socket is detected, a state of the TCP socket is changed from a connection setting request state to a connection setting state, a sum of the transmission data packet and the reception data packet is larger than a threshold, and the connection release waiting state and the time waiting state are identified , The communication state is determined to be the good state Can.

In various embodiments, the instructions further cause the at least one processor to identify whether the communication state is in a good state, detect a TCP socket for connection establishment, determine whether the state of the TCP socket is a connection establishment request state And identifies whether or not the number of transmission data packets of an application executed in the electronic device is greater than the number of received data packets, and if the communication state is not a good state and a TCP socket for connection setting is detected , The connection establishment request status is identified, and if the number of transmission data packets is larger than the number of the reception data packets, the communication status can be determined as the shortage status.

In various embodiments, the instructions cause the at least one processor to detect a TCP socket performing retransmission and to determine whether the number of transmit and receive data packets of the application running on the electronic device is less than a threshold Identifies whether the link speed, SNR (signal) and received signal strength indication (RSSI) of the electronic device is greater than a threshold value, discovers a TCP socket performing the retransmission, The communication state may be determined as a block state if the number of packets and the number of the received data packets is smaller than a threshold value and the link speed, SNR and RSSI are larger than a threshold value.

In various embodiments, the block state may include a state in which an application running in the electronic device is blocked by a network firewall.

In various embodiments, the instructions cause the at least one processor to detect a TCP socket for connection establishment, to identify whether the state of the TCP socket is a new connection establishment request state, Identifying whether a sum of transmit data packets and receive data packets of the application is less than a threshold, detecting a TCP socket for the connection establishment, identifying the new connection establishment request status, It is possible to determine the communication state to be the slow state.

In various embodiments, the instructions cause the at least one processor to display the communication state on the electronic device and to display a message on the electronic device based on the communication state, can do.

In various embodiments, the instructions cause the at least one processor to acknowledge at least one of a state of the transport protocol and a count of the transport protocol, and determine at least one of a state of the acknowledged transport protocol and a count of the transport protocol And determine a backhaul failure based on the determined backhaul failure and perform control on the backhaul failure based on the determined backhaul failure.

In various embodiments, the instructions cause the at least one processor to verify that the total count of the transport protocol is greater than or equal to a threshold, to ensure that the connection establishment count of the transport protocol is maintained or reduced, And determine the backhaul failure based on the results.

In various embodiments, the instructions cause the at least one processor to verify that the number of transmit data packets and receive data packets of an application executing in the electronic device is less than or equal to a threshold value, To determine the backhaul failure.

In various embodiments, the instructions may cause the at least one processor to determine that a retransmission segment of the transport protocol is above a threshold, and to determine the backhaul failure based on the determined result.

In various embodiments, the instructions may cause the at least one processor to determine that an error has occurred in a received segment of the transport protocol and to determine the backhaul failure based on the determined results.

In various embodiments, the instructions may cause the at least one processor to display information about the backhaul failure and to display an indicator for modifying the network based on the backhaul failure.

In various embodiments, the instructions may cause the at least one processor to identify an external device to send information about the backhaul failure and to transmit information about the backhaul failure to the identified external device .

Figure 3 shows a flow diagram 300 of an electronic device according to various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. The operating entity of the illustrated flowchart 300 can be understood as an electronic device 101 or a component of an electronic device 101 (e.g., processor 120).

Referring to FIG. 3, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may identify a network state at operation 301. In one embodiment, the network conditions may include a communication state of the electronic device 101 or a backhaul state. In one embodiment, the communication state of the electronic device 101 may include a poor state, a good state, a blocked state, and a sluggish state. Processor 120 may determine the communication state of electronic device 101 described above by identifying a transport protocol state (i.e., a TCP socket state). In one embodiment, the backhaul state of the electronic device 101 is configured to communicate with the external communication device on the Internet (eg, Wi-Fi) when the electronic device 101 communicates via an external communication device : A backhaul connection state in which a cloud is connected) or a backhaul connection failure state in which the external communication apparatus and the Internet are not connected. In various embodiments, the backhaul connection failure state may be referred to as a backhaul failure.

According to various embodiments, the processor 120 may, at operation 303, control the electronic device based on the identified network conditions. For example, if the identified network state corresponds to one of the communication states described above, the processor 120 displays the determined communication state on a display (e.g., display 160 of FIG. 1) of the electronic device 101 can do. If the identified network condition corresponds to a backhaul failure, the processor 120 may display the backhaul failure status on the display 160, or may display a network change indicator < RTI ID = 0.0 > Can be displayed on the display device (160). In one embodiment, the processor 120 may be configured to display the identified backhaul failure status on the display device 160, or automatically display a change to another network, without displaying it, if the identified network condition corresponds to a backhaul failure Can be performed. In one embodiment, a change to another network due to a backhaul failure may be provided as a user selectable option. For example, if an option is automatically activated by the user indicating that the processor 120 is capable of changing to another network if it identifies a backhaul failure, the processor 120 may send the identified backhaul failure status to the display 160 ), Or can automatically perform a change to another network without displaying it. If the option is disabled, the processor 120 may not automatically perform a change to another network.

In various embodiments, a process and an example of determining a communication state of an electronic device by identifying a transmission protocol state and performing a network change based on the determined communication state are described in FIGS. 4 to 15B, described below.

4 shows a flow diagram of an electronic device according to various embodiments of the present invention.

In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 4 is part of operation 301 of FIG. 3, and operation 405 of FIG. 4 is part of operation 303 of FIG. 3, and the operating entity of the illustrated flowchart 400 is an electronic device 101 or an electronic device (E. G., Processor 120) of processor 101. < / RTI >

4, at operation 401, the processor 120 may identify a transport protocol state. According to one embodiment of the present invention, the processor 120 may identify the TCP socket state. For example, in the case of connection oriented communication directed by TCP, preparations for communication between a client and a server can be performed before data communication is started. In this preliminary preparation, the TCP socket state can change dynamically. For example, the TCP socket state may include a connection establishment request (SYN_SENT), a connection establishment (ESTABLISHED), and a connection release (FIN_WAIT). The processor 120 may identify that the TCP socket state is changed to the above-described states. The general operation of the TCP socket state change can be represented as shown in FIG.

At operation 403, the processor 120 may determine the communication state based on the identified transport protocol state. For example, the processor 120 may determine the communication state of the electronic device 101 by identifying the TCP socket state. In various embodiments, the communication state may include a poor state, a good state, a blocked state, and a sluggish state. These communication states can be determined by considering not only the state of the TCP socket, but also the received signal strength, link speed, and the like. In this way, the electronic device 101 can detect various communication states that are difficult to distinguish only by physical channel characteristics. For example, when the communication state is in the block state, the physical channel of the network currently in use is excellent, but the communication may not be performed as shown in FIG.

At operation 405, the processor 120 may change the network based on the communication state. For example, the processor 120 may perform a network change from the Wi-Fi network to the cellular network if the determined communication state is a block state. In various embodiments, the processor 120 can control the display device 160 of the electronic device 101 to display the determined communication state and whether or not the network is changed, before changing the network. In various embodiments, the processor 120 may perform network changes based on user input or on a specific threshold. The electronic device 101 can communicate with external electronic devices (e.g., server 108, electronic device 104) in a modified network environment by measuring the communication state and performing the network change, as described above have.

In various embodiments, the processor 120 may identify the state of the transport protocol, determine the communication state of the electronic device 101 based on the state of the identified transport protocol, and perform a network change based on the determined communication state . In one embodiment, the state of the transport protocol may include the state of the TCP socket of the application running in the electronic device 101. [ In one embodiment, the communication state of the electronic device 101 may be determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state.

Figure 5 illustrates a sequence diagram for transmitting data using the TCP protocol according to various embodiments of the present invention. In various embodiments, the electronic device may identify a TCP socket condition to detect a communication condition. As shown in FIG. 5, a TCP connection may be formed through a sequence of a plurality of states. The TCP socket state can be changed from the current state to the next state in response to a specific event. For example, the server 503 (e.g., the server 108) may wait for a TCP connection establishment request from the client 501 (e.g., the electronic device 101) in a LISTEN state 505. The client 501 sends a signal (e.g., a syn packet) requesting a connection setting to the server 503 in a state of a connection setting request (SYN_SENT) 407 and sends a connection setting request to the server 503 ). For example, the client 501 may wait for an acknowledgment (e.g., syn + ack packet) of the server 503 to the connection establishment request. The server 503 can maintain the LISTEN state 505 until receiving a signal (e.g., a syn packet) requesting connection establishment from the client 501. [ When the server 503 receives the signal requesting connection establishment, the server 503 can change the state to the connection setting request reception (SYN_RECEIVED) 509 state. The server 503 transmits a signal including an acknowledgment (e.g., syn + ack packet) to the connection setting request to the client 501 in the state of receiving a connection setting request (SYN_RECEIVED) 509, You can wait for an acknowledgment. The client 501 can change an acknowledgment (e.g., syn + ack packet) to a connection establishment (ESTABLISHED) 511 state for the connection setting request from the server 503. [ The client 501 may send an acknowledgment (e. G., Ack packet) to the server 503 about the connection establishment in the ESTABLISHED state 511 and the server 503 may send an acknowledgment The connection setting state 511 can be obtained. In the connection setting state, the client 501 can open the connection and send and receive data to the server 503. [ In various embodiments, the connection establishment state may refer to a normal state in which data may be sent to the client 501 (e.g., electronic device 101). The client 501 may transmit a connection release signal (e.g., a fin packet) to the server 503 in the first connection release state (FIN_WAIT_1) 513. [ After transmitting the connection release signal, the client 501 may wait for an acknowledgment of the connection cancellation signal or may wait for an acknowledgment for the connection cancellation request previously transmitted from the server 503. [ When the server 503 receives a connection release signal (e.g., a fin packet), it can be changed to a connection release wait state (CLOSE_WAIT) 515. The server 503 can transmit an acknowledgment (e.g., ack packet) to the client 501 about the connection release signal received from the client 501. [ Here, the client 501 may include a local user. Although not shown in FIG. 5, a state in which the client 501 waits for an acknowledgment of the connection release signal from the server 503 may be defined as a CLOSING state. The client 501 may change to the second connection release state (FIN_WAIT_2) 517 when receiving an acknowledgment for the connection release signal from the server 503. [ The server 503 may send a signal (e.g., a fin packet) indicating the release of the connection of the server 503 to the client 501 and wait for an acknowledgment thereof in the final acknowledgment (LAST_ACK) 519 state . The client 501 can be changed to the TIME_WAIT state 521 when receiving a signal indicating a connection release (e.g., a fin packet). The client 501 may send an acknowledgment signal (e.g., ack packet) to the server 503 indicating that the server 503 is disconnected, in the state of time wait (TIME_WAIT) 521. [ In addition, the client 501 may wait a sufficient time to confirm that the server 503 has received an acknowledgment for the request to disconnect the connection. In various embodiments, the client 501 may maintain a time wait state for a maximum segment lifetime (e.g., about 1 minute to 4 minutes). The server 503 can be changed to the connection end (CLOSED) 523 state when receiving an acknowledgment for the connection release from the client 501. [ In the CLOSED state, there may not be a connection between the client and the server. In various embodiments, since the TCP is a protocol involving an acknowledgment, the electronic device may classify the state of the TCP socket described above into a temporary state and a permanent state. In various embodiments, the electronic device 101 may view the state of a TCP socket that is waiting for an acknowledgment from a remote device (e.g., server 108) as a transient state. For example, a connection establishment request 507 state, a first connection release 513 state, a closing state, and a final acknowledgment 519 state may be viewed as a temporary state. In various embodiments, the electronic device 101 may view the transient state of the TCP socket states in a permanent state. The electronic device 101 can identify the various TCP socket states described above and can determine the communication state based thereon.

6 illustrates an example of the interface of the electronic device 101 displayed on the electronic device 101 when the communication status according to various embodiments of the present invention is a block status. The interface of the electronic device 101 may include a display device 160. 6, in various embodiments, the message of the SNS application may not be transmitted by the network firewall, even though the Wi-Fi signal quality is good and the status of the backhaul network is good. In various embodiments, the electronic device 101 may display various message transfer indicators on the display device 160 indicating the message transfer status of the messenger application. For example, in FIG. 6, the first message transmission indicator 604 indicates a normally transmitted message and the second message transmission indicator 606 is not normally transmitted, indicating a pending message. The Wi-Fi status indicator 602 indicates that the quality of the Wi-Fi signal is good, so that it may be difficult for the user to grasp the cause of the undelivered message. The electronic device 101 may use the TCP socket state to detect such block state.

In one embodiment, the processor 120 may determine that the number of received packets increases as the number of connection setting sockets increases. In one embodiment, the processor 120 may determine the communication state of the electronic device 101 to be in a good state when the TCP socket state is changed. In one embodiment, the processor 120 may determine that the communication state of the electronic device 101 is insufficient if the TCP socket state stuck in a certain state.

In various embodiments, a red flag technique may be used to indicate a particular problem condition that has occurred in the network. For example, the electronic device may accumulate a red flag whenever a particular problem condition is detected. The electronic device can identify the transport protocol status by analyzing cumulative red flags (CRFs). Red flag accumulation can be defined as shown in FIGS. 7A and 7B.

Figure 7A shows a flow diagram illustrating a red flag accumulation in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 7A is a part of operation 401 of FIG. 4, and the operating entity of the illustrated flowchart 710 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

In various embodiments, the processor 120 may use an accumulation-red flag scheme to detect problems in the signal in the network. In various embodiments, the processor 120 may view the red flag as an identifier indicating a problem and accumulate it by recording a red flag each time a problem is encountered. This approach can be expressed in a cumulative red flag fashion.

Referring to FIG. 7A, at operation 701, the processor 120 may determine whether a new retransmission is detected. For example, the processor 120 can check if a TCP socket undergoing retransmission is detected. The processor 120 may accumulate a red flag when a new retransmission is detected.

At operation 703, the processor 120 may determine whether a new final acknowledgment is detected. For example, the processor 120 may determine whether a TCP socket state is newly detected in the final acknowledgment state. Processor 120 may accumulate a red flag if a new final acknowledgment is detected.

At operation 705, the processor 120 may determine whether a new disconnect signal is detected. For example, the processor 120 can check whether or not the TCP socket state is newly detected as a disconnected state. The processor 120 may accumulate a red flag when a new disconnect signal is detected.

At operation 707, the processor 120 may verify that an acknowledgment for the connection establishment request has not been detected. For example, the processor 120 can determine whether there is no acknowledgment of the server when the TCP socket state is in the connection establishment request state. Processor 120 may accumulate a red flag if an acknowledgment for a connection establishment request is not detected.

At operation 709, the processor 120 may determine whether a new connection establishment request is detected and a new connection establishment socket is not detected. For example, the processor 120 can check whether a TCP socket state is newly detected as a connection establishment request, and a connection establishment socket is not newly detected. The processor 120 may accumulate a red flag when a new connection establishment request is detected and a new connection setting socket is not detected.

At operation 711, the processor 120 may accumulate a red flag. According to various embodiments, the processor 120 may determine that a new retransmission is detected, a new final acknowledgment is detected, a new disconnect signal is detected, an acknowledgment for a connection setup request is not detected, Or when a new connection setting request is detected and a new connection setting socket is not detected, at least one condition is satisfied, the red flag can be accumulated. In various embodiments, the results of operations 701 through 709 may not affect each other. For example, at operation 701, if processor 120 detects a new retransmission, it may accumulate a red flag at operation 711, regardless of whether a new final acknowledgment has been detected or a new disconnect signal has been detected. In various embodiments, the processor 120 may perform operations 701 through 709 sequentially, or may perform each operation separately, regardless of the order.

Figure 7B shows a flow diagram illustrating a red flag accumulation in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 7A is a part of operation 401 of FIG. 4, and the operating entity of the illustrated flowchart 710 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to FIG. 7B, at operation 713, the processor 120 may determine if the transmitted packet is greater than the received packet, a new connection configured socket is detected, and the sum of the received and transmitted packets is less than the threshold. If the above condition is met, at operation 723, the processor 120 may accumulate the Red flag.

At operation 715, the processor 120 may determine that a new de-coupled signal is detected, a new retransmission is detected, and the transmitted packet is below a threshold. For example, the threshold may be 10 packets. If a new de-connection signal is detected, a new retransmission is detected, and the transmitted packet is below the threshold, at operation 723, the processor 120 may accumulate the Red flag.

At operation 717, the processor 120 may determine if the RSSI is below a threshold. For example, the processor 120 may determine if the RSSI is below a certain threshold. Processor 120 may accumulate a red flag at operation 723 if the RSSI is below a certain threshold.

At act 719, the processor 120 may determine if the link speed is below a threshold. For example, the processor 120 may determine if the network link speed of the electronic device 101 is below a certain threshold. The processor 120 may accumulate the Red flag at operation 723 if the network link speed is below the threshold.

At operation 721, the processor 120 may determine if the loss exceeds a threshold. For example, the processor 120 may determine whether the loss in data transmission and reception exceeds a certain threshold. The processor 120 may accumulate the red flag at operation 723 if the loss exceeds the threshold.

At operation 723, the processor 120 may accumulate a red flag. According to various embodiments, processor 120 may detect a new de-coupling signal when a transmission packet is greater than a received packet, a new connection setting socket is detected, and the sum of received and transmitted packets is less than a threshold, And when the transmission packet is less than the threshold, when the RSSI is less than the threshold, when the link speed is less than the threshold, or when the loss exceeds the threshold, the red flag is accumulated . In various embodiments, the results of operations 713 through 721 may not affect each other. For example, at operation 713, if the transmitted packet is greater than the received packet, a new connection set socket is detected, and the sum of the received packet and transmitted packet is less than the threshold, then the RSSI is less than the threshold, The red flag can be accumulated in operation 723. [ In various embodiments, the processor 120 may perform operations 713 through 721 sequentially, or may perform each operation separately, regardless of the order.

In various embodiments, the processor 120 may notify the user that the network state is in an insufficient state, and may change the network based thereon if the red flag is accumulated and exceeds a specified threshold.

As described with reference to Figures 4 to 7B, an electronic device according to various embodiments of the present invention can determine the communication state based on the state of a TCP socket. According to one embodiment, the communication state can be determined to be any one of a good state, a short state, a block state, and a sluggish state. Hereinafter, more detailed embodiments for determining each communication state will be described.

Figure 8 shows a flow chart for determining a good state in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 8 is a part of operation 403 of FIG. 4, the operating entity of the illustrated flowchart 800 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

8, at operation 801, the processor 120 may detect a socket for a new connection establishment. In various embodiments, the processor 120 may newly detect sockets for client and server connection establishment. After socket detection for connection establishment, the processor 120 may identify a change in the following TCP socket state. For example, for various reasons, the TCP socket state may be stuck in the aforementioned transient state. Processor 120 may track the state of the TCP socket to escape from this trapped state.

At operation 803, the processor 120 can determine whether the connection establishment request state has been changed to the connection establishment state. For example, after the processor 120 transmits and receives an acknowledgment to the server, the processor 120 can check whether the TCP socket state of the client has been changed from the connection establishment request state to the connection establishment state. The processor 120 may determine the communication state of the electronic device 101 to be in a good state at operation 709 if the TCP socket state is changed to the connection establishment state.

At operation 805, the processor 120 may determine if the sum of transmitted and received packets exceeds a threshold. For example, when the TCP socket state is not changed to the connection establishment state, the processor 120 can determine whether the sum of the transmission packet and the reception packet exceeds the threshold. For example, the processor 120 may compare the sum of a transmission data packet that the electronic device 101 transmits to the external device and a reception data packet that the electronic device 101 receives from the external device with a specific threshold value. The processor 120 may determine the communication state of the electronic device 101 to be in a good state if the sum of the transmitted packet and the received packet exceeds a certain threshold.

At operation 807, the processor 120 may determine whether a new connection release wait state and a new time wait state are detected. For example, when the sum of the transmission packet and the reception packet is smaller than a specific threshold, the processor 120 can check whether a new connection release waiting state and a new time waiting state are detected. For example, the processor 120 can detect a connection release waiting state and a time waiting state when a network is normally connected and a packet can be normally received. The processor 120 may determine the communication state of the electronic device 101 to be in a good state when a new connection release waiting state and a time waiting state are detected. If a new connection release waiting state and a time waiting state are not detected, the processor 120 may again perform an operation of detecting a new connection setting socket.

At operation 809, the processor 120 may determine the communication state to be in a good state. For example, the processor 120 may determine the communication state of the electronic device 101 to be in a good state when the conditions in the operations 701 to 707 are satisfied, respectively. In various embodiments, the good state may mean that the user does not experience any problems in performing the communication. In various embodiments, processor 120 may determine which TCP socket state is good among a plurality of TCP socket states and update a list of TCP socket states that are in good state to prevent unnecessary retransmission (updated). For example, the processor 120 may update the socket list with the name "goodAreaSYN" if the connection establishment request status is in a good state. Processor 120 may update the list of sockets named "goodAreaRetrans" if retransmission occurs in the good state. Processor 120 may update the list of sockets named "goodAreaFin" if the first disconnected state is in a good state. Processor 120 may update the socket list with the name "goodAreaLastAck" if the final acknowledgment is in a good state. Processor 120 may update the list of sockets named "goodAreaClosing" if the closed state is in a good state. Through the above-described operation, the processor 120 can determine the communication state of the electronic device 101 as a good state.

In various embodiments, the processor 120 detects a TCP socket for connection establishment, identifies whether the state of the detected TCP socket changes from a connection establishment request state to a connection establishment state, Identifies whether the sum of the transmission data packet and the reception data packet of the executed application is larger than a threshold value, identifies whether the TCP socket state is a connection release waiting state or a time waiting state, detects a TCP socket for connection establishment , When the state of the TCP socket is changed from the connection setting request state to the connection setting state and the sum of the transmission data packet and the reception data packet is larger than the threshold and the connection release waiting state and the time waiting state are identified, Can be determined as a good state.

Figure 9 shows a flowchart for determining a poor state in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 9 is a part of operation 403 of FIG. 4, and the operating entity of the illustrated flowchart 900 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

9, at operation 901, the processor 120 of the electronic device 101 can determine whether the communication state is in a good state. For example, the processor 120 can determine whether the communication state of the electronic device 101 is in the good state described above with reference to FIG. 8, before determining whether the communication state is in a state of insufficient. Here, the good state may include a case where the sum of the transmission packet and the reception packet is larger than the threshold value. The processor 120 may perform the following operations 903 through 909 if the communication state is not in a good state.

At operation 903, the processor 120 may determine whether a socket for new connection establishment is detected. In various embodiments, the processor 120 may newly detect a socket for establishing a connection between a client (e.g., electronic device 101) and a server (e.g., server 108). The processor 120 may determine the communication state of the electronic device 101 to be in a deficient state when a socket for establishing a connection is newly detected.

At operation 905, the processor 120 may determine whether a new connection establishment request status is detected. For example, if a socket for a new connection establishment is not detected, the processor 120 can check whether a new connection establishment request status is detected. For example, the processor 120 may determine that the communication state of the electronic device 101 is in a deficient state when a socket for establishing a connection is not newly detected, and a new connection establishment request state is detected.

At operation 907, the processor 120 may determine whether the difference between the number of transmitted packets and the number of received packets exceeds a threshold value. For example, the processor 120 may determine if the difference between the number of transmitted data packets and the number of received data packets exceeds a certain threshold value, if no new connection establishment request status is detected. For example, if the processor 120 determines that the communication state is not a good state at operation 901, no socket for new connection establishment is detected at operation 903, no new connection establishment request state is detected at operation 905, When the difference between the number of received data packets and the number of received data packets exceeds the threshold value, the communication state of the electronic device 101 can be determined to be in a deficient state. If the difference between the number of transmitted packets and the number of received packets does not exceed the threshold value, the processor 120 may again perform the operation of determining whether the communication state is good. Operations 903 to 907 are independent operations, and the processor 120 can perform each operation sequentially, or in any order.

At operation 909, the processor 120 may determine the communication state to be in a deficient state. For example, when the processor 120 satisfies the conditions in the operations 903 through 907, respectively, the processor 120 can determine the communication status of the electronic device 101 to be in a deficient state through the above-described operations.

In various embodiments, the processor 120 identifies whether the communication state of the electronic device 101 is in a good state, detects a TCP socket for connection establishment, and determines whether the state of the TCP socket is a connection establishment request state And identifies whether or not the number of transmission data packets of the application executed in the electronic device 101 is larger than the number of received data packets. If the communication state of the electronic device 101 is not in the good state, If the socket is detected, the connection establishment request status is identified, and the number of transmission data packets is greater than the number of reception data packets, the communication status of the electronic device 101 can be determined to be in a deficient state.

Figure 10 shows a flow diagram for determining a blocked state in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 10 is a part of operation 403 of FIG. 4, wherein the operating entity of the illustrated flowchart 1000 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to FIG. 10, at operation 1001, the processor 120 may detect a socket that performs retransmission. For example, the processor 120 may detect a socket that performs retransmission. In various embodiments, as the number of detected sockets increases, the number of send queues may increase.

At operation 1003, the processor 120 may determine whether the number of transmitted and received packets is less than a threshold. For example, the processor 120 may determine whether the number of transmitted packets and received packets is less than a threshold value during the time that TCP is timeout. The timeout of the TCP allows the electronic device 101 to send data to external electronic devices (e.g., server 108, electronic device 104), then set a timer, And may not be able to receive a response. In one embodiment, the processor 120 may determine whether the number of data packets transmitted and received by the application is less than a threshold, even if the Wi-Fi network environment is good. The processor 120 may perform an operation of detecting a socket that performs retransmission again when the number of transmission packets and received packets is not less than the threshold value.

At operation 1005, the processor 120 may determine whether the link speed, signal to noise ratio (SNR), or RSSI, respectively, exceeds a specified threshold. For example, if the number of transmitted and received packets is less than the threshold, the processor 120 may compare the link speed, SNR, or RSSI to a specified threshold, respectively, to determine if the application exceeds the threshold, even if the application is blocked by the network firewall. have. The processor 120 may perform an operation of detecting a socket that performs retransmission again if the link speed, SNR, or RSSI does not exceed the specified threshold, respectively.

At operation 1007, the processor 120 may determine the communication state as a block state. For example, the processor 120 may determine the communication state to a block state if the link speed, SNR, or RSSI exceeds a specified threshold and the number of transmitted and received packets is less than a threshold. Operations 1001 to 1005 are independent operations, and the processor 120 can perform each operation sequentially, or in any order. In various embodiments, the block status may be that the relevant application is blocked by the firewall. In various embodiments, the processor 120 may maintain a transmit (e.g., outgoing, send or transmit) data queue in terms of kernel memory usage by the socket. If the size of the transmission data queue increases as the number of sockets subject to retransmission increases, the wireless connection between the electronic device 101 and a Wi-Fi access point (AP) may be considered to be good. Although the wireless connection state is good, the processor 120 may determine that a particular application is blocked by a firewall if the application has fewer transmit and receive data packets. Through the operations described above, the processor 120 can determine the communication state of the electronic device 101 as a block state.

In various embodiments, the processor 120 detects a TCP socket that performs retransmission, identifies whether the number of transmit data packets and receive data packets of the application running on the electronic device 101 is less than a threshold, It is possible to identify whether the link speed, SNR (signal) and received signal strength indication (RSSI) of the electronic device 101 are greater than a threshold value, to identify a TCP socket for retransmission, If the number of packets is smaller than the threshold, and the link speed, SNR and RSSI are larger than the threshold value, the communication state of the electronic device 101 can be determined as a block state. In one embodiment, the block state may include a state in which an application running in the electronic device 101 is blocked by a network firewall.

Figure 11 shows a flow chart for determining a sluggish state in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 11 is part of operation 403 of Fig. 4, and the operating entity of the illustrated flowchart 1100 can be understood as an electronic device 101 or a component of electronic device 101 (e.g., processor 120).

Referring to FIG. 11, at operation 1101, the processor 120 may detect a socket for a new connection establishment. In various embodiments, the processor 120 may newly detect a socket for establishing a connection between a client (e.g., electronic device 101) and a server (e.g., server 108).

At operation 1103, the processor 120 may determine whether a new connection establishment request status is detected. For example, when the processor 120 newly detects a socket for establishing a connection, it can check whether or not a new connection establishment request status is detected. If a new connection establishment request status is not detected, the processor 120 may again perform the operation of detecting a socket for new connection establishment.

At operation 1105, processor 120 may determine if the sum of transmitted and received packets is less than a threshold. For example, the processor 120 may determine if the sum of the transmit data packet and the receive data packet is less than a threshold value when a new connection establishment request status is detected. In one embodiment, processor 120 may determine if the sum of transmit and receive packets is less than a threshold during the time that TCP is timed out. If the sum of the transmitted and received packets is not less than a certain threshold, the processor 120 may again detect a socket for new connection establishment. Operations 1101 to 1105 are independent operations, and the processor 120 can perform each operation sequentially, or in any order.

At operation 1107, the processor 120 may determine the communication state to be in a sluggish state. For example, the processor 120 may determine that the communication state of the electronic device 101 is in a sluggish state when a new connection establishment request state is detected and the sum of the transmission packet and the reception packet is less than the threshold. In various embodiments, a stuck state may mean that a particular application is slowing down of data due to WiFi access point policies. Through the operations described above, the processor 120 may determine the communication state of the electronic device to be in a sluggish state.

In various embodiments, the processor 120 detects a TCP socket for connection establishment, identifies whether the state of the TCP socket is a new connection establishment request state, and determines whether the transmission data packet of the application running on the electronic device 101 And when the sum of the transmission data packet and the reception data packet is smaller than the threshold value, the connection establishment request status is identified, The communication state of the electronic device 101 can be determined as a sluggish state.

12 illustrates a flow diagram for identifying a communication state and changing a network in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. The operating entity of the illustrated flowchart 1200 may be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to FIG. 12, in operation 1201, the processor 120 may identify the transport protocol state. For example, a pattern of sockets may be identified based on contexts according to radio link characteristics. In various embodiments, the pattern of sockets may be a pattern of TCP socket states. For example, the TCP socket state may include connection setup request transmission (SYN_SENT), connection setup (ESTABLISHED), and connection release (FIN_WAIT). The processor 120 may identify that the TCP socket state is changed to the above-described states.

At operation 1203, the processor 120 may detect a wireless connection state. For example, the wireless connection state may include at least one of RSSI, link speed, loss, or SNR. The processor 120 can detect the communication state using the wireless connection state detected together with the TCP socket state identified above. For example, the communication state may include a good state, a short state, a block state, and a sluggish state.

At operation 1205, the processor 120 may determine whether the communication state is in an insufficient state. For example, the processor 120 may indicate a bad Wi-Fi signal quality. In various embodiments, the TCP socket state pattern may be such that if the new connection release state increases and the number of received packets is small, the new connection establishment request state increases and the number of received packets is small, The state may increase and the number of received packets may be small, the new final acknowledgment state may increase, the number of received packets may be small, or the number of received packets may be small and the number of retransmissions may increase. If the communication state is found to be in an insufficient state, the processor 120 may perform a network change at operation 1211. [

At operation 1207, the processor 120 may determine whether the communication state is block state. For example, the processor 120 can check whether the communication state is in a block state or not, if the communication state is not in an insufficient state. For example, the block state may indicate that a particular application is blocked by a network firewall, although the quality of the Wi-Fi signal is good. In various embodiments, in the block state, the electronic device 101 may have good RSSI and link speed. In the block state, at the network layer level, an application may have TCP sockets with a small number of connection establishment states. These sockets may undergo retransmissions, and the transmitted packets may be trapped in a transmission queue. In various embodiments, in the block state, many connection establishment request socket states may not change to the connection establishment state. If the communication state is a block state, at operation 1211, the processor 120 may perform a network change.

In operation 1209, the processor 120 may determine whether the communication state is in a sluggish state. For example, the processor 120 can check whether the communication state is in the non-block state or not, if the communication state is not the block state. In various embodiments, the electronic device 101 may have good RSSI and link speeds in the wireless network if it is in a low state. In the low state, the socket in the connection setting state increases, but the number of data packets received by the application may be small. In this case, the sockets of the application may not perform retransmission. If not, the processor 120 may again identify the transfer protocol state and, although not shown in the figure, the processor 120 may determine the communication state to be in a good state. In various embodiments, in the good state, the new connection establishment socket may increase and the number of received packets may be less. If it is in the good state, the new connection release waiting state is increased and the new connection release state may not be displayed. In various embodiments, in the good state, the TCP socket state may be changed from a connection establishment request state to a connection establishment state.

For operation 1211, the processor 120 may perform a network change. For example, the processor 120 may perform a network change if the communication state is in a poor state. For example, the processor 120 may control the communication module 180 to change the network from the Wi-Fi network to the cellular network. However, the network change is not limited to this, and it is possible to change to various kinds of networks in the current network. Through the operations described above, the processor 120 can identify the TCP socket state, determine the communication state, and perform the network change based on the determined communication state. The above-described operations 1205 to 1209 are independent operations, and the processor 120 can perform each operation sequentially, or in any order.

13 shows a flow diagram of an electronic device for monitoring the status of a transport layer protocol in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. The operating entity of the illustrated flowchart 1300 may be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to FIG. 13, at operation 1301, the processor 120 may monitor the transport protocol status. In various embodiments, the transport protocol may comprise TCP. Processor 120 may analyze the TCP socket state. For example, the processor 120 may identify patterns in which the TCP socket state is changing and may also analyze physical channel characteristics such as the number of transmitted and received packets, RSSI, link rate, or loss, The communication state can be determined. In various embodiments, the communication state may include a good state, a low state, a block state, and a sluggish state. The processor 120 may monitor the TCP socket state described above to determine the communication state of the electronic device 101. [

In operation 1303, the processor 120 may indicate the communication status. For example, the processor 120 may display on the display device 160 of the electronic device 101 the previously determined communication status. In one embodiment, the processor 120 may indicate to the display device 160 that there is a problem with the network connection of the application currently operating on the electronic device 101. For example, referring to FIG. 14, the processor 120 of the electronic device 101 displays a screen including a dialog window 1401-1 in which a user exchanges messages with another user via an application, to the display device 160 Can be controlled. For example, when the processor 120 transmits and receives messages to and from the external electronic device 102 via an SNS application such as a KakaoTalk, Watts app, Facebook, or Messenger, the processor 120 transmits the transmitted and received messages to the electronic device 101. [ On the display device 160 of the display device. In the case where a message is exchanged with another user through the above-described SNS application, the interface of the electronic device 101 includes a message dialog window 1403-1 and a pop-up window 1403-3 indicating that the application is experiencing a failure in accessing the Internet And the processor 120 may control the display device 160 to display a screen including the interface. In one embodiment, the processor 120 controls to display on the display device 160 of the electronic device 101 that an application is having trouble transmitting and receiving data packets when a particular application is blocked by a network firewall . For example, referring to FIG. 14, the processor 120 of the electronic device 101 may generate a pop-up window 1405- < Desc / Clms Page number 8 > indicating whether to change the network from the current network to the cellular network, 1) and an indicator 1405-3 that allows the user to select whether or not to change the network by referring to the contents of the pop-up window on the display device 160. [ For example, the electronic device 101 may display on the display device 160 of the electronic device 101 whether to change the network to the LTE, LTE-A or 5G network in the Wi-Fi network. Thereby, by changing the network, the processor 120 can smoothly operate the application. In one embodiment, the interface of electronic device 101 may include a pop-up window 1407 indicating that an application is experiencing an Internet access failure on an SSID (service set identifier), and processor 120 may include an interface It is possible to control the display device 160 to display the screen. The SSID may represent the wireless network name, and Wi-Fi devices such as a notebook or a smart phone may attempt wireless connection through SSID classification. In one embodiment, the pop-up window 1409 indicating that the application is experiencing a failure to access the Internet may at least partially overlap the interface of the existing electronic device 101, and the processor 120 may display a screen including the nested interface So that it can be displayed on the display device 160.

In various embodiments, the electronic device 101 may display a pop-up window indicating that the application is having a failure in accessing the Internet, as described above, as well as indicating the communication status and network change determined through monitoring. For example, the processor 120 may control to display the communication status on the display device 160 when the current communication status is in the low status, the block status, and the low status, and may include an indication that the user can select the network change It is possible to control the display device 160 to display a pop-up window.

In various embodiments, the processor 120 may control to display the communication status of the electronic device 101 on the display device 160 and may provide information about the network change based on the communication status of the electronic device 101 It is possible to control the display device 101 to display a message including the message. The instructions stored in the memory 130 of the electronic device 101 cause the processor 120 to display the communication status of the electronic device 101 on the display device 160, And display a message on the display device 160 including information on the network change.

In various embodiments, the processor 120 may use the socket ID and IP address to identify the TCP socket state. For example, a socket ID may include an INODE number, and an IP address may include a source and destination address, a universally unique identifier (UUID). In various embodiments, the processor 120 may maintain a list of good states to avoid false alarms on communication conditions. This allows the processor 120 to identify that some of the sockets are stuck in a particular state.

In various embodiments, the processor 120 can identify a TCP socket state by generating a TCP socket state list. For example, as shown in Table 1, the processor 120 may generate a TCP socket state list using a socket ID or an IP address.

Referring to Table 1, the processor 120 can generate a connection setting state list, a connection setting request state list, a retransmission list, and a connection release waiting state list by using a socket ID, A status list, a final acknowledgment status list, a closing status list, and a time waiting status list. For example, the processor 120 may generate a connection establishment status list using a socket ID. Processor 120 may check the socket for new connection establishment in the previous and current states. In various embodiments, the processor 120 may generate a connection establishment request status list using a socket ID. For example, when the previous and current communication states are good, the processor 120 can check whether the TCP socket state is a new connection establishment request state or whether there is an acknowledgment to the connection establishment request. In various embodiments, the processor 120 may generate a retransmission list using a socket ID. For example, the processor 120 can verify that the application is performing a new retransmission if the current communication state is in a good state. In various embodiments, the processor 120 may generate a connection release wait state list using a socket ID. For example, if the current communication state is in a good state, the processor 120 can check whether the TCP socket state is a new connection release standby state.

In various embodiments, the processor 120 may use the IP address to identify the TCP socket state. For example, the processor 120 may generate a new disconnected state list using the IP address. For example, when the current communication state is in a good state, the processor 120 can check whether the TCP socket state is a new connection release state using the IP address. In various embodiments, the processor 120 may use the IP address to generate a final acknowledgment status list. For example, the processor 120 may check if the TCP socket state remains in the final acknowledgment state if the current communication state is in a good state. In various embodiments, the processor 120 may use the IP address to generate a closing state list. For example, the processor 120 can check if the TCP socket state remains in the closed state if the current communication state is in a good state. In various embodiments, the processor 120 may use the IP address to generate a time waiting status list. For example, the processor 120 may check whether the TCP socket state is a new time-awaiting state in the previous and current state. Through the operations described above, the processor 120 can update the list of TCP socket states when in the good state, using the socket ID or the IP address.

As described above, the processor 120 can identify the state of the transfer protocol of the electronic device 101 using the ID and IP address of the TCP socket. For example, the processor 120 can determine the communication state of the electronic device 101 by identifying the state of the TCP socket corresponding to each MAC address and IP address. For example, as shown in Table 2, the processor 120 can detect the TCP socket state of the electronic device 101 while performing communication via a specific application. For example, the processor 120 can determine the communication state of the electronic device 101 by identifying the state of the TCP socket corresponding to each MAC address and IP address. For example, as shown in Table 2, the processor 120 can detect the TCP socket state of the electronic device 101 while performing communication via a specific application.

Referring to Table 2, the processor 120 can detect the TCP socket state according to each MAC address and IP address. The processor 120 may determine the communication state of the electronic device 101 by identifying the detected TCP socket state. For example, the processor 120 may detect the TCP socket state of the electronic device 101 when data transmission / reception through the AAA to EEE application is completed (e.g., when video streaming is completed). In this case, the processor 120 determines that the communication state of the electronic device 101 is in a good state by identifying that the TCP socket state of the electronic device 101 is a persistent TCP socket state such as a sensing state and a number of connection establishment states .

In one embodiment, the processor 120 may detect the TCP socket state of the electronic device 101 while communicating through a particular application, as shown in Table 3.

Referring to Table 3, the processor 120 can detect the TCP socket state according to each MAC address and IP address. The processor 120 may determine the communication state of the electronic device 101 by identifying the detected TCP socket state. For example, the processor 120 can detect the TCP socket state of the electronic device 101 when data transmission / reception through the AAA to GGG application is completed (e.g., when video streaming is completed). In this case, the processor 120 can determine the communication state of the electronic device 101 to be in a good state by identifying that the TCP socket state of the electronic device 101 has been changed from the plurality of connection setting states to the connection release waiting states.

In one embodiment, the processor 120 may detect the TCP socket state of the electronic device 101 during communication through a particular application, as shown in Table 4.

Referring to Table 4, the processor 120 can detect the TCP socket state according to each MAC address and IP address. The processor 120 may determine the communication state of the electronic device 101 by identifying the detected TCP socket state. For example, the processor 120 may detect the TCP socket state of the electronic device 101 when data transmission / reception through the AAA to EEE application is completed (e.g., when message transmission is completed). In this case, the processor 120 can determine that the communication state of the electronic device 101 is in the block state by identifying that the TCP socket state of the electronic device 101 is only the connection setting state and the first connection release state.

In one embodiment, the processor 120 may detect the TCP socket state of the electronic device 101 while communicating through a particular application, as shown in Table 5.

Referring to Table 5, the processor 120 can detect the TCP socket state according to each MAC address and IP address. The processor 120 may determine the communication state of the electronic device 101 by identifying the detected TCP socket state. For example, the processor 120 may detect the TCP socket state of the electronic device 101 when data transmission / reception through the AAA to EEE application is completed. In this case, the processor 120 determines that the communication state of the electronic device 101 is in a short state by identifying that the TCP socket state of the electronic device 101 is a connection setting state, a connection release waiting state, and a first connection release state .

In one embodiment, the processor 120 may detect information including a retransmission counter of the electronic device 101 while communicating through a particular application, as shown in Table 6.

Referring to Table 6, the processor 120 may detect a local IP address, a remote IP address, a socket status, a transmission queue, a reception queue, a timer, and a retransmission counter for each line number. Processor 120 may determine the communication state of the electronic device by identifying the detected transmission queue value and the retransmission counter value. For example, the processor 120 may determine that the first transmission queue value is 0, the second transmission queue value is a non-zero value, and that the line number 2 corresponds to the transport layer. Processor 120 may check the retransmission counter value. For example, the processor 120 may identify that the first retransmission counter value is 0, while the second retransmission counter value is a non-zero value. The processor 120 can determine that the communication state of the electronic device 101 is in the block state by identifying that the retransmission counter value is a non-zero value.

15A illustrates an example of an interface of an electronic device displayed in an electronic device when the communication status is in a block status according to various embodiments of the present invention. The electronic device in the following description may include all or a portion (e.g., processor 120 and display device 160) of the electronic device 101 of FIG.

Referring to FIG. 15A, the processor 120 may detect that the chat application is blocked by the network firewall by identifying the TCP socket state of the chat application. In various embodiments, the processor 120 may use the socket ID and IP address to identify the TCP socket state. The processor 120 can control the display device 160 to display a first indicator 1501 and a second indicator 1503 indicating that the message transmission is not properly performed when the application is blocked by the network firewall have. For example, the processor 120 may identify when the number of connection setting sockets 1505 of the chat application is less than a certain threshold, and when the retransmission count 1507 is not zero. Through this, the processor 120 can view the chat application as blocked by the network firewall and determine the communication state of the electronic device 101 as a block state.

Figure 15B illustrates an example of an interface of an electronic device displayed on an electronic device when the communication state is in a good state according to various embodiments of the present invention. The electronic device in the following description may include all or a portion (e.g., processor 120 and display device 160) of the electronic device 101 of FIG.

Referring to FIG. 15B, the processor 120 can detect that the chat application is not blocked or delayed by the network firewall by identifying the TCP socket state of the chat application. In various embodiments, the processor 120 may use the socket ID and IP address to identify the TCP socket state. The processor 120 may control the display device 160 to display an indicator 1509 indicating that the message transmission is successful if the application is not blocked or delayed by the network firewall. For example, the processor 120 may identify when the number of connection setting sockets 1511 of the chat application is greater than a threshold, and when the number of retransmission counts 1513 is zero. Through this, the processor 120 can determine that the chat application is not blocked by the network firewall and that the message transmission is smooth. That is, the processor 120 can determine the communication state of the electronic device 101 as a good state.

As described above, the electronic device and its method of operation according to various embodiments identify a transmission protocol state, i.e., a TCP socket state, and determine, based on the identified TCP socket state, that the communication state of the electronic device 101 is good Can be determined to be one of a state, a shortage state, a block state, and a sluggish state, and an optimal network environment can be provided to the user by changing the network based on the determined communication state.

Generally, Wi-Fi wireless network technology indicates that an electronic device communicates through at least one external communication providing device (e.g., an AP). Apart from the strength of the signal that the electronic device receives from the external communication provision device, there may be a substantial Internet connection. The actual Internet connection described above may refer to a connection between an external communication providing device and the Internet (e.g., a cloud), and such a connection may be referred to as a backhaul connection.

In a wireless network technology such as Wi-Fi, a socket can be used as a unit for performing communication. In most data transmission implementations, a socket may be an endpoint that connects communications between a plurality of entities performing communication, i.e., start and end. Currently, the TCP socket method is also used in hypertext transfer protocol (HTTP), file transfer protocol (FTP), and QUIC (quick UDP internet connections). A large number of sockets can be opened and closed to send and receive one communication message (e.g., one emoticon sent via the messenger application). The above-described sockets can be formed or destroyed through a certain period (step), respectively, and can exist in a specific state in each step. FIG. 16, which will be described later, shows a sequence diagram illustrating a process of changing a socket state when a TCP socket is created and destroyed.

FIG. 16 illustrates a sequence diagram 1600 illustrating a state change of a transport protocol socket in accordance with various embodiments of the present invention.

16, the TCP socket state of a client (e.g., client 501 in FIG. 5) and a server (e.g., server 503 in FIG. 5) according to various embodiments may be changed to a different state can be changed. In FIG. 16, the dotted arrow 1601 may indicate a normal transition to the client 501, and the line arrow 1602 indicates a normal translation to the server 503 Quot; appl "1603 may mean a state change when an application is running," recv "1604 may mean a state change when a segment is received, quot; and " send "1605 may mean that they are transmitted in the conversion.

 In various embodiments, the changing step may start in the CLOSED state 1610. The application may be in a passive open state in event 1611 and the TCP socket state may be detected in the connection termination state 1610 (LISTEN) 1612) state. In the event 1613, the application may be in an active open state, and a signal (e.g., a SYN packet) requesting connection establishment from the client 501 to the server 503 is transmitted, State 1610 to the connection establishment request (SYN_SENT) 1616 state. The connection establishment request 1616 state may indicate active opening. When the server 503 receives a signal (e.g., a SYN packet) requesting a connection setting from the client 501 in the event 1615, the server 503 transmits a connection setting request (SYN_RCVD) The socket state is changed and the server 503 can send an acknowledgment (e.g., SYN, ACK packet) to the client 501 for the connection probe request. At event 1617 the server 503 may receive a signal requesting connection establishment from the client 501 and the server 503 may send an acknowledgment for the connection establishment request to the client 501. [ At event 1619, the application may be in a close or timeout state. In the event 1621, when the server 503 receives an ACK packet from the client 501, the TCP socket state can be changed from the connection setting request reception state 1614 state to the connection setting state 1618, 503 may not transmit anything to the client 501. [ In the event 1623, when the client 501 receives the SYN, ACK packet from the server 503, the TCP socket state can be changed from the connection setting request 1616 state to the connection setting 1618 state, The base station 501 can transmit an ACK packet to the server 503. [ At event 1625, the application may be in a blocked state and the client 501 may send a connection release signal (e.g., a FIN packet) to the server 503. At event 1627, the application may be in a blocked state and the client 501 may send a disconnect signal to the server 503. In event 1629, when the server 503 receives the FIN packet, the TCP socket state can be changed from the connection setting state 1618 to the connection release wait state (CLOSE_WAIT) 1620, and the server 503 The client 501 can transmit an ACK packet. In one embodiment, the connection release wait 1620 state may refer to a passive close state. In the event 1631, when the client 501 receives the FIN packet from the server 503, the TCP socket state is changed from the first connection release FIN_WAIT_1 1622 state to the CLOSING 1624 state And the client 501 can send an ACK packet to the server 503. [ At event 1633, the application may be in a blocked state and the server 503 may send a FIN packet to the client 501. [ In event 1635, when the client 501 receives an ACK packet from the server 503, the TCP socket state changes from the first connection release 1622 state to the second connection release (FIN_WAIT_2) 1628 state And the client 501 may not transmit anything to the server 503. In event 1637, if the client receives a FIN, ACK packet, the TCP socket state may be changed from the first connection release 1622 state to the TIME_WAIT 1630 state, The server 503 can transmit an ACK packet. In event 1639, when the client 501 receives an ACK packet from the server 503, the TCP socket state may be changed from the closing 1624 state to the time waiting 1630 state, The server 503 may not transmit anything. At event 1641, if the client 501 receives an ACK packet from the server 503, the last acknowledgment (LAST_ACK) 1626 state may be changed to the disconnected state 1610, May not send anything to the server 503. As described above, various information about the electronic device 101 can be obtained by using all the steps from generation to extinction at least once in the course of performing TCP communication. For example, by analyzing the count of active sockets among all active sockets, information about the backhaul connection state or connection quality can be obtained.

In general, the quality of the Wi-Fi channel and the way backhaul connections are checked on a regular basis can be used to determine if there is a Wi-Fi backhaul connection. The above-described checking method is not applied flexibly according to the current communication state, but can be used periodically when the number of transmission packets and received packets is small, or when the RSSI is weak, every designated time. In the case where the backhaul connection confirmation is performed only when the above conditions are satisfied, when the number of transmission packets and reception packets is small due to deterioration of the network conditions and when the user does not use the electronic device and the number of transmission packets and reception packets Small cases may not be distinguished. The transmission packet and the reception packet are changed only when the user is actively using the Internet. In the case of back-ground traffic or when the user does not use the electronic device for a while, Detecting changes can be difficult. When the backhaul connection confirmation is performed only when the number of transmission packets and reception packets is small, the transmission quality and the reception quality are good, but it may be difficult to detect the situation where the Internet is not operated due to the backhaul connection problem. When the quality of the Wi-Fi connection is low, features of the physical link layer can be used to identify the backhaul connection. Even if the transmission / reception quality of the signal is not good, the Internet can operate in the electronic device due to the reflected signal, and even if the signal quality from the communication providing device (e.g. AP) is good, Can occur. If the user is located close to an AP that provides Wi-Fi, i.e., if the quality of the signal is good and there is a problem with the backhaul connection, then the usual way to verify the backhaul connection described above is to connect the backhaul connection The backhaul connection failure detection can be delayed. Various embodiments of the present invention can more quickly detect a backhaul failure using a transport protocol socket (e.g., TCP socket) state count if the electronic device fails to connect to the backhaul. In various embodiments, when a backhaul failure is detected, the electronic device may provide an interface for change to another AP or cellular communication. Through this, the user experience of performing communication can be improved. In various embodiments, when a backhaul failure is detected, the electronic device may display the detected backhaul failure status on the display device, or may automatically change to another network without displaying it. In various embodiments, the electronic device may provide the user with an option for network automatic change upon backhaul failure. In various embodiments, the electronic device performs the backhaul connection test only in situations where there is a high probability that there will be a problem with the backhaul, thereby reducing unnecessary operations and enhancing battery efficiency. 17 to 32, which will be described later, explain that the electronic device determines the backhaul failure by checking at least one of the state of the transmission protocol and the count of the transmission protocol, and performs control for the backhaul failure.

Figure 17 illustrates a flow diagram 1700 of an electronic device that determines a backhaul failure based on at least one of a state of a transport protocol and a count of a transport protocol in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 17 is part of operation 301 of FIG. 3, and operation 1705 of FIG. 17 is part of operation 303 of FIG. 3, and the operation subject of the illustrated flowchart 1700 is electronic device 101 or electronic May be understood as a component of the device 101 (e.g., processor 120).

17, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may verify at least one of a state of a transport protocol and a count of a transport protocol at operation 1701. [ For example, the processor 120 may determine a socket count, a retransmission segment or a reception segment of a TCP socket corresponding to a total socket count and connection establishment state of a transport protocol (i.e., TCP).

According to various embodiments, the processor 120 may determine, at act 1703, a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol. In one embodiment, the processor 120 may determine a backhaul failure if the total socket count of the transport protocol is increased but the socket count corresponding to the connection establishment state does not increase. In one embodiment, the processor 120 may determine a backhaul failure if there are insufficient received or transmitted packets and the retransmission segment of the transmission protocol increases. In one embodiment, the processor 120 may determine a backhaul failure if there are insufficient received or transmitted packets and a received segment error in the transport protocol is identified. In one embodiment, the processor 120 can determine a backhaul failure in the situation where the interface as shown in Fig. 18 is displayed. In one embodiment, the indicator 1802 indicating the Wi-Fi signal strength on the display (e.g., display 160 of FIG. 1) of the electronic device 101 may indicate that the Wi-Fi signal strength is good . For example, if one or more of the four steps displayed by the indicator 1802 indicating the Wi-Fi signal strength is activated and displayed, the Wi-Fi signal strength can be regarded as good. For example, The indicator 1802 indicating the strength of the Wi-Fi signal can indicate that all the four stages are activated. In one embodiment, if the indicator 1802 indicating the Wi-Fi signal strength indicates good Wi-Fi signal strength, but the indicators 1804 through 1808 indicating a message transmission failure are displayed, Recognizing that there is a problem with the backhaul connection, you can determine the backhaul failure.

According to various embodiments, the processor 120 may, at operation 1705, perform control over the backhaul failure based on the determined backhaul failure. For example, the processor 120 may display a backhaul failure on the display 160 of the electronic device 101 and display a network change indicator so that the user can change the network. In various embodiments, the network change indicator may include indicators for changing the network for communication to another AP or cellular network. In various embodiments, the processor 120 may share information about determined backhaul failures with external electronics in determining a backhaul failure. 19 to 24, which will be described later, show a flow chart of the electronic device 101 for determining a backhaul failure and an example thereof.

19 illustrates a flow diagram 1900 of an electronic device that determines a backhaul failure based on a total count of connection and a connection establishment count in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 19 is part of operation 1701 of Fig. 17, and operation 1903 of Fig. 19 is part of operation 1703 of Fig. 17, and the operation subject of the illustrated flowchart 1900 is electronic device 101 or electronic device 101 (E. G., Processor 120). ≪ / RTI >

Referring to FIG. 19, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may determine at 1901 that an increase in the total socket count of the transport protocol and a maintenance or reduction of the connection establishment count have. In one embodiment, the processor 120 can see that the total number of TCP socket counts is increased, but the socket counts folded into the connection establishment state do not increase. For example, the above-described state may indicate a state in which a socket for which a backhaul connection is disconnected from an arbitrary point and a connection set state is decreased, and packets to be transmitted by the application are accumulated. In one embodiment, the state of the transport protocol is as shown in FIG. The graph 2000 of FIG. 20 is a polling cycle for the horizontal axis and a TCP socket count 2002 for the vertical axis. For example, processor 120 may see that while the polling cycle is in progress, the count of the new connection setup 2006 does not increase and the count of the new connection setup request 2008 increases. For example, in Fig. 20, the count of the new connection establishment request 2008 may be fixed at 0 and may not increase. The processor 120 increments the count of the new connection establishment request 2008 from 0 to 2 at the moment the polling cycle 2004 goes from 1 to 2, i.e., the polling cycle 2004 goes from 1 to 2 , The count of the new connection establishment request 2008 is increased from 0 to 3 and the polling cycle 2004 is changed from 7 to 9, that is, at the moment the polling cycle 2004 is shifted from 7 to 9, The count of the new connection establishment request 2008 is increased from 0 to 1 at the moment the polling cycle 2004 is shifted from 11 to 12, that is, the polling cycle 2004 is shifted from 11 to 12, It can be seen that the count of the new connection establishment request 2008 increases from 0 to 2 when the polling cycle 2004 is 13 to 15, that is, the polling cycle 2004 is shifted from 13 to 15. Due to an increase in the count of the connection establishment request 2008, the total socket count of the transmission protocol can increase.

According to various embodiments, the processor 120 may, at operation 1903, determine a backhaul failure based on the acknowledgment results. For example, as shown in FIG. 20, the processor 120 increases the total number of TCP socket counts by increasing the number of new connection setting request counts, confirms that the socket count of the connection setting state does not increase, It can be determined that a failure has occurred. In one embodiment, the processor 120 may determine a backhaul failure by comparing the difference between the total number of TCP socket counts and the socket count of the connection establishment state to a threshold value. For example, the processor 120 may determine that the state in which a response (e.g., syn packet) is not received continues beyond the threshold time, or if the difference between the total number of TCP socket counts and the socket count of the connection establishment state exceeds the threshold A large, backhaul failure can be determined if this condition persists for a critical period of time.

21 shows a flow diagram 2100 of an electronic device for determining a backhaul failure based on a retransmission state of a transmission protocol according to various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 17 is a part of operation 1701 of Fig. 17, and operation 2103 of Fig. 21 is part of operation 1703 of Fig. 17, and the operation subject of the illustrated flowchart 2100 is electronic device 101 or electronic device 101 (E. G., Processor 120). ≪ / RTI >

21, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, can confirm, at operation 2101, the lack of received or transmitted packets and an increase in the retransmission segment of the transmitted protocol . For example, if the number of packets to be received and the number of packets to be transmitted decrease, that is, in a deteriorated transmission and reception environment, the processor 120 can confirm that the number of failed packets increases. In one embodiment, the state of the transport protocol is as shown in FIG. The graph 2200 of FIG. 22A shows a polling cycle 2204 for the horizontal axis and a count 2202 for the vertical axis. For example, during the polling cycle, the processor 120 may determine that the count of the transmission protocol transmission packet 2206 and the transmission protocol reception packet 2208 is low while the count of the transmission protocol retransmission segment 2210 is high have. For example, in FIG. 22A, the processor 120 determines whether the polling cycle 2204 is 4 to 5, that is, the polling cycle 2204 moves from 4 to 5, , The count of the transmission protocol reception packet 2208 is decreased from 2 to 0, and the transmission protocol retransmission segment 2210 is maintained at 1. [ According to the above-described confirmation result, the processor 120 can confirm that the count of the transmission protocol transmission packet 2206 is relatively low while the count of the transmission protocol retransmission segment 2210 is relatively high.

According to various embodiments, the processor 120 may, at operation 2103, determine a backhaul failure based on the acknowledgment result. For example, the processor 120 can ascertain the increase in the retransmission segment of the transmission protocol and determine the backhaul failure as time elapses, as in Fig. 22B. Eg., At time T _0, the client may transmit the data to: (a server 503 of FIG. 5) (2251-1 to 2251-4) (such as client 501 of Figure 5) Server . In one embodiment, the client 501 fails to transmit the data 3 2251-3 and can retransmit the data 3 (2251-4). The server 503 can receive data from the client 501 and send the acknowledgments 2253-1 through 2253-3 to the client 501. [ The count and segment of the TCP socket at T _{0 are shown} in Table 7 below.

Referring to Table 7, the total socket count of the TCP socket is 15, the connection setting count is 10, the in-segment error count is 18, the retransmission count is 17, and the transmitted segments are 1000. According to one embodiment, at time T ₁ , the client 501 fails to transmit data 1 2255-1 to server 503 and may retransmit data 1 2255-2 through 2255-4 . The count and segment of the TCP socket in T _{1 are shown} in Table 8 below.

Referring to Table 8, the processor 120 can confirm that the retransmission count is increased from 17 to 19 while the time is changed from T ₀ to T ₁ . The processor 120 can confirm that the retransmission count has increased and determine the backhaul failure as described above.

23 shows a flow diagram 2300 of an electronic device for determining a backhaul failure based on a reception error of a transmission protocol according to various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 23 is part of operation 1701 of Fig. 17, and operation 2303 of Fig. 23 is part of operation 1703 of Fig. 17, and the operation subject of the illustrated flowchart 2300 is electronic device 101 or electronic device 101 (E. G., Processor 120). ≪ / RTI >

23, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, can check at operation 2301 the lack of received or transmitted packets and errors in the received segments of the transmitted protocol . For example, processor 120 may ascertain an increase in received segment error in a degraded transmission and reception environment. In one embodiment, the state of the transport protocol is as shown in Figure 24A. 24A is a polling cycle 2404, and the ordinate axis is a count 2402. In FIG. For example, during the polling cycle, the processor 120 may determine that the count of the transmission protocol transmission packet 2406 and the count of the transmission protocol reception packet 2408 are low and that the reception segment error of the transmission protocol 2410 ) Is increased. For example, in FIG. 24A, the processor 120 determines if the polling cycle 2404 is 3 to 4, that is, when the polling cycle 2404 is shifting from 3 to 4, the receive segment error 2410 ) Increases from 0 to 2 and the polling cycle 2404 goes from 6 to 7, i.e., at the moment the polling cycle 2404 goes from 6 to 7, the receive segment error 2410 1, and the transmission protocol reception packet 2408 is maintained at 2 while the polling cycle 2404 is from 4 to 7. [ According to the above-described confirmation result, the processor 120 can confirm that the count of the transmission protocol reception packet 2408 is relatively low, but the count of the reception segment error 2410 of the transmission protocol is relatively high.

According to various embodiments, the processor 120 may determine, at operation 2303, a backhaul failure based on the acknowledgment result. For example, the processor 120 may determine an increase in the in-segment error of the transmission protocol and determine a backhaul failure as time elapses, as shown in Fig. 24B. For example, at time T _0, the server (such as server (503 in FIG. 5)) is a client: the data (such as client 501 in Fig. 5) (2451-1 to 2451-3), to be transmitted have. In one embodiment, the server 503 fails to transmit the data 2 2451-3 and may retransmit the data 2 (2451-3). The client 501 can receive data from the server 503 and send the acknowledgments 2453-1 and 2453-2 to the server 503. [ The count and segment of the TCP socket at T _{0 are shown} in Table 9 below.

Referring to Table 9, the total socket count of the TCP socket is 15, the connection setting count is 10, the in-segment error count is 18, the retransmission count is 17, and the received segments are 1000. According to one embodiment, at time T ₁ , the server 503 sends data 1 2455-1 to the client 501 and the client 501 sends an acknowledgment 2457-1 Can be transmitted. In one embodiment, the server 503 tries to transmit data 2 (2455-2 through 2455-3), but the client 501 may fail to receive data 2. The count and segment of TCP socket in T _{1 are shown} in Table 10 below.

Referring to Table 10, the processor 120 determines that the in-segment error count is increased from 18 to 20, and the received segment is increased from 1000 to 1002, because the client 501 does not receive data from the server 503. [ . Processor 120 may determine that the received segment error count has increased and determine a backhaul failure, as described above. 25 to 31 show various control operations that the electronic device 101 performs in order to cope with a backhaul failure when it determines a backhaul failure.

25 shows a flow diagram 2500 of an electronic device for indicating a backhaul failure and a network change indicator in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 25 is a part of operation 1705 of Fig. 17, and the operating entity of the illustrated flowchart 2500 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., the processor 120).

Referring to FIG. 25, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may indicate a backhaul failure at operation 2501. For example, the processor 120 may indicate a backhaul failure determined through the status and count of the transfer protocol to a display device (e.g., the display device 160 of FIG. 1) of the electronic device 101. In various embodiments, an indication of a backhaul failure may include a message indicating that the Internet connection of the electronic device 101 is broken.

According to various embodiments, the processor 120 may, at operation 2503, display a network change indicator. For example, the processor 120 may display on the display device 160 a message indicating whether the Wi-Fi network is changed to a cellular network and at least one or more indicators that the network can be changed by the user's selection. Examples in which a backhaul failure and a network change indicator are displayed on the display device 160 of the electronic device 101 will be described with reference to Figs. 26 to 28 to be described later.

26 illustrates an example interface 2600 of an electronic device for indicating a network change indicator in a backhaul failure according to various embodiments of the present invention.

Referring to FIG. 26, the processor 120 may display on the display device 160 an interface 2602 that displays a network change indicator in case of a backhaul failure. For example, the interface 2602 includes an indicator 2604 including a message indicating that the Internet connection is disconnected due to a backhaul failure, a notification 2604 indicating whether or not the WiFi network is changed to the cellular network, A first change indicator 2608 in which a network change is not performed through a user's input and a second change indicator 2610 in which a network change is performed through a user's input have. The user may switch to the cellular network from the Wi-Fi network after detecting the backhaul failure by selecting and entering the second change indicator 2610. [

FIG. 27 illustrates an example interface 2700 of an electronic device that indicates a change to another access point (AP) upon a backhaul failure in accordance with various embodiments of the present invention.

Referring to FIG. 27, the processor 120 may display on the display device 160 an interface 2710 indicating an indicator indicating a change to another AP upon a backhaul failure. For example, the interface 2710 may include an indicator 2712 that includes a message indicating that the Internet connection has been lost due to a backhaul failure, an indicator 2714 that includes a message asking whether to connect to another AP because the Wi- A first change indicator 2716 in which the network change is not performed through the input of the user, and a second change indicator 2718 in which the network change is performed through the input of the user. The electronic device 101 may guide the user through the user interface to change from the AP currently connected to the user to another AP located nearby. In one embodiment, the processor 120 may direct the user to change to another AP by displaying the address of the other APs on the interface 2720 in case of a backhaul failure. For example, the interface 2720 may include an indicator 2722 indicating an AP change, an indicator 2724 including a message to guide a change to another AP, addresses 2726-1 through 2726-6 of other APs, . ≪ / RTI > In one embodiment, other APs recommended for the user may include APs with good network quality (e.g., the backhaul network is operating normally). If the user selects one of the addresses 2726-1 through 2726-6 of the other APs on the interface 2720, the processor 120 may attempt to connect to the AP having the corresponding address. In one embodiment, interface 2720 may also include an indicator (not shown) indicating the address of the external device to which to send information about the backhaul failure. The external apparatus to which information on the backhaul failure may be transmitted may include an external apparatus identified in FIG. 29 to be described later.

28 illustrates an example of an interface 2800 of an electronic device that optionally presents a network change indicator upon backhaul failure according to various embodiments of the present invention.

Referring to FIG. 28, the processor 120 may optionally generate an operation to automatically change the network when the backhaul fails, and provide the generated information to the user. In one embodiment, the interface 2802 may include a network automatic change indicator 2804 including a change indicator 2806, a message to guide automatic network change upon occurrence of a backhaul failure. When the change indicator 2806 is activated through the user's input, if the processor 120 detects a backhaul failure, the network can be automatically changed without displaying a separate notification window. For example, when a backhaul failure occurs, the processor 120 may change from a currently connected WiFi network to a cellular network or to another WiFi network that is frequently used. If the change indicator 2806 is deactivated, the processor 120 may not automatically perform the network change even if a backhaul failure occurs. 29 to 31, which will be described later, illustrate the operation of the electronic device 101 to share a backhaul failure with other electronic devices in case of a backhaul failure, or to provide a service according to a backhaul failure.

29 shows a flow diagram 2900 of an electronic device sharing a backhaul failure with other electronic devices in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 29 is a part of operation 1705 of Fig. 17, and the operating entity of the illustrated flowchart 2900 can be understood as an electronic device 101 or a component of electronic device 101 (e.g., processor 120).

29, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may identify an external device to which to send information about a backhaul failure, at operation 2901. For example, the external device may be an AP connected to the electronic device 101, may be devices included in the same network, may be devices registered on a common account basis, or may be irrelevant devices. In one embodiment, devices registered on a common account basis may be devices belonging to one IoT cloud account. In one embodiment, the external device that will send information about the backhaul failure may be electronic devices that communicate using a NAN (neighbor awareness network). In one embodiment, information about an external device to send information about a backhaul failure can be managed in the server. For example, by identifying an external device to which the server will send information about a backhaul failure and sending information (e.g., address) about the external device identified by the electronic device 101, Information about the backhaul failure can be transmitted to the device.

According to various embodiments, at operation 2903, the processor 120 may send information about a backhaul failure to an identified external device. In one embodiment, electronic device 101 may send information about a backhaul failure to other devices connected to the same AP, such as example 3010 of Figure 30A. For example, the electronic device 101 may detect a backhaul failure and send information about the detected backhaul to the electronic device 3014-1 connected to the AP 3001 connected to the electronic device 101 have. Although not shown, an electronic device 3014-1 that has received information about a backhaul failure from the electronic device 101 may share information about backhaul failures with other electronic devices 3014-2 to 3014-6 . In one embodiment, the electronic device 101 may send information about a backhaul failure to an AP 3001 that is coupled to the electronic device 101, such as the example 3020 of FIG. 30B. For example, after the AP 3001 connected to the electronic device 101 receives information on the backhaul failure, the AP 3001 transmits information about the received backhaul failure to another (3026) to the electronic devices 3024-1 through 3024-4. 30A and 30B, the electronic device 101 may share a backhaul failure with devices connected to the same AP. In one embodiment, the processor 101 may share information about backhaul failures with external electronic devices through a non-connection based information sharing scheme using NAN.

31 shows a flow diagram 3100 of an electronic device that stores and provides information related to backhaul failures in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 31 is part of operation 1705 of Fig. 17, and the operating entity of the illustrated flowchart 3100 can be understood as an electronic device 101 or a component of electronic device 101 (e.g., processor 120).

31, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may store information related to a backhaul failure upon occurrence of a backhaul failure, For example, whenever a backhaul failure occurs, the processor 120 generates information (e.g., name, security) related to the AP where the backhaul has occurred, geofence information using the AP, signal quality information Information of the devices existing in the vicinity of the backhaul failure (e.g., device name, signal strength of each device, location information of the device, etc.), and how many times the backhaul failure occurred. In one embodiment, the processor 120 may use stored information to sense locations where backhaul failures frequently occur, APs, and the like.

According to various embodiments, at operation 3103, the processor 120 may use the information associated with the stored backhaul failure to control the display device. For example, the processor 120 may use information associated with stored backhaul failures to detect locations, APs, and the like where backhaul failures frequently occur, : An indicator indicating a warning may be displayed on the display device 160 of Fig. 1), or an AP where a backhaul failure frequently occurs may be displayed in a subordinate order in the connectable AP list.

32 shows a flow diagram 3200 of an electronic device for checking backhaul failures and performing control over backhaul failures in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. The operating entity of the illustrated flowchart 3200 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

32, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may obtain transport protocol related information at operation 3201. [ For example, the transmission protocol related information may include at least one of a total number of TCP socket counts, a socket count of a connection establishment state, a number of received and transmitted packets, a retransmission segment count of a TCP socket, or a received segment count of a TCP socket . ≪ / RTI >

According to various embodiments, at operation 3203, the processor 120 may determine whether the connection establishment count of the transport protocol is increased. For example, the processor 120 can check whether the connection setting count indicating the connection setting state among the states of the TCP socket increases with the passage of time. If the connection establishment count of the transport protocol increases, the processor 120 may again perform operations to obtain transport protocol related information. If the connection establishment count of the transport protocol does not increase, the processor 120 may perform operation 3205. [

According to various embodiments, at operation 3205, the processor 120 may determine whether a received packet or a transmitted packet is good. In various embodiments, a good received packet or a transmitted packet may indicate that there is no shortage of received or transmitted packets. For example, the processor 120 may determine that the received packet or the transmitted packet no longer increases, or that the increasing trend is gentle, over time, and may determine that the received packet or the transmitted packet is insufficient. If the received packet or the transmitted packet is good, that is, if the received packet or the transmitted packet is not insufficient, the processor 120 may perform the operation of acquiring the transfer protocol related information again. If the received packet or the transmitted packet is not good, that is, the received packet or the transmitted packet is insufficient, the processor 120 may perform the operation 3207. [

According to various embodiments, at operation 3207, the processor 120 may determine whether the total count of the transport protocol is increased. For example, the processor 120 may determine whether the total number of TCP socket counts is increasing based on the acquired transmission protocol related information. In one embodiment, the processor 120 can determine whether the total number of TCP socket counts increases over time. If the total count of the transport protocol increases, the processor 120 may perform an operation 3213, and if the total count of the transport protocol does not increase, the processor 120 may perform an operation 3209. [

According to various embodiments, at operation 3209, the processor 120 may determine whether the retransmission segment count of the transport protocol is increased. For example, the processor 120 may perform retransmission of failed data if it fails to transmit data to the server (e.g., server 503 of FIG. 5) due to the quality of the degraded transmitted and received packets, The increase of the retransmission segment count of the transmission protocol due to the retransmission performance can be confirmed. If the retransmission segment count of the transport protocol increases, the processor 120 may perform an operation 3213. If the retransmission segment count of the transport protocol does not increase, the processor 120 may perform an operation 3211.

According to various embodiments, at operation 3211, the processor 120 may determine whether the received segment error of the transport protocol is reduced. In one embodiment, the processor 120 may verify that the receive segment error of the transport protocol increases if the data from the server 503 fails to be received due to the quality of the degraded send and receive packets. If the receive segment error of the transport protocol decreases, i. E. The receive segment error of the transport protocol does not increase, the processor 120 may again obtain the transport protocol related information. If the receive segment error of the transport protocol does not decrease, i. E. The receive segment error of the transport protocol increases, the processor 120 may perform an operation 3213.

According to various embodiments, at operation 3213, the processor 120 may check for a backhaul failure. For example, the processor 120 may check for a backhaul failure and determine a backhaul failure if the total count of the transport protocol is increased but the connection protocol count of the transport protocol does not increase. The processor 120 checks for a lack of a received packet or a transmission packet of the transmission protocol, and when the retransmission segment count of the transmission protocol increases or when an increase in the reception segment error of the transmission protocol is confirmed and the backhaul failure is checked, You can decide.

According to various embodiments, at operation 3215, the processor 120 may perform control for a backhaul failure. For example, the processor 120 may determine a backhaul failure and provide a network change (e.g., a display change) to the display device of the electronic device 101 Indicator can be displayed. In one embodiment, the processor 120 alerts the user of a backhaul failure by sharing information about the backhaul failure with the identified external device, storing information about the backhaul failure, and displaying information about the stored backhaul failure on the display device can do. 33 to 39, which will be described later, describe a concrete implementation operation of the electronic device 101 for checking the state of the backhaul.

33 shows a flow diagram 330 of an electronic device illustrating an implementation for examining a backhaul condition in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. The operating entity of the illustrated flowchart 3300 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to FIG. 33, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may obtain thresholds at operation 3301. For example, the thresholds may include received signal strength, backhaul connection checking, received segments, and thresholds associated with the transmitting segment.

According to various embodiments, the processor 120 may check, at operation 3303, a new connection establishment state or time waiting state. For example, processor 120 may check for an increase in the connection set count of the TCP socket and check for a new connection establishment state. Processor 120 may check for an increase in the time wait state count of the TCP socket and check for a new time wait state.

According to various embodiments, the processor 120 may check for an in-segment error at operation 3305. For example, the processor 120 can confirm that a segment error occurs due to poor reception quality due to lack of received packets.

According to various embodiments, the processor 120 may check retransmission, at operation 3307. For example, the processor 120 may verify that retransmission occurs due to poor transmission quality due to lack of transmission packets.

According to various embodiments, the processor 120 may check the backhaul at operation 3309. [ For example, the processor 120 may check an AP connected to the electronic device 101 and a backhaul indicating that the Internet is connected.

According to various embodiments, the processor 120 may update the count at an operation 3311. For example, the processor 120 may set the previous TCP connection setup count to the current TCP connection setup count, the previous time wait count to the time wait count, the previous TCP usage count to the TCP usage count, The count may be updated to the retransmission segment count, the previous in-segment error count may be updated to the in-segment error count, the previous in-segment count may be in in-segment count, and the previous out-segment count may be updated in out-segment count.

34 illustrates a flow diagram 3400 of an electronic device for obtaining a threshold according to various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 34 is a part of operation 3301 of FIG. 33, and the operating entity of the illustrated flowchart 3400 may be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

Referring to Figure 34, an electronic device (e.g., processor 120 of Figure 1), in accordance with various embodiments, may obtain a plurality of thresholds at operation 3401. For example, the plurality of threshold values RSSI_POOR_SIGNAL_THRESHOLD = -83, RSSI_LOW_SIGNAL_THRESHOLD = -70, THRESHOLD BACKHAUL_CONNECTIVITY_CHECK_HIGH = 5, THRESHOLD BACKHAUL_CONNECTIVITY_CHECK_LOW = 2, THRESHOLD BACKHAUL_CONNECTIVITY_CHECK_POOR = 2, TCP_POOR_SEG_RX = 0, THRESHOLD_TCP_POOR_SEG_RX_TX = 15, THRESHOLD_WAITING_CYCLE_CHECK_HIGH = 5, THRESHOLD_WAITING_CYCLE_CHECK_HIGH = 3, THRESHOLD_WAITING_CYCLE_CHECK_POOR = 2, and THRESHOLD_MAX_WAITING_CYCLE = 60.

According to various embodiments, the processor 120 may obtain an RSSI threshold value at operation 3403. For example, processor 120 may obtain a threshold value for RSSI by comparing the current RSSI to a threshold value.

According to various embodiments, processor 120 may obtain a plurality of counts at operation 3405. For example, the plurality of counts may include a current TCP connection setting count (currTcpEstablishedCount), a retransmission segment count (retransSegCount), an inSegErrorCount, an inSegCount, an outSegCount, a TCP usage count TcpInUseCount), an orphanCount, and a time wait count (timeWaitCount). In one embodiment, the current TCP connection setup count may indicate the number of TCP connections for which the current state is a connection establishment state. In one embodiment, the in-segment count may indicate the total number of segments received including the segments received in error. This count may include segments received on the current connection established connection. In one embodiment, the out segment count may comprise the total number of segments transmitted including the currently connected segments. These counts can exclude retransmitted sockets. In one embodiment, the retransmission segment count may comprise the total number of retransmitted segments. This count may indicate the number of transmitted TCP sockets including one or more previously transmitted sockets. In one embodiment, the in-segment error count may indicate the total number of segments received in error (e.g., bad TCP checksums). In one embodiment, the TCP usage count may indicate the total number of TCP sockets, and the hop count may indicate sockets without inodes, except for the time wait state, Sockets can be represented.

According to various embodiments, processor 120 may set a count at operation 3407. [ For example, the processor 120 may set the TCP usage count as the difference between the TCP usage count and the odd count, and may set the in-segment count difference diffInSegCount to the difference between the in-segment count and the previous in-segment count , The difference of the out segment count (diffOutSegCount) can be set as the difference between the out segment count and the previous out segment count, and the difference in the in-segment error count (diffInSegErrorCount) can be set to the difference between the in-segment error count and the previous segment error count And can set the difference in the retransmission segment count (diffRetransSegCount) to the difference between the retransmission segment count and the previous retransmission segment count.

35 shows a flow diagram 3500 of an electronic device for obtaining a received signal strength indication (RSSI) threshold according to various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 35 is part of operation 3403 of FIG. 34, and the operating entity of the illustrated flowchart 3500 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

35, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may obtain the current RSSI value at operation 3501. [

According to various embodiments, processor 120 may check at operation 3503 whether the current RSSI value is equal to or greater than RSSI_LOW_SIGNAL_THRESHOLD. If the current RSSI value is equal to or greater than RSSI_LOW_SIGNAL_THRESHOLD, the processor 120 may perform operation 3505, and if the current RSSI value is not equal to or greater than RSSI_LOW_SIGNAL_THRESHOLD, the processor 120 may perform operation 3507. [

According to various embodiments, the processor 120 may set the internet connection counter threshold to THRESHOLD_BACKHAUL_CONNECTIVITY_CHECK_HIGH and the wait cycle threshold to THRESHOLD_WAITING_CHECK_HIGH, at operation 3505.

According to various embodiments, processor 120 may verify at operation 3507 that the current RSSI value is greater than RSSI_POOR_SIGNAL_THRESHOLD and less than RSSI_LOW_SIGNAL_THRESHOLD. If the current RSSI value is greater than RSSI_POOR_SIGNAL_THRESHOLD and less than RSSI_LOW_SIGNAL_THRESHOLD, processor 120 may perform operation 3509 and processor 120 may perform operation 3511 if the current RSSI value is not greater than RSSI_POOR_SIGNAL_THRESHOLD and not less than RSSI_LOW_SIGNAL_THRESHOLD.

According to various embodiments, the processor 120 may set the Internet connection counter threshold to THRESHOLD_BACKHAUL_CONNECTIVITY_CHECK_LOWH and the wait cycle threshold to THRESHOLD_WAITING_CHECK_LOW, at operation 3509.

According to various embodiments, the processor 120 may set the Internet Connection Counter Threshold to THRESHOLD_BACKHAUL_CONNECTIVITY_CHECK_POOR and the Wait Cycle Threshold to THRESHOLD_WAITING_CHECK_POOR, at operation 3511.

36 shows a flow diagram 3600 of an electronic device for checking a new connection establishment state and a time waiting state in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 36 is part of operation 3303 of FIG. 33, and the operating entity of the illustrated flowchart 3600 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

36, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may verify at operation 3601 that the current TCP connection setting count is greater than the previous TCP connection setting count. Processor 120 may perform operation 3607 if the current TCP connection setup count exceeds the previous TCP connection setup count and may perform operation 3603 if the current TCP connection setup count does not exceed the previous TCP connection setup count have.

According to various embodiments, processor 120 may, at operation 3603, determine whether the time wait count is greater than the previous time wait count. Processor 120 may perform operation 3609 if the time wait count exceeds the previous time wait count, and may perform operation 3605 if the time wait count does not exceed the previous time wait count.

According to various embodiments, processor 120 may check at operation 3605 whether the TCP usage count is greater than the previous TCP usage count. Processor 120 may perform operation 3611 if the TCP usage count exceeds the old TCP usage count and may perform operation 3617 if the TCP usage count does not exceed the previous TCP usage count.

According to various embodiments, the processor 120 may set the in-error segment wait cycle to zero and the retransmit segment wait cycle to zero, at operation 3607. [

According to various embodiments, the processor 120 may determine at operation 3609 whether the wait cycle threshold is greater than THRESHOLD_WAITING_CYCLE_CHECK_POOR. Processor 120 may perform operation 3613 if the wait cycle threshold is greater than THRESHOLD_WAITING_CYCLE_CHECK_POOR and may perform operation 3605 if the wait cycle threshold does not exceed THRESHOLD_WAITING_CYCLE_CHECK_POOR.

According to various embodiments, the processor 120 may set the Internet connection counter to a value obtained by subtracting the old TCP usage count from the Internet connection counter and the TCP usage count at operation 3611. [

According to various embodiments, the processor 120 may set the Internet Connection Counter to 0 and the Internet Connection Wait Cycle to 0, at operation 3613.

According to various embodiments, the processor 120 may increase the internet connection counter at an operation 3615.

According to various embodiments, processor 120 may, at act 3617, determine whether the Internet connection counter is greater than zero. If the Internet connection counter exceeds zero, the processor 120 may perform an operation 3615 and terminate the step if the Internet connection counter does not exceed zero.

Figure 37 shows a flow diagram 3700 of an electronic device for inspecting in-segment and out-segment errors in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. 37 is a part of operation 3305 of FIG. 33, the operating entity of the illustrated flowchart 3600 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., processor 120).

37, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, may determine at operation 3701 whether the difference in the in-segment error count is greater than zero. Processor 120 may perform operation 3703 if the difference in the in-segment error count is greater than zero, and may perform operation 3705 if the difference in in-segment error count does not exceed zero.

According to various embodiments, processor 120 may determine at operation 3703 if the sum of the difference in segment segment error count and the difference in out segment error count is less than THRESHOLD_TCP_POOR_SEG_RX_TX. The processor 120 may perform an operation 3707 if the sum of the difference in the in-segment error count and the difference in the out-segment error count is less than THRESHOLD_TCP_POOR_SEG_RX_TX, and if the sum of the difference in the in-segment error count and the difference in the out-segment error count is THRESHOLD_TCP_POOR_SEG_RX_TX If not, operation 3705 may be performed.

According to various embodiments, the processor 120 may determine at operation 3705 whether the in-error segment wait cycle is greater than zero. The processor 120 may perform an operation 3707 if the in-error segment wait cycle exceeds zero and terminate the operation if the in-error segment wait cycle does not exceed zero.

According to various embodiments, processor 120 may increase the value of the in-error segment wait cycle at operation 3707. [

 38 shows a flow diagram 3800 of an electronic device for inspecting a retransmission segment in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 38 is a part of operation 3307 of Fig. 33, and the operating entity of the illustrated flowchart 3800 can be understood as an electronic device 101 or a component of the electronic device 101 (e.g., the processor 120).

38, the electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, can confirm at operation 3801 that the difference in the retransmission segment count is greater than zero. Processor 120 may perform operation 3803 if the difference in the retransmission segment count is greater than zero and perform operation 3805 if the difference in the retransmission segment count is not greater than zero.

According to various embodiments, processor 120 may check at operation 3803 whether the difference in segment count is greater than TCP_POOR_SEG_RX. Processor 120 may perform operation 3807 if the difference in the in-segment count is greater than TCP_POOR_SEG_RX, and may perform operation 3805 if the in-segment count difference is not greater than TCP_POOR_SEG_RX.

According to various embodiments, processor 120 may determine at operation 3805 whether the retransmission segment wait cycle is greater than zero. The processor 120 may perform an operation 3807 if the retransmission segment wait cycle exceeds zero and terminate the step if the retransmit segment wait cycle does not exceed zero.

According to various embodiments, the processor 120 may increase the retransmission segment wait cycle at operation 3807. [

Figure 39 shows a flow diagram 3900 of an electronic device for checking the state of a backhaul in accordance with various embodiments of the present invention. In the following embodiments, each operation may be performed sequentially, but not necessarily sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Fig. 39 is part of operation 3309 of Fig. 33, and the operating entity of the illustrated flowchart 3900 can be understood as an electronic device 101 or a component of electronic device 101 (e.g., processor 120).

39, an electronic device (e.g., processor 120 of FIG. 1), in accordance with various embodiments, can determine, at act 3901, whether the internet connection counter exceeds the internet connection counter threshold. If the Internet connection counter exceeds the Internet connection counter threshold, the processor 120 may perform an operation 3907, and if the Internet connection counter does not exceed the Internet connection counter threshold, Can be performed.

According to various embodiments, the processor 120 may, at act 3903, determine whether the retransmission segment wait cycle exceeds the wait cycle threshold. The processor 120 may perform operation 3909 if the retransmission segment wait cycle exceeds the wait cycle threshold and may perform operation 3905 if the retransmit segment wait cycle does not exceed the wait cycle threshold.

According to various embodiments, the processor 120 may, at act 3905, determine whether the in-error segment wait cycle exceeds the wait cycle threshold. The processor 120 may perform an operation 3909 if the in-error segment wait cycle exceeds the wait-cycle threshold, and perform an operation 3911 if the in-error segment wait cycle does not exceed the wait cycle threshold have.

According to various embodiments, processor 120 may, at act 3907, determine whether the internet connection wait cycle exceeds a wait cycle threshold. Processor 120 may perform operation 3909 if the internet connection wait cycle exceeds the wait cycle threshold and may perform operation 3903 if the internet connection wait cycle does not exceed the wait cycle threshold.

According to various embodiments, the processor 120 may set the value corresponding to the backhaul to true at operation 3909. [

According to various embodiments, the processor 120 may check at operation 3911 whether the internet connection wait cycle exceeds THRESHOLD_MAX_WAITING_CYCLE. Processor 120 may perform operation 3909 if the internet connection wait cycle exceeds THRESHOLD_MAX_WAITING_CYCLE and may terminate the step if the internet connection wait cycle does not exceed THRESHOLD_MAX_WAITING_CYCLE.

 The method of operation of an electronic device (e.g., electronic device 101 of FIG. 1) according to various embodiments includes the operations of identifying a state of a transport protocol, 101), and changing the network based on the communication state.

In various embodiments, the state of the transport protocol may include a state of a transmission control protocol (TCP) socket of an application executing in the electronic device.

In various embodiments, the communication state may be determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state.

In various embodiments, the operation of determining the communication state comprises: detecting a TCP socket for connection establishment; identifying whether the state of the TCP socket is changed from a connection establishment request state to a connection establishment state; Identifying whether a sum of a transmit data packet and a receive data packet of an application executing in the electronic device is greater than a threshold; identifying whether the state of the TCP socket is a connection release waiting state and a time waiting state; , A TCP socket for connection setting is detected, the state of the TCP socket is changed from a connection setting request state to a connection setting state, the sum of the transmission data packet and the reception data packet is larger than the threshold, And when the time waiting state is identified, the communication state is determined as the good state It may include the operation.

In various embodiments, the determining of the communication state includes: identifying whether the communication state is in a good state; detecting a TCP socket for connection establishment; determining whether the state of the TCP socket is a connection establishment request Identifying whether the number of transmission data packets in an application executed in the electronic device is greater than the number of received data packets; and determining whether the communication state is not good, And determining that the communication state is the insufficient state if the TCP connection socket is detected and the connection establishment request state is identified and the number of transmission data packets is greater than the number of the reception data packets.

In various embodiments, the determining the communication state comprises: detecting a TCP socket performing retransmission; and determining whether the number of transmit data packets and receive data packets of the application running on the electronic device is less than a threshold Identifying a link speed, an SNR (signal) and a received signal strength indication (RSSI) of the electronic device that are greater than a threshold; and identifying a TCP socket performing the retransmission And determining that the communication state is in a block state if the number of the transmission data packet and the reception data packet is smaller than a threshold value and the link speed, SNR, and RSSI are larger than a threshold value.

In various embodiments, the block state may include a state in which an application running in the electronic device is blocked by a network firewall.

In various embodiments, the determining of the communication state comprises: detecting a TCP socket for connection establishment; identifying whether the state of the TCP socket is a new connection establishment request state; Identifying whether a sum of a transmit data packet and a receive data packet of an executed application is less than a threshold; detecting a TCP socket for establishing the connection; identifying the new connection establishment request status; And if the sum of the received data packets is less than the threshold, determining the communication state to be in the slack state.

In various embodiments, the state of the transport protocol may be identified using the ID and IP address of the TCP socket.

The method of operation of the electronic device 101 in various embodiments may include displaying the communication state on the electronic device and displaying a message on the electronic device based on the communication state, Operation.

The method of operation of the electronic device 101 in various embodiments may include at least one of confirming at least one of a state of the transmission protocol and a count of the transmission protocol, and at least one of a state of the identified transmission protocol and a count of the transmission protocol Determining a backhaul failure based on the determined backhaul failure, and performing an operation for controlling the backhaul failure based on the determined backhaul failure.

In various embodiments, the operation of determining a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol comprises: confirming that the total count of the transport protocol is greater than or equal to a threshold; Confirming that the connection establishment count of the transport protocol is maintained or reduced, and determining the backhaul failure based on the confirmed results.

In various embodiments, the operation of determining a backhaul failure based on at least one of the status of the identified transport protocol and the count of the transport protocol comprises: determining whether a backhaul failure is detected based on at least one of a transmission data packet and a number of received data packets Is less than or equal to a threshold value, and determining the backhaul failure based on the confirmed result.

In various embodiments, the operation of determining a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol comprises: confirming that a retransmission segment of the transport protocol is above a threshold; And determining the backhaul failure based on the identified result.

In various embodiments, the operation of determining a backhaul failure based on the state of the identified transport protocol and the count of the transport protocol comprises: confirming that an error has occurred in the received segment of the transport protocol; And determining the backhaul failure based on the backhaul failure.

In various embodiments, performing the control for the backhaul failure based on the determined backhaul failure comprises: displaying information about the backhaul failure; and generating an indicator for changing the network based on the backhaul failure And < / RTI >

In various embodiments, performing the control for the backhaul failure based on the determined backhaul failure may include: identifying an external device to which information about the backhaul failure is to be transmitted; And sending information about the failure.

The electronic device according to the various embodiments disclosed herein can be various types of devices. An electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

It should be understood that the various embodiments of the present document and the terminology used herein are not intended to limit the technical features described in this document to the specific embodiments, but to include various modifications, equivalents, or alternatives of the embodiments. In the description of the drawings, like reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly dictates otherwise. At least one of A or B, at least one of A and B, at least one of A or B, A, B or C, at least one of A, B and C, , B, or C, "may include any one of the items listed in the corresponding phrase of the phrases, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may simply be used to distinguish the component from the other component, Order). It is to be understood that any (e.g., first) component may be referred to as being "coupled" or "connected" to another (eg, second) component, with or without the term "functionally" When mentioned, it means that said component can be connected directly (e. G. By wire) to said another component, wirelessly, or via a third component.

The term "module" as used herein may include units implemented in hardware, software, or firmware, and may be used interchangeably with terms such as, for example, logic, logic blocks, components, or circuits. A module may be an integrally constructed component or a minimum unit of the component or part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

The various embodiments of the present document may include one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) readable by a machine (e.g., electronic device 101) (E. G., Program 140). ≪ / RTI > For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) may invoke and execute at least one of the stored one or more instructions from a storage medium. This enables the device to be operated to perform at least one function in accordance with the at least one command being called. The one or more instructions may include code generated by the compiler or code that may be executed by the interpreter. A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transient' means that the storage medium is a tangible device and does not include a signal (e.g., electromagnetic waves), which means that data is permanently stored in the storage medium Do not distinguish between cases where they are temporarily stored.

According to one embodiment, a method according to various embodiments disclosed herein may be provided in a computer program product. A computer program product can be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a machine readable storage medium (e.g., compact disc read only memory (CD-ROM)), or via an application store (e.g. PlayStore ^TM ) For example, smartphones), directly or online (e.g., downloaded or uploaded). In the case of on-line distribution, at least a portion of the computer program product may be temporarily stored, or temporarily created, on a storage medium readable by a machine, such as a manufacturer's server, a server of an application store, or a memory of a relay server.

According to various embodiments, each component (e.g., a module or program) of the components described above may include one or more entities. According to various embodiments, one or more of the above-described components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into one component. In such a case, the integrated component may perform one or more functions of each component of each of the plurality of components in a manner similar or similar to that performed by the corresponding one of the plurality of components prior to the integration . In accordance with various embodiments, operations performed by a module, program, or other component may be performed sequentially, in parallel, repetitively, or heuristically, or one or more of the operations may be performed in a different order, Or one or more other operations may be added.

Claims (15)

A method of operating an electronic device, Identifying a state of a transport protocol; Determining a communication state of the electronic device based on the state of the transmission protocol; And changing the network based on the communication state. The method according to claim 1, Wherein the state of the transport protocol comprises a state of a transmission control protocol (TCP) socket of an application executing in the electronic device. The method of claim 2, Wherein the communication state is determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state. The method of claim 3, Wherein the determining of the communication state comprises: Detecting a TCP socket that performs retransmission, Identifying whether the number of transmission data packets and reception data packets of an application running in the electronic device is less than a threshold; Identifying whether the link speed, SNR (signal) and received signal strength indication (RSSI) of the electronic device is greater than a threshold; Determining that the communication state is in a block state if the number of the transmission data packets and the number of the reception data packets is smaller than a threshold value and the link speed, SNR, and RSSI are greater than a threshold value; Methods of inclusion. The method according to claim 1, Displaying the communication state on the electronic device, And displaying a message on the electronic device including information about a network change based on the communication state. The method according to claim 1, Confirming at least one of a state of the transmission protocol and a count of the transmission protocol; Determining a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol; And performing control on the backhaul failure based on the determined backhaul failure. The method of claim 6, Determining a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol, Confirming that an error has occurred in the received segment of the transmission protocol; And determining the backhaul failure based on the identified result. The method of claim 6, And performing the control for the backhaul failure based on the determined backhaul failure, Identifying an external device to which to transmit information about the backhaul failure, And transmitting information about the backhaul failure to the identified external device. In an electronic device, Communication module, At least one processor, A memory operably coupled to the at least one processor, Wherein the memory, when executed, causes the at least one processor to: Identify the state of the transport protocol, Determine a communication state of the electronic device based on the state of the transmission protocol, And to change the network based on the communication state. The method of claim 9, Wherein the state of the transport protocol comprises a state of a transmission control protocol (TCP) socket of an application executing in the electronic device. The method of claim 10, Wherein the communication state is determined to be at least one of a good state, a poor state, a blocked state, and a sluggish state. The method of claim 11, Wherein the instructions cause the at least one processor to: Detects a TCP socket that performs retransmission, Identifying whether the number of transmission data packets and reception data packets of an application executed in the electronic device is smaller than a threshold, Identifying whether the link speed, SNR (signal) and received signal strength indication (RSSI) of the electronic device is greater than a threshold, A TCP socket for performing the retransmission is discarded, and if the number of transmission data packets and the number of reception data packets is smaller than a threshold value and the link speed, SNR and RSSI are larger than a threshold value, Device. The method of claim 9, Wherein the instructions cause the at least one processor to: Displaying the communication status on the electronic device, And cause the electronic device to display a message containing information on network changes based on the communication status. The method of claim 9, Wherein the instructions cause the at least one processor to: Checking at least one of a status of the transmission protocol and a count of the transmission protocol, Determining a backhaul failure based on at least one of a status of the identified transport protocol and a count of the transport protocol, And to control the backhaul failure based on the determined backhaul failure. 15. The method of claim 14, Wherein the instructions cause the at least one processor to: Confirms that an error has occurred in the received segment of the transmission protocol, And determine the backhaul failure based on the identified result.

Images