Method and device for providing bluetooth low energy service

Abstract

An operation method of a first electronic device in a wireless communication system according to an embodiment of the present disclosure may comprise the actions of: transmitting, during a first sub-event within a first event, a first frame including a first payload composed of first blocks and a second payload composed of second blocks; receiving, during the first sub-event within the first event from a second electronic device, a Nack message indicating that at least one block among the first blocks and the second blocks is not received; and, during a second sub-event subsequent to the first sub-event within the first event, repeatedly transmitting the at least one block corresponding to the Nack message to the second electronic device.

Description

Method and device for providing low-power Bluetooth service

[0001] The present disclosure relates to a method of an electronic device providing a BLE service based on limited resources.

[0002] The Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched.

[0003] In an IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects, creating new value in human life. IoT, through the convergence and integration of existing IT (information technology) technologies with various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] LE (low energy) electronic devices with Bluetooth Core Version 5.2 or later can support BLE audio services through BIS (broadcast isochronous stream) or CIS (connected isochronous stream) methods.

[0005] Recently, the use of BLE audio services through BIS or CIS methods is expanding for the purpose of providing audio services simultaneously to a small group of users rather than an unspecified number of users, such as TVs or mobile electronic devices.

[0006] The present disclosure proposes a method for transmitting reliable BLE data.

[0007] According to one embodiment, a method of operating a first electronic device in a wireless communication system may include: transmitting, in a first sub-event within a first event, a first frame including a first payload comprised of first blocks and a second payload comprised of second blocks; receiving, in the first sub-event within the first event, a Nack message from a second electronic device indicating that at least one block among the first blocks and the second blocks is not received; and, in a second sub-event subsequent to the first sub-event within the first event, repeatedly transmitting, to the second electronic device, the at least one block corresponding to the Nack message.

[0008] According to one embodiment, a method of operating a second electronic device in a wireless communication system may include: receiving, in a first sub-event within a first event, a first frame from the first electronic device, the first frame including a first payload comprised of first blocks and a second payload comprised of second blocks; transmitting, in the first sub-event within the first event, a Nack message to the first electronic device, the Nack message indicating that at least one block among the first blocks and the second blocks is not received; and in a second sub-event subsequent to the first sub-event within the first event, repeatedly receiving, from the first electronic device, the at least one block corresponding to the Nack message.

[0009] According to one embodiment, in a wireless communication system, a first electronic device includes a transceiver; and a control unit. The control unit may control, in a first sub-event within a first event, to transmit a first frame including a first payload composed of first blocks and a second payload composed of second blocks, to receive, from a second electronic device, a Nack message indicating that at least one block among the first blocks and the second blocks is not received in the first sub-event within the first event, and to repeatedly transmit, to the second electronic device, the at least one block corresponding to the Nack message in a second sub-event subsequent to the first sub-event within the first event.

[0010] According to one embodiment, in a wireless communication system, a second electronic device includes a transceiver; and a control unit. The control unit may receive, in a first sub-event within a first event, a first frame including a first payload composed of first blocks and a second payload composed of second blocks from the first electronic device, transmit, in the first sub-event within the first event, a Nack message indicating that at least one block among the first blocks and the second blocks is not received to the first electronic device, and in a second sub-event subsequent to the first sub-event within the first event, repeatedly receive, from the first electronic device, the at least one block corresponding to the Nack message.

[0011] A method and device according to one embodiment of the present disclosure can broadcast reliable BLE audio data.

[0012] Additionally, the method and device according to one embodiment of the present disclosure can increase the probability of successful packet reception by a sink electronic device.

[0013] FIG. 1 illustrates a system including a plurality of electronic devices according to one embodiment of the present disclosure.

[0014] FIG. 2 illustrates an example of a plurality of electronic devices performing communication via a CIS method according to one embodiment of the present disclosure.

[0015] FIG. 3 illustrates an example of a plurality of electronic devices performing communication via a BIS method according to one embodiment of the present disclosure.

[0016] FIG. 4A and FIG. 4B illustrate an example of a plurality of electronic devices transmitting audio data via the CIS method according to one embodiment of the present disclosure.

[0017] FIG. 5 illustrates an example of a plurality of electronic devices transmitting data using HDT (higher data throughput) multi-block according to one embodiment of the present disclosure.

[0018] FIG. 6 illustrates an example of an HDT packet format according to one embodiment of the present disclosure.

[0019] FIG. 7 illustrates an example of a control header in an HDT packet format according to one embodiment of the present disclosure.

[0020] FIG. 8 illustrates an example of a PDU header in an HDT packet format according to one embodiment of the present disclosure.

[0021] FIG. 9 illustrates an example of retransmitting an HDT packet in a CIS manner according to one embodiment of the present disclosure.

[0022] FIG. 10 illustrates another example of retransmitting an HDT packet in a CIS manner according to one embodiment of the present disclosure.

[0023] FIG. 11 and FIG. 12 illustrate an example of transmitting an HDT multi-block in a CIS manner according to one embodiment of the present disclosure.

[0024] FIG. 13 and FIG. 14 illustrate another example of transmitting HDT multi-blocks in a CIS manner according to one embodiment of the present disclosure.

[0025] FIG. 15 illustrates an example of a case where block repetition transmission is not performed according to one embodiment of the present disclosure.

[0026] FIG. 16 illustrates an example of adjustable block repetition according to one embodiment of the present disclosure.

[0027] FIG. 17 illustrates a configuration of a first electronic device according to one embodiment of the present disclosure.

[0028] FIG. 18 illustrates a configuration of a second electronic device according to one embodiment of the present disclosure.

[0029] FIG. 19 illustrates an example of determining the number of retransmissions of a block without transmitting messages between electronic devices according to one embodiment of the present disclosure.

[0030] FIG. 20 illustrates an example of a PDU header in an HDT packet format according to one embodiment of the present disclosure.

[0031] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings. In describing an embodiment of the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of an embodiment of the present disclosure, such detailed description will be omitted. The terms described below are defined in consideration of the functions of an embodiment of the present disclosure, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents throughout this specification.

[0032] It should be noted that the technical terms used in this specification are merely used to describe specific embodiments and are not intended to limit the embodiments of the present disclosure. Alternatively, unless specifically defined otherwise herein, the technical terms used in this specification should be interpreted as having a meaning generally understood by those skilled in the art to which the present disclosure pertains, and should not be interpreted in an excessively broad or narrow sense. Alternatively, if a technical term used in this specification is an incorrect technical term that does not accurately express the spirit of the present disclosure, it should be replaced with a technical term that can be correctly understood by a person skilled in the art. Alternatively, general terms used in an embodiment of the present disclosure should be interpreted as defined in a dictionary or according to the context, and should not be interpreted in an excessively narrow sense.

[0033] Alternatively, the singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consist of" or "comprises" should not be construed to necessarily include all of the various components or various operations described in the specification, and should be construed to mean that some of the components or some of the operations may not be included, or that additional components or operations may be included.

[0034] Alternatively, terms including ordinal numbers, such as "first," "second," etc., used herein may be used to describe various components, but the components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component."

[0035] When a component is referred to as being "connected" or "connected" to another component, it may be directly connected or connected to that other component, but there may also be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0036] Hereinafter, an embodiment according to the present disclosure will be described in detail with reference to the attached drawings. Regardless of the drawing numbers, identical or similar components will be given the same reference numbers and redundant descriptions thereof will be omitted. Alternatively, when describing an embodiment of the present disclosure, if it is determined that a detailed description of a related known technology may obscure the gist of the present disclosure, the detailed description thereof will be omitted. Alternatively, it should be noted that the attached drawings are only intended to facilitate easy understanding of the spirit of the present disclosure and should not be construed as limiting the spirit of the present disclosure by the attached drawings. The spirit of the present disclosure should be construed to extend to all modifications, equivalents, and substitutes other than the attached drawings.

[0037] LE electronic devices with Bluetooth Core Version 5.2 or later can support BLE audio services via the connected isochronous stream (CIS) method or the broadcast isochronous stream (BIS) method.

[0038] The CIS method is an acknowledgment protocol, allowing a CIS sink device to send feedback on data transmitted by a CIS source device. CIS is a unicast method, allowing one-to-one communication between a CIS source device and a CIS sink device.

[0039] BIS is a non-acknowledgment protocol. A BIS source device can broadcast data to multiple BIS sink devices using a broadcast method. To ensure data reliability when using BIS, the BIS source device can retransmit the same data multiple times.

