Electronic device, method, and non-transitory computer-readable storage medium for maintaining communication link in wireless environment
By resetting or delaying the LSTO timer based on CRC verification, the method addresses BLE communication link instability, enhancing stability and quality of service by preventing premature link termination.
Patent Information
- Application Number
- PCT/KR2026/003679
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-06-18
- Filing Date
- 2026-03-06
- Publication Date
- 2026-11-19
AI Technical Summary
Existing Bluetooth Low Energy (BLE) communication systems face challenges in maintaining stable communication links due to link supervision timeout (LSTO) issues, particularly when CRC errors occur, leading to premature link termination and reduced quality of service.
Implementing a method to reset or delay the LSTO timer based on cyclic redundancy check (CRC) verification results, allowing the system to continue communication despite CRC errors, thereby enhancing the stability and quality of BLE connections.
The proposed method effectively maintains BLE communication links by preventing premature termination, improving the quality of service and reducing power consumption by optimizing the LSTO timer management.
Smart Images

Figure KR2026003679_19112026_PF_FP_ABST
Abstract
Description
Electronic device, method, and non-transient computer-readable storage medium for maintaining a communication link in a wireless environment
[0001] The following descriptions relate to an electronic device, a method, and a non-transient computer-readable storage medium for maintaining a communication link in a wireless environment.
[0002] BLE (Bluetooth® low energy) can provide reduced power consumption and a wide communication range between connected devices compared to legacy Bluetooth® (or classic Bluetooth). BLE can be provided on the ISM (industrial, scientific, and medical) radio band.
[0003] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.
[0004] An electronic device is provided. The electronic device may include a communication circuit for BLE (Bluetooth Low Energy). The electronic device may include at least one processor including a processing circuit. The electronic device may include a memory including one or more storage media for storing instructions. When executed individually or collectively by the at least one processor, the instructions may cause the electronic device to receive a packet from an external electronic device via a communication link established between the electronic device and the external electronic device using the communication circuit. When executed individually or collectively by the at least one processor, the instructions may cause the electronic device to perform a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link. The above instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to reset the LSTO (link supervision timeout) timer being executed in relation to the communication link based on the detection of a CRC error through the CRC verification.
[0005] A method is provided. The method may include the operation of receiving a packet from an external electronic device through a communication link established between the electronic device and the external electronic device. The method may include the operation of performing a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link. The method may include the operation of resetting a link supervision timeout (LSTO) timer running with respect to the communication link based on detecting a CRC error through the CRC verification.
[0006] A non-transient computer-readable storage medium is provided. The non-transient computer-readable storage medium may store one or more programs. The one or more programs may include instructions that cause the electronic device to receive a packet from an external electronic device through a communication link established between the electronic device and the external electronic device when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to perform a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to reset a link supervision timeout (LSTO) timer being executed with respect to the communication link based on detecting a CRC error through the CRC verification when executed by the electronic device.
[0007] Figure 1 illustrates an example of a wireless environment including an electronic device and an external electronic device.
[0008] FIG. 2 is a schematic view of an exemplary electronic device or external electronic device.
[0009] Figure 3 illustrates the expiration of the LSTO (link supervision timeout) timer of an electronic device.
[0010] Figure 4 is a flowchart illustrating a method for setting an LSTO timer based on a cyclic redundancy check (CRC) error.
[0011] Figure 5 illustrates an LSTO timer that is reset based on a CRC error.
[0012] Figure 6 is a flowchart illustrating a method for setting an LSTO timer depending on whether a CRC error is detected.
[0013] Figure 7 is a flowchart illustrating a method for setting an LSTO timer based on CRC error and packet data rate.
[0014] FIG. 8 is a flowchart illustrating a method for setting an LSTO timer based on CRC errors and the size of the packet's payload.
[0015] FIG. 9 is a flowchart illustrating a method for setting an LSTO timer based on CRC errors and the number of transmissions available for the communication link.
[0016] FIG. 10 is a flowchart illustrating a method for setting an LSTO timer based on the number of times a CRC error and valid packets were not received consecutively.
[0017] FIG. 11 is a flowchart illustrating a method for performing one or more operations to extend the expiration of an LSTO timer based on a CRC error.
[0018] Figure 12 is a flowchart illustrating a method to disable the function of delaying the time when a communication link is released based on a CRC error.
[0019] FIG. 13 illustrates an LSTO timer that is maintained to run continuously in relation to a communication link based on a CRC error depending on the deactivation of the function.
[0020] FIG. 14 is a block diagram of an electronic device in a network environment according to various embodiments.
[0021] Figure 1 illustrates an example of a wireless environment including an electronic device and an external electronic device.
[0022] Referring to FIG. 1, the wireless environment (100) may include an external electronic device (101) and an electronic device (102).
[0023] The external electronic device (101) may be described as a device that functions as a hearing aid (HA) device, a peripheral device, a server device, a secondary device, an audio sink device, or a sub device within a wireless environment (100). For example, the external electronic device (101) may be a wearable device such as a smart ring, a smartwatch, or wireless earphones (e.g., a true wireless stereo (TWS) device).
[0024] When the external electronic device (101) is a TWS device, the external electronic device (101) may be configured to output audio (190) through the speaker of the external electronic device (101). For example, the external electronic device (101) may receive a packet (112) from the electronic device (102). The packet (112) may be received from the electronic device (102) through a communication link (110) established between the external electronic device (101) and the electronic device (102). The external electronic device (101) may output audio (190) through the speaker of the external electronic device (101) using the packet (112). Meanwhile, the external electronic device (101) may transmit a packet (111) to the electronic device (102) through the communication link (110) based on the reception of the packet (112). As a non-limiting example, packet (111) may be an acknowledgment packet indicating that packet (112) has been received (successfully (or normally)). For example, the expiration of the LSTO timer of the electronic device (102) or the LSTO of the electronic device (102), which will be described below, may be deferred as packet (111) is received by the electronic device (102). For example, the LSTO timer of the electronic device (102) may be reset as packet (111) is received.
[0025] As an example without limitation, an external electronic device (101) may transmit a packet (113) to an electronic device (102) via a communication link (110) to maintain a communication link (110). For example, the size of the payload of the packet (113) may be smaller than the size of the payload of the packet (111) and / or the size of the payload of the packet (112). For example, the size of the payload of the packet (113) may be 0 (zero or null). The communication link (110) may be maintained as the packet (113) is received (successfully (or normally)) by the electronic device (102). For example, the expiration of the LSTO timer of the electronic device (102) or the LSTO of the electronic device (102), which will be described below, may be delayed as the packet (113) is received by the electronic device (102). For example, the LSTO timer of the electronic device (102) may be reset as the packet (113) is received by the electronic device (102). The electronic device (102) may transmit a packet (114) to the external electronic device (101) via the communication link (110) based on receiving the packet (113) from the external electronic device (101) via the communication link (110). The packet (114) may be an acknowledgment packet indicating that the packet (113) has been received (successfully (or normally)). The external electronic device (101) may receive the packet (114) from the electronic device (102) via the communication link (110). For example, the expiration of the LSTO timer of the external electronic device (101) or the LSTO of the external electronic device (101), which will be described below, may be delayed as the packet (114) is received by the external electronic device (101). For example, the LSTO timer of the external electronic device (101) may be reset as the packet (114) is received by the external electronic device (101).
[0026] The external electronic device (101) can correspond to the electronic device (1302) of FIG. 13.
[0027] The electronic device (102) may be described as a device functioning as a central device, client device, primary device, audio source device, or main device within the wireless environment (100). For example, the electronic device (102) may be a smartphone, tablet, laptop computer, desktop computer, or television. The electronic device (102) may be configured to transmit a packet (112) to an external electronic device (101). The packet (112) may be transmitted to the external electronic device (101) via a communication link (110). For example, the packet (112) may be transmitted to output audio (190) through the speaker of the external electronic device (101). Transmitting the packet (112) may be described as performing audio streaming to the external electronic device (101).
[0028] As an example without limitation, the electronic device (102) may transmit a packet (116) to an external electronic device (101) via the communication link (110) to maintain the communication link (110). For example, the size of the payload of the packet (116) may be smaller than the size of the payload of the packet (112). For example, the size of the payload of the packet (116) may be 0. The communication link (110) may be maintained as the packet (116) is received (successfully (or normally)) by the external electronic device (101). For example, the expiration of the LSTO timer of the external electronic device (101) or the LSTO of the external electronic device (101), which will be described below, may be delayed as the packet (116) is received by the external electronic device (101). For example, the LSTO timer of the external electronic device (101) may be reset as the packet (116) is received by the external electronic device (101). The external electronic device (101) may transmit a packet (115) to the electronic device (102) via the communication link (110) based on receiving the packet (116) from the electronic device (102) via the communication link (110). The packet (115) may be an acknowledgment packet indicating that the packet (116) has been received (successfully (or normally)). The electronic device (102) may receive the packet (115) from the external electronic device (101) via the communication link (110). For example, the expiration of the LSTO timer of the electronic device (102) to be described below or the LSTO of the electronic device (102) may be delayed as the packet (115) is received by the electronic device (102). For example, the LSTO timer of the electronic device (102) may be reset as the packet (115) is received by the electronic device (102).
[0029] The electronic device (102) may include at least a part of the electronic device (1301) of FIG. 13 or correspond to at least a part of the electronic device (1301) of FIG. 13.
[0030] Figure 2 is a schematic view of an exemplary electronic device.
[0031] Referring to FIG. 2, the external electronic device (101) or the electronic device (102) may include at least one processor (210), memory (220), and communication circuit (230). The external electronic device (101) (e.g., TWS device) or the electronic device (102) may include a speaker (240).
[0032] At least one processor (210) may include a processing circuit. At least one processor (210) may include a single processor or multiple processors. At least one processor (210) may control one or more components (e.g., a communication circuit (230) and / or a speaker (240)) of an external electronic device (101) or an electronic device (102).
[0033] The memory (220) may store one or more programs configured to be executed individually and / or collectively by at least one processor (210). The one or more programs may include instructions. The instructions may cause an external electronic device (101) or an electronic device (102) to perform operations described with reference to FIG. 1 and FIG. 4 through 13. The memory (220) may include one or more storage media.
[0034] The communication circuit (230) may be available for communication between an external electronic device (101) and an electronic device (102). The communication circuit (230) may be available for Bluetooth (or BLE (Bluetooth low energy)). The communication circuit (230) may be controlled by at least one processor (210).
[0035] The speaker (240) may be available to output audio (e.g., audio (190)). For example, when the external electronic device (101) is worn, the audio may be output from the speaker (240) toward the user's ear.
[0036] The following operations described as being performed by the electronic device (102) are merely exemplary. For example, the operations of the electronic device (102) described below may be replaced by the operations of the external electronic device (101). The following operations described as being performed by the external electronic device (101) are merely exemplary. For example, the operations of the external electronic device (101) described below may be replaced by the operations of the electronic device (102).
[0037] Figure 3 illustrates the expiration of the LSTO (link supervision timeout) timer of an electronic device.
[0038] The packets in FIG. 3 transmitted from the electronic device (102) may correspond to packet (112) or packet (116). The packets in FIG. 3 transmitted from the external electronic device (101) may correspond to packet (111) or packet (115). The connection events described with reference to FIG. 3 (e.g., EVENT COUNTER K-3, EVENT COUNTER K-2, EVENT COUNTER K-1, EVENT COUNTER K, or EVENT COUNTER M) may be associated with a communication link (110).
[0039] Referring to FIG. 3, an electronic device (102) can transmit a packet (302) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (302) to the external electronic device (101) according to a channel index of a connection event having an event counter (K-3) in response to an anchor point (341) of a connection event having an event counter (K-3) (K is a natural number greater than or equal to 3). The external electronic device (101) can receive the packet (302) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive the packet (302) from the electronic device (102) based on identifying the anchor point (341) and the channel index. An external electronic device (101) can transmit a packet (301) (e.g., an acknowledgment packet) to an electronic device (102) via a communication link (110) based on receiving a packet (302). The electronic device (102) can receive a packet (301) from the external electronic device (101) via a communication link (110).
[0040] The electronic device (102) can set the LSTO timer of the electronic device (102) upon receiving the packet (301).
[0041] For example, the LSTO timer of the electronic device (102) may be run in response to an anchor point of a connection event. For example, the LSTO timer may be run from the anchor point of the connection event before a reception synchronization timeout is detected within the connection event or before an invalid packet (e.g., detected by cyclic redundancy check (CRC) verification) is detected within the connection event. For example, the electronic device (102) may reset the LSTO timer of the electronic device (102) that was run from the anchor point (341) upon reception of a packet (301).
[0042] As another example, the LSTO timer of the electronic device (102) may be executed from the anchor point of the connection event based on whether a receive synchronization timeout is detected within the connection event or whether an invalid packet is detected within the connection event. For example, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point (341) upon receiving the packet (301).
[0043] As another example, the LSTO timer of the electronic device (102) may be executed from the timing at which the receive synchronization timeout is detected or the timing at which the invalid packet is detected, based on whether the receive synchronization timeout is detected within the connection event or whether the invalid packet is detected within the connection event. For example, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) upon receiving the packet (301).
[0044] Below, the LSTO timer of the electronic device (102) is described as being executed from the anchor point of the connection event based on whether a receive synchronization timeout is detected within the connection event or whether an invalid packet is detected within the connection event, but this is merely exemplary. The LSTO timer of the electronic device (102) may be executed in response to the anchor point of the connection event as described above, or from the timing when a receive synchronization timeout is detected or when the invalid packet is detected.
[0045] For example, the electronic device (102) may perform CRC verification in relation to the packet (301) based on identifying an access address (e.g., including the PCA-A (physical channel address - air portion) of the LE HDT (higher data throughput)) corresponding to the communication link (110) from the packet (301). For example, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point (341) based on the packet (301) being identified as a valid packet through the CRC verification. For example, the electronic device (102) may reset the LSTO timer of the electronic device (102) that is being executed from the anchor point of another connection event (e.g., related to the communication link (110)) prior to the connection event having the event counter (K-3) based on the packet (301) being identified as a valid packet through the CRC verification.
[0046] The electronic device (102) can transmit a packet (304) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (304) to the external electronic device (101) according to the channel index of the connection event having an event counter (K-2) in response to an anchor point (342) of a connection event having an event counter (K-2). The value of the connection peripheral latency for the communication link (110) can be set to 2, as indicated by the indication (380). The connection peripheral latency can be described as skipping receiving packets through connection events to reduce power consumption within the external electronic device (101). For example, when the value of the connection peripheral latency is 2, the external electronic device (101) can skip receiving packets through two connection events. As an example not limited to, the value of the connection periphery delay for the communication link (110) may be set according to a connection parameter update procedure. Since the value of the connection periphery delay for the communication link (110) is 2, the external electronic device (101) may refrain from (or skip) (or bypass) receiving a packet (e.g., packet (304)) within the connection event having an event counter (K-2). For example, the external electronic device (101) may not receive a packet (e.g., packet (304)) within the connection event having an event counter (K-2) according to the value of the connection periphery delay set to 2.Because the external electronic device (101) does not receive a packet (e.g., packet (304)) within the connection event having an event counter (K-2), the electronic device (102) may not receive a valid packet (e.g., detected by CRC verification) (e.g., an acknowledgment packet for packet (304)) within the connection event having an event counter (K-2). For example, the electronic device (102) may detect a reception synchronization timeout (381) within the connection event having an event counter (K-2). Based on detecting the reception synchronization timeout (381), the electronic device (102) may execute the LSTO timer of the electronic device (102). For example, as indicated by the indication (382), the LSTO timer of the electronic device (102) may be executed from the anchor point (342).
[0047] The electronic device (102) can transmit a packet (306) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (306) to the external electronic device (101) according to the channel index of the connection event having an event counter (K-1) in response to an anchor point (343) of a connection event having an event counter (K-1). Since the value of the connection periphery delay for the communication link (110) is 2, the external electronic device (101) can refrain from (or skip) (or bypass) receiving a packet (e.g., packet (306)) within the connection event having an event counter (K-1). For example, the external electronic device (101) may not receive a packet (e.g., packet (306)) within the connection event having an event counter (K-1) according to the value of the connection peripheral delay set to 2. Because the external electronic device (101) does not receive a packet (e.g., packet (306)) within the connection event having an event counter (K-1), the electronic device (102) may not receive a valid packet (e.g., an acknowledgment packet for packet (306)) within the connection event having an event counter (K-1). For example, the electronic device (102) may detect a receive synchronization timeout (383) within the connection event having an event counter (K-1). For example, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running from the anchor point (342) based on the detection of the receive synchronization timeout (383).
[0048] The electronic device (102) can transmit a packet (308) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (308) to the external electronic device (101) according to a channel index of said connection event having an event counter (K) in response to an anchor point (344) of said connection event having an event counter (K). The external electronic device (101) can receive the packet (308) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive the packet (308) from the electronic device (102) based on identifying the anchor point (344) and said channel index. The external electronic device (101) can transmit a packet (307) (e.g., an acknowledgment packet) to the electronic device (102) via the communication link (110) based on receiving a packet (308). The electronic device (102) can receive the packet (307) from the external electronic device (101) via the communication link (110).
[0049] The electronic device (102) may perform CRC verification with respect to the packet (307) based on identifying an access address corresponding to the communication link (110) from the packet (307). The electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue executing from the anchor point (342) based on the packet (307) being identified as an invalid packet through the CRC verification. For example, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue executing from the anchor point (342) based on the detection of a CRC error through the CRC verification, as indicated by the indication (330).
[0050] The electronic device (102) can transmit a packet (310) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (310) to the external electronic device (101) according to the channel index of the connection event having an event counter (M) in response to an anchor point (345) of a connection event having an event counter (M) (M is a natural number greater than K+1). For example, the connection event interval of the connection event having an event counter (M) may include a timing in which the LSTO timer of the electronic device (102), which is continuously running from the anchor point (342), expires according to the value of the LSTO timer of the electronic device (102). For example, the connection event having an event counter (M) can be described as a connection event that includes a timing in which the LSTO timer of the electronic device (102) which is continuously running from the anchor point (342) expires according to the value of the LSTO timer of the electronic device (102).
[0051] An external electronic device (101) can (successfully) receive a packet (310) from an electronic device (102) via a communication link (110). For example, the external electronic device (101) can receive the packet (310) from the electronic device (102) based on identifying an anchor point (345) and the channel index. Based on receiving the packet (310), the external electronic device (101) can transmit a packet (309) (e.g., an acknowledgment packet) to the electronic device (102) via the communication link (110). The electronic device (102) can receive the packet (309) from the external electronic device (101) via the communication link (110).
[0052] The electronic device (102) may perform CRC verification with respect to the packet (309) based on identifying an access address corresponding to the communication link (110) from the packet (309). The electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue executing from the anchor point (342) based on the packet (309) being identified as an invalid packet through the CRC verification. For example, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue executing from the anchor point (342) based on the detection of a CRC error through the CRC verification, as indicated by the indication (331). Since the LSTO timer of the electronic device (102) is maintained to run continuously from the anchor point (342) based on the detection of a CRC error through the CRC verification as indicated by the indication (331), the LSTO timer of the electronic device (102) may expire in response to the end timing of the connection event having an event counter (M), as indicated by the indication (332). The LSTO timer of the electronic device (102) may expire based on the failure to continuously receive valid packets from the external electronic device (101) between the connection event having an event counter (K) and the connection event having an event counter (M). For example, the LSTO of the electronic device (102) may occur at the end timing of the connection event having an event counter (M). For example, the electronic device (102) can release the communication link (110) based on the expiration of the LSTO timer of the electronic device (102) (or the LSTO of the electronic device (102)).
[0053] As a non-limiting example, if the value of the LSTO timer of the electronic device (102) is small relative to the value of the connection peripheral delay, the number of transmissions of the electronic device (102) available for the communication link (110) may be relatively small. Even though the number of transmissions of the electronic device (102) available for the communication link (110) is relatively small, releasing the communication link (110) based on the end timing of the connection event having an event counter (M), as described in the example with reference to FIG. 3, may reduce the quality of service associated with the communication link (110).
[0054] For example, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time (or timing) at which the communication link (110) is released even if a CRC error is detected through CRC verification performed in relation to a packet received from an external electronic device (101) via a communication link (110) (e.g., a packet transmitted from the external electronic device (101) based on identifying an anchor point and channel index of a connection event associated with the communication link (110) having (or including) an access address corresponding to the communication link (110)) in order to enhance the quality of the service. For example, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the detection of a CRC error as indicated by the indication (330) and the indication (331). Setting the LSTO timer of the electronic device (102) to delay the time when the communication link (110) is released is described in more detail below.
[0055] Figure 4 is a flowchart illustrating a method for setting an LSTO timer based on a cyclic redundancy check (CRC) error.
[0056] Referring to FIG. 4, in operation 410, the electronic device (102) can receive a packet from an external electronic device (101) via a communication link (110) using a communication circuit (230). For example, the packet may be transmitted from the external electronic device (101) based on identifying an anchor point and a channel index of a connection event associated with the communication link (110). For example, the electronic device (102) may receive the packet from the external electronic device (101) within (or inside) the connection event based on identifying the anchor point and the channel index of the connection event.
[0057] In operation 420, the electronic device (102) may perform CRC verification with respect to the packet received in operation 410. For example, the electronic device (102) may perform the CRC verification based on identifying that the packet received in operation 410 has an access address corresponding to a communication link (110). For example, the electronic device (102) may perform the CRC verification by comparing a value included in a CRC field included in the packet with a value calculated from data (or payload) within the packet.
[0058] In operation 430, the electronic device (102) can detect a CRC error through the CRC verification performed in operation 420. For example, the electronic device (102) can detect the CRC error based on identifying, according to the comparison, that the value calculated from the data in the packet is different from the value included in the CRC field included in the packet. For example, the electronic device (102) can identify the packet received in operation 410 as an invalid packet through the CRC verification performed in operation 420.
[0059] In operation 440, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the detection of the CRC error. For example, the CRC error detected in operation 430 may indicate that the payload of the packet received in operation 410 is invalid, but the CRC error detected in operation 430 may indicate that the packet is transmitted to the electronic device (102) through the communication link (110). For example, since the CRC error detected in operation 430 indicates that the payload of the packet received in operation 410 is invalid, the electronic device (102) may discard the payload of the packet received in operation 410 based on the fact that the CRC error is detected through the CRC verification. For example, even if the CRC error detected in operation 430 indicates that the payload of the packet received in operation 410 is invalid, the CRC error detected in operation 430 may indicate that the external electronic device (101) transmits a packet to the electronic device (102) using the frequency negotiated with the electronic device (102) at the timing negotiated with the electronic device (102). Since the CRC error detected in operation 430 indicates that the external electronic device (101) transmits a packet to the electronic device (102) using the frequency negotiated with the electronic device (102) at the timing negotiated with the electronic device (102), the electronic device (102) may set the LSTO timer of the electronic device (102) to block the communication link (110) from being released. For example, if the LSTO timer of the electronic device (102) is not running in relation to the communication link (110), the electronic device (102) may refrain from running the LSTO timer of the electronic device (102) based on the CRC error detected in operation 430 (from the anchor point of the connection event).For example, when the LSTO timer of the electronic device (102) is running in relation to the communication link (110), the electronic device (102) may reset the LSTO timer of the electronic device (102). For example, resetting the LSTO timer of the electronic device (102) may include initializing the LSTO timer of the electronic device (102) and running the initialized LSTO timer of the electronic device (102). For example, resetting the LSTO timer of the electronic device (102) may include initializing the LSTO timer of the electronic device (102) and refraining from or forgo running the initialized LSTO timer of the electronic device (102).
[0060] Resetting the LSTO timer of the electronic device (102) is described in more detail with reference to FIG. 5.
[0061] Figure 5 illustrates an LSTO timer that is reset based on a CRC error.
[0062] The packets in FIG. 5 transmitted from the electronic device (102) may correspond to packet (112) or packet (116). The packets in FIG. 5 transmitted from the external electronic device (101) may correspond to packet (111) or packet (115). The connection events described with reference to FIG. 5 may be associated with a communication link (110).
[0063] Referring to FIG. 5, an electronic device (102) can transmit a packet (302) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (302) to the external electronic device (101) according to a channel index of said connection event having an event counter (K-3) in response to an anchor point (341) of said connection event having an event counter (K-3). The external electronic device (101) can (successfully) receive a packet (302) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive a packet (302) from the electronic device (102) based on identifying the anchor point (341) and said channel index. An external electronic device (101) can transmit a packet (301) (e.g., an acknowledgment packet) to an electronic device (102) via a communication link (110) based on receiving a packet (302). The electronic device (102) can receive a packet (301) from the external electronic device (101) via a communication link (110).
[0064] The electronic device (102) may set the LSTO timer of the electronic device (102) upon receiving the packet (301). For example, the electronic device (102) may perform CRC verification with respect to the packet (301) based on identifying an access address (e.g., PCA-A of LE HDT) corresponding to the communication link (110) from the packet (301). For example, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point (341) based on the packet (301) being identified as a valid packet through the CRC verification. For example, when the LSTO timer of the electronic device (102) is running from an anchor point of another connection event (e.g., related to a communication link (110)) prior to the connection event having an event counter (K-3), the electronic device (102) may reset the LSTO timer of the electronic device (102) based on the packet (301) being identified as a valid packet through the CRC verification.
[0065] The electronic device (102) can transmit a packet (304) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (304) to the external electronic device (101) according to the channel index of the connection event having an event counter (K-2) in response to an anchor point (342) of a connection event having an event counter (K-2). The value of the connection periphery delay for the communication link (110) can be set to 2, as indicated by the indication (380). As a non-limiting example, the value of the connection periphery delay for the communication link (110) can be set according to a connection parameter update procedure. Since the value of the connection periphery delay for the communication link (110) is 2, the external electronic device (101) may refrain from (or skip) (or bypass) receiving a packet (e.g., packet (304)) within the connection event having an event counter (K-2). For example, the external electronic device (101) may not receive a packet (e.g., packet (304)) within the connection event having an event counter (K-2) according to the value of the connection periphery delay set to 2. Since the external electronic device (101) does not receive a packet (e.g., packet (304)) within the connection event having an event counter (K-2), the electronic device (102) may not receive a valid packet within the connection event having an event counter (K-2). For example, the electronic device (102) may detect a reception synchronization timeout (381) within the connection event having an event counter (K-2). The electronic device (102) can execute the LSTO timer of the electronic device (102) based on detecting a reception synchronization timeout (381). For example, as indicated by the indication (382), the LSTO timer of the electronic device (102) can be executed from an anchor point (342).
[0066] The electronic device (102) can transmit a packet (306) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (306) to the external electronic device (101) according to the channel index of the connection event having an event counter (K-1) in response to an anchor point (343) of a connection event having an event counter (K-1). Since the value of the connection periphery delay for the communication link (110) is 2, the external electronic device (101) can refrain from (or skip) (or bypass) receiving a packet (e.g., packet (306)) within the connection event having an event counter (K-1). For example, the external electronic device (101) may not receive a packet (e.g., packet (306)) within the connection event having an event counter (K-1) according to the value of the connection peripheral delay set to 2. Because the external electronic device (101) does not receive a packet (e.g., packet (306)) within the connection event having an event counter (K-1), the electronic device (102) may not receive a valid packet (e.g., an acknowledgment packet for packet (306)) within the connection event having an event counter (K-1). For example, the electronic device (102) may detect a receive synchronization timeout (383) within the connection event having an event counter (K-1). For example, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running from the anchor point (342) based on the detection of the receive synchronization timeout (383).
[0067] The electronic device (102) can transmit a packet (308) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (308) to the external electronic device (101) according to a channel index of said connection event having an event counter (K) in response to an anchor point (344) of said connection event having an event counter (K). The external electronic device (101) can receive the packet (308) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive the packet (308) from the electronic device (102) based on identifying the anchor point (344) and said channel index. An external electronic device (101) may transmit a packet (307) (e.g., an acknowledgment packet) to an electronic device (102) via a communication link (110) based on receiving a packet (308). The electronic device (102) may receive a packet (307) from the external electronic device (101) via a communication link (110). For example, the electronic device (102) may receive a packet (307) from the external electronic device (101) based on identifying an anchor point (344) and the channel index.
[0068] The electronic device (102) may perform CRC verification with respect to the packet (307) based on identifying an access address corresponding to the communication link (110) from the packet (307). The electronic device (102) may reset the LSTO timer of the electronic device (102) running from the anchor point (342), as indicated by the indication (584), based on the packet (307) being identified as an invalid packet through the CRC verification. For example, the electronic device (102) may reset the LSTO timer of the electronic device (102) running from the anchor point (342), as indicated by the indication (584), based on the detection of a CRC error through the CRC verification, as indicated by the indication (330).
[0069] For example, unlike the example of FIG. 3, the time at which the communication link (110) is released can be delayed because the electronic device (102) resets the LSTO timer of the electronic device (102) based on the detection of a CRC error through the CRC verification, as indicated by the indication (330). For example, let us assume that the external electronic device (101) does not transmit a packet to the electronic device (102) via the communication link (110) after the end of the connection event having an event counter (K). For example, the LSTO timer of the electronic device (102) can expire after the end timing of the connection event having an event counter (M), even if the external electronic device (101) does not transmit a packet to the electronic device (102) via the communication link (110) after the end of the connection event having an event counter (K).
[0070] For example, an electronic device (102) can transmit a packet (310) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (310) to the external electronic device (101) according to the channel index of the connection event having an event counter (M) in response to an anchor point (345) of a connection event having an event counter (M) (M is a natural number greater than K+1). The external electronic device (101) may not receive the packet (310) transmitted from the electronic device (102) via the communication link (110). Because the external electronic device (101) cannot receive the packet (310) transmitted from the electronic device (102) via the communication link (110), the electronic device (102) can detect (or identify) a receive synchronization timeout (585) within the connection event having an event counter (M). Even if the receive synchronization timeout (585) is detected within the connection event having an event counter (M), the LSTO timer of the electronic device (102) that is reset within the connection event having an event counter (K) may not expire. For example, even if a receive synchronization timeout is detected consecutively by the electronic device (102) between the connection event having an event counter (K+1) and the connection event having an event counter (M), the LSTO timer of the electronic device (102) that is reset within the connection event having an event counter (K) may not expire. Since the LSTO timer of the electronic device (102) does not expire upon the termination of the connection event having an event counter (M), the communication link (110) may not be released upon the termination of the connection event having an event counter (M).
[0071] For example, the electronic device (102) can transmit a packet (512) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (512) to the external electronic device (101) according to the channel index of the connection event having an event counter (M+1) in response to an anchor point (546) of a connection event having an event counter (M+1).
[0072] As described above, the electronic device (102) can lengthen the duration for which the communication link (110) is maintained by resetting the LSTO timer of the electronic device (102) based on the detection of a CRC error in a packet containing an access address corresponding to the communication link (110) in relation to a CRC verification performed in connection with the communication link (110) (e.g., resetting the LSTO timer of the electronic device (102) running from the anchor point (342) as indicated by the indication (584). By lengthening the duration, the electronic device (102) can enhance the quality of service provided through wireless communication between the external electronic device (101) and the electronic device (102).
[0073] Figure 6 is a flowchart illustrating a method for setting an LSTO timer depending on whether a CRC error is detected.
[0074] Referring to FIG. 6, in operation 610, the electronic device (102) can identify whether a receive synchronization timeout occurs within a connection event associated with a communication link (110). The electronic device (102) can identify that the receive synchronization timeout does not occur based on receiving a packet from an external electronic device (101) within the connection event. The electronic device (102) can identify that the receive synchronization timeout occurs based on not receiving a packet from an external electronic device (101) within the connection event. For example, the electronic device (102) can perform operation 620 under conditions where the receive synchronization timeout occurs within the connection event, and perform operation 630 under conditions where the receive synchronization timeout does not occur within the connection event.
[0075] In operation 620, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on identifying that the receive synchronization timeout occurs within the connection event. For example, if the LSTO timer of the electronic device (102) is running from an anchor point of the other connection event, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running. For example, if the LSTO timer of the electronic device (102) is not running from an anchor point of another connection event prior to the connection event (e.g., related to the communication link (110)), the electronic device (102) may run the LSTO timer of the electronic device (102) from an anchor point of the connection event.
[0076] In operation 630, the electronic device (102) may perform CRC verification with respect to said packet based on receiving said packet from the external electronic device (102) via the communication link (110) within said connection event. For example, said packet on which the CRC verification is performed may have an access address corresponding to the communication link (110). For example, operation 630 may correspond to operation 420 of FIG. 4.
[0077] In operation 640, the electronic device (102) can set the LSTO timer of the electronic device (102) to delay the time when the communication link (110) is released, independently of whether a CRC error is detected according to the CRC verification performed in operation 630.
[0078] For example, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is not detected according to the CRC verification performed in operation 630 (or based on the fact that a valid packet is received within the connection event). For example, if the LSTO timer of the electronic device (102) is not running from the anchor point of the other connection event, the electronic device (102) may refrain from running the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) may reset the LSTO timer of the electronic device (102).
[0079] For example, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the detection of the CRC error according to the CRC verification performed in operation 630. For example, if the LSTO timer of the electronic device (102) is not running from the anchor point of the other connection event, the electronic device (102) may refrain from running the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) may reset the LSTO timer of the electronic device (102).
[0080] Figure 7 is a flowchart illustrating a method for setting an LSTO timer based on CRC error and packet data rate.
[0081] Referring to FIG. 7, in operation 710, the electronic device (102) can identify whether a receive synchronization timeout occurs within a connection event associated with a communication link (110). The electronic device (102) can identify that the receive synchronization timeout does not occur based on receiving a packet from an external electronic device (101) within the connection event. The electronic device (102) can identify that the receive synchronization timeout occurs based on not receiving a packet from an external electronic device (101) within the connection event. For example, the electronic device (102) can perform operation 740 under conditions where the receive synchronization timeout occurs within the connection event, and perform operation 720 under conditions where the receive synchronization timeout does not occur within the connection event.
[0082] In operation 720, the electronic device (102) may perform CRC verification with respect to the packet based on the fact that the packet is received from an external electronic device (101) via a communication link (110) within the connection event. For example, the packet on which the CRC verification is performed may have an access address corresponding to the communication link (110). For example, operation 720 may correspond to operation 420 of FIG. 4.
[0083] In operation 725, the electronic device (102) can identify whether a CRC error is detected through the CRC verification performed in operation 720. For example, the electronic device (102) can perform operation 730 based on whether the CRC error is detected through the CRC verification, and perform operation 750 based on whether the CRC error is not detected through the CRC verification.
[0084] In operation 730, the electronic device (102) can identify whether the data rate of the packet received within the connection event is higher than the threshold data rate, based on identifying that a CRC error is detected through the CRC verification performed in operation 720. By example, without limitation, the data rate being higher than the threshold data rate may indicate that the quality of the communication link (110) is relatively high, and the data rate being lower than the threshold data rate may indicate that the quality of the communication link (110) is relatively low. Since the quality of the communication link (110) being relatively high may indicate that the CRC error is highly unlikely to have occurred due to the state of the communication link (110), the electronic device (102) can perform operation 740 under the condition that the data rate is higher than the threshold data rate. Since the relatively low quality of the communication link (110) may indicate a high probability that the CRC error occurred depending on the state of the communication link (110), the electronic device (102) can perform operation 750 under conditions where the data rate is lower than the threshold data rate.
[0085] FIG. 7 illustrates the performance of operation 730 according to operation 725, but this is merely illustrative. Operation 730 may be performed before operation 710, operation 720, and / or operation 725 are performed. For example, since the data rate may be identified based on negotiation (e.g., connection parameter update procedure) between the electronic device (102) and the external electronic device (101) in relation to the communication link (110) before operation 710, operation 720, and / or operation 725 are performed, operation 730 may be performed before operation 710, operation 720, and / or operation 725 are performed. For example, if operation 740 is not executed under conditions where the reception synchronization timeout occurs according to operation 710, operation 740 may be performed based on the fact that the CRC error is detected through the CRC verification and the data rate is identified as being higher than the threshold data rate. For example, if operation 750 is not executed under conditions where the CRC error is not detected through the CRC verification, operation 750 may be performed based on the fact that the CRC error is detected through the CRC verification and the data rate is identified as being lower than the threshold data rate.
[0086] In operation 740, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the receive synchronization timeout is identified within the connection event. In operation 740, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the CRC error is detected through the CRC verification and that the data rate is identified as being higher than the threshold data rate. For example, if the LSTO timer of the electronic device (102) is running from an anchor point of another connection event prior to the connection event, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110). For example, if the LSTO timer of the electronic device (102) is not running from an anchor point of another connection event prior to the connection event, the electronic device (102) can run the LSTO timer of the electronic device (102) from an anchor point of the connection event.
[0087] In operation 750, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is not detected through the CRC verification. In operation 750, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is detected through the CRC verification and the data rate is identified as being lower than the threshold data rate. For example, if the LSTO timer of the electronic device (102) is not executed from the anchor point of the other connection event, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) can reset the LSTO timer of the electronic device (102).
[0088] Although not illustrated in FIG. 7, the electronic device (102) may perform operation 750 based on the fact that the CRC error is detected through the CRC verification and the data rate is identified as being higher than the threshold data rate, and may perform operation 740 based on the fact that the CRC error is detected through the CRC verification and the data rate is identified as being lower than the threshold data rate.
[0089] FIG. 8 is a flowchart illustrating a method for setting an LSTO timer based on CRC errors and the size of the packet's payload.
[0090] Referring to FIG. 8, in operation 810, the electronic device (102) can identify whether a receive synchronization timeout occurs within a connection event associated with a communication link (110). The electronic device (102) can identify that the receive synchronization timeout does not occur based on receiving a packet from an external electronic device (101) within the connection event. The electronic device (102) can identify that the receive synchronization timeout occurs based on not receiving a packet from an external electronic device (101) within the connection event. For example, the electronic device (102) can perform operation 840 under conditions where the receive synchronization timeout occurs within the connection event, and perform operation 820 under conditions where the receive synchronization timeout does not occur within the connection event.
[0091] In operation 820, the electronic device (102) may perform CRC verification with respect to the packet based on the fact that the packet is received from an external electronic device (101) via a communication link (110) within the connection event. For example, the packet on which the CRC verification is performed may have an access address corresponding to the communication link (110). For example, operation 820 may correspond to operation 420 of FIG. 4.
[0092] In operation 825, the electronic device (102) can identify whether a CRC error is detected through the CRC verification performed in operation 820. For example, the electronic device (102) can perform operation 830 based on whether the CRC error is detected through the CRC verification, and perform operation 850 based on whether the CRC error is not detected through the CRC verification.
[0093] In operation 830, the electronic device (102) can identify whether the size of the payload of the packet received within the connection event is greater than a threshold size based on identifying that a CRC error is detected through the CRC verification performed in operation 820. By example, without limitation, the size of the payload being greater than the threshold size may indicate that the packet was not transmitted solely to maintain the communication link (110), and the size of the payload being smaller than the threshold size may indicate that the packet was transmitted solely to maintain the communication link (110). Since the fact that the packet was not transmitted solely to maintain the communication link (110) may indicate that the CRC error is highly likely not to have occurred due to the state of the communication link (110), the electronic device (102) can perform operation 840 under the condition that the size of the payload is greater than the threshold size. Since the above packet is transmitted solely to maintain the communication link (110), it can indicate that the CRC error is likely to have occurred depending on the state of the communication link (110), so the electronic device (102) can perform operation 850 under the condition that the size of the payload is smaller than the threshold size.
[0094] FIG. 8 illustrates the performance of operation 830 according to operation 825, but this is merely illustrative. Operation 830 may be performed before operation 820 and / or operation 825 is performed. For example, operation 830 may be performed before operation 820 and / or operation 825 is performed because the size of the payload may be identified based on the type of packet determined by negotiation (e.g., connection parameter update procedure) between the electronic device (102) and the external electronic device (101) in relation to the communication link (110) before operation 820 and / or operation 825 is performed. For example, if operation 840 is not executed under conditions where the reception synchronization timeout occurs according to operation 810, operation 840 may be performed based on the fact that the CRC error is detected through the CRC verification and that the size of the payload is identified as being larger than the threshold size. For example, if operation 850 is not executed under conditions where the CRC error is not detected through the CRC verification, operation 850 may be performed based on the fact that the CRC error is detected through the CRC verification and that the size of the payload is identified as being smaller than the threshold size.
[0095] In operation 840, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the receive synchronization timeout is identified within the connection event. In operation 840, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the CRC error is detected through the CRC verification and that the size of the payload is identified as being larger than the threshold size. For example, if the LSTO timer of the electronic device (102) is running from an anchor point of another connection event prior to the connection event, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110). For example, if the LSTO timer of the electronic device (102) is not running from an anchor point of another connection event prior to the connection event, the electronic device (102) can run the LSTO timer of the electronic device (102) from an anchor point of the connection event.
[0096] In operation 850, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is not detected through the CRC verification. In operation 850, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is detected through the CRC verification and that the size of the payload is identified as being smaller than the threshold size. For example, if the LSTO timer of the electronic device (102) is not executed from the anchor point of the other connection event, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) can reset the LSTO timer of the electronic device (102).
[0097] Although not illustrated in FIG. 8, the electronic device (102) may perform operation 850 based on the fact that the CRC error is detected through the CRC verification and the size of the payload is identified as being larger than the threshold size, and may perform operation 840 based on the fact that the CRC error is detected through the CRC verification and the size of the payload is identified as being smaller than the threshold size.
[0098] FIG. 9 is a flowchart illustrating a method for setting an LSTO timer based on CRC errors and the number of transmissions available for the communication link.
[0099] Referring to FIG. 9, in operation 910, the electronic device (102) can identify whether a receive synchronization timeout occurs within a connection event associated with a communication link (110). The electronic device (102) can identify that the receive synchronization timeout does not occur based on receiving a packet from an external electronic device (101) within the connection event. The electronic device (102) can identify that the receive synchronization timeout occurs based on not receiving a packet from an external electronic device (101) within the connection event. For example, the electronic device (102) can perform operation 940 under conditions where the receive synchronization timeout occurs within the connection event, and perform operation 920 under conditions where the receive synchronization timeout does not occur within the connection event.
[0100] In operation 920, the electronic device (102) may perform CRC verification with respect to the packet based on the fact that the packet is received from an external electronic device (101) via a communication link (110) within the connection event. For example, the packet on which the CRC verification is performed may have an access address corresponding to the communication link (110). For example, operation 920 may correspond to operation 420 of FIG. 4.
[0101] In operation 925, the electronic device (102) can identify whether a CRC error is detected through the CRC verification performed in operation 920. For example, the electronic device (102) can perform operation 930 based on whether the CRC error is detected through the CRC verification, and perform operation 950 based on whether the CRC error is not detected through the CRC verification.
[0102] In operation 930, the electronic device (102) can identify whether the number of transmissions available for the communication link (110) is greater than a threshold number of transmissions based on identifying that a CRC error is detected through the CRC verification performed in operation 920. The number may be described as the number of transmissions of the electronic device (102) available for the communication link (110) or as the number of transmissions of the external electronic device (101) available for the communication link (110). For example, the number may be identified according to the value of the connection event interval for the communication link (110), the value of the connection peripheral delay for the communication link (110), and the value of the LSTO timer of the electronic device (102) (or the value of the LSTO timer for the communication link (110). For example, if the value of the LSTO timer is 5 (s) (seconds), the value of the connection event interval is 42.5 (ms) (milliseconds), and the value of the connection periphery delay is 23, the number may be identified as 4 (e.g., a value less than 4.90 calculated from 5000 / (42.5 X (23+1)) and closest to 4.90). As a non-limiting example, the threshold number of transmissions may be 6, which is the minimum number of communication possible for a Link Layer Control PDU (protocol data unit) as described in the Bluetooth specification.
[0103] As an example not limited to, the fact that the number is greater than the threshold number of transmissions indicates that it is relatively efficient to execute the LSTO timer or maintain the LSTO timer to continue executing based on the detection of the CRC error through the CRC verification, and the fact that the number is less than the threshold number of transmissions indicates that it is relatively efficient to reset the LSTO timer or refrain from executing the LSTO timer based on the detection of the CRC error through the CRC verification. For example, the electronic device (102) can perform operation 940 under conditions where the number is greater than the threshold number of transmissions. For example, the electronic device (102) can perform operation 950 under conditions where the number is less than the threshold number of transmissions.
[0104] According to embodiments, the number may be described as the remaining number of transmissions available for the communication link (110).
[0105] FIG. 9 illustrates the performance of operation 930 according to operation 925, but this is merely illustrative. Operation 930 may be performed before operation 910, operation 920, and / or operation 925 are performed. For example, since the number may be identified according to negotiation (e.g., connection parameter update procedure) between the electronic device (102) and the external electronic device (101) in relation to the communication link (110) before operation 910, operation 920, and / or operation 925 are performed, operation 930 may be performed before operation 910, operation 920, and / or operation 925 are performed. For example, if operation 940 is not executed under conditions where the reception synchronization timeout occurs according to operation 910, operation 940 may be performed based on the fact that the CRC error is detected through the CRC verification and that the number is identified as being greater than the threshold number of transmissions. For example, if operation 950 is not executed under conditions where the CRC error is not detected through the CRC verification, operation 950 may be performed based on the fact that the CRC error is detected through the CRC verification and that the number is identified as being less than the threshold number of transmissions.
[0106] In operation 940, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the receive synchronization timeout is identified within the connection event. In operation 940, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the CRC error is detected through the CRC verification and that the number is identified as being greater than the threshold number of transmissions. For example, if the LSTO timer of the electronic device (102) is running from an anchor point of another connection event prior to the connection event, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110). For example, if the LSTO timer of the electronic device (102) is not running from an anchor point of another connection event prior to the connection event, the electronic device (102) can run the LSTO timer of the electronic device (102) from an anchor point of the connection event.
[0107] In operation 950, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is not detected through the CRC verification. In operation 950, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is detected through the CRC verification and the number is identified as being less than the threshold number of transmissions. For example, if the LSTO timer of the electronic device (102) is not executed from the anchor point of the other connection event, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) can reset the LSTO timer of the electronic device (102).
[0108] FIG. 10 is a flowchart illustrating a method for setting an LSTO timer based on the number of times a CRC error and valid packets were not received consecutively.
[0109] Referring to FIG. 10, in operation 1010, the electronic device (102) can identify whether a receive synchronization timeout occurs within a connection event associated with a communication link (110). The electronic device (102) can identify that the receive synchronization timeout does not occur based on receiving a packet from an external electronic device (101) within the connection event. The electronic device (102) can identify that the receive synchronization timeout occurs based on not receiving a packet from an external electronic device (101) within the connection event. For example, the electronic device (102) can perform operation 1040 under conditions where the receive synchronization timeout occurs within the connection event, and perform operation 1020 under conditions where the receive synchronization timeout does not occur within the connection event.
[0110] In operation 1020, the electronic device (102) may perform CRC verification with respect to the packet based on the fact that the packet is received from an external electronic device (101) via a communication link (110) within the connection event. For example, the packet on which the CRC verification is performed may have an access address corresponding to the communication link (110). For example, operation 1020 may correspond to operation 420 of FIG. 4.
[0111] In operation 1025, the electronic device (102) can identify whether a CRC error is detected through the CRC verification performed in operation 1020. For example, the electronic device (102) can perform operation 1030 based on whether the CRC error is detected through the CRC verification, and perform operation 1050 based on whether the CRC error is not detected through the CRC verification.
[0112] In operation 1030, the electronic device (102) can identify whether the number of times a valid packet was not continuously received from the external electronic device (101) via the communication link (110) is less than a threshold number, based on identifying that a CRC error was detected through the CRC verification performed in operation 1020. The number can be identified by adding 1 to the number of times a valid packet was not continuously received from the external electronic device (101) via the communication link (110) prior to the connection event.
[0113] As an example not limited to, if the above number is less than the threshold number, it indicates that the quality of the communication link (110) is relatively high, and if the above number is more than the threshold number, it indicates that the quality of the communication link (110) is relatively low. Since the quality of the communication link (110) is relatively high, it indicates that there is a high probability that the CRC error did not occur according to the state of the communication link (110), the electronic device (102) can perform operation 1040 under the condition that the above number is less than the threshold number. Since the quality of the communication link (110) is relatively low, it indicates that there is a high probability that the CRC error occurred according to the state of the communication link (110), the electronic device (102) can perform operation 1050 under the condition that the above number is more than the threshold number.
[0114] In operation 1040, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the receive synchronization timeout is identified within the connection event. In operation 1040, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110) based on the fact that the CRC error is detected through the CRC verification and that the number is identified as being less than the threshold number. For example, if the LSTO timer of the electronic device (102) is running from an anchor point of another connection event prior to the connection event, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running in relation to the communication link (110). For example, if the LSTO timer of the electronic device (102) is not running from an anchor point of another connection event prior to the connection event, the electronic device (102) can run the LSTO timer of the electronic device (102) from an anchor point of the connection event.
[0115] In operation 1050, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is not detected through the CRC verification. In operation 1050, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the fact that the CRC error is detected through the CRC verification and the number is identified as being greater than the threshold number. For example, if the LSTO timer of the electronic device (102) is not executed from the anchor point of the other connection event, the electronic device (102) may refrain from executing the LSTO timer of the electronic device (102) from the anchor point of the connection event. For example, if the LSTO timer of the electronic device (102) is running from the anchor point of the other connection event, the electronic device (102) can reset the LSTO timer of the electronic device (102).
[0116] Although not illustrated in FIG. 10, the electronic device (102) may reset (or initialize) the number of times valid packets have not been received consecutively (e.g., used in operation 1030) under conditions of performing operation 1050. For example, if the number used for operation 1030 is 10, the electronic device (102) may adjust the number to 0 based on performing operation 1050.
[0117] FIG. 11 is a flowchart illustrating a method for performing one or more operations to extend the expiration of an LSTO timer based on a CRC error.
[0118] Referring to FIG. 11, in operation 1110, the electronic device (102) can receive a packet from an external electronic device (101) through a communication link (110). Operation 1110 can correspond to operation 410 of FIG. 4.
[0119] In operation 1120, the electronic device (102) may perform CRC verification with respect to the packet based on identifying that the packet received in operation 1110 includes an access address corresponding to a communication link (110). Operation 1120 may correspond to operation 420 of FIG. 4.
[0120] In operation 1130, the electronic device (102) can detect a CRC error through the CRC verification performed in operation 1120. Operation 1130 can correspond to operation 430 of FIG. 4.
[0121] In operation 1140, the electronic device (102) may perform one or more operations to delay the expiration of the LSTO timer of the electronic device (102) based on the detection of the CRC error through the CRC verification. For example, the electronic device (102) may perform operation 1140 to delay the time when the communication link (110) is released.
[0122] For example, the electronic device (102) may extend the length of a connection event to transmit one or more packets within a connection event (e.g., a connection event used to receive the packet in operation 1110) transmitted from an external electronic device (101) based on detecting the CRC error through the CRC verification. For example, the electronic device (102) may transmit a packet containing a field (e.g., a more data field) indicating that more data is enabled to the external electronic device (101) via the communication link (110) based on detecting the CRC error through the CRC verification. For example, the electronic device (102) may reduce a subrate factor based on detecting the CRC error through the CRC verification. The subrate factor may be described as a communication cycle skipped for lower power consumption. For example, if the subrate factor is 5, the electronic device (102) (or external electronic device (101)) can perform communication at every communication cycle corresponding to 5 connection events by skipping 5 connection events. For example, the electronic device (102) can disable skipping one or more connection events for the communication link (110) based on the value of the connection peripheral delay for the communication link (110) based on detecting the CRC error through the CRC verification. For example, the electronic device (102) can perform a connection parameter update procedure with the external electronic device (101) to reduce the value of the connection peripheral delay based on detecting the CRC error through the CRC verification.For example, the electronic device (102) can disable the skipping of one or more connection events for the communication link (110) by transmitting a packet containing the field indicating that additional data is enabled based on detecting the CRC error through the CRC verification.
[0123] As a non-limiting example, an external electronic device (101) functioning as a peripheral device in relation to the electronic device (102) may perform an operation corresponding to the operation of the electronic device (102) described above. For example, the external electronic device (101) may refrain from terminating a connection event in which a reception synchronization timeout occurs and may identify whether additional packets are received from the electronic device (102) via the communication link (110) within said connection event. For example, the external electronic device (101) may transmit a packet containing the field indicating that additional data is activated to the electronic device (102) via the communication link (110). For example, the external electronic device (101) may identify whether packets are received from the electronic device (102) within one or more other connection events (related to the communication link (110)) following said connection event, independently of the value of the connection peripheral delay set in relation to the communication link (110).
[0124] One of the operations of the electronic device (102) described with reference to FIG. 11 may be combined with one or more other operations of the electronic device (102) described with reference to FIG. 11. One of the operations of the external electronic device (101) described with reference to FIG. 11 may be combined with one or more other operations of the external electronic device (101) described with reference to FIG. 11.
[0125] As described above, the electronic device (102) can delay the time when the communication link (110) is released by performing operations to increase the number of times communication between the electronic device (102) and the external electronic device (101) can be performed through the communication link (110).
[0126] The operations described with reference to FIG. 11 may be combined with the operations described with reference to FIG. 4 through 10. For example, the electronic device (102) may reset the LSTO timer of the electronic device (102) and reduce the subrate factor based on the detection of a CRC error through CRC verification. However, the present disclosure is not limited thereto.
[0127] Figure 12 is a flowchart illustrating a method to disable the function of delaying the time when a communication link is released based on a CRC error.
[0128] Referring to FIG. 12, in operation 1210, the electronic device (102) may set the LSTO timer of the electronic device (102) to delay the time at which the communication link (110) is released based on the detection of a CRC error. For example, operation 1210 may correspond to operation 440 of FIG. 4.
[0129] In operation 1220, the electronic device (102), after performing operation 1210, can receive a packet from an external electronic device (101) via a communication link (110) using a communication circuit (230). The packet may include an access address corresponding to the communication link (110).
[0130] In operation 1230, the electronic device (102) may perform CRC verification with respect to the packet. For example, the CRC verification may be performed based on identifying that the packet has the access address corresponding to the communication link (110).
[0131] In operation 1240, the electronic device (102) can detect a CRC error through the CRC verification performed in operation 1230.
[0132] In operation 1250, the electronic device (102) may disable the function of delaying the time at which the communication link (110) is released based on the detection of the CRC error through the CRC verification. For example, the electronic device (102) may disable the function based on a past history of delaying the time at which the communication link (110) is released in operation 1210. For example, disabling the function may include disabling the LSTO timer of the electronic device (102) and / or refraining from running the LSTO timer of the electronic device (102) despite the CRC error. For example, depending on the disabling of the function, the LSTO timer of the electronic device (102) may be maintained to be run continuously in relation to the communication link (110) based on the CRC error, or the LSTO timer of the electronic device (102) may be run in relation to the communication link (110) based on the CRC error. For example, disabling the above function may include releasing the communication link (110) (immediately or directly) in response to the CRC error. For example, depending on disabling the above function, the communication link (110) may be released before the expiration of the LSTO timer.
[0133] As a non-limiting example, if the electronic device (102) reset the LSTO timer of the electronic device (102) despite a CRC error based on the identification that the number of times valid packets were not received consecutively (e.g., 6 times) is greater than the threshold number (e.g., 5 times), as described with reference to FIG. 10, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running based on the CRC error based on the identification that the number of times valid packets were not received consecutively (e.g., 6 times) after the reset is greater than the threshold number (e.g., 5 times). The operations of the electronic device (102) described with reference to FIG. 12 are described in more detail with reference to FIG. 13.
[0134] FIG. 13 illustrates an LSTO timer that is maintained to run continuously in relation to a communication link based on a CRC error depending on the deactivation of the function.
[0135] Referring to FIG. 13, an electronic device (102) can transmit a packet (308) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (308) to the external electronic device (101) according to a channel index of a connection event having an event counter (K) in response to an anchor point (344) of a connection event having an event counter (K). The external electronic device (101) can receive the packet (308) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive the packet (308) from the electronic device (102) based on identifying the anchor point (344) and the channel index. An external electronic device (101) may transmit a packet (307) (e.g., an acknowledgment packet) to an electronic device (102) via a communication link (110) based on receiving a packet (308). The electronic device (102) may receive a packet (307) from the external electronic device (101) via a communication link (110). For example, the electronic device (102) may receive a packet (307) from the external electronic device (101) based on identifying an anchor point (344) and the channel index.
[0136] The electronic device (102) may perform CRC verification with respect to the packet (307) based on identifying an access address corresponding to the communication link (110) from the packet (307). The electronic device (102) may reset the LSTO timer of the electronic device (102) that is running from an anchor point (not shown in FIG. 13) prior to the anchor point (344) (e.g., anchor point (342) of FIG. 3 or anchor point (342) of FIG. 5) based on the packet (307) being identified as an invalid packet through the CRC verification, as indicated by the indication (584). For example, the electronic device (102) can reset the LSTO timer of the electronic device (102) that is running from the anchor point (not shown in FIG. 13) prior to the anchor point (344) (e.g., anchor point (342) of FIG. 3 or anchor point (342) of FIG. 5) based on the detection of a CRC error through the CRC verification as indicated by the indication (330), as indicated by the indication (584).
[0137] As a non-limiting example, the electronic device (102) may disable the function of resetting the LSTO timer of the electronic device (102) despite a CRC error, based on the reset of the LSTO timer of the electronic device (102), when a condition defined in relation to the communication link (110) is satisfied (e.g., an example described with reference to FIG. 12).
[0138] The electronic device (102) can transmit a packet (1310) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (1310) to the external electronic device (101) according to the channel index of the connection event having an event counter (J) in response to an anchor point (1345) of a connection event having an event counter (J) (J is a natural number greater than K). The external electronic device (101) can receive a packet (1310) from the electronic device (102) via the communication link (110). Based on receiving the packet (1310), the external electronic device (101) can transmit a packet (1309) (e.g., an acknowledgment packet) to the electronic device (102) via the communication link (110).
[0139] The external electronic device (101) transmits a packet (1309) to the electronic device (102), but the electronic device (102) may not receive the packet (1309) from the external electronic device (101) via the communication link (110) within the connection event having an event counter (J). For example, the electronic device (102) may detect a reception synchronization timeout (1381) within the connection event having an event counter (J). The electronic device (102) may execute the LSTO timer of the electronic device (102) based on detecting the reception synchronization timeout (1381). For example, as indicated by the indication (1382), the LSTO timer of the electronic device (102) may be executed from the anchor point (1345).
[0140] The electronic device (102) can transmit a packet (1312) to an external electronic device (101) via a communication link (110). For example, the electronic device (102) can transmit a packet (1312) to the external electronic device (101) according to the channel index of the connection event having an event counter (J+1) in response to an anchor point (1346) of a connection event having an event counter (J+1). The external electronic device (101) can receive the packet (1312) from the electronic device (102) via the communication link (110). For example, the external electronic device (101) can receive the packet (1312) from the electronic device (102) based on identifying the anchor point (1346) and the channel index. An external electronic device (101) may transmit a packet (1311) (e.g., an acknowledgment packet) to an electronic device (102) via a communication link (110) based on receiving a packet (1312). The electronic device (102) may receive a packet (1311) from the external electronic device (101) via a communication link (110). For example, the electronic device (102) may receive a packet (1311) from the external electronic device (101) based on identifying an anchor point (1346) and the channel index.
[0141] The electronic device (102) may perform CRC verification in relation to the packet (1311) based on identifying an access address corresponding to the communication link (110) from the packet (1311). The electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running from the anchor point (1345) based on the packet (1311) being identified as an invalid packet through the CRC verification. For example, maintaining the LSTO timer of the electronic device (102) to continue running from the anchor point (1345) may be performed based on the deactivation of the function. For example, the electronic device (102) may maintain the LSTO timer of the electronic device (102) to continue running from the anchor point (1345) based on the detection of a CRC error through the CRC verification as indicated by the indication (1331). As a non-limiting example, the electronic device (102) may release the communication link (110) based on the detection of the CRC error through the CRC verification, as indicated by the indication (1331). The release of the communication link (110) may be performed based on the deactivation of the function. As a non-limiting example, the release of the communication link (110) may be performed before the LSTO timer of the electronic device (102) expires according to the value of the LSTO timer of the electronic device (102) (e.g., negotiated with the external electronic device (101)) so as to be continuously executed from the anchor point (1345).
[0142] The operations of the electronic device (102) described above can be performed by the electronic device (1401) of FIG. 14. The operations of the external electronic device (101) described above can be performed by the electronic device (1402) of FIG. 14.
[0143] FIG. 14 is a block diagram of an electronic device (1401) in a network environment (1400) according to various embodiments. Referring to FIG. 14, in the network environment (1400), the electronic device (1401) may communicate with an electronic device (1402) through a first network (1498) (e.g., a short-range wireless communication network) or may communicate with at least one of an electronic device (1404) or a server (1408) through a second network (1499) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (1401) may communicate with the electronic device (1404) through a server (1408). According to one embodiment, the electronic device (1401) may include a processor (1420), memory (1430), input module (1450), sound output module (1455), display module (1460), audio module (1470), sensor module (1476), interface (1477), connection terminal (1478), haptic module (1479), camera module (1480), power management module (1488), battery (1489), communication module (1490), subscriber identification module (1496), or antenna module (1497). In some embodiments, at least one of these components (e.g., connection terminal (1478)) may be omitted from the electronic device (1401), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (1476), camera module (1480), or antenna module (1497)) may be integrated into a single component (e.g., display module (1460)).
[0144] The processor (1420) can, for example, execute software (e.g., program (1440)) to control at least one other component (e.g., hardware or software component) of the electronic device (1401) connected to the processor (1420) and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (1420) can store commands or data received from other components (e.g., sensor module (1476) or communication module (1490)) in volatile memory (1432), process the commands or data stored in volatile memory (1432), and store the resulting data in non-volatile memory (1434). According to one embodiment, the processor (1420) may include a main processor (1421) (e.g., a central processing unit or an application processor) or an auxiliary processor (1423) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (1401) includes a main processor (1421) and an auxiliary processor (1423), the auxiliary processor (1423) may be configured to use less power than the main processor (1421) or to be specialized for a specified function. The auxiliary processor (1423) may be implemented separately from the main processor (1421) or as part thereof.
[0145] The auxiliary processor (1423) may control at least some of the functions or states associated with at least one component of the electronic device (1401) (e.g., display module (1460), sensor module (1476), or communication module (1490)) on behalf of the main processor (1421) while the main processor (1421) is in an inactive (e.g., sleep) state, or together with the main processor (1421) while the main processor (1421) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (1423) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (1480) or communication module (1490)). According to one embodiment, the auxiliary processor (1423) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (1401) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (1408)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.
[0146] The memory (1430) can store various data used by at least one component of the electronic device (1401) (e.g., processor (1420) or sensor module (1476)). The data may include, for example, input data or output data for software (e.g., program (1440)) and related commands. The memory (1430) may include volatile memory (1432) or non-volatile memory (1434).
[0147] The program (1440) may be stored as software in memory (1430) and may include, for example, an operating system (1442), middleware (1444), or an application (1446).
[0148] The input module (1450) can receive commands or data to be used for a component of the electronic device (1401) (e.g., processor (1420)) from outside the electronic device (1401) (e.g., user). The input module (1450) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).
[0149] The sound output module (1455) can output a sound signal to the outside of the electronic device (1401). The sound output module (1455) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.
[0150] The display module (1460) can visually provide information to an external (e.g., user) of the electronic device (1401). The display module (1460) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (1460) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.
[0151] The audio module (1470) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (1470) can acquire sound through the input module (1450) or output sound through the sound output module (1455) or an external electronic device (e.g., electronic device (1402)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (1401).
[0152] The sensor module (1476) can detect the operating state of the electronic device (1401) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (1476) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.
[0153] The interface (1477) may support one or more specified protocols that can be used for the electronic device (1401) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (1402)). According to one embodiment, the interface (1477) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.
[0154] The connection terminal (1478) may include a connector through which the electronic device (1401) can be physically connected to an external electronic device (e.g., electronic device (1402)). According to one embodiment, the connection terminal (1478) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).
[0155] The haptic module (1479) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (1479) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.
[0156] The camera module (1480) can capture still images and video. According to one embodiment, the camera module (1480) may include one or more lenses, image sensors, image signal processors, or flashes.
[0157] The power management module (1488) can manage the power supplied to the electronic device (1401). According to one embodiment, the power management module (1488) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).
[0158] The battery (1489) can supply power to at least one component of the electronic device (1401). According to one embodiment, the battery (1489) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
[0159] The communication module (1490) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (1401) and an external electronic device (e.g., electronic device (1402), electronic device (1404), or server (1408)), and the performance of communication through the established communication channel. The communication module (1490) may include one or more communication processors that operate independently of the processor (1420) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (1490) may include a wireless communication module (1492) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (1494) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (1404) via a first network (1498) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (1499) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (1492) can identify or authenticate the electronic device (1401) within a communication network such as the first network (1498) or the second network (1499) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (1496).
[0160] The wireless communication module (1492) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (1492) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (1492) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (1492) can support various requirements specified in the electronic device (1401), external electronic device (e.g., electronic device (1404)), or network system (e.g., second network (1499)). According to one embodiment, the wireless communication module (1492) can support a Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for realizing URLLC.
[0161] An antenna module (1497) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (1497) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (1497) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (1498) or a second network (1499), may be selected from the plurality of antennas, for example, by a communication module (1490). A signal or power may be transmitted or received between the communication module (1490) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (1497).
[0162] According to various embodiments, the antenna module (1497) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.
[0163] At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.
[0164] According to one embodiment, commands or data may be transmitted or received between the electronic device (1401) and an external electronic device (1404) through a server (1408) connected to a second network (1499). Each of the external electronic devices (1402, or 1404) may be the same or a different type of device as the electronic device (1401). According to one embodiment, all or part of the operations performed on the electronic device (1401) may be performed on one or more of the external electronic devices (1402, 1404, or 1408). For example, if the electronic device (1401) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (1401) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (1401). The electronic device (1401) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (1401) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In one embodiment, the external electronic device (1404) may include an Internet of Things (IoT) device. The server (1408) may be an intelligent server using machine learning and / or neural networks.According to one embodiment, an external electronic device (1404) or server (1408) may be included within the second network (1499). The electronic device (1401) may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.
[0165] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure pertains.
[0166] As described above, an electronic device (e.g., electronic device (102)) may include a communication circuit for BLE (Bluetooth low energy) (e.g., communication circuit (230)), at least one processor (e.g., at least one processor (210)) including a processing circuit, and a memory (e.g., memory (220)) including one or more storage media for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the electronic device may be caused to receive a packet from an external electronic device via a communication link established between the electronic device and the external electronic device using the communication circuit, perform a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link, and reset a link supervision timeout (LSTO) timer running in relation to the communication link based on the detection of a CRC error through the CRC verification.
[0167] The above instructions may cause the electronic device to maintain the LSTO timer to continue executing in relation to the communication link based on the detection of a receive synchronization timeout in relation to the communication link when executed individually or collectively by the at least one processor.
[0168] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the payload of the packet to be discarded based on the detection of the CRC error through the CRC verification.
[0169] The above instructions, when executed individually or collectively by the at least one processor, may cause the electronic device to receive the packet transmitted from the external electronic device within the connection event based on identifying the anchor point of the connection event associated with the communication link and the channel index of the connection event.
[0170] The above instructions may cause the electronic device to reset the LSTO timer running in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the data rate of the packet is identified as being lower than the threshold data rate when the above instructions are executed individually or collectively by the at least one processor, and to maintain the LSTO timer to continue running in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the data rate of the packet is identified as being higher than the threshold data rate.
[0171] The above instructions may cause the electronic device to reset the LSTO timer being executed in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the size of the payload of the packet is identified as being smaller than the threshold size when the above instructions are executed individually or collectively by the at least one processor, and to maintain the LSTO timer to be executed continuously in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the size of the payload of the packet is identified as being larger than the threshold size.
[0172] The above instructions may cause the electronic device to reset the LSTO timer being executed in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the number of transmissions available for the communication link is identified as being less than the threshold number of transmissions, and to maintain the LSTO timer to be executed continuously in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the number of transmissions available for the communication link is identified as being more than the threshold number of transmissions.
[0173] The number of transmissions available for the communication link can be identified based on the value of the connection event interval for the communication link, the value of the connection peripheral delay for the communication link, and the value of the LSTO timer.
[0174] The above instructions may cause the electronic device to reset the LSTO timer that is being executed in relation to the communication link based on the fact that, when executed individually or collectively by the at least one processor, the CRC error is detected through the CRC verification and the number of times a valid packet has not been continuously received from the external electronic device through the communication link is identified as being greater than a threshold number, and to maintain the LSTO timer so as to be continuously executed in relation to the communication link based on the fact that the CRC error is detected through the CRC verification and the number of times a valid packet has not been continuously received from the external electronic device through the communication link is identified as being less than the threshold number.
[0175] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the packet to extend the length of the connection event to additionally transmit one or more packets within the connection event transmitted from the external electronic device, based on the detection of the CRC error through the CRC verification.
[0176] When the above instructions are executed individually or collectively by the at least one processor, the electronic device may be caused to transmit a packet containing a field indicating that more data is enabled to the external electronic device via the communication link using the communication circuit, based on the detection of the CRC error through the CRC verification.
[0177] When the above instructions are executed individually or collectively by the at least one processor, they may cause the electronic device to reduce the subrate factor until a valid packet is received from the external electronic device through the communication link, based on the detection of the CRC error through the CRC verification.
[0178] The above instructions may cause the electronic device to disable the skipping of one or more connection events for the communication link, which are performed according to the value of the connection peripheral delay for the communication link, based on the detection of the CRC error through the CRC verification when executed individually or collectively by the at least one processor.
[0179] The above instructions may cause the electronic device to reset the LSTO timer being executed in relation to the communication link based on the detection in relation to the communication link that a valid packet is received from the external electronic device through the communication link when executed individually or collectively by the at least one processor.
[0180] A method of an electronic device (e.g., electronic device (102) or external electronic device (101)) as described above may include the operation of receiving a packet from an external electronic device through a communication link established between the electronic device and the external electronic device, the operation of performing a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link, and the operation of resetting a link supervision timeout (LSTO) timer running in relation to the communication link based on detecting a CRC error through the CRC verification.
[0181] The above method may include an operation to maintain the LSTO timer so as to be continuously executed in relation to the communication link based on the detection of a receive synchronization timeout in relation to the communication link.
[0182] The above method may include an operation to discard the payload of the packet based on the detection of the CRC error through the CRC verification.
[0183] The above method may include the operation of receiving the packet transmitted from the external electronic device within the connection event based on identifying the anchor point of the connection event associated with the communication link and the channel index of the connection event.
[0184] The above method may include an operation to reset the LSTO timer being executed in relation to the communication link based on the detection in relation to the communication link that a valid packet is received from the external electronic device through the communication link.
[0185] A non-transient computer-readable storage medium as described above may store one or more programs. The one or more programs may include instructions that cause the electronic device to receive a packet from the external electronic device through a communication link established between the electronic device and the external electronic device when executed by the electronic device (e.g., electronic device (102) or external electronic device (101)), perform a cyclic redundancy check (CRC) verification with respect to the packet based on identifying that the packet has an access address corresponding to the communication link, and reset a link supervision timeout (LSTO) timer being executed in relation to the communication link based on the detection of a CRC error through the CRC verification.
[0186] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs.
[0187] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.
[0188] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.
[0189] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).
[0190] Various embodiments of the present document may be implemented as software (e.g., program (1440)) comprising one or more instructions stored in a storage medium (e.g., internal memory (1436) or external memory (1438)) readable by a machine (e.g., electronic device (1401)). For example, a processor (e.g., processor (1420)) of the machine (e.g., electronic device (1401)) may call at least one of the one or more instructions stored from the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.
[0191] According to one embodiment, the method according to the various embodiments disclosed herein may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.
[0192] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
Claims
1. In an electronic device, Communication circuit for BLE (Bluetooth Low Energy); At least one processor including a processing circuit; and The memory includes one or more storage media for storing instructions, and the instructions, when executed individually or collectively by the at least one processor, Using the above communication circuit, a packet is received from an external electronic device through a communication link established between the electronic device and the external electronic device, and Based on identifying that the above packet has an access address corresponding to the communication link, cyclic redundancy check (CRC) verification is performed with respect to the packet, and Based on the detection of a CRC error through the above CRC verification, to reset the LSTO (link supervision timeout) timer running in relation to the communication link, causing the above electronic device, Electronic device.
2. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the detection of a receive synchronization timeout in relation to the communication link, to maintain the LSTO timer to be continuously executed in relation to the communication link, causing the above electronic device, Electronic device.
3. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the detection of the above CRC error through the above CRC verification, to discard the payload of the above packet, causing the above electronic device, Electronic device.
4. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on identifying the anchor point of the connection event associated with the communication link and the channel index of the connection event, to receive the packet transmitted from the external electronic device within the connection event, causing the above electronic device, Electronic device.
5. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the fact that the above CRC error is detected through the above CRC verification and the data rate of the packet is identified as being lower than the threshold data rate, the above LSTO timer running in relation to the communication link is reset, and Based on the fact that the above CRC error is detected through the above CRC verification and the data rate of the packet is identified as being higher than the threshold data rate, the LSTO timer is maintained to be continuously executed in relation to the communication link, causing the above electronic device, Electronic device.
6. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the fact that the above CRC error is detected through the above CRC verification and that the size of the payload of the packet is identified as being smaller than the threshold size, the above LSTO timer running in relation to the communication link is reset, and Based on the fact that the above CRC error is detected through the above CRC verification and that the size of the payload of the above packet is identified as being larger than the threshold size, the LSTO timer is maintained to be continuously executed in relation to the communication link, causing the above electronic device, Electronic device.
7. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the fact that the above CRC error is detected through the above CRC verification and that the number of transmissions available for the communication link is identified as being less than the threshold number of transmissions, the above LSTO timer running in relation to the communication link is reset, and Based on the fact that the above CRC error is detected through the above CRC verification and the number of transmissions available for the communication link is identified as being greater than the threshold number of transmissions, the above LSTO timer is maintained to be continuously executed in relation to the communication link. causing the above electronic device, Electronic device.
8. In claim 7, the number of transmissions available for the communication link is, Identified according to the value of the connection event interval for the communication link, the value of the connection peripheral delay for the communication link, and the value of the LSTO timer, Electronic device.
9. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the fact that the above CRC error is detected through the above CRC verification and that the number of times valid packets have not been continuously received from the external electronic device through the communication link is identified as being greater than a threshold number, the above LSTO timer running in relation to the communication link is reset, and Based on the fact that the above CRC error is detected through the above CRC verification and the number of times a valid packet has not been continuously received from the external electronic device through the communication link is identified as being less than the above threshold number, the LSTO timer is maintained to be continuously executed in relation to the communication link. causing the above electronic device, Electronic device.
10. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the detection of the above CRC error through the above CRC verification, the length of the connection event is extended to additionally transmit one or more packets within the connection event transmitted from the external electronic device. causing the above electronic device, Electronic device.
11. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the detection of the above CRC error through the above CRC verification, the communication circuit is used to transmit a packet containing a field indicating that more data is enabled to the external electronic device via the communication link. causing the above electronic device, Electronic device.
12. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the detection of the above CRC error through the above CRC verification, to reduce the subrate factor until a valid packet is received from the external electronic device through the communication link, causing the above electronic device, Electronic device.
13. In claim 1, when the instructions are executed individually or collectively by the at least one processor, Based on the fact that the above CRC error is detected through the above CRC verification, to disable the skipping of one or more connection events for the communication link performed according to the value of the connection peripheral delay for the communication link, causing the above electronic device, Electronic device.
14. In a method of an electronic device, The operation of receiving a packet from an external electronic device through a communication link established between the electronic device and the external electronic device, and An operation to perform cyclic redundancy check (CRC) verification with respect to said packet based on identifying that said packet has an access address corresponding to said communication link, and Based on the detection of a CRC error through the above CRC verification, the operation of resetting the LSTO (link supervision timeout) timer running in relation to the communication link is included. method.
15. In a non-transient computer-readable storage medium storing one or more programs, said one or more programs, when executed by an electronic device, Receiving a packet from an external electronic device through a communication link established between the electronic device and the external electronic device, and Based on identifying that the above packet has an access address corresponding to the communication link, cyclic redundancy check (CRC) verification is performed with respect to the packet, and Based on the detection of a CRC error through the above CRC verification, to reset the LSTO (link supervision timeout) timer running in relation to the above communication link, Including instructions that cause the above electronic device, Computer-readable storage media.