[0040] The term 'electronic device' as used herein may be referred to as a terminal, a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit (SS), a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmit / receive unit (WTRU), a mobile node, a mobile, or other terms. Various embodiments of the electronic device may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals that integrate combinations of such functions. In addition, the electronic device may include, but is not limited to, a machine-to-machine (M2M) terminal, a machine-type communication (MTC) terminal / device. In this specification, an electronic device may also be referred to simply as a device or apparatus.

[0041] FIG. 1 illustrates a system including a plurality of electronic devices according to one embodiment of the present disclosure.

[0042] Referring to FIG. 1, a first electronic device (100) functions as a CIS source device or a BIS source device and can transmit (or broadcast) data to at least one sink device. The second electronic device (110) to the seventh electronic device (160) function as a CIS sink device or a BIS sink device and can receive data transmitted (or broadcast) from the source device. For convenience of explanation, FIG. 1 illustrates one source device and six sink devices, but the technical idea of ​​the present disclosure is not limited thereto, and the number of source devices and / or sink devices may be implemented in various ways.

[0043] For example, the first electronic device (100) may be implemented as a portable communication device (e.g., a smartphone or a Bluetooth speaker) and may transmit (or broadcast) audio data via BLE. The second electronic device (110) and the third electronic device (120) may be implemented as a pair of wireless earphones worn on the user's left and right ears, respectively, and may receive audio data transmitted (or broadcasted) from the first electronic device (100). The fourth electronic device (130) and the fifth electronic device (140) may be implemented as a pair of wireless earphones worn on the user's left and right ears, respectively, and may receive audio data transmitted (or broadcasted) from the first electronic device (100). The sixth electronic device (150) and the seventh electronic device (160) may be implemented as a pair of wireless earphones worn on the user's left and right ears, respectively, and may receive audio data transmitted (or broadcasted) from the first electronic device (100).

[0044] According to one embodiment, each of the second electronic device (110) to the seventh electronic device (160) may operate as an independent sink device and receive audio data transmitted (or broadcasted) from the first electronic device (100).

[0045] The first electronic device (100) can transmit (or broadcast) configuration information necessary for the second electronic device (110) to the seventh electronic device (160) to receive data, respectively. Each of the second electronic device (110) to the seventh electronic device (160) can receive data based on the configuration information transmitted (or broadcast) by the first electronic device (100).

[0046] FIG. 2 illustrates an example of a plurality of electronic devices performing communication via a CIS method according to one embodiment of the present disclosure.

[0047] CIS stands for isochronous data logical transport, which allows connected electronic devices to transmit isochronous data unidirectionally and / or bidirectionally. Isochronous data can be transmitted on an LE-S or LE-F logical link using CIS logical transport, and each CIS can be connected to an LE asynchronous connection (LE ACL). Each CIS event can support variable-size packets and / or the transmission of one or more packets.

[0048] Each connected isochronous group (CIG) event can occur at a periodic isochronous interval (ISO). For example, a CIG event can be implemented in a range of 5 ms to 4 s in multiples of 1.25 ms. A CIG event can include at least one CIS event. A CIS event can be a time resource allocated for unicast communication between a source device and a specific sink device.

[0049] Referring to FIG. 2, a first CIG event (CIG Event x) may include a first CIS event (CIS 0 Event y) and a second CIS event (CIS 1 Event y). The first CIS event (CIS 0 Event y) may be a time resource for transmitting and receiving audio data of a preset size for a left channel (Left) (e.g., a left device among a pair of wireless earphones) of a source device and a sink device. The second CIS event (CIS 1 Event y) may be a time resource for transmitting and receiving audio data of a preset size for a right channel (Right) (e.g., a right device among a pair of wireless earphones) of a source device and a sink device.

[0050] In each of the first CIS event (CIS 0 Event y) and the second CIS event (CIS 1 Event y), the source device can perform a BLE role as a central (C) and the sink device can perform a BLE role as a peripheral (P). In each of the first CIS event (CIS 0 Event y) and the second CIS event (CIS 1 Event y), in the "C->P" section, the source device can transmit audio data to the sink device, and in the "P->C" section, the sink device can transmit feedback (ACK / NACK) for the audio data to the source device.

[0051] In one embodiment, a maximum delay allowable point in time for the yth audio frame (or audio data) may be set. For example, if the content of the source device includes a video (e.g., YouTube, a game, etc.), issues may arise not only with simultaneous playback (synchronization) between sink devices, but also with audio / video sync (A / V sync) between the video played on the source device and the audio played on the sink devices, and the sink device needs to receive the data until the maximum delay allowable point in time. For example, in the case of a game, since there is no time to play the delay through video buffering when considering the responsiveness felt by the user, scalability issues may arise as the number of audio sink devices increases.

[0052] After an isochronous interval from the start time of a first CIG event (CIG Event x), a second CIG event (CIG Event x+1) may occur. The second CIG event (CIG Event x+1) may include a third CIS event (CIS 0 Event y+1) and a second CIS event (CIS 1 Event y+1). The third CIS event (CIS 0 Event y+1) may be a time resource for transmitting and receiving audio data for a left channel (Left) of a source device and a sink device (e.g., a left device of a pair of wireless earphones). The second CIS event (CIS 1 Event y+1) may be a time resource for transmitting and receiving audio data for a right channel (Right) of a source device and a sink device (e.g., a right device of a pair of wireless earphones).

[0053] In one embodiment, a maximum delay allowance for the y+1th audio frame (or audio data) may be set.

[0054] FIG. 3 illustrates an example of a plurality of electronic devices performing communication via a BIS method according to one embodiment of the present disclosure.

[0055] In Fig. 3, when transmitting audio frames via the BIS method rather than the CIS method, data transmission can be possible before the playback time of each audio frame even if the number of sink devices increases (enhanced scalability). However, due to the nature of the BIS method not receiving feedback (ACK / NACK) on whether each sink device has received data, the PER (packet error rate) may be relatively higher than that of the CIS method. To address this, the source device may repeatedly transmit the same data (packet) multiple times.

[0056] Broadcasting can be a method of streaming data (or audio frames) from at least one source device to multiple sink devices using a group of synchronized streams. Each stream used in broadcasting can be referred to as a broadcast isochronous stream (BIS), and a group of BISs can be referred to as a broadcast isochronous group (BIG).

[0057] A BIS logical transport can be used to transmit one or more isochronous data streams to all devices within the BIS (e.g., within a certain distance). A BIS can contain one or more subevents for transmitting isochronous data packets. A BIS can support the transmission of multiple isochronous data packets within each BIS event.

[0058] Referring to FIG. 3, a first BIG event (BIG Event x) may include a first BIS event (BIS 0 Event y) and a second BIS event (BIS 1 Event y). The first BIS event (BIS 0 Event y) may be a time resource for a source device to broadcast audio data (or audio frame) of a preset size for a left channel (Left) of at least one sink device (e.g., a left device of a pair of wireless earphones). The second BIS event (BIS 1 Event y) may be a time resource for a source device to broadcast audio data (or audio frame) of a preset size for a right channel (Right) of at least one sink device (e.g., a right device of a pair of wireless earphones).

[0059] In a first BIS event (BIS 0 Event y), the source device can transmit the yth audio frame for the left channel (Left) of at least one sink device, for example, three times. In a second BIS event (BIS 1 Event y), the source device can transmit the yth audio frame for the right channel (Right) of at least one sink device, for example, three times.

[0060] In one embodiment, a maximum delay allowance point for the yth audio frame (or audio data) may be set. In FIG. 3, the audio frame is transmitted using the BIS method, so that multiple sink devices can receive the yth audio frame before the maximum delay allowance point.

[0061] A second BIG event (BIG Event x+1) may occur after an ISO interval from the start time of a first BIG event (BIG Event x). The second BIG event (BIG Event x+1) may include a third BIS event (BIS 0 Event y+1) and a fourth BIS event (BIS 1 Event y+1). The third BIS event (BIS 0 Event y+1) may be a time resource for a source device to broadcast audio data (or an audio frame) for a left channel (Left) of at least one sink device (e.g., a left device of a pair of wireless earphones). The fourth BIS event (BIS 1 Event y+1) may be a time resource for a source device to broadcast audio data (or an audio frame) for a right channel (Right) of at least one sink device (e.g., a right device of a pair of wireless earphones).

[0062] In the third BIS event (BIS 0 Event y+1), the source device can transmit the y+1th audio frame for the left channel (Left) of at least one sink device three times. In the fourth BIS event (BIS 1 Event y+1), the source device can transmit the y+1th audio frame for the right channel (Right) of at least one sink device three times.

[0063] In one embodiment, a maximum delay allowance point for the y+1th audio frame (or audio data) may be set. In FIG. 3, the audio frame is transmitted using the BIS method, so that multiple sink devices can receive the y+1th audio frame before the maximum delay allowance point.

[0064] FIG. 4A and FIG. 4B illustrate an example of a plurality of electronic devices transmitting audio data via the CIS method according to one embodiment of the present disclosure.

[0065] When transmitting audio data through an isochronous stream in LE Audio, a Number of Subevents (NSE), a Burst Number (BN), and a Flush Timeout (FT) can be set. The NSE indicates the number of times a packet can be transmitted, the BN indicates the number of payloads that can be transmitted in one event, and the FT indicates the lifetime of a payload in an event unit. According to one embodiment, a source device can transmit control information including an NSE, a BN, and a FT for at least one sink device to the at least one sink device.

[0066] Referring to FIG. 4A, a first CIG event (CIG Event X) may include a first CIS event (CIS 0 Event X) and a second CIS event (CIS 1 Event X). The first CIS event (CIS 0 Event X) may be a time resource for transmitting and receiving audio data of a preset size for a left channel (Left) (e.g., a left device among a pair of wireless earphones) of a source device and at least one sink device. The second CIS event (CIS 1 Event X) may be a time resource for transmitting and receiving audio data of a preset size for a right channel (Right) (e.g., a right device among a pair of wireless earphones) of a source device and at least one sink device.

[0067] In the first CIS event (CIS 0 Event X), the source device transmits a first audio frame (0) to the first sink device, and the first sink device can transmit an ACK message to the source device upon successfully receiving the first audio frame (0). In the first CIS event (CIS 0 Event X), the source device transmits a second audio frame (1) to the first sink device, and the first sink device can transmit an ACK message to the source device upon successfully receiving the second audio frame (1).

[0068] In a second CIS event (CIS 1 Event X), the source device transmits a first audio frame (0) to a second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the first audio frame (0). In a second CIS event (CIS 1 Event X), the source device transmits a second audio frame (1) to a second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the second audio frame (1).

[0069] The second CIG event (CIG Event X+1) may include a third CIS event (CIS 0 Event X+1) and a fourth CIS event (CIS 1 Event X+1).

[0070] In a third CIS event (CIS 0 Event X+1), the source device transmits a third audio frame (2) to the first sink device, and the first sink device can transmit an ACK message to the source device if it successfully receives the third audio frame (2). The source device transmits a fourth audio frame (3) to the first sink device, and the first sink device can transmit a NACK message to the source device if it does not successfully receive the fourth audio frame (3). The source device retransmits the fourth audio frame (3) to the first sink device, and may not receive an ACK message for the fourth audio frame (3) from the first sink device (Missing ACK). Thereafter, the source device retransmits the fourth audio frame (3) to the first sink device again, and the source device can successfully receive an ACK message for the fourth audio frame (3) from the first sink device.

[0071] At the fourth CIS event (CIS 1 Event X+1), the source device transmits a third audio frame (2) to the second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the third audio frame (2). At the fourth CIS event (CIS 1 Event X+1), the source device transmits a fourth audio frame (3) to the second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the fourth audio frame (3).

[0072] Referring to FIG. 4b, a first CIG event (CIG Event X) may include a first CIS event (CIS 0 Event X) and a second CIS event (CIS 1 Event X). Unlike the embodiment of FIG. 4a, in the embodiment of FIG. 4b, the source device may alternately transmit audio frames assigned to the first CIS event (CIS 0 Event X) and audio frames assigned to the second CIS event (CIS 1 Event X).

[0073] In a first CIS event (CIS 0 Event X), the source device transmits a first audio frame (0) to a first sink device, and the first sink device can transmit an ACK message to the source device upon successfully receiving the first audio frame (0). Thereafter, in a second CIS event (CIS 1 Event X), the source device transmits a first audio frame (0) to a second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the first audio frame (0). Thereafter, in a first CIS event (CIS 0 Event X), the source device transmits a second audio frame (1) to the first sink device, and the first sink device can transmit an ACK message to the source device upon successfully receiving the second audio frame (1). Thereafter, in a second CIS event (CIS 1 Event X), the source device transmits a second audio frame (1) to the second sink device, and the second sink device can transmit an ACK message to the source device upon successfully receiving the second audio frame (1).

[0074] FIG. 5 illustrates an example of a plurality of electronic devices transmitting data using HDT (higher data throughput) multi-block according to one embodiment of the present disclosure.

[0075] A higher data throughput (HDT) packet structure may be introduced for BLE high-speed transmission and / or high-quality audio. HDT multi-blocks can improve retransmission efficiency through selective ack.

[0076] Referring to FIG. 5, a source device (or first electronic device) may perform a BLE role as a central (C), and a sink device (or second electronic device) may perform a BLE role as a peripheral (P). The source device (or first electronic device) may transmit an HDT multi-block including a header, data block #0, data block #1, data block #2, etc. The sink device (or second electronic device) may transmit a selective feedback (Selective Ack) for the HDT multi-block.

[0077] FIG. 6 illustrates an example of an HDT packet format according to one embodiment of the present disclosure.

[0078] Referring to FIG. 6, the HDT packet format may be composed of four parts: a sync, a control header, a PDU header, and a payload zone. A first electronic device (or source device) may transmit an HDT multi-block (chunk), and a second electronic device (or sink device) may use a selective feedback (Selective Ack) method.

[0079] A first electronic device (or source device) may perform fragmentation and / or recombination on a first payload (payload 0) at a link layer to generate a first LL block (LL block #0) and a second LL block (LL block #1). The first electronic device (or source device) may perform fragmentation and / or recombination on a second payload (payload 1) at a link layer to generate a third LL block (LL block #0) and a fourth LL block (LL block #1).

[0080] A source device (or first electronic device) can transmit an HDT packet format as a central (C). The HDT packet format can transmit an LL block in each of PHY Interval #0, PHY Interval #1, and PHY Interval #2. The HDT packet format can include PITS and a Trailer. According to one embodiment, the maximum number of LL blocks in a single packet can be set to 16. According to one embodiment, the length of the PHY Interval and the data chunk can be set independently.

[0081] The sink device (or second electronic device) can transmit an optional ACK message for the HDT packet format to the source device (or first electronic device) as a peripheral (P).

[0082] FIG. 7 illustrates an example of a control header in an HDT packet format according to one embodiment of the present disclosure.

[0083] Referring to FIG. 7, the Control Header in the HDT packet format may include a PCA-A (Physical channel address - Air portion) field, a NESN (Next expected sequence number) field, a PFI (Packet format indicator) field, a RI (Rate indicator) field, an RFU (Reserved for future use) field, a PDU LEN (PDU length) field, a PDU HEADER LEN (PDU header length) field, a PHY INT (Physical layer interval size) field, and a HEC-C (Header Error Check-Control) field. According to one embodiment, the termination sequence (FEC TERM field and TERM field) may be only a part of bit processing.

[0084] For a description of each field included in the Control Header in the HDT packet format, see [Table 1].

[0085] [Table 1]

[0086]

[0087] The PDU LEN field may include a PDU HDR LEN field, a PHY INT field, and an RFU field. The PDU HDR LEN field may indicate the length of the PDU header in octets, and the PHY INT field may indicate the length of the payload area in octets.

[0088] FIG. 8 illustrates an example of a PDU header in an HDT packet format according to one embodiment of the present disclosure.

[0089] Referring to FIG. 8, the PDU header in the HDT packet format may include Initial Octets, Extended Header, Rx Portion, and Tx Portion.

[0090] The above Initial Octets may include an XHP field indicating whether an Extended Header field exists, an RxPP field indicating whether an Rx Portion exists (e.g., if RxPP=1, an Rx Portion exists, and if RxPP=0, an Rx Portion does not exist), an MD / CIE field identical to the existing LE specification, an SN (sequence number) field including the three LSBs of a sequence number, a TxPP field indicating whether a Tx Portion exists (e.g., if TxPP=1, a Tx Portion exists, and if TxPP=0, a Tx Portion does not exist), and an RFU field.

[0091] The above Extended Header may include Another Octet field, Feature Present field, and FIB (Feature Information Block) field.

[0092] The above Rx Portion may include an Rx Payload Map field and an Rx Bitmap field. The Rx Payload Map field may be composed of four 2-bit fields (e.g., 01 10 10 01). The Rx Payload Map field value may be set as shown in Table 2.

[0093] [Table 2]

[0094]

[0095] The Rx Bitmap field is located along the RxPayloadMap field in payload number order, and bit B (Blocked) can indicate whether block b has been acked. For example, bit 0 can indicate a block that has not been acked.

[0096] The above Tx Portion may include a Tx Payload Map field, a Tx RFU field, and an LL descriptor. If the Tx Portion does not exist, data may not be transmitted. Bit p of the Tx Payload Map field may indicate that payload SN + p is being transmitted.

[0097] The above LL descriptor may include a Payload Length field, an LLID field, a B (Blocked) field, an Nb field, a Block Size field, an RFU field, and a TxBlockMap field. The Payload Length field indicates the length of one PDU payload data, and the LLID field may be the same as the current LE specification. If the B (Blocked) field is set to 0, it may indicate the entire payload, and if the B (Blocked) field is set to 1, it may indicate that the payload is divided into blocks. The Nb field may indicate the number of blocks into which the payload data is divided (2 ≤ Nb ≤ 16), and the Block Size field may indicate the size of the block. The TxBlockMap field may be 8 bits when Nb ≤ 8, and 16 bits when Nb > 8.

[0098] FIG. 9 illustrates an example of retransmitting an HDT packet in a CIS manner according to one embodiment of the present disclosure.

[0099] Electronic devices can use block-level retransmission when transmitting HDT packets using the CIS method. However, there may be situations where retransmission occurs again after a single retransmission. While the retransmitted data can be sent to the next payload, for audio data, the next payload is typically not ready. As the retransmission success rate of an electronic device increases, the minimum value of the Flush Timeout (FT) required to ensure data reliability can be lowered, reducing latency.

[0100] Referring to FIG. 9, a single frame (either Frame 1 or Frame 4) may be split into two payloads, each of which may contain four blocks. For example, the first frame may be implemented as 3400 bytes, and one block within the payload may be implemented as 425 bytes.

[0101] In a first sub-event within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame including eight blocks. In a first sub-event within a first CIS event (CIS 0 Event X), a second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the eight blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 1_6 Nack, Payload 1_7 Nack) to the first electronic device (or source device) indicating that it did not receive a sixth block and a seventh block of the first payload within the first frame.

[0102] In a second sub-event within a first CIS event (CIS 0 Event X), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) to the second electronic device (or sink device) (e.g., block 6 and block 7 of the first payload within the first frame). In a second sub-event within a first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit a feedback message (Payload 1_6 Nack) to the first electronic device (or source device) indicating that it did not receive some of the retransmitted blocks (e.g., block 6 of the first payload within the first frame).

[0103] In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit at least one block within the first frame that requires retransmission (e.g., block 6 of the first payload within the first frame) and at least one block within the second frame. In a first sub-event within the first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether it has received each of the blocks transmitted from the first electronic device (or source device).

[0104] In a second sub-event within the second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit at least one block (e.g., the 8th block within the second frame) that was not transmitted within the second frame.

[0105] FIG. 10 illustrates another example of retransmitting an HDT packet in a CIS manner according to one embodiment of the present disclosure.

[0106] In FIG. 10, a first electronic device (or source device) can transmit data blocks (chunks) requiring retransmission multiple times within a single subevent. This allows a second electronic device (or sink device) to increase the reception probability for the retransmitted blocks. According to one embodiment, the first electronic device (or source device) and / or the second electronic device (or sink device) can further improve the reception probability for the retransmitted blocks by applying a HARQ scheme.

[0107] Referring to FIG. 10, a single frame (either Frame 1 or Frame 4) may be split into two payloads, each of which may contain four blocks. For example, the first frame may be implemented as 3400 bytes, and one block within the payload may be implemented as 425 bytes.

[0108] In a first sub-event within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame including eight blocks. In a first sub-event within a first CIS event (CIS 0 Event X), a second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the eight blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 1_6 Nack, Payload 1_7 Nack) to the first electronic device (or source device) indicating that it did not receive a sixth block and a seventh block of the first payload within the first frame.

[0109] In a second sub-event within a first CIS event (CIS 0 Event X), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) (e.g., the sixth block and the seventh block of the first payload within the first frame) to the second electronic device (or sink device) multiple times. For example, the first electronic device (or source device) may retransmit each of the sixth block and the seventh block of the first payload within the first frame four times. In a second sub-event within a first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit an Ack message to the first electronic device (or source device) indicating successful reception of the retransmitted blocks.

[0110] In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit a second frame including eight blocks. In a first sub-event within the second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the eight blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 2_3 Nack, Payload 2_4 Nack, Payload 3_5 Nack) to the first electronic device (or source device) indicating that it has not received the third and fourth blocks of the second payload and the fifth block of the third payload within the second frame.

[0111] In a second sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) (e.g., the third and fourth blocks of the second payload within the second frame, and the fifth block of the third payload) to the second electronic device (or sink device) multiple times. For example, the first electronic device (or source device) may retransmit the third block and the fourth block of the second payload three times each, and retransmit the fifth block of the third payload twice. In a second sub-event within a second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit an Ack message to the first electronic device (or source device) indicating successful receipt of the retransmitted blocks.

[0112] Various embodiments may be provided in the present disclosure for determining the number of retransmissions of a block requiring retransmission.

[0113] In one embodiment, the number of retransmissions of a block requiring retransmission may be determined based on a Flush Timeout (FT). The FT may be associated with the lifetime of a payload in the CIS method (used when calculating the flush point) and may directly affect the transport latency (Transport Latency CIG_Sync_Delay + ISO_Interval x FT - SDU_Interval). In one embodiment, when performing block retransmission, the number of retransmissions of a block may be determined by setting a weight for an imminent payload with a FT to minimize the payload being discarded.

[0114] According to one embodiment, a block retransmission number (BRN) satisfying mathematical expression 1 can be determined.

[0115] [Mathematical Formula 1]

[0116]

[0117] Here, the MLB can be a value converted to bytes as (MPT_C - min_overhead) as Maximum Length in Byte (min_overhead = Sync-word + CTRL Header + T_PDU_Header). The T_PDU_Header is the time taken to send the PDU_Header, but since the length of the PDU header in HDT is variable, it can be calculated assuming a set value. may be the sum of the lengths of the retransmission blocks of Payload R. The above α may be a ratio of allocating a portion of MPT_C for Priority Payload (0≤α≤Max_α, 0≤Max_α≤1).

[0118] In one embodiment, the α value may be adjusted based on the Remaining Subevent Number (RSN) (the smaller the RSN, the higher the α value). The RSN may be the number of subevents remaining before the FP (Flush Point) of a payload. The FP may be set to the point after a specific subevent of a specific CIS Event, at which the payload is discarded.

[0119] According to one embodiment, the RSN may be determined based on mathematical expression 2.

[0120] [Equation 2]

[0121]

[0122] Above is the Subevent order of the current subevent, and the above can be a Subevent order of FP (Flush Point).

[0123] FIG. 11 and FIG. 12 illustrate an example of transmitting an HDT multi-block in a CIS manner according to one embodiment of the present disclosure.

[0124] Referring to FIG. 11, the first frame (Frame 1) can be divided into four payloads (Payload 0 to Payload 3), and each of the four payloads (Payload 0 to Payload 3) can include four blocks. The second frame (Frame 2) can be divided into four payloads (Payload 4 to Payload 7), and each of the four payloads (Payload 4 to Payload 7) can include four blocks. For example, the first frame (Frame 1) and the second frame (Frame 2) can each be implemented with 1600 bytes, and one block within the payload can be implemented with 100 bytes.

[0125] ① In a first sub-event within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame including 16 blocks. ② In a first sub-event within a first CIS event (CIS 0 Event X), a second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the 16 blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 1_6 Nack, Payload 2_10 Nack, Payload 2_11 Nack) to the first electronic device (or source device) indicating that it has not received the 6th block of the first payload, and the 10th and 11th blocks of the second payload within the first frame.

[0126] ③ In a second sub-event within a first CIS event (CIS 0 Event X), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) (e.g., the 6th block of the first payload within the first frame, and the 10th and 11th blocks of the second payload) to the second electronic device (or sink device) multiple times. ④ In a second sub-event within a first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit an Ack message to the first electronic device (or source device) indicating successful reception of the retransmitted blocks.

[0127] In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit a second frame including 16 blocks. In a first sub-event within the second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the 16 blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 4_3 Nack, Payload 4_4 Nack, Payload 5_5 Nack, Payload 7_13 Nack) to the first electronic device (or source device) indicating that it has not received the third and fourth blocks of the fourth payload, the fifth block of the fifth payload, and the thirteenth block of the seventh payload within the second frame.

[0128] In a second sub-event within the second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) multiple times.

[0129] Referring to FIG. 11, a PDU Header in an HDT packet format may include Initial Octets, Extended Header, Rx Portion, and Tx Portion. According to one embodiment, the RFU field in the Initial Octets may include information indicating whether the corresponding block is a repeated block (block repetition; BR). For example, if BR=0, it may indicate that the block is not a repeated block, and if BR=1, it may indicate that the block is repeated. According to one embodiment, the Tx RFU field in the Tx Portion may include a block retransmission count (block repetition; BRN). The BRN may be determined by a controller (or source device).

[0130] Referring to FIGS. 11 and 12, ① in the first sub-event within the first CIS event (CIS 0 Event X), the first electronic device (or source device) may transmit an HDT packet including four payloads (Payload 0 to Payload 3). The SN (sequence number) of the HDT packet may be set to 000 and the BR (block repetition) may be set to 0. The TxPayloadMap field within the PDU header of the HDT packet may be set to, for example, 1111. The Payload Length field in the LL descriptor of the above HDT packet may be set to 400d (i.e., the length of the payload is 400 bytes), the LLID field may be set for each payload, the Blocked field may be set to 1 (i.e., indicating that the payload is divided into blocks), the Nb field may be set to 4d (i.e., the number of divided blocks is 4), the Block Size field may be set to 100d (i.e., the length of the block is 100 bytes), and the TxBlockMap field for all payloads may be set to "~1111" (i.e., transmitted in all blocks).

[0131] Referring to FIGS. 11 and 12, ② in the first sub-event within the first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit an HDT packet to the first electronic device (or source device) indicating that the 6th block of the first payload within the first frame and the 10th and 11th blocks of the second payload were not received. The NESN (Next expected sequence number) of the HDT packet may be set to, for example, 001. The RxPayloadMap field within the PDU header of the HDT packet may be set to "01 10 10 01" to indicate that the first payload and the second payload within the first frame were not received. The Rx Bitmap field for the first payload within the PDU header of the HDT packet may be set to "xxxx1101" to indicate a Nack for the 6th block of the first payload. The Rx Bitmap field for the second payload in the PDU header of the above HDT packet may be set to “xxxx1001” to indicate Nack for the 10th and 11th blocks of the second payload.

[0132] Referring to FIGS. 11 and 12, in the second sub-event within the ③ first CIS event (CIS 0 Event X), the first electronic device (or source device) may transmit an HDT packet for retransmitting the 6th block of the first payload within the first frame, and the 10th and 11th blocks of the second payload, to the second electronic device (or sink device) multiple times. The SN (sequence number) of the HDT packet may be set to 001, and the BR (block repetition) may be set to 0. The TxPayloadMap field within the PDU header of the HDT packet may be set to, for example, 0011. The Payload Length field in the LL descriptor of the above HDT packet may be set to 400d (i.e., the length of the payload is 400 bytes), the LLID field may be set for each payload, the Blocked field may be set to 1 (i.e., indicating that the payload is divided into blocks), the Nb field may be set to 4d (i.e., the number of divided blocks is 4), the Block Size field may be set to 100d (i.e., the length of the block is 100 bytes), the TxBlockMap field for the first payload may be set to "~0010" (i.e., the 6th block of the first payload may be transmitted), and the TxBlockMap field for the second payload may be set to "~0110" (i.e., the 10th and 11th blocks of the 12th payload may be transmitted).

[0133] In one embodiment, the Tx RFU field in the PDU header of the HDT packet may indicate a block repetition number (BRN). For example, if the Tx RFU field is set to 5d, the block to be retransmitted may be retransmitted five times. For example, the 6th block of the first payload in the first frame, and the 10th and 11th blocks of the second payload may each be repeatedly retransmitted five times. In this case, the 10th and 11th blocks of the second payload may be transmitted together or independently.

[0134] According to one embodiment, the RFU field in the LL descriptor of the HDT packet may be utilized as a Repeat offset bit. According to one embodiment, the RFU field is set to 1 bit, and if the value of the RFU field is 1, the number of repetitions for the corresponding payload may be reduced by 1. For example, if the value of the RFU field for the second payload is 1, each of the 10th and 11th blocks of the second payload may be retransmitted repeatedly 4 times (4=5-1).

[0135] Referring to FIGS. 11 and 12, in the second sub-event within the ④ first CIS event (CIS 0 Event X), the second electronic device (or sink device) may transmit an HDT packet indicating successful reception of retransmitted blocks to the first electronic device (or source device). The NESN of the HDT packet may be set to, for example, 100. The RxPayloadMap field within the PDU header of the HDT packet may be set to "01 01 01 01" to indicate successful reception of retransmitted blocks. According to one embodiment, the RxPP within the PDU header of the HDT packet may be set to 0.

[0136] FIG. 13 and FIG. 14 illustrate another example of transmitting HDT multi-blocks in a CIS manner according to one embodiment of the present disclosure.

[0137] Referring to FIG. 13, the first frame (Frame 1) can be divided into four payloads (Payload 0 to Payload 3), and each of the four payloads (Payload 0 to Payload 3) can include four blocks. The second frame (Frame 2) can be divided into four payloads (Payload 4 to Payload 7), and each of the four payloads (Payload 4 to Payload 7) can include four blocks. For example, the first frame (Frame 1) and the second frame (Frame 2) can each be implemented with 1600 bytes, and one block within the payload can be implemented with 100 bytes.

[0138] The operations of ①②③④ in Fig. 13 are identical to the operations of ①②③④ in Fig. 11 described above, so their description is omitted.

[0139] ⑤ In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit a second frame including 16 blocks. ⑥ In a first sub-event within a second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit a feedback message to the first electronic device (or source device) indicating whether each of the 16 blocks has been received. For example, the second electronic device (or sink device) may transmit a feedback message (Payload 4_3 Nack, Payload 4_4 Nack, Payload 5_5 Nack, Payload 7_13 Nack) to the first electronic device (or source device) indicating that it has not received the third and fourth blocks of the fourth payload, the fifth block of the fifth payload, and the thirteenth block of the seventh payload within the second frame.

[0140] ⑦ In a second sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may retransmit blocks corresponding to the Nack message received from the second electronic device (or sink device) multiple times. ⑧ In a second sub-event within a second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit an Ack message to the first electronic device (or source device) indicating successful reception of the retransmitted blocks.

[0141] Referring to FIG. 13, a PDU header in an HDT packet format may include Initial Octets, Extended Header, Rx Portion, and Tx Portion. According to one embodiment, an RFU field in the Initial Octets may include information indicating whether a corresponding block is a repeated block (block repetition; BR). For example, if BR=0, it may indicate that the block is not a repeated block, and if BR=1, it may indicate that the block is a repeated block. According to one embodiment, an RFU field in an LL descriptor of the PDU header may include a block retransmission count (block repetition; BRN) for each payload. The BRN may be determined by a controller (or source device).

[0142] Referring to FIGS. 13 and 14, in the first sub-event within the ⑤ second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit an HDT packet including four payloads (Payload 4 to Payload 7). The SN (sequence number) of the HDT packet may be set to 100 and the BR may be set to 0. The TxPayloadMap field within the PDU header of the HDT packet may be set to, for example, 1111. The Payload Length field in the LL descriptor of the above HDT packet may be set to 400d (i.e., the length of the payload is 400 bytes), the LLID field may be set for each payload, the Blocked field may be set to 1 (i.e., indicating that the payload is divided into blocks), the Nb field may be set to 4d (i.e., the number of divided blocks is 4), the Block Size field may be set to 100d (i.e., the length of the block is 100 bytes), and the TxBlockMap field for all payloads may be set to "~1111" (i.e., transmitted in all blocks).

[0143] Referring to FIGS. 13 and 14, in the first sub-event within the ⑥ second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit an HDT packet to the first electronic device (or source device) indicating that it did not receive the third and fourth blocks of the fourth payload within the second frame, the fifth block of the fifth payload, and the thirteenth block of the seventh payload. The NESN of the HDT packet may be set to, for example, 100. The RxPayloadMap field within the PDU header of the HDT packet may be set to "10 01 10 10" to indicate that the fourth, fifth, and seventh payloads within the second frame were not received. The Rx Bitmap field for the fourth payload within the PDU header of the HDT packet may be set to "xxxx0011" to indicate a Nack for the third and fourth blocks of the fourth payload. The Rx Bitmap field for the 5th payload in the PDU header of the HDT packet may be set to "xxxx1110" to indicate a Nack for the 5th block of the 5th payload. The Rx Bitmap field for the 7th payload in the PDU header of the HDT packet may be set to "xxxx1110" to indicate a Nack for the 13th block of the 7th payload.

[0144] Referring to FIGS. 13 and 14, in the second sub-event within the ⑦ second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit an HDT packet for retransmitting the third and fourth blocks of the fourth payload within the second frame, the fifth block of the fifth payload, and the thirteenth block of the seventh payload to the second electronic device (or sink device) multiple times. The SN of the HDT packet may be set to 100 and the BR may be set to 1. The TxPayloadMap field within the PDU header of the HDT packet may be set to, for example, 1011. The Payload Length field in the LL descriptor of the above HDT packet may be set to 400d (i.e., the length of the payload is 400 bytes), the LLID field may be set for each payload, the Blocked field may be set to 1 (i.e., indicating that the payload is divided into blocks), the Nb field may be set to 4d (i.e., the number of divided blocks is 4), the Block Size field may be set to 100d (i.e., the length of the block is 100 bytes), the TxBlockMap field for the fourth payload may be set to "~1100", the TxBlockMap field for the fifth payload may be set to "~0001", and the TxBlockMap field for the seventh payload may be set to "~0001".

[0145] In one embodiment, the RFU field in the LL descriptor of the HDT packet may indicate a block repetition number (BRN). For example, if the RFU field is set to 4, the block to be retransmitted may be retransmitted 4 times. For example, the 3rd and 4th blocks of the 4th payload in the 2nd frame, the 5th block of the 5th payload, and the 13th block of the 7th payload may be retransmitted 3 times. In this case, the 3rd and 4th blocks of the 4th payload may be transmitted together or independently.

[0146] Referring to FIGS. 13 and 14, in the second sub-event within the ⑧ second CIS event (CIS 0 Event X+1), the second electronic device (or sink device) may transmit an HDT packet to the first electronic device (or source device) indicating successful reception of retransmitted blocks. The NESN of the HDT packet may be set to, for example, 000. The RxPayloadMap field within the PDU header of the HDT packet may be set to "01 01 01 01" to indicate successful reception of retransmitted blocks. According to one embodiment, the RxPP within the PDU header of the HDT packet may be set to 0.

[0147] FIG. 15 illustrates an example of a case where block repetition transmission is not performed according to one embodiment of the present disclosure.

[0148] Referring to FIG. 15, an SDU frame (any one of SDU 1 to SDU 4) can be split into two payloads (e.g., Payload 0 and Payload 1 for SDU 1), and each of the two payloads (e.g., Payload 0 and Payload 1 for SDU 1) can include four blocks. For example, each SDU frame (any one of SDU 1 to SDU 4) can be implemented with 1600 bytes, and one block within the payload can be implemented with 200 bytes.

[0149] If block repetition is not applied, retransmissions for a specific block may continue to occur, and blocks that reach the Flush Point (FP) may be discarded. This disclosure proposes a method to ensure reliability by using a certain level of FP for each block.

[0150] In a first sub-event (SE) within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame (SDU 1) including eight blocks (1 to 8). If a second electronic device (or sink device) sends a Nack message for some blocks (e.g., blocks 1, 2, 7, and 8) among the eight blocks (1 to 8), in a second sub-event within the first CIS event (CIS 0 Event X), the first electronic device (or source device) may retransmit some blocks (e.g., blocks 1, 2, 7, and 8). Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks.

[0151] In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit some blocks (e.g., 1, 2, 7, 8) of the first frame for which a Nack message was received and some blocks (e.g., 1 to 4) of the second frame. The second electronic device (or sink device) may transmit an Ack / Nack message for each of the received blocks. In a second sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit some blocks (e.g., 2, 7, 8) of the first frame for which a Nack message was received and the remaining blocks (e.g., 5 to 8) of the second frame. Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks.

[0152] In a first sub-event within a third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may transmit some blocks (e.g., 7, 8) of the first frame for which the Nack message was received, some blocks (e.g., 5, 6) of the second frame for which the Nack message was received, and some blocks (e.g., 1 to 4) of the third frame. The second electronic device (or sink device) may transmit an Ack / Nack message for each of the blocks received. In a second sub-event within a third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may transmit some blocks (e.g., 8) of the first frame for which the Nack message was received, some blocks (e.g., 5) of the second frame for which the Nack message was received, and the remaining blocks (e.g., 5 to 8) of the third frame. Afterwards, the second electronic device (or sink device) can transmit an Ack / Nack message for each of the retransmitted blocks.

[0153] In a first sub-event within a fourth CIS event (CIS 0 Event X+3), the first electronic device (or source device) may transmit some blocks (e.g., 8) of the first frame for which a Nack message was received, some blocks (e.g., 5) of the second frame for which a Nack message was received, and some blocks (e.g., 1 to 6) of the fourth frame. The second electronic device (or sink device) may transmit an Ack / Nack message for each of the received blocks. In a second sub-event within a fourth CIS event (CIS 0 Event X+3), the first electronic device (or source device) may transmit some blocks (e.g., 5) of the second frame for which a Nack message was received, and the remaining blocks (e.g., 7 to 8) of the third frame. Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks.

[0154] In one embodiment, if the FP (Flush Point) for blocks within the first frame is after the fourth CIS event (CIS 0 Event X+3), the blocks within the first frame may not be discarded. In one embodiment, the first electronic device (or source device) and / or the second electronic device (or sink device) may perform retransmission by considering the FP of each block within the frame so that each block is not discarded. In one embodiment, if the FP for blocks within the second frame is after the fifth CIS event (CIS 0 Event X+4), the blocks within the second frame may not be discarded.

[0155] FIG. 16 illustrates an example of adjustable block repetition according to one embodiment of the present disclosure.

[0156] Referring to FIG. 16, an SDU frame (any one of SDU 1 to SDU 4) can be split into two payloads (e.g., Payload 0 and Payload 1 for SDU 1), and each of the two payloads (e.g., Payload 0 and Payload 1 for SDU 1) can include four blocks. For example, each SDU frame (any one of SDU 1 to SDU 4) can be implemented with 1600 bytes, and one block within the payload can be implemented with 200 bytes.

[0157] When adjustable block repetition (ADR) is applied, repeated retransmissions of specific blocks can be performed, enabling efficient retransmission within limited resources. Blocks that reach the Flush Point (FP) can be discarded. This disclosure proposes a method that applies ADR to each block to ensure reliability.

[0158] < When Adjustable Block Repetition is not applied >

[0159] In a first sub-event (SE) within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame (SDU 1) including eight blocks (1 to 8). If a second electronic device (or sink device) sends a Nack message for some blocks (e.g., blocks 3 to 8) among the eight blocks (1 to 8), in a second sub-event within the first CIS event (CIS 0 Event X), the first electronic device (or source device) may retransmit some blocks (e.g., blocks 3 to 8). Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks.

[0160] In a first sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit some blocks (e.g., 7, 8) of the first frame for which a Nack message was received and some blocks (e.g., 1 to 6) of the second frame. The second electronic device (or sink device) may transmit an Ack / Nack message for each of the received blocks. In a second sub-event within a second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may transmit some blocks (e.g., 7, 8) of the first frame for which a Nack message was received and some blocks (e.g., 5, 6) of the second frame for which a Nack message was received, and the remaining blocks (e.g., 7, 8) of the second frame. Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks. At this time, if the FP for the blocks of the first frame is after the second CIS event (CIS 0 Event X+1) (FT=2), some blocks (e.g., 8) of the first frame that received the Nack message again may be discarded.

[0161] In a first sub-event within a third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may transmit some blocks (e.g., 6) of the second frame for which a Nack message was received and some blocks (e.g., 1 to 7) of the third frame. The second electronic device (or sink device) may transmit an Ack / Nack message for each of the received blocks. In a second sub-event within a third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may transmit some blocks (e.g., 6) of the second frame for which a Nack message was received, some blocks (e.g., 6 and 7) of the third frame for which a Nack message was received, and the remaining blocks (e.g., 8) of the third frame. Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks. At this time, if the FP for the blocks of the second frame is after the third CIS event (CIS 0 Event X+2) (FT=2), some blocks (e.g., 6) of the second frame that received the Nack message again may be discarded.

[0162] < When Adjustable Block Repetition is applied >

[0163] FIG. 16 illustrates a case where adjustable block repetition is applied, for example, when Max_α = 0.5 and FT = 2 are set. In a first sub-event (SE) within a first CIS event (CIS 0 Event X), a first electronic device (or source device) may transmit a first frame (SDU 1) including eight blocks (1 to 8). If a second electronic device (or sink device) sends a Nack message for some blocks (e.g., blocks 3 to 8) among the eight blocks (1 to 8), the first electronic device (or source device) may retransmit some blocks (e.g., blocks 3 to 8) in a second sub-event within the first CIS event (CIS 0 Event X). Thereafter, the second electronic device (or sink device) may transmit an Ack / Nack message for each of the retransmitted blocks.

[0164] In the first sub-event within the second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may set RSN = 1, α = 0.25 and transmit some blocks (e.g., 7, 8) of the first frame from which the Nack message was received and some blocks (e.g., 1 to 6) of the second frame. The second electronic device (or sink device) may transmit Ack / Nack messages for each of the blocks received. In the second sub-event within the second CIS event (CIS 0 Event X+1), the first electronic device (or source device) may set RSN = 0, α = 0.5 and repeatedly transmit some blocks (e.g., 7, 8) of the first frame from which the Nack message was received, some blocks (e.g., 5, 6) of the second frame from which the Nack message was received, and the remaining blocks (e.g., 7, 8) of the second frame. Thereafter, the second electronic device (or sink device) can transmit an Ack / Nack message for each of the retransmitted blocks. At this time, if the FP for the blocks of the first frame is after the second CIS event (CIS 0 Event X+1) (FT=2), some blocks of the first frame (e.g., 7, 8) that received the Ack message through repeated transmission may not be discarded.

[0165] In the first sub-event within the third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may set RSN = 1, α = 0.25, repeatedly transmit some blocks (e.g., 6) of the second frame from which the Nack message was received, and transmit some blocks (e.g., 1 to 6) of the third frame. The second electronic device (or sink device) may transmit Ack / Nack messages for each of the blocks received. In the second sub-event within the third CIS event (CIS 0 Event X+2), the first electronic device (or source device) may set RSN = 0, α = 0.5, repeatedly transmit some blocks (e.g., 6) of the second frame from which the Nack message was received, and transmit some blocks (e.g., 6) of the third frame from which the Nack message was received, and the remaining blocks (e.g., 7 and 8) of the third frame. Thereafter, the second electronic device (or sink device) can transmit an Ack / Nack message for each of the retransmitted blocks. At this time, if the FP for the blocks of the second frame is after the third CIS event (CIS 0 Event X+2) (FT=2), some blocks (e.g., 6) of the second frame that received the Ack message through repeated transmission may not be discarded.

[0166] The adjustable block repetition of the present disclosure allows an electronic device (or source device) to repeatedly transmit a block (LL Block) requiring retransmission in a single Subevent. In one embodiment, the electronic device (or source device) determines how many times to repeatedly transmit the block based on available resources, thereby ensuring higher retransmission reliability. In one embodiment, the electronic device (or source device) can flexibly adjust the FT to prevent the block from being discarded in the FP. In one embodiment, the electronic device (or source device) can apply Block Repetition according to priority and situation when transmitting multiple service data in a single packet.

[0167] Embodiments of the present disclosure may be applicable to all transmission methods in which HDT packets are used, such as not only CIS but also ACL (access control list) and CHS (Connected Hybrid Stream).

[0168] FIG. 17 illustrates a configuration of a first electronic device according to one embodiment of the present disclosure.

[0169] The first electronic device of FIG. 17 may be implemented as any one of the electronic devices, the first electronic device, or the source device illustrated in FIGS. 1 to 16, FIG. 19, and FIG. 20.

[0170] Referring to FIG. 17, the first electronic device may include a processor (1701), a transceiver (1703), and a memory (1705). In the present disclosure, the processor (1701) may be defined as a circuit or application-specific integrated circuit or at least one processor. The processor (1701) may also be referred to as a control unit or controller.

[0171] The processor (1701) can control the overall operation of the first electronic device described in the embodiments proposed in the present disclosure. Specifically, the processor (1701) can control the operation of any one of the electronic devices illustrated in FIGS. 1 to 16, FIG. 19, and FIG. 20, the first electronic device, or the source device, for example.

[0172] The transceiver (1703) can transmit and receive signals with other electronic devices or at least one sink device. The transceiver (1703) may also be referred to as a transceiver or a transceiver.

[0173] The memory (1705) can store at least one of information transmitted and received through the transceiver (1703) and information generated through the processor (1701).

[0174] According to one embodiment, the processor (1701) may transmit, in a first sub-event within a first event, a first frame including a first payload comprised of first blocks and a second payload comprised of second blocks. According to one embodiment, the processor (1701) may receive, from a second electronic device, a Nack message indicating that at least one block among the first blocks and the second blocks was not received in the first sub-event within the first event. According to one embodiment, the processor (1701) may control, in a second sub-event subsequent to the first sub-event within the first event, to repeatedly transmit, to the second electronic device, the at least one block corresponding to the Nack message.

[0175] According to one embodiment, the processor (1701) may transmit a second frame including a third payload composed of third blocks and a fourth payload composed of fourth blocks to the second electronic device in a first sub-event within a second event subsequent to the first event. According to one embodiment, the processor (1701) may receive, from the second electronic device, a Nack message indicating that at least one block among the third blocks and the fourth blocks was not received in the first sub-event within the second event. According to one embodiment, the processor (1701) may control, in a second sub-event subsequent to the first sub-event within the second event, to repeatedly transmit the at least one block corresponding to the Nack message to the second electronic device.

[0176] According to one embodiment, a PDU (protocol data unit) header for the first frame may include a block repetition (BR) and a block repetition number (BRN), wherein the BR may indicate whether a block is a block to be repeatedly transmitted, and the BRN may indicate the number of times the block is repeatedly transmitted.

[0177] According to one embodiment, the PDU header for the first frame further includes a repetition offset bit, and the repetition offset bit may indicate an offset that increases or decreases the number of repetition transmissions of the block.

[0178] According to one embodiment, the number of times the block is repeatedly transmitted may be determined based on at least one of a Flush Timeout (FT) for the block, a Remaining Subevent Number (RSN), a sum of a retransmission block length, and a priority of the block.

[0179] FIG. 18 illustrates a configuration of a second electronic device according to one embodiment of the present disclosure.

[0180] The second electronic device of FIG. 18 may be implemented as any one of the electronic devices, the second electronic device, or the sink device illustrated in FIGS. 1 to 16, FIG. 19, and FIG. 20.

[0181] Referring to FIG. 18, the second electronic device may include a processor (1801), a transceiver (1803), and a memory (1805). In the present disclosure, the processor (1801) may be defined as a circuit or application-specific integrated circuit or at least one processor. The processor (1801) may also be referred to as a control unit or controller.

[0182] The processor (1801) can control the overall operation of the second electronic device described in the embodiments proposed in the present disclosure. Specifically, the processor (1801) can control the operation of any one of the electronic devices, the second electronic device, or the sink device illustrated in FIGS. 1 to 16, FIG. 19, and FIG. 20, for example.

[0183] The transceiver (1803) can transmit and receive signals with other electronic devices or source devices. The transceiver (1803) may also be referred to as a transceiver or a transceiver.

[0184] The memory (1805) can store at least one of information transmitted and received through the transceiver (1803) and information generated through the processor (1801).

[0185] Various embodiments may be provided in the present disclosure for determining the number of retransmissions of a block requiring retransmission.

[0186] In one embodiment, a first electronic device can determine the number of retransmissions of a block by transmitting a message to a second electronic device. In this case, whether BR is applied can be expressed using 1 bit, and the number of repetitions can be determined algorithmically (based on α).

[0187] According to one embodiment, the first electronic device and / or the second electronic device calculates the number of repetitions without sending or receiving messages (BR (block repetition) is always applied), and the value of α in the aforementioned [Mathematical Formula 1] can be determined in advance based on a connection parameter. According to one embodiment, the number of repetitions per block can be protocol-dependently determined based on a sub_interval and a flush point per block (or per payload to which the block belongs).

[0188] FIG. 19 illustrates an example of determining the number of retransmissions of a block without transmitting messages between electronic devices according to one embodiment of the present disclosure.

[0189] In Fig. 19, assumptions 1) to 3) below can be applied.

[0190] 1) The transmission speed (data rate) for the transmission packet is determined in advance by another algorithm and then given.

[0191] 2) Maximize the use of sub_event's time resources when retransmitting (i.e., leave no time to spare).

[0192] 3) The number of repetitions per block is proportional to the reciprocal of the time remaining until the flush point, and the ratio is set in advance.

[0193] In Fig. 19, Sub_interval = 2.8 ms, Payload n = {B0, B1, B2, B3}, Payload n+1 = {B4, B5, B6, B7} can be set. At this time, the retransmission target blocks can be Retransmission target blocks = {B0, B4, B5}. The remaining FP (Remaining flush point) can be set to Payload n = 2.8 ms and Payload n+1 = 25.6 ms.

[0194] For example, the retransmission rate is determined to be 3 Mbps, in which case 6 blocks may be included in a retransmission packet (re-Tx packet). In this case, the blocks included in payload n may be retransmitted 4 times, and the blocks included in payload n+1 may not be retransmitted.

[0195] FIG. 20 illustrates an example of a PDU header in an HDT packet format according to one embodiment of the present disclosure.

[0196] Referring to FIG. 20, the PDU Header in the HDT packet format may include Initial Octets, Rx Portion, Tx Portion, and Extended Header. The Initial Octets may include an XHP field indicating whether an Extended Header field exists, an RxPP field indicating whether an Rx Portion exists (for example, if RxPP=1, an Rx Portion exists, and if RxPP=0, an Rx Portion does not exist), an MD / CIE field identical to the existing LE specification, an SN (sequence number) field including three LSBs of a sequence number, a TxPP field indicating whether a Tx Portion exists (for example, if TxPP=1, a Tx Portion exists, and if TxPP=0, a Tx Portion does not exist), and an RFU field.

[0197] The above Extended Header may include Another Octet field, BR field, and BR representation field.

[0198] According to one embodiment, one bit of the lower 7 bits of the Extended Header may be set to a BR field (or BR bit). According to one embodiment, when the BR field (or BR bit) is set to a first value (e.g., 1), it may indicate that BR is enabled, and when the BR field (or BR bit) is set to a second value (e.g., 0), it may indicate that BR is disabled.

[0199] According to one embodiment, A, B, C, and D in the BR representation field may be configured as follows.

[0200] A: Indicates the number of retransmissions for the first payload indicated in Tx Portion.

[0201] B: Indicates the number of retransmissions for the second payload indicated in Tx Portion.

[0202] C: Indicates the number of retransmissions for the third payload indicated in Tx Portion.

[0203] D: Indicates the number of retransmissions for the fourth payload indicated in Tx Portion.

[0204] In this disclosure, for convenience of explanation, the BR representation field is illustrated as including A, B, C, and D, but the BR representation field may indicate the number of retransmissions for various numbers of payloads.

[0205] In one embodiment, each of A, B, C, and D in the BR representation field may include one of the following values ​​to indicate the number of retransmissions of the corresponding payload. For example, A in the BR representation field may be set to 0001, and the number of repetitions of the first payload indicated by Tx Portion may be set to 2.

[0206] [Table 3]

[0207]

[0208] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0209] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of operating a first electronic device in a wireless communication system, In a first sub-event within a first event, an action of transmitting a first frame comprising a first payload comprising first blocks and a second payload comprising second blocks; In the first sub-event within the first event, an operation of receiving a Nack message from a second electronic device indicating that at least one block among the first blocks and the second blocks is not received; and A method characterized in that, in a second sub-event subsequent to the first sub-event within the first event, the method comprises an action of repeatedly transmitting the at least one block corresponding to the Nack message to the second electronic device.

2. In paragraph 1, In a first sub-event within a second event subsequent to the first event, an action of transmitting a second frame comprising a third payload comprising third blocks and a fourth payload comprising fourth blocks to the second electronic device; In the first sub-event within the second event, an operation of receiving a Nack message from the second electronic device indicating that at least one block among the third blocks and the fourth blocks is not received; and A method characterized in that, in a second sub-event subsequent to the first sub-event within the second event, the method further comprises an action of repeatedly transmitting the at least one block corresponding to the Nack message to the second electronic device.

3. In paragraph 1, The PDU (protocol data unit) header for the first frame includes BR (block repetition) and BRN (block repetition number), A method characterized in that the BR indicates whether the block is a block to be repeatedly transmitted, and the BRN indicates the number of times the block is repeatedly transmitted.

4. In paragraph 3, The PDU header for the first frame further includes a repetition offset bit, A method characterized in that the above repetition offset bit indicates an offset that increases or decreases the number of repetition transmissions of the block.

5. In the third paragraph, the number of repetition transmissions of the block is A method characterized in that it is determined based on at least one of the sum of the FT (Flush Timeout), RSN (Remaining Subevent Number), and retransmission block length for the block, and the priority of the block.

6. In a method of operating a second electronic device in a wireless communication system, In a first sub-event within a first event, an act of receiving a first frame from a first electronic device, the first frame including a first payload comprising first blocks and a second payload comprising second blocks; In the first sub-event within the first event, an operation of transmitting a Nack message to the first electronic device indicating that at least one block among the first blocks and the second blocks is not received; and A method characterized in that, in a second sub-event subsequent to the first sub-event within the first event, the method comprises an action of repeatedly receiving from the first electronic device at least one block corresponding to the Nack message.

7. In paragraph 6, In a first sub-event within a second event subsequent to the first event, an operation of receiving a second frame from the first electronic device, the second frame including a third payload comprising third blocks and a fourth payload comprising fourth blocks; In the first sub-event within the second event, an operation of transmitting a Nack message to the first electronic device indicating that at least one block among the third blocks and the fourth blocks is not received; and A method characterized in that, in a second sub-event subsequent to the first sub-event within the second event, the method further comprises an action of repeatedly receiving from the first electronic device at least one block corresponding to the Nack message.

8. In paragraph 6, The PDU (protocol data unit) header for the first frame includes BR (block repetition) and BRN (block repetition number), A method characterized in that the BR indicates whether the block is a block to be repeatedly transmitted, and the BRN indicates the number of times the block is repeatedly transmitted.

9. In paragraph 8, The PDU header for the first frame further includes a repetition offset bit, A method characterized in that the above repetition offset bit indicates an offset that increases or decreases the number of repetition transmissions of the block.

10. In paragraph 8, the number of repetition transmissions of the block is A method characterized in that it is determined based on at least one of the sum of the FT (Flush Timeout), RSN (Remaining Subevent Number), and retransmission block length for the block, and the priority of the block.

11. In a first electronic device in a wireless communication system, Transmitter and receiver; and comprising a control unit, wherein the control unit is: In a first sub-event within a first event, a first frame is transmitted including a first payload consisting of first blocks and a second payload consisting of second blocks, In the first sub-event within the first event, a Nack message is received from the second electronic device indicating that at least one block among the first blocks and the second blocks is not received, A device characterized in that, in a second sub-event subsequent to the first sub-event within the first event, the device controls to repeatedly transmit the at least one block corresponding to the Nack message to the second electronic device.

12. In the 11th paragraph, the control unit, In a first sub-event within a second event subsequent to the first event, a second frame including a third payload consisting of third blocks and a fourth payload consisting of fourth blocks is transmitted to the second electronic device, In the first sub-event within the second event, a Nack message is received from the second electronic device indicating that at least one block among the third blocks and the fourth blocks is not received, A device characterized in that, in a second sub-event subsequent to the first sub-event within the second event, the device controls to repeatedly transmit the at least one block corresponding to the Nack message to the second electronic device.

13. In paragraph 11, The PDU (protocol data unit) header for the first frame includes BR (block repetition) and BRN (block repetition number), A device characterized in that the BR indicates whether the block is a block to be repeatedly transmitted, and the BRN indicates the number of times the block is repeatedly transmitted.

14. In a second electronic device in a wireless communication system, Transmitter and receiver; and comprising a control unit, wherein the control unit is: In a first sub-event within a first event, a first frame is received from a first electronic device, the first frame including a first payload consisting of first blocks and a second payload consisting of second blocks, In the first sub-event within the first event, a Nack message is transmitted to the first electronic device indicating that at least one block among the first blocks and the second blocks is not received, A device characterized in that, in a second sub-event subsequent to the first sub-event within the first event, the device repeatedly receives from the first electronic device at least one block corresponding to the Nack message.

15. In paragraph 14, the control unit, In a first sub-event within a second event subsequent to the first event, a second frame including a third payload consisting of third blocks and a fourth payload consisting of fourth blocks is received from the first electronic device, In the first sub-event within the second event, a Nack message is transmitted to the first electronic device indicating that at least one block among the third blocks and the fourth blocks is not received, A device characterized in that, in a second sub-event subsequent to the first sub-event within the second event, the device repeatedly receives from the first electronic device at least one block corresponding to the Nack message.

Images