KR20210086517A - Method for transceiving data in bluetooth network environment and electronic device thereof - Google Patents

Abstract

Disclosed is an electronic device which includes: a first communication circuit supporting wireless communication; a second communication circuit supporting Bluetooth communication; a processor operably connected to the first communication circuit and the second communication circuit; and a memory operably connected to the processor. The processor can be set to use the second communication circuit, generate a first device and a link based on a protocol supporting synchronized connection, receive a second data, which is acquired by the first device from a second time slot among a plurality of time slots of a single transceiving section of the link, from the first device through the link, receive a third data, which includes additional data to the second data, within a re-transmission section, which is set for re-transmission of data, among the plurality of time slots, and transmit an audio data generated based on the second data and the third data to an external electronic device by using the first communication circuit. On top of that, various embodiments disclosed in the present invention are possible. The present invention aims to provide a method for transceiving data in Bluetooth network environment and an electronic device thereof, which are able to provide audio data with an improved sound quality.

Description

A method for transmitting and receiving data in a Bluetooth network environment and an electronic device therefor {METHOD FOR TRANSCEIVING DATA IN BLUETOOTH NETWORK ENVIRONMENT AND ELECTRONIC DEVICE THEREOF}

Embodiments disclosed in this document relate to a method for transmitting and receiving data in a Bluetooth network environment and an electronic device therefor.

Bluetooth standard technology defined by Bluetooth™ special interest group (SIG) defines a protocol for short-range wireless communication between electronic devices. In a Bluetooth network environment, electronic devices may transmit or receive data packets including content such as text, voice, image, or video in a designated frequency band (eg, about 2.4 gigahertz (GHz)).

For example, a user equipment (UE) such as a smartphone, tablet, desktop computer, or laptop computer may transmit data packets to other user terminals or accessory devices. have. The accessory device may include at least one of an earphone, a headset, a speaker, a mouse, a keyboard, and a display device.

In a Bluetooth network environment, the electronic device and the external electronic device may perform real-time audio data exchange. For example, the electronic device and the external electronic device may exchange audio data based on a hands-free profile (HFP). In the HFP, the electronic device and the external electronic device may exchange audio data at designated intervals.

A topology representing the Bluetooth network environment may include one user device (eg, a device under test (DUT)) transmitting a data packet and at least one device receiving a data packet from the user device. For example, when an earphone (or headset) is connected to a smartphone, the earphone may receive a data packet from the smartphone.

For example, the user device may obtain audio data from an earphone including at least one microphone. The user device may transmit audio data obtained from the earphone to the external electronic device while performing a call with the external electronic device. Since the earphone is worn on the user's ear, there may be a distance from the user's mouth. Due to the distance between the mouth and the earphone, the quality of audio data obtained by the earphone may be deteriorated.

Various embodiments disclosed in this document may provide an electronic device and method for data transmission/reception using a retransmission section in a Bluetooth network environment.

An electronic device according to an embodiment disclosed in this document is operatively connected to a first communication circuit supporting wireless communication, a second communication circuit supporting Bluetooth communication, and the first communication circuit and the second communication circuit. a processor and a memory operatively coupled to the processor, wherein the memory, when executed, causes the processor, using the second communication circuit, to establish a link with a first device based on a protocol supporting a synchronous connection. generate, transmit first data through the link in a first time slot among a plurality of time slots of one transmission/reception period of the link, and in a second time slot of the plurality of time slots, the first device Receives second data including audio data obtained by , from the first device through the link, and receives additional data for the second data within a retransmission interval set for data retransmission among the plurality of time slots one or more instructions for receiving the third data including the included data through the link, and transmitting the second data and audio data generated based on the third data to an external electronic device using the first communication circuit; can be saved

An electronic device according to an embodiment disclosed in this document includes an audio receiving circuit connected to at least one microphone, a wireless communication circuit configured to support Bluetooth communication, a processor operatively connected to the audio receiving circuit and the wireless communication circuit; and a memory operatively coupled to the processor, wherein the memory, when executed, causes the processor to connect, using the wireless communication circuitry, with a first external electronic device via a first link, the wireless communication using a circuit to connect to a second external electronic device through a second link, and transmit first link information including channel information of the first link to the second external electronic device through the second link; An extended synchronous connection oriented (eSCO) link is created with the first external electronic device through the first link, and in a first time slot among a plurality of time slots of one transmission/reception section of the eSCO link, the first external Receive first data from an electronic device, and transmit second data including audio data obtained using the audio receiving circuit to the first external electronic device in a second time slot among the plurality of time slots; , one or more instructions for transmitting additional data for improving the sound quality of the audio data in a retransmission interval set for data retransmission among the plurality of time slots.

A method for transmitting audio data of an electronic device according to an embodiment disclosed in this document includes an operation of generating an extended synchronous oriented (eSCO) link with a first device through a first link, and one transmission/reception section of the eSCO link transmitting first data in a first one of a plurality of time slots, receiving second data from a first device in a second one of the plurality of time slots, the plurality of times attempting to receive third data within at least one retransmission time slot of the slots, and if the third data is received within the at least one retransmission time slot, based on the second data and the third data and transmitting the generated audio data to an external electronic device.

According to various embodiments disclosed in this document, the electronic device may provide audio data of improved sound quality by using additional data.

Also, the electronic device may provide audio data of improved sound quality by using an external electronic device having a relatively high performance.

Also, the electronic device may determine an electronic device to perform retransmission, thereby reducing battery consumption of the electronic device due to retransmission.

In addition, various effects directly or indirectly identified through this document may be provided.

1 is a block diagram of an electronic device in a network environment according to various embodiments of the present disclosure;
2 illustrates a topology in a Bluetooth network environment according to various embodiments of the present disclosure.
3 illustrates electronic devices of a Bluetooth network according to an embodiment.
4 is a block diagram of electronic devices according to an exemplary embodiment.
5 is a signal flow diagram for communication between electronic devices according to various embodiments of the present disclosure;
6 illustrates a user interface (UI) indicating connection of devices in a Bluetooth network environment according to an exemplary embodiment.
7 is a signal flow diagram for generating a link between a user device and a first device according to an embodiment.
8A illustrates packet exchange with additional data transmission according to an embodiment.
8B illustrates packet exchange with additional data transmission according to an embodiment.
9 is a flowchart of a method for transmitting and receiving additional data for a user device according to an embodiment.
10 is a flowchart of a method for transmitting and receiving additional data by a first device according to an exemplary embodiment.
11 is a flowchart of a method for transmitting and receiving additional data by a second device according to an embodiment.
12 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.
13 illustrates packet exchange by transmission of additional data of a second device according to an embodiment.
14 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.
15 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.
16 illustrates packet exchange by transmission of additional data of a second device according to an embodiment.
17 is a flowchart of a method of transmitting audio data by a user device according to an embodiment.
18 is a flowchart of a method of changing an audio data transmission device of a user device according to an embodiment.
19 is a flowchart of a method of changing an audio data transmission apparatus of a first apparatus according to an exemplary embodiment.
20 is a flowchart of a method of changing an audio data transmission apparatus of a second apparatus according to an exemplary embodiment.
21 illustrates an example of packet exchange according to a change in an audio data transmission apparatus.
22 shows another example of packet exchange according to a change in an audio data transmission device.
In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that various modifications, equivalents, and/or alternatives of the embodiments of the present invention are included.

1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments of the present disclosure.

Referring to FIG. 1 , in a network environment 100 , the electronic device 101 communicates with the electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199 . It may communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes a processor 120 , a memory 130 , an input device 150 , a sound output device 155 , a display device 160 , an audio module 170 , and a sensor module ( 176 , interface 177 , haptic module 179 , camera module 180 , power management module 188 , battery 189 , communication module 190 , subscriber identification module 196 , or antenna module 197 . ) may be included. In some embodiments, at least one of these components (eg, the display device 160 or the camera module 180 ) may be omitted or one or more other components may be added to the electronic device 101 . In some embodiments, some of these components may be implemented as one integrated circuit. For example, the sensor module 176 (eg, a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented while being embedded in the display device 160 (eg, a display).

The processor 120, for example, executes software (eg, the program 140) to execute at least one other component (eg, a hardware or software component) of the electronic device 101 connected to the processor 120 . It can control and perform various data processing or operations. According to an embodiment, as at least part of data processing or operation, the processor 120 converts commands or data received from other components (eg, the sensor module 176 or the communication module 190) to the volatile memory 132 . may be loaded into the volatile memory 132 , process commands or data stored in the volatile memory 132 , and store the resulting data in the non-volatile memory 134 . According to an embodiment, the processor 120 includes a main processor 121 (eg, a central processing unit or an application processor), and an auxiliary processor 123 (eg, a graphic processing unit or an image signal processor) that can be operated independently or together with the main processor 121 . , a sensor hub processor, or a communication processor). Additionally or alternatively, the auxiliary processor 123 may be configured to use less power than the main processor 121 or to be specialized for a designated function. The auxiliary processor 123 may be implemented separately from or as a part of the main processor 121 .

The auxiliary processor 123 may be, for example, on behalf of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or when the main processor 121 is active (eg, executing an application). ), together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display device 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to an embodiment, the auxiliary processor 123 (eg, an image signal processor or a communication processor) may be implemented as a part of another functionally related component (eg, the camera module 180 or the communication module 190). have.

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

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

The input device 150 may receive a command or data to be used by a component (eg, the processor 120 ) of the electronic device 101 from the outside (eg, a user) of the electronic device 101 . The input device 150 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (eg, a stylus pen).

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

The display device 160 may visually provide information to the outside (eg, a user) of the electronic device 101 . The display device 160 may include, for example, a display, a hologram device, or a projector and a control circuit for controlling the corresponding device. According to an embodiment, the display device 160 may include a touch circuitry configured to sense a touch or a sensor circuit (eg, a pressure sensor) configured to measure the intensity of a force generated by the touch. have.

The audio module 170 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 170 acquires a sound through the input device 150 , or an external electronic device (eg, a sound output device 155 ) connected directly or wirelessly with the electronic device 101 . The sound may be output through the electronic device 102 (eg, a speaker or a headphone).

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, user state), and generates an electrical signal or data value corresponding to the sensed state. can do. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.

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

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

The haptic module 179 may convert an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

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

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

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

The communication module 190 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (eg, the electronic device 102, the electronic device 104, or the server 108). It can support establishment and communication through the established communication channel. The communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication. According to an embodiment, the communication module 190 is a wireless communication module 192 (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (eg, : It may include a local area network (LAN) communication module, or a power line communication module). Among these communication modules, a corresponding communication module may be a first network 198 (eg, a short-range communication network such as Bluetooth, WiFi direct, or infrared data association (IrDA)) or a second network 199 (eg, a cellular network, the Internet, or It may communicate with the external electronic device 104 through a computer network (eg, a telecommunication network such as a LAN or WAN). These various types of communication modules may be integrated into one component (eg, a single chip) or may be implemented as a plurality of components (eg, multiple chips) separate from each other. The wireless communication module 192 uses subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199 . The electronic device 101 may be identified and authenticated.

The antenna module 197 may transmit or receive a signal or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module 197 may include one antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern. According to an embodiment, the antenna module 197 may include a plurality of antennas. In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is connected from the plurality of antennas by, for example, the communication module 190 . can be selected. A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna. According to some embodiments, other components (eg, RFIC) other than the radiator may be additionally formed as a part of the antenna module 197 .

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and a signal ( e.g. commands or data) can be exchanged with each other.

According to an embodiment, the command or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external electronic devices 102 and 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or part of the operations performed by the electronic device 101 may be performed by one or more of the external electronic devices 102 , 104 , or 108 . For example, when the electronic device 101 needs to perform a function or service automatically or in response to a request from a user or other device, the electronic device 101 may perform the function or service itself instead of executing the function or service itself. Alternatively or additionally, one or more external electronic devices may be requested to perform at least a part of the function or the service. The one or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit a result of the execution to the electronic device 101 . The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this purpose, for example, cloud computing, distributed computing, or client-server computing technology may be used.

2 illustrates a topology 200 of a Bluetooth network environment according to various embodiments.

Referring to FIG. 2 , the user device 201 and at least one device 202-1, 202-2, and/or 202-3 included in the topology 200 include the electronic device 101 illustrated in FIG. 1 . ) and at least some may include the same or similar components, and at least some may perform the same or similar functions. For example, the user device 201 and at least one of the devices 202-1, 202-2, and/or 202-3 may perform wireless communication in a short range according to a Bluetooth network defined by the Bluetooth SIG. have. The Bluetooth network may include, for example, a Bluetooth legacy network or a Bluetooth low energy (BLE) network. According to an embodiment, the user device 201 and the at least one device 202-1, 202-2, and/or 202-3 perform wireless communication through one of a Bluetooth legacy network and a BLE network. Alternatively, wireless communication may be performed through two networks.

The user device 201 includes, for example, a user terminal such as a smartphone, tablet, desktop computer, or laptop computer, and includes at least one device 202-1, 202-2, and/or 202-3. may include accessory devices such as earphones, headsets, speakers, mice, keyboards, or display devices. According to an embodiment, the at least one device 202-1, 202-2, and/or 202-3 of FIG. 2 is another device (eg, the first device 202-1, the second device 202). -2) and/or the third device 202 - 3 ) may be recognized before connection, or information (eg, address information) of another device may be stored before connection. For example, in the case of an accessory device (eg, earphone) including the first device 202-1 and the second device 202-2, the first device 202-1 and the second device 202-2 ) can recognize each other before connecting, or store each other's address information. According to an embodiment, the user device 201 and the at least one device 202-1, 202-2, and/or 202-3 may be configured to update each other's address information. For example, the first device 202-1 updates address information of the second device 202-2 stored in the memory, or the second device 202-2 updates the address information of the second device 202-2 stored in the memory. ) address information can be updated.

According to an embodiment, the user device 201 may serve as a master device, and at least one of the devices 202-1, 202-2, and/or 202-3 may serve as a slave device. have. The number of devices performing the role of the slave device is not limited to the example shown in FIG. 2 . According to an embodiment, the role of the master device or the slave device may be determined in an operation in which a link (eg, 205, 210, and/or 215) between devices is generated. According to another embodiment, one device (eg, the first device 202-1) of the first device 202-1 and the second device 202-2 serves as a master device, and the other A device (eg, the second device 202 - 2 ) may serve as a slave device.

The master device may control a physical channel. For example, a master device may transmit a data packet, while a slave device may transmit a data packet to the master device only after receiving the data packet. As another example, a channel resource (eg, a frequency hopping channel) for data packet transmission may be generated based on a clock of the master device. In a Bluetooth legacy network, a time resource (eg, a time slot) may be determined based on a clock of a master device. The time slot may be, for example, 625 microseconds. In a BLE network, a master device and a slave device transmit a data packet every specified interval, and when a data packet is received, a response can be made after a specified time (eg, T_IFS (the inter frame space), about 150 μs). .

According to an embodiment, the user device 201 sends a data packet including content such as text, audio, image, or video to at least one device 202-1, 202-2, and/or 202-3. can be transmitted. According to the type of content included in the data packet, not only the user device 201 but also at least one of the devices 202-1, 202-2, and/or 202-3 may transmit the data packet. For example, when music is played on the user device 201 , only the user device 201 may include content through a link created with the devices 202-1, 202-2, and/or 202-3. While being able to transmit a data packet, when a call is made on the user device 201 , it creates not only the user device 201 but also at least one of the devices 202-1, 202-2, or 202-3. A data packet including content (eg, audio data) may be transmitted to the user device 201 through the linked link. When only the user device 201 transmits the data packet, the user device 201 is referred to as a source device, and at least one of the devices 202-1, 202-2, and/or 202-3 may be referred to as a sink device.

When the user device 201 creates (or establishes) a plurality of links with the at least one device 202-1, 202-2, and/or 202-3 in order to transmit a data packet, the user Resource consumption and/or power consumption of the device 201 may increase. Accordingly, the user device 201 may only form a first link 205 with the first device 202-1, and may transmit a data packet to the first device 202-1 through the first link 205. . In this case, at least one other device (eg, the second device 202 - 2 and/or the third device 202 - 3 ) is configured to receive a data packet including the content transmitted by the user device 201 . The first link 205 may be monitored. In this case, the user device 201 is a device under test (DUT), the first device 202-1 is a primary earbud or primary equipment (PE), and at least one other device (eg, the second device 202-2) ) and/or the third device 202 - 3 ) may be referred to as a secondary earbud, or secondary equipment (SE).

According to an embodiment, the first device 202 - 1 may create the second device 202 - 2 and the third link 215 . The first device 202 - 1 connects to the first via the third link 215 so that the second device 202 - 2 can monitor the first link 205 and send a response message to the user device 201 . Information associated with the link 205 may be transmitted to the second device 202 - 2 through the third link 215 . Hereinafter, the term “monitoring” may refer to a state in which at least a portion of a packet transmitted through a corresponding link is attempted to be received or a state in which at least a portion of the packet can be received. For example, when the second device 202 - 2 monitors the first link 205 , the second device 202 - 2 is the user device 201 or the first device via the first link 205 . At least a portion of a packet transmitted by the 202-1 (eg, electronic devices forming the first link 205) may be received or attempted to be received. In this case, the user device 201 may recognize the second device 202 - 2 using the second link 210 , but the user device 201 may recognize the second device 202 - 2 through the first link 205 . You may not be aware of your existence. The information associated with the first link 205 may include address information (eg, a Bluetooth address of the master device of the first link 205 , a Bluetooth address of the user device 201 , and/or a Bluetooth address of the first device 202-1 ). address), piconet (eg topology 200) clock information (eg CLKN (clock native) of the master device of the first link 205), logical transport (LT) address information (eg: Information allocated by the master device of the first link 205), used channel map information, link key information, service discovery protocol (SDP) information (eg, the first link 205) service and/or profile information related to ), and/or supported feature information. The information associated with the first link 205 may further include, for example, an extended inquiry response (EIR) packet. The EIR packet may include resource control information of the first link 205 and/or information about a manufacturer. The second device 202 - 2 may determine a hopping channel (or frequency hopping channel) of the first link 205 through the address information and the clock information, and an encrypted data packet through the link key information. can be decrypted. The second device 202 - 2 has an access code (or channel access code) corresponding to the first link 205 and address information based on the information associated with the first link 205 . (eg, LT address information) may be generated, and a response message including the generated access code and address information may be transmitted to the user device 201 . In this case, the user device 201 may determine whether to retransmit the data packet based on the response message transmitted from the second device 202 - 2 even though the user device 201 does not establish a link with the second device 202 - 2 .

According to another embodiment, when the first device 202-1 and the second device 202-2 are devices supporting the same user account or a similar user account (eg, a family account), the first device 202-1 1) and the second device 202-2 are an external device (eg, external server 203) that interworks with the first device 202-1 or the second device 202-2 through the same or similar user account Information associated with the first link 205 may be shared through the . The topology 200 may further include, for example, an external server 203 . In an embodiment, the third device 202 - 3 may also be a device that supports the same user account or a similar account (eg, a family account) as the first device 202-1 . For example, the first device 202-1 transmits information related to the first link 205 to the external server 203, and the external server 203 transmits the information related to the first link 205 to the second to the device 202-2 and/or the third device 202-3. The external server 203, for example, when a request is received from the second device 202-2 and/or the third device 202-3, the first device 202-1 and/or the user device 201 ) (eg, information associated with the first link 205 ) may be transmitted to the second device 202 - 2 and/or the third device 202 - 3 . The external server 203 sends a first link to the first device 202 - 1 and/or the user device 201 when a request is received from the second device 202 - 2 and/or the third device 202 - 3 . Request transmission of information associated with 205 , and receive information associated with first link 205 from first device 202-1 and/or user device 201 . When a request is received from the second device 202-2 and/or the third device 202-3, the external server 203 transmits information related to the first link 205 stored in the external server 203 to the second device. 202-2 and/or the third device 202-3.

According to another embodiment, the second device 202 - 2 may receive information related to the first link 205 from the user device 201 . For example, the user device 201 may transmit information associated with the first link 205 to the second device 202 - 2 via the second link 210 . For example, after transmission of information associated with the first link 205 , the user device 201 may release the second link 210 .

3 illustrates electronic devices of a Bluetooth network 300 according to an embodiment.

According to an embodiment, the user device 201 may create a first device 202-1 and a first link 205 and create a second device 202-2 and a second link 210. have. According to an embodiment, the first device 202-1 and the second device 202-2 may create a third link 215 . According to an embodiment, the second device 202 - 2 receives the information associated with the first link 205 from the first device 202-1 through the third link 215 and receives the first link 205 . can be monitored. For example, the second device 202 - 2 may acquire audio data exchanged between the user device 201 and the first device 202 - 2 by monitoring the first link 205 .

Referring to FIG. 3 , for example, the user device 201 may be a portable electronic device (eg, a smart phone). For example, the first device 202-1 and/or the second device 202-2 may be wireless earphones or wireless earbuds. For example, the user device 201 may transmit audio data to the first device 202-1 via the first link 205 . The first device 202-1 and the second device 202-2 may be configured to output audio data received from the user device 201 through the first link 205 . As another example, when performing a voice call, the first device 202-1 and/or the second device 202-2 may receive audio data from the user device 201, and the first device ( 202-1) and/or audio data obtained through a microphone (not shown) of the second device 202-2 may be transmitted to the user device 201 .

In the example of FIG. 3 , the user device 201 may obtain audio data from the first device 202-1 and/or the second device 202-2. For example, the user device 201 may perform a call (eg, a voice call or a video call) with an external electronic device (not shown). In this case, the user device 201 may acquire audio data to perform a call. As another example, the user device 201 may acquire audio data according to execution of a specified application (eg, voice chatting, messenger, voice assistant, or voice recording).

In one embodiment, the user device 201 may obtain audio data based on a synchronous connection protocol. For example, the synchronous connection protocol may include a protocol that supports real-time audio data exchange (eg, a protocol that supports HFP). The user device 201 may create a synchronous connection for exchanging real-time audio data. The user device 201 may generate a link for exchanging real-time audio data with the first device 202-1 through the first link 205 . For example, the user device 201 may create a synchronous connection oriented (SCO) link or an extended SCO (eSCO) link through the first link 205 .

In one embodiment, the user device 201 may create an eSCO link with the first device 202-1. Upon creation of the eSCO link, the user device 201 and the first device 202-1 may negotiate various parameters associated with the eSCO link. For example, parameters associated with the eSCO link may include a transmission/reception interval (eg, TeSCO; interval eSCO), a retransmit window eSCO (WeSCO), and/or a packet type.

In another example, the user device 201 creates a first eSCO link through the first device 202-1 and the first link 205, and the second device 202-2 and the second link 210 ) to create a second eSCO link. The first device 202-1 and the second device 202-2 have a first eSCO link via a first link 205 via a third link 215 and a second eSCO via a second link 210 via a third link 215 . The parameters to be used on the link (eg, TeSCO, WeSCO, and/or packet type) can be negotiated. The first device 202-1 and the second device 202-2 may negotiate with the user device 201 via the third link 215 so that the negotiated parameters are used in the first eSCO link and the second eSCO link. can As another example, the user device 201 selects parameters to be used for the first eSCO link and the second eSCO link, and sends the selected parameters to the first device 202-1 and the second device 202-2. may notify.

According to an embodiment, the transmission/reception interval TeSCO may include information on a time period during which the user device 201 and the first device 202-1 perform data exchange. For example, the transmission/reception period may include a plurality of time slots. In the case of an eSCO link, a master device (eg, user device 201) and a slave device (eg, first device 202-1) of the eSCO link are set to exchange data within a time corresponding to one TeSCO. can For example, the first slot of the transmission/reception section may be set to be used for data transmission of the master device, and the second slot may be set to be used for data transmission of the slave device. For another example, the first N (eg, N is 1 or 3) slots of the transmission/reception section are set to be used for data transmission of the master device, and the slots following the N slots are used for data transmission of the slave device can be set to be

The retransmission interval WeSCO may include information (eg, the number of slots) on the length of a time interval used by retransmission of data within the transmission/reception interval TeSCO. The retransmission period may include at least one time slot subsequent to a time slot for initial data transmission/reception between the master device and the slave device within one transmission/reception section. For example, when the master device and the slave device use the first and second time slots of the transmission/reception interval, the retransmission interval may start from the third time slot. With respect to the data sent by the master device to the slave device, if data including NACK is received from the slave device or data including ACK is not received, the master device uses the time slot set for the master device in WeSCO to send data may try to retransmit. As another example, the slave device may also attempt to retransmit data using a time slot set for the slave device in WeSCO. If data re-reception fails even within WeSCO, the master device and the slave device may be set to try to exchange new data, rather than re-transmit existing data, in the next transmission/reception section.

The packet type may include information of packets for various audio transmissions. For the eSCO link, EV (evolution) type packets (eg, EV3, EV4, EV5, 2-EV3, 2-EV5, 3-EV3, 3-EV5) may be used. For example, parameters of the eSCO link according to the packet type may be shown in Table 1. 10TeSCO/2 in the table below may mean that when TeSCO is 12 slots, the master-slave packet length is 10*12/2, for example, 60 bytes.

single slot packet 3-slot packet Tesco (slots) EV3: 6
2-EV3: 6-12 (even)
3-EV3: 6-18 (even) EV4: 16
EV5: 16
2-EV5: 16
3-EV5: 16 WeSCO (slots) 0, 2, 4 0, 6 Master-Slave Packet Length (Bytes) 10TeSCO/2 10TeSCO/2 Slave-Master Packet Length (Bytes) 10TeSCO/2 10TeSCO/2

In the example of FIG. 3 , the user device 201 may obtain the user's voice from the first device 202-1 and the second device 202-2. Various methods may be considered to improve the sound quality of the user's voice. For example, the first device 202-1 and/or the second device 202-2 may use audio data acquired by the first device 202-1 and/or the second device 202-2. The enhanced audio data may be generated and transmitted to the user device 201 . As another example, when the first device 202-1 or the second device 202-2 cannot generate and transmit enhanced audio data due to limited performance (eg, limited resources, memory, or computational power), the first The device 202-1 and/or the second device 202-2 may provide audio enhancement (eg, noise reduction, noise suppression, data recovery using multi-channel audio data, and/or signal-to-noise (SNR) enhancement). ) to the user device 201 to improve audio data by the user device 201 . However, in the case of an eSCO link, since only limited slots are used for data transmission, and slots thereafter are set as slots for retransmission, the first device 202-1 and/or the second device 202-2 may not be able to transmit additional data. In addition, in the network topology in which the second device 202-2 monitors the first link 205, since the radio resource of the first link 205 is used by the first device 202-1, the second 2 The data of the device 202 - 2 may not be transmitted to the user device 201 . In addition, when both the first device 202-1 and the second device 202-2 transmit data, both the first device 202-1 and the second device 202-2 transmit data when the data transmission fails. Since retransmission may be repeated in the retransmission period, power consumption of the first device 202-1 and the second device 202-2 may increase.

Hereinafter, various embodiments of the present document may be described with reference to FIGS. 4 to 17 . Hereinafter, the user device 201, the first device 202-1, and/or the second device 202-2 may exchange data within a retransmission interval within the transmission/reception interval. The user device 201 , the first device 202-1 , and/or the second device 202-2 may enhance audio data using data received within the retransmission period.

4 is a block diagram of electronic devices according to an exemplary embodiment.

According to various embodiments, various electronic devices (eg, the user device 201 , the first device 202-1 , and the second device 202-2) disclosed herein are described above with reference to FIG. 1 . It may include at least some of the components of an electronic device (eg, the electronic device 101 of FIG. 1 ).

According to various embodiments, the user device 201 includes a processor 320 (eg, the processor 120 of FIG. 1 ), a memory 330 (eg, the memory 130 of FIG. 1 ), a first communication circuit ( 391) (eg, the communication module 190 of FIG. 1 ) and/or the second communication circuit 392 (eg, the communication module 190 of FIG. 1 ). The processor 320 may be operatively coupled to the first communication circuit 391 , the second communication circuit 392 , and the memory 330 . The memory 330 may store one or more instructions that, when executed, cause the processor 320 to perform various operations of the user device 201 . The second communication circuit 392 may be configured to support wireless communication based on a Bluetooth protocol (eg, legacy Bluetooth and/or BLE). The first communication circuit 391 may be configured to support communication based on a wireless communication standard (eg, cellular and/or Wi-Fi) excluding the Bluetooth protocol. The user device 201 may further include a configuration not shown in FIG. 4 . For example, the user device 201 further includes a display (eg, the display device 160 of FIG. 1 ), an audio input/output device (eg, the audio module 170 of FIG. 1 ), and/or a housing. can do.

The user device 201 may be connected to the first device 202-1 through a first link 205 . For example, the user device 201 and the first device 202-1 may communicate in units of time slots set based on the clock of the master device of the first link 205 . For example, one time slot may be configured such that the master device transmits data to the slave device or the slave device transmits data to the master device. For example, one time slot may have a length of 625 μs (micro second).

The user device 201 may transmit the data packet over the first link 205 . For example, the user device 201 may transmit audio data in a synchronous connection oriented (SCO) or extended SCO (eSCO) scheme.

The user device 201 may receive a response message to the data transmitted through the first link 205 . For example, the user device 201 may receive a response message transmitted from the first device 202-1 through the first link 205 . The user device 201 may receive the response message transmitted from the second device 202 - 2 through the first link 205 . For example, the user device 201 may receive a response message transmitted by the second device 202 - 2 using the information of the first device 202-1 through the first link 205 . According to an embodiment, the response message indicates a negative acknowledgment (NACK) or a response within a specified time after data transmission (eg, a time slot allocated to the first device 202-1 within the transmission/reception interval) If the message is not received, the user device 201 may retransmit the data via the first link 205 . A value of an automatic repeat request number (ARQN) field of a header of a packet indicating negative acknowledgment may be set to 0. For example, the user device 201 may retransmit data within a retransmission window of the first link 205 .

According to an embodiment, the user device 201 may be connected to the second device 202 - 2 through a second link 210 . For example, the user device 201 may establish the second link 210 after connection with the first device 202-1. The fact that the user device 201 can transmit information related to the first link 205 to the second device 202 - 2 through the second link 210 is as described above with reference to FIGS. 2 and 3 . According to an embodiment, the second link 210 may be omitted. In this case, the second device 202 - 2 may receive information related to the first link 205 from the first device 202-1 or from an external server (eg, the external server 203 in FIG. 2 ). have.

According to an embodiment, the first device 202-1 includes a processor 421 (eg, the processor 120 of FIG. 1 ), a memory 431 (eg, the memory 130 of FIG. 1 ), and an audio output circuit. 471 (eg, audio module 170 of FIG. 1 ), audio receiving circuit 481 (eg, audio module 170 of FIG. 1 ), and/or communication circuitry 491 (eg, communication of FIG. 1 ) module 190). The processor 421 may be operatively coupled to the communication circuit 491 , the audio output circuit 471 , the audio receiving circuit 481 , and the memory 431 . The audio output circuit 471 may be set to output sound. The audio receiving circuit 481 may include one or a plurality of microphones. In an embodiment, each of the plurality of microphones may correspond to a different audio reception path. For example, when the audio receiving circuit 481 includes the first microphone and the second microphone, the audio signal obtained by the first microphone and the audio signal by the second microphone may be referred to as different audio channels. . The processor 421 may acquire audio data by using at least one of a plurality of microphones connected to the audio receiving circuit 481 . The processor 421 may, for example, dynamically select or determine at least one microphone for acquiring audio data among a plurality of microphones. The processor 421 may acquire audio data by performing beamforming using a plurality of microphones. The memory 431 may store one or more instructions that, when executed, cause the processor 421 to perform various operations of the first device 202-1. The first device 202-1 may further include a configuration not shown in FIG. 4 . For example, the first device 202-1 may further include an indicator (eg, the display device 160 of FIG. 1 ), an input interface (eg, the interface 177 of FIG. 1 ), and/or a housing. may include As another example, the first device 202-1 includes a sensor (eg, a proximity sensor and/or a heart rate sensor) configured to detect whether the first device 202-1 is worn (eg, the sensor module ( 176)) may be further included.

The first device 202-1 may be connected to the user device 201 through a first link 205 . For example, the user device 201 and the first device 202-1 may communicate in units of time slots set based on the clock of the master device of the first link 205 . For example, one time slot may be configured such that the master device transmits data to the slave device or the slave device transmits data to the master device. For example, one time slot may have a length of 625 μs (micro second).

The first device 202-1 may receive a data packet from the user device 201 via the first link 205 . In an embodiment, the first device 202-1 may transmit a response message to the received data packet to the user device 201 through the first link 205 . For example, the first device 202-1 may transmit a response message indicating ACK when data is successfully received, and a response message indicating NACK when data reception fails. In another embodiment, the first device 202-1 may be configured to transmit a response message indicating a NACK regardless of whether data is received in order to trigger retransmission of the user device 201 . In another embodiment, the first device 202-1 may be configured to transmit a response message indicating NACK only when data reception fails, and not to transmit a response message when data reception is successful. According to an embodiment, the response message received from the first device 202-1 may further include audio data obtained by the audio receiving circuit 481 .

According to an embodiment, the first device 202-1 may be connected to the second device 202-2 through a third link 215 . For example, the first device 202-1 may establish a third link 215 with the second device 202-2. For example, the channel access code (CAC) of the first link 205 may be generated based on a low address part (LAP) of the Bluetooth address of the master device of the first link 205 . The CAC is used for communication between two electronic devices (eg, the user device 201 and the first device 202-1) of the corresponding link (eg, the first link 205) after the connection of the associated link is completed. may be an access code. The first device 202-1 may transmit the generated CAC and/or the Bluetooth address of the master device of the first link 205 to the second device 202-2 as at least part of the first link information. . In this case, the first device 202 - 1 may transmit the first link information to the second device 202 - 2 through the third link 215 .

For example, LT_ADDR may be an address allocated by the master device of the first link 205 . The first device 202-1 may transmit the LT_ADDR to the second device 202-2 as at least part of the first link information.

For example, the used channel map may be channel hopping information set by the master device of the first link 205 . The first device 202-1 may transmit the used channel map to the second device 202-2 as at least part of the first link information.

For example, the clock information may include clock information of a master device and/or a slave device of the first link 205 . The first device 202-1 may transmit clock information to the second device 202-2 as at least part of the first link information.

According to various embodiments, the second device 202 - 2 includes a processor 422 (eg, the processor 120 of FIG. 1 ), a memory 432 (eg, the memory 130 of FIG. 1 ), and an audio output. circuitry 472 (eg, audio module 170 of FIG. 1 ), audio receiving circuit 482 , and/or communication circuitry 492 (eg, communication module 190 of FIG. 1 ). The processor 422 may be operatively coupled to the communication circuit 492 , the audio output circuit 472 , the audio receive circuit 482 , and the memory 432 . The audio output circuit 472 may be set to output a sound. The audio receiving circuit 482 may include one or a plurality of microphones. In an embodiment, each of the plurality of microphones may correspond to a different audio reception path. For example, when the audio receiving circuit 482 includes the first microphone and the second microphone, the audio signal obtained by the first microphone and the audio signal by the second microphone may be referred to as different audio channels. . The memory 432 may store one or more instructions that, when executed, cause the processor 422 to perform various operations of the second device 202 - 2 . The second device 202 - 2 may further include a configuration not shown in FIG. 4 . For example, the second device 202 - 2 includes an indicator (eg, the display device 160 of FIG. 1 ), an audio input device (eg, the audio module 170 ), and an input interface (eg, the interface of FIG. 1 ). 177)), and/or a housing. As another example, the second device 202 - 2 may further include a sensor (eg, a proximity sensor and/or a heart rate sensor) configured to detect whether the second device 202 - 2 is worn.

According to an embodiment, the user device 201 includes a first communication circuit 391 supporting wireless communication, a second communication circuit 392 supporting Bluetooth communication, the first communication circuit 391 and the second communication circuit 391 . A processor 320 operatively coupled to the communication circuit 392 , and a memory 330 operatively coupled to the processor. The memory 330 may store one or more instructions that, when executed, cause the processor 320 to perform operations to be described later. For example, the processor 320 uses the second communication circuit 392 to link with the first device 202-1 based on a synchronous connection protocol (eg, eSCO) (eg, the first link 205 ). )) can be created. For example, the synchronous connection protocol may be referred to as a protocol for transmitting and receiving real-time audio data. The processor 320 transmits first data (eg, data including first audio data or NULL data) through the link in a first time slot among a plurality of time slots in one transmission/reception section of the link. 1 device can transmit. The processor 320 receives second data (eg, data including second audio data or NULL data) acquired by the first device 202-1 in a second time slot among the plurality of time slots. It can be received from the first device 202-1 through a link. The processor 320 receives third data including additional data for the second data within a retransmission interval set for data retransmission among the plurality of time slots, and based on the second data and the third data and the audio data generated by the method may be transmitted to an external electronic device using the first communication circuit 391 .

The processor 320 may transmit information indicating whether to support the additional data to the first device when the link is created with the first device 202-1. For example, information indicating whether the additional data is supported may be indicated by codec information used for audio data of the link.

The processor 320 may be configured to retransmit the first data within the retransmission interval when the second data is not received in the second time slot or second data including a negative acknowledgment is received. have.

For example, the third audio data included in the third data may be audio data of an audio channel different from the second audio data included in the second data. The third data may be audio data obtained by the second device 202-2 different from the first device 202-1. The third audio data may be audio data of a different section from the second audio data in the time domain.

According to an embodiment, the processor 320 may transmit additional data for improving the sound quality of the first audio data to the first device within the retransmission period.

According to an embodiment, the first device 202-1 includes an audio receiving circuit 481 connected to at least one microphone, a communication circuit 491 configured to support Bluetooth communication, the audio receiving circuit 481 and the wireless A processor 421 operatively coupled to the communication circuit 491 , and/or a memory 431 operatively coupled to the processor 421 . The memory 431 may store one or more instructions that, when executed, cause the processor 421 to perform operations to be described later. The processor 421 connects to the user device 201 through the first link 205 using the wireless communication circuit 491 , and the second device 202 - 2 through the third link 215 . can be connected with The processor 421 may transmit the first link information including the channel information of the first link 205 to the second device 202 - 2 through the third link 215 . The processor 421 may generate an extended synchronous connection oriented (eSCO) link based on a synchronous connection protocol with the user device 201 through the first link 205 . The processor 421 receives first data from the user equipment 201 in a first time slot among a plurality of time slots of one transmission/reception interval of the eSCO link, and a second time among the plurality of time slots. In the slot, second data (eg, data including the second audio data obtained using the audio receiving circuit 481 ) may be transmitted. The processor 421 uses third data (eg, the audio receiving circuit 481 ) including additional data for improving the sound quality of the second data in a retransmission period set for data retransmission of the plurality of time slots. data including the obtained third audio data) may be set to be transmitted.

For example, the audio receiving circuit 481 is connected to a first microphone and a second microphone, the second audio data is obtained through the first microphone, and third audio data of the third data is 2 It can be acquired through a microphone. For example, the second audio data and the third audio data may be obtained in different time domains.

The processor 421 transmits the additional data if the audio codec information associated with the eSCO link corresponds to a specified codec, and does not transmit the additional data if the audio codec information associated with the eSCO link does not correspond to the specified codec. can

The processor 421 may receive additional data for improving the sound quality of the first audio data from the first external electronic device in the retransmission period.

5 illustrates a signal flow diagram 500 for communication between electronic devices according to various embodiments of the present disclosure.

Referring to FIG. 5 , in operation 505 , the user device 201 may establish a first link (eg, the first link 205 of FIG. 2 ) with the first device 202-1. According to an embodiment, the user device 201 may be connected to the first device 202-1 through a first link 205 .

In operation 510 , the user device 201 may establish a second link (eg, the second link 210 of FIG. 2 ) with the second device 202 - 2 . According to an embodiment, the user device 201 may be connected to the second device 202 - 2 through a second link 210 . The establishment of the second link 210 is exemplary, and embodiments of the present document are not limited thereto. For example, the user device 201 and the second device 202 - 2 may establish the second link 210 before the establishment of the first link 205 (eg, operation 505). For example, the second link 210 may be released after sharing of the first link information (eg, operation 520 ). As another example, establishment of the second link 210 (eg, operation 510 ) may be omitted. For example, operation 505 may be performed based on an input to the user device 201 .

6 illustrates a user interface (UI) indicating connection of devices in a Bluetooth network environment according to various embodiments of the present disclosure. 6 shows an embodiment in which the first device 202-1 and the second device 202-2 are configured as a set, the user device 201 only shows a connection with the first device 202-1. The same principle can be applied to interfaces.

Referring to FIG. 6 , at reference numeral 601 , the user device 201 recognizes the first device 202-1 by receiving an advertising signal transmitted from the first device 202-1 ( a first user interface 610 for notifying the user of the recognized first device 202-1 and the first device 202-1 and the second device 202-2 to the user device 201 may be output through the display 360 of For example, the first device 202-1 and the second device 202-2 may constitute one set or one pair. The user of the user device 201 may recognize the first device 202-1 and the second device 202-2 as one electronic device.

The first user interface 610 may be, for example, an image 615 representing the shapes of the first device 202-1 and the second device 202-2 or the first device 202-1 and the second device. At least one of text 617 indicating the device name (eg, My Galaxy Buds) of 202 - 2 may be included. For another example, although not shown in FIG. 6 , the first user interface 610 may indicate whether the first device 202-1 or the second device 202-2 has a previous connection history.

According to an embodiment, the advertising signal may include information for connection (or pairing) between the user device 201 and the first device 202-1. For example, the advertising signal may include identification information of the first device 202-1, user account information, current pairing information indicating whether the first device 202-1 is pairing with another device, the first device ( 202-1) is a pairing list indicating a list of previously paired devices, simultaneous pairing information indicating devices that can be paired with the first device 202-1 at the same time, transmit power, detection area, or battery It may include at least one of status information. As another example, when the first device 202-1 forms a set with the second device 202-2, the advertising signal may include identification information of the second device 202-2 and user account information. , current pairing information indicating whether the second device 202-2 is pairing with another device, a pairing list indicating a list of devices with which the second device 202-2 has previously been paired, a second device ( 202-2) may further include at least one of simultaneous pairing information indicating a device capable of pairing at the same time, transmission power, detection area, or battery state information.

According to an embodiment, the first device 202-1 may transmit an advertising signal through a multicast method or a broadcast method.

According to an embodiment, the first device 202-1 may transmit an advertising signal according to a specified condition. For example, the first device 202-1 may transmit an advertising signal in response to detecting that the case in which the first device 202-1 is stored is opened. As another example, the first device 202-1 may transmit an advertising signal in response to power being supplied or receiving a user input. As another example, the first device 202-1 may transmit an advertising signal at every designated period.

According to an embodiment, the user device 201 automatically responds to receiving a user input for the connection UI 618 requesting a connection with the first device 202-1, or automatically without a user input. A first link (eg, the first link 205 of FIG. 2 ) may be established (eg, operation 505 of FIG. 5 ) with step 202-1. According to an embodiment, the user device 201 and the first device 202-1 may establish the first link 205 according to a procedure based on the Bluetooth standard. For example, the user device 201 and the first device 202-1 perform a baseband page procedure for recognizing the counterpart device, a link manager protocol (LMP) version, and a clock offset. offset), and/or an LMP procedure for identifying a supported feature (eg, a supported feature), a host request/response procedure for confirming the connection, and whether the counterpart device is a trusted device. An authentication procedure, an encryption procedure, and/or a setup complete procedure for notifying the host of the completion of the connection (eg, the first link 205 ) may be performed to check whether the .

When the first link 205 is established, as indicated by reference numeral 602 , the user device 201 displays a second user interface 620 indicating that the first device 202-1 is connected with the user device 201 . It can be output through (360). The second user interface 620 further includes, for example, the first electronic device 202-1 and an image 625 indicating battery states of the first device 202-1 and the second device 202-2. may include The second user interface 620 illustrated in FIG. 6 is exemplary and embodiments of the present document are not limited thereto. The image 625 of FIG. 6 is, for example, an image (eg, one battery type and/or one battery state) integrally representing the battery states of the first device 202-1 and the second device 202-2. image containing the battery level). The second user interface 620 may further include battery information of the cases of the first device 202-1 and the second device 202-2.

Although not shown in FIG. 6 , according to an embodiment, the user device 201 is connected to the first device 202 with an external device other than the first device 202-1 and the second device 202-2. When -1) is discovered, the user device 201 may be configured so that the first device 202-1 or the second device 202-2 may monitor a pre-connected link between the user device 201 and an external device. ) may transmit information about a pre-connected link to the first device 202-1 or the second device 202-2. In this case, the first user interface 610 may include information indicating that the first device 202-1 or the second device 202-2 can be added. When a user input requesting addition of the first device 202-1 or the second device 202-2 is received, the user device 201 is the first device 202-1 or the second device 202-2. ) to transmit information about a pre-connected link.

Referring back to Fig. 5 (referring back to Fig. 5), in operation 515, the first device 202-1 and the second device 202-2 connect to a third link (eg, the third link ( 215)) can be established. The establishment of the third link 215 is exemplary, and various embodiments of the present document are not limited thereto. For example, the first device 202-1 and the second device 202-2 may establish the third link 215 before establishment of the first link 205 (eg, operation 505). As another example, the first device 202-1 and the second device 202-2 may establish the third link 215 before establishment of the second link 210 (eg, operation 510). In another example, the first device 202-1 and the second device 202-2 may be configured to establish the third link 215 substantially simultaneously with the establishment of the first link 205 or the establishment of the second link 210 . ) can be established. As another example, establishment (eg, operation 515) of the third link 215 may be omitted, and in this case, the first link information (eg, operation 520) is transmitted to the second link through an external server (not shown). may be shared with the device 202-2.

In operation 520 , information associated with the first link 205 may be shared with the second device 202 - 2 . According to an embodiment, the user device 201 or the first device 202-1 may share information related to the first link 205 to the second device 202-2. For example, the first device 202-1 may transmit information related to the first link 205 to the second device 202-2 via the third link 215 . As another example, the user device 201 may transmit information related to the first link 205 to the second device 202 - 2 via the second link 210 . As another example, the user device 201 or the first device 202-1 is an external server (eg, the external server 203 of FIG. 2 ) or an external electronic device (eg, the first device 202-1) and the charging case of the second device 202 - 2 ) may transmit information related to the first link 205 to the second device 202 - 2 . According to an embodiment, the user device 201 or the first device 202-1 may determine whether to share information related to the first link 205 . For example, when the user device 201 or the first device 202-1 is determined to share information related to the first link 205, the user device 201 or the first device 202-1 sends the second device 202-2 to the first link 205 Relevant information can be conveyed. The information associated with the first link 205 may include, for example, at least one of address information, clock information, channel information, SDP result information, information about a supported function, key information, or an EIR packet.

In operation 525 , the user device 201 may transmit a data packet (eg, a first data packet) including content to the first device 202-1 through the first link 205 . In operation 530 , the second device 202 - 2 may monitor the first link 205 based on at least a part of information related to the first link 205 (eg, address information or clock information). The second device 202 - 2 may receive the same data packet as the data packet (eg, the first data packet) received by the first device 202 - 1 through monitoring. Operation 530 may be referred to as shadowing, listening, or snooping.

According to various embodiments, each of the first link 205 , the second link 210 , and the third link 215 may be a link based on a Bluetooth legacy protocol or a BLE protocol.

Fig. 7 shows a signal flow diagram 700 for creating a link between a user device and a first device according to an embodiment.

According to an embodiment, after creation of the first link 205 (eg, operation 505 in FIG. 5 ), the user device 201 and the first device 202-1 connect to a link for exchanging audio data (eg, an eSCO link). ) can be created. For example, the user device 201 may generate a link for exchanging audio data according to execution of an application or call application requesting voice recognition or execution of a function of the corresponding application. In this case, the user device 201 may generate a link for exchanging audio data through the first link 205 . The link for exchanging audio data may be, for example, a link having the same channel access code as that of the first link 205 and a different address (eg, LT_ADDR) from the first link 205 .

In operation 705 , the user device 201 may transmit information for establishing a link to the first device 202-1. The user device 201 may transmit information for link establishment using a link manager (LM) message (eg, eSCO_req LM message). Information for link establishment includes transmission/reception interval information (eg TeSCO), retransmission interval information (eg WeSCO), packet type information (eg transmission packet type and/or reception packet type), and packet size information (eg transmission packet size). and/or received packet size), and/or address information (eg, LT_ADDR). For example, information for link establishment may be referred to as a parameter associated with a link.

In operation 710, if link operation is possible according to the information for link establishment received by the first device 202-1, the first device 202-1 may transmit a response message (eg, accepted_ext Message). . For example, the response message may include information indicating consent to the link establishment information received from the user device 201 . When the first device 202-1 agrees to create a link for exchanging audio data but wants to change a parameter of the link, the first device 202-1 sends a message for link establishment including the parameter to be changed. (eg, eSCO_req Message) may be transmitted to the user device 201 . The user device 201 and the first device 202-1 may negotiate until a response message (eg, accepted_ext Message) to the message for link establishment is received from the counterpart device.

In operation 715 , the user device 201 and the first device 202-1 may transmit/receive a packet (eg, a packet including audio data) through the generated eSCO link.

8A illustrates packet exchange with additional data transmission according to an embodiment.

In the example of FIG. 8A , the first device 202-1 and the user device 201 may be connected through a link generated according to the operations of FIG. 7 . It may be assumed that the second device 202 - 2 monitors the link between the first device 202-1 and the user device 201 . The user 899 may, as a user of the user device 201 , speak while wearing the first device 202-1 and the second device 202-2, for example. The user device 201 may be connected to the external electronic device 890 for voice call, video call, audio data recording, or voice recognition. Also, in the example of FIG. 8A , the second device 202 - 2 may be configured to transmit additional data. For example, the first device 202-1 and/or the user device 201 may allow the second device 202-2 to transmit additional data after eSCO link establishment of FIG. 7 or while performing eSCO link establishment operations. You can decide to send it. For another example, the first device 202-1 may negotiate with the second device 202-2 or determine that the second device 202-2 transmit additional data via the third link 215. have. In one embodiment, if the user device 201 is unaware of the existence of the second device 202 - 2 , the user device 201 sends additional data that the second device 202 - 2 transmits to the first device 202 . -1) can be recognized as transmitted. For example, the first device 202-1 may cause the first device 202-1 to transmit additional data after establishing the eSCO link of FIG. 7 with the user device 201 or while performing the establishment operations of the eSCO link. It may be determined, and the second device 202 - 2 may determine to transmit additional data through negotiation with the second device 202 - 2 . For example, the second device 202 - 2 may include information about a link established between the user device 201 and the first device 202-1 (eg, the first link 205 ) and the first device 202-1 ) by transmitting the additional data based on the information (eg, device address information), the user device 201 may determine that the first device 202-1 has transmitted the additional data.

In FIG. 8A , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) of 16 slots and a retransmission interval (WeSCO) of 4 slots. can be set. Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto. Also, in FIG. 8A , it is assumed that the user device 201 is the master device of the eSCO link, but various embodiments of the present document are not limited thereto.

In the example of FIG. 8A , the user device 201 may receive the first external data 891 from the external electronic device 890 . For example, the user device 201 receives the first external data 891 and/or the second external data from the external electronic device 890 via the first communication circuit 391 (eg, a cellular network and/or the Internet). (892) can be received.

In the first slot S1 of the first transmission/reception period T1, the user device 201 may transmit the first data 801 through the eSCO link. The first device 202-1 and the second device 202-2 may receive the first data 801 . For example, the first data 801 may include audio data corresponding to at least a portion of the audio data included in the first external data 891 . As another example, the first data 801 may correspond to NULL data.

In the second slot S2 of the first transmission/reception period T1, the first device 202-1 may transmit the second data 802 through the eSCO link. The second data 802 may include, for example, audio data acquired by the first device 202-1 in a time period prior to the first transmission/reception period T1. For example, the second data 802 may further include ACK/NACK information for the first data 801 . ARQN information of the header of the second data 802 may be set to ACK.

In the third slot S3 of the first transmission/reception period T1, the user device 201 may transmit the third data 803 through the eSCO link. For example, the third data 803 may be a POLL packet including ACK information for the second data 802 .

According to an embodiment, the second device 202 - 2 may transmit additional data using at least one slot of the first retransmission period W1. In the fourth time slot S4 set for retransmission of the first device 202-1 in the first retransmission period W1, the second device 202-2 receives additional data (eg, fourth data 804). ) can be sent. For example, the additional data may include audio data acquired by the second device 202 - 2 at substantially the same time as the second data 802 . For another example, the additional data may include any audio enhancement parameters obtained at substantially the same time as the second data 802 . In FIG. 8A , the second device 202 - 2 is shown to transmit additional data, but embodiments of the present document are not limited thereto. For example, the first device 202-1 and/or the user device 201 may be configured to transmit additional data within a retransmission interval.

In the example of FIG. 8A , the user device 201 may generate enhanced audio data using the second data 802 and the fourth data 804 . The user device 201 may transmit enhanced audio data (not shown) to the external electronic device 890 . In one example, the user device 201 may recognize that the fourth data 804 has been received from the first device 202-1. Since the second device 202-2 transmits the fourth data 804 using the radio resource of the eSCO link generated via the first link 202-1, the user device 201 transmits the fourth data ( 804 ) may be recognized as being received from the first device 202-1.

In the first transmission/reception period T1, all data transmission/reception was successfully performed, but in the second transmission/reception interval T2, data transmission/reception may be interrupted due to deterioration of the communication environment.

In the first slot S1 of the second transmission/reception period T2, the user device 201 may transmit the fifth data 805 through the eSCO link. The first device 202-1 and the second device 202-1 may receive the fifth data 805 . The fifth data 805 may include audio data corresponding to at least a portion of the audio data included in the first external data 891 and/or the second external data 892 .

In the second slot S2 of the second transmission/reception period T2, the first device 202-1 may transmit the sixth data 806 through the eSCO link. The sixth data 806 may include audio data acquired by the first device 202-1 in a time period prior to the second transmission/reception period T2. For example, ARQN information of a header of the sixth data 806 may be set to ACK. In the example of FIG. 8A , the user device 201 may fail to receive the sixth data 806 .

In the third time slot S3 of the second retransmission period W2, the user device 201 receives data for retransmitting the fifth data (hereinafter, the seventh data (hereinafter referred to as the seventh data) according to the failure of reception of the ACK for the fifth data. 807)) through the eSCO link. For example, the seventh data 807 may include at least a portion of the fifth data 805 and information indicating NACK in a header.

In the fourth time slot S4 of the second retransmission period W2 , the second device 202 - 2 may transmit the eighth data 808 including additional data. Even when NACK-indicating information (eg, the seventh data 807) is received from the user device 201, the second device 202-2 is configured for additional data transmission among slots configured for retransmission. (eg, the fourth slot S4) may be used to transmit additional data. The user device 201 may fail to receive the eighth data 808 .

In the fifth time slot S5 of the second retransmission period W2 , the user device 201 may retransmit the seventh data 807 . In the sixth time slot S6 of the second retransmission period W2 , the first device 202-1 may attempt to retransmit the sixth data 806 . In the example of FIG. 8A , the user device 201 may acquire only the sixth data 806 transmitted in the sixth time slot S6 . For another example, although not shown, the user device 201 may fail to receive the retransmitted data in the second retransmission period W2 . In this case, in the subsequent transmission/reception section (not shown), the user device 201 receives new data (eg, ninth data (not shown) even when the sixth data 806 and/or the eighth data 808 fails to be received). time)) can be attempted.

The transmission of additional data using the retransmission interval described above in FIG. 8A is exemplary, and embodiments are not limited thereto. For example, various embodiments described below may be used with respect to a type of additional data, an apparatus for transmitting additional data, a method for transmitting additional data, and/or retransmission of data.

8B illustrates packet exchange with additional data transmission according to an embodiment.

According to an example, not only the second device 202 - 2 , but also the user device 201 may be configured to transmit additional data. Hereinafter, a method in which the user device 201 and the second device 202 - 2 transmit additional data may be described with reference to FIG. 8B . Unless otherwise stated, the descriptions described above with respect to FIG. 8A may be applied to the description below.

Referring to FIG. 8B , the user device 201 and the second device 202 - 2 may be configured to transmit additional data. For example, the first device 202-1 and/or the user device 201 may perform the eSCO link establishment or eSCO link establishment operations of FIG. 7 between the user device 201 and the second device 202- 2) may decide to transmit additional data. In an embodiment, the user device 201 may recognize that the additional data transmitted by the second device 202 - 2 is transmitted by the first device 202 - 1 .

In the first slot S1 of the first transmission/reception period T1, the user device 201 may transmit the first data 801 through the eSCO link. In the second slot S2 of the first transmission/reception period T1, the first device 202-1 may transmit the second data 802 through the eSCO link.

In the third slot S3 of the first transmission/reception period T1, the user device 201 may transmit the third data 803 through the eSCO link. The third data 803 may include additional data obtained by the user device 201 or received from the external electronic device 890 . For example, the additional data may be additional data for the first data 801 . For example, the third data 803 may include ACK information for the second data 802 in a header. The first device 202-1 and/or the second device 202-2 may use the first data 801 and the third data 803 to generate enhanced audio data.

In the first slot S1 of the second transmission/reception period T2, the user device 201 may transmit the fifth data 805 through the eSCO link. The first device 202-1 and the second device 202-1 may fail to receive the fifth data 805 . The fifth data 805 may include audio data corresponding to at least a portion of audio/audio data included in the first external data 891 and/or the second external data 892 .

In the second slot S2 of the second transmission/reception period T2, the first device 202-1 may transmit the sixth data 806 through the eSCO link. For example, ARQN information of a header of the sixth data 806 may be set to NACK. In the example of FIG. 8B , the user device 201 may fail to receive the sixth data 806 .

In the third time slot S3 of the second retransmission period W2 , the user device 201 may transmit the seventh data 807 including additional data. For example, the seventh data 807 may include additional data for the fifth data 805 . The seventh data 807 may include information indicating NACK in the header.

In the fourth time slot S4 of the second retransmission period W2 , the second device 202 - 2 may transmit the eighth data 808 including additional data. The user device 201 may fail to receive the eighth data 808 .

In the fifth time slot S5 of the second retransmission period W2 , the user device 201 may retransmit the fifth data 805 . The user device 201 may retransmit the fifth data 805 in the fifth time slot S5 instead of the third time slot S3 set for additional data transmission. In this case, the header of the fifth data 805 may include information indicating NACK. In the sixth time slot S6 of the second retransmission period W2 , the first device 202-1 may attempt to retransmit the sixth data 806 .

8A and 8B, the user device 201, the first device 202-1, and the second device 202-2 are each shown as using one slot for data transmission, but The embodiments are not limited thereto. For example, the user device 201 , the first device 202-1 , and/or the second device 202-2 may transmit data using a plurality of consecutive slots.

In one example, each of the user device 201 , the first device 202-1 , and the second device 202-2 may be configured to transmit data using three consecutive slots. In this case, one transmission/reception interval of the eSCO link may include 18 slots, and the retransmission interval within one transmission/reception interval may include 6 slots. For example, the user device 201 transmits data (eg, first data) by using the three leading slots within the transmission/reception period, and the first device 202-1 transmits the first 3 slots following the first data. It can be set to transmit data (eg, second data) using the slots. Six slots from the 8th slot in the transmission/reception interval may be set as the retransmission interval. For example, the first three slots of the retransmission period are used for data transmission (eg, ACK/NACK and/or additional data transmission) of the user device 201, and the rear three slots are used for the first device 202-1 ) or data transmission (eg, transmission of ACK/NACK and/or additional data) of the second device 202 - 2 . In another example, the user device 201 is configured to transmit data using three consecutive slots, and each of the first device 202-1 and the second device 202-2 uses one slot. It can be set to transmit data. In this case, one transmission/reception interval of the eSCO link may include 18 slots, and the retransmission interval within one transmission/reception interval may include 6 slots. For example, the user device 201 transmits data (eg, first data) using the three leading slots within the transmission/reception section, and the first device 202-1 transmits 1 following the first data. It can be set to transmit data (eg, second data) using the slots. Six slots from the fourth slot in the transmission/reception interval may be set as the retransmission interval. For example, the first three slots of the retransmission section are used for data transmission (eg, ACK/NACK and/or additional data transmission) of the user device 201, and the fourth slot between the retransmission stations is used for the first device ( 202-1) or data transmission (eg, transmission of ACK/NACK and/or additional data) of the second device 202-2.

In the example of FIGS. 8A and 8B , the first device 202-1 transmits the acquired audio data (the second data 802 or the sixth data 806), and the second device 202-2 Although it is illustrated that additional data is transmitted in the retransmission sections W1 and W2, embodiments of the present document are not limited thereto. For example, as described below with reference to FIGS. 19 and 22 , the second device 202 - 2 may transmit audio data. The second device 202 - 2 may be configured to transmit audio data in a transmission slot (eg, S2 ) rather than a retransmission period. The first device 202-1 may be configured to transmit additional data in the retransmission period. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

9 is a flowchart 900 of a method for transmitting and receiving additional data for a user device according to an embodiment.

In operation 905 , the user device 201 may create a first link 205 with the first device 202-1. For example, the user device 201 may generate the first link 205 according to operation 505 of FIG. 5 .

In operation 910 , the user device 201 may determine whether the first device 202-1 supports additional data transmission/reception. For example, when the user device 201 and the first device 202-1 support additional data transmission/reception, the user device 201 may perform additional data transmission/reception according to embodiments of the present document.

According to an embodiment, the user device 201 may determine whether the first device 202-1 supports additional data transmission/reception based on capability information of the first device 202-1. When pairing with the first device 202-1, the user device 201 may determine whether the first device 202-1 supports additional data transmission/reception. The user device 201 provides the capability information (eg, support feature) of the first device 202-1 from the first device 202-1 during or after the first link 205 connection. (supported feature) information).

According to an embodiment, the user device 201 may determine whether the first device 202-1 supports additional data transmission/reception based on a specified signal received from the first device 202-1. For example, when the user device 201 receives a command COMMAND indicating that the first device 202-1 supports the additional data, the user device 201 determines that the first device 202-1 supports the additional data. can

If additional data is not supported (eg, 910-N), in operation 915 , the user device 201 may transmit/receive audio data without supporting additional data. In this case, the user device 201 and the first device 202-1 may use the retransmission section only for data retransmission. According to an embodiment, even if the first device 202-1 does not support the additional data, the user device 201 performs audio data (eg, among the first device 202-1 and the second device 202-2). : In the second slot S2) of FIGS. 8A and 8B, a device to transmit data) may be determined. A method of determining the audio data transmission device of the user device 201 may be described later with reference to FIG. 18 .

When the first device 202-1 supports transmission/reception of additional data (eg, 910-Y), in operation 920 , the user device 201 negotiates a transmission method of additional data with the first device 202-1. can do. For example, the negotiation of the method of transferring the additional data may include negotiation of at least one of a transmission time of the additional data, a sending entity of the additional data, a retransmission method associated with the additional data transmission, and/or a type of the additional data. The user device 201 exchanges information on the additional data transmission method with the first device 202-1, or transmits information on the additional data transmission method to the first device 202-1 to determine the additional data transmission method. can negotiate For example, the user device 201 may negotiate with the first device 202-1 a subject to transmit additional data (eg, the user device 201 and/or the first device 202-1) and the additional data. You can decide when to send data (eg time slots). According to an embodiment, the user device 201 may transmit data in audio data (eg, the second slot S2 of FIGS. 8A and 8B ) among the first device 202-1 and the second device 202-2. device) can be determined. For example, the user device 201 may determine a device to transmit audio data during negotiation of an additional data transfer method (eg, operation 920 ). A method of determining the audio data transmission device of the user device 201 may be described later with reference to FIG. 18 .

In operation 925 , the user device 201 may create a link (eg, an eSCO link) for transmitting and receiving audio data with the first device 202-1. For example, the user device 201 may generate a link for transmitting and receiving audio data according to operations 705 and 710 of FIG. 7 .

In operation 930 , the user device 201 may transmit/receive audio data according to the negotiated method. In this case, the user equipment 201 may transmit the additional data or receive the additional data in at least a part of the retransmission interval WeSCO according to the negotiated method.

In the example of FIG. 9 , operations 910 and 920 are illustrated as being performed prior to operation 925 , but embodiments of the present document are not limited thereto. For example, operation 910 may be performed while operation 905 is being performed. As another example, operation 920 may be performed while operation 925 is being performed. As another example, operation 920 may be omitted. In this case, the user device 201 may transmit/receive additional data according to a designated method without a separate negotiation procedure. As another example, if it is determined in operation 915 that additional data transmission/reception is necessary during audio data transmission/reception without additional data support (eg, quality degradation occurs), operation 910 or less may be performed to perform additional data transmission/reception.

According to an embodiment, operations 910 and 920 may be performed while a link for audio data transmission/reception is being created (eg, operation 925). For example, the user device 201 may transmit link establishment information (eg, operation 705 of FIG. 7 ) for generating a link for audio data transmission/reception to the first device 202-1. The link establishment information may include codec information to be used for audio data transmission/reception. The user device 201 may indicate that the user device 201 supports transmission and reception of additional data by setting the corresponding codec information to a specified value. When consent information for the corresponding codec information is received from the first device 202-1 (eg, operation 710 of FIG. 7 ), the user device 201 indicates that the first device 202-1 supports additional data transmission/reception. it can be decided that Also, for example, the user device 201 may negotiate the additional data transmission/reception method by including information on the additional data transmission/reception method in the link establishment information. As another example, when it is determined that the first device 202-1 supports additional data transmission/reception, the user device 201 uses a separate message during or after creation of a link for transmitting/receiving audio data using a separate message. A transmission/reception method may be negotiated with the first device 202-1.

10 is a flowchart 1000 of a method for transmitting and receiving additional data by the first device according to an exemplary embodiment.

In operation 1005 , the first device 202-1 may create a first link 205 with the user device 201 . For example, the first device 202-1 may generate the first link 205 according to operation 505 of FIG. 5 .

In operation 1010 , the first device 202-1 may determine whether the user device 201 supports transmission/reception of additional data. According to an embodiment, the first device 202-1 may determine whether the user device 201 supports transmission/reception of additional data based on capability information of the user device 201 . The first device 202-1 receives the capability information (eg, supported feature) of the user device 201 from the user device 201 during or after the first link 205 connection. ) information) can be received. For example, the support feature information of the user device 201 may include information indicating whether the user device 201 supports additional data. According to an embodiment, the first device 202-1 is configured to use a user device (eg, a signal including a command indicating that additional data is supported) received from the first device 202-1. 201) may determine whether to support additional data transmission/reception.

If additional data is not supported (eg, 1010 -N), in operation 1015 , the first device 202-1 may transmit/receive audio data without supporting additional data. In this case, the user device 201 and the first device 202-1 may use the retransmission interval WeSCO only for data retransmission.

If additional data is supported (eg, 1010 -Y), in operation 1020 , the first device 202-1 may negotiate a method of transmitting the additional data with the user device 201 . The negotiation of the additional data transfer method may be referred to as described above with respect to FIG. 9 .

In operation 1025 , the first device 202-1 may connect to the second device 202-2. For example, the first device 202-1 may connect with the second device 202-2 by creating the third link 215 according to operation 515 of FIG. 5 . Although operation 1025 is shown to be performed after operation 1020 in FIG. 10 , embodiments of the present document are not limited thereto. For example, operation 1025 may be performed prior to operation 1005 or operation 1010 .

In operation 1030 , the first device 202-1 may share first link information with the second device 202-2. For example, the first device 202-1 may share the first link information according to operation 520 of FIG. 5 .

In operation 1035 , the first device 202-1 may negotiate an additional data transfer method with the second device 202-2. For example, the first device 202-1 may negotiate an additional data delivery method with the second device 202-2 when creating an eSCO link with the user device 201 . According to an embodiment, when the first device 202-1 transmits additional data based on information about the eSCO link created with the user device 201 (eg, a transmission/reception interval (TeSCO) or a retransmission interval (WeSCO)) , or which device will negotiate with the second device 202 - 2 to transmit. For example, in the first transmission slot of the retransmission interval (eg, the fourth slot S4 of FIG. 8A ), the second device 202-2 transmits the additional data or the first device 202-1 transmits the additional data can be negotiated to send As another example, based on data (eg, response data including ACK or NACK) received from the user device 201 in the first reception slot of the retransmission interval (eg, the third slot S3 of FIG. 8A ) The second device 202-2 may transmit the additional data or the first device 202-1 may negotiate to transmit the additional data.

In one example, operation 1035 may be omitted. For example, the first device 202-1 and the second device 202-2 may transmit additional data according to a specified method. As another example, the first device 202-1 may notify the second device 202-2 of a method to be used for additional data transmission.

According to an embodiment, the first device 202-1 is a device to transmit audio data (eg, a device to transmit data in the second slot S2 in FIGS. 8A and 8B ) with the second device 202-2 ). can negotiate For example, the user device 201 may determine a device to transmit audio data during negotiation of an additional data delivery method (eg, operation 1035 ). A method of determining the audio data transmission device of the user device 201 may be described later with reference to FIGS. 19 and 20 .

In operation 1040 , the first device 202-1 may create a link (eg, an eSCO link) for transmitting and receiving audio data with the user device 201 . For example, the first device 202-1 may generate a link for transmitting/receiving audio data according to operations 705 and 710 of FIG. 7 . 10 , the first device 202-1 is illustrated as performing operation 1040 after operation 1035, but embodiments of the present document are not limited thereto. For example, the first device 202-1 may perform operation 1040 at any time after the creation of the first link 205 with the user device 201 (eg, operation 1005). The first device 202-1 may, for example, perform operation 1040 prior to operation 1010 .

In operation 1045, the first device 202-1 may transmit/receive audio data according to the negotiated method. For example, the first device 202-1 may be configured to transmit additional data in at least a part of the retransmission interval according to the negotiated method. As another example, the first device 202-1 may be configured to receive additional data from the user device 201 in at least a part of the retransmission interval according to the negotiated method. As another example, when the first device 202-1 and/or the second device 202-2 is configured to transmit additional data, the first device 202-1 and the second device ( 202-2) may be set to transmit additional data at different timings.

11 is a flowchart 1100 of a method for transmitting and receiving additional data by a second device according to an embodiment.

In operation 1105 , the second device 202 - 2 may establish a link with the first device 202-1 . For example, the second device 202 - 2 may connect with the first device 202-1 by creating the third link 215 according to operation 515 of FIG. 5 .

In operation 1110 , the second device 202 - 2 may receive first link information from the first device 202-1. For example, the second device 202 - 2 may receive the first link information according to operation 520 of FIG. 5 .

In operation 1115 , the second device 202 - 2 may negotiate an additional data transfer method with the first device 202-1. For example, according to operation 1035 of FIG. 10 , an additional data transfer method may be negotiated with the first device 202-1. As another example, when additional data is transmitted in a specified manner, operation 1115 may be omitted.

In operation 1120 , the second device 202 - 2 may transmit/receive audio data according to the negotiated method. In this case, the second device 202-1 may transmit the additional data or receive the additional data in at least a part of the retransmission interval according to the negotiated method. For example, the second device 202-2 transmits additional data to the user device (eg, an eSCO link) using radio resources of a link (eg, an eSCO link) established between the user device 201 and the first device for transmitting and receiving voice data. 201) can be sent. The second device 202 - 2 may receive the additional data transmitted from the user device 201 by listening to the link for transmitting and receiving voice data established between the user device 201 and the first device.

12 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.

In the example of FIG. 12 , the first device 202-1 may be configured to transmit additional data within a retransmission interval. For example, the user device 201 and the second device 202 - 2 may be configured not to transmit additional data.

In FIG. 12 , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) (eg, T1 or T2) of 16 slots, and retransmission of 4 slots. It can be set to have a section (WeSCO) (eg, W1 or W2). In this example, the retransmission period (eg, W1 or W2) may include a third time slot S3, a fourth time slot S4, a fifth time slot S5, and a sixth time slot S6. have. Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto. Also, in FIG. 12 , it is assumed that the user device 201 is the master device of the eSCO link, but various embodiments of the present document are not limited thereto.

In an embodiment, in the first time slot S1 of the first transmission/reception period T1, the user device 201 transmits the first data 1201 to the first device 202-1 through the generated eSCO link. can send In the second time slot S2, the first device 202-1 transmits the second data 1202 including audio data obtained by the first device 202-1 to the user device 201 via the eSCO link. ) can be sent. In one example, the second data 1202 may further include ACK information for the first data 1201 . In the first time slot (eg, the third time slot S3) of the subsequent first retransmission period W1, the user equipment 201 receives the third data 1203 including an ACK for the second data 1202. ) to the first device 202-1 through the eSCO link.

In the fourth time slot S4 of the first transmission/reception period T1, the first device 202-1 transmits the fourth data 1204 including additional data to the user device 201 through the eSCO link. can The additional data may include information for enhancing the audio data of the second data 1202 . For example, the fourth data 1204 may include audio data of another channel acquired at the same time as the audio data of the second data 1202 . For example, the second data 1202 is audio data acquired through the first microphone of the first device 202-1, and the fourth data 1204 is the second microphone of the first device 202-1. It may be audio data obtained through As another example, the fourth data 1204 may include a sound quality improvement parameter for improving the sound quality of the second data 1202 . The user device 201 may perform sound quality improvement using the second data 1202 and the fourth data 1204 . For example, the sound quality improvement parameter includes comparison information between audio data acquired through the first microphone of the first device 202-1 and audio data acquired through the second microphone of the first device 202-1 ( Examples: similarity, correlation value and/or Euclidean distance). For example, the sound quality improvement parameter is based on a comparison between audio data obtained through a first microphone of the first device 202-1 and audio data obtained through a second microphone of the first device 202-1 and may include the generated reception sensitivity information.

In an embodiment, in the first time slot S1 of the second transmission/reception period T2, the user device 201 may transmit the fifth data 1205 through the eSCO link. The fifth data 1205 may be data contiguous with the first data 1201 stored in the transmission buffer to be transmitted to the first device 202-1 by the user device 201 . In the second time slot S2, the first device 202-1 may transmit the sixth data 1206 including the audio data obtained by the first device 202-1 through the eSCO link. . The sixth data 1206 may be continuous data of the second data 1202 that the first device 202-1 stores in a transmission buffer for transmission to the user device 201 . In one example, the sixth data 1206 may further include ACK information for the fifth data 1205 . In this example, the user device 201 may fail to receive the sixth data 1206 . In this case, in the first time slot (eg, the third time slot S3) of the subsequent first retransmission period W1, the user device 201 transmits the seventh data 1207 including the NACK to the eSCO link. may be transmitted to the first device 202-1 through the

In response to the reception of the seventh data 1207 , in the fourth time slot S4 of the second transmission/reception period T2 , the first device 202-1 transmits the sixth data 1206 to the user device 201 . can be resent. For example, if an affirmative acknowledgment for the previously transmitted sixth data 1206 is not received from the user device 201 , the first device 202-1 retransmits the retransmission of the sixth data 1206 . Retransmission may be repeatedly attempted within a section (eg, the second retransmission section W2). In this case, the first device 202-1 may omit transmission of additional data. As another example, the first device 202-1 attempts retransmission of the sixth data 1206 within a retransmission interval (eg, the second retransmission interval W2), and You may receive a positive acknowledgment response. In this case, the first device 202-1 may check whether additional data can be transmitted during the remaining retransmission period (eg, the second retransmission period W2). When it is determined that the transmission of the additional data can be performed, the first device 202-1 may transmit the additional data to the user device 201 .

In the second transmission/reception period T2 of FIG. 12 , the user device 201 may fail to receive data transmitted from the first device 202-1. The second device 202 - 2 may identify that the user device 201 has failed to receive data from the first device 202-1 by monitoring data transmitted from the user device 201 . When it is identified that repeated data reception failure from the user device 201 is identified, in the third transmission/reception section (not shown) subsequent to the second transmission/reception section T2, the second device 202-2 transmits audio data and/or It can be set to transmit additional data. In the third transmission/reception section (not shown), the first device 202-1 does not transmit data, and the second device 202-2 transmits data (eg: audio data and/or additional data). As another example, the first device 202-1 may transmit a signal instructing the second device 202-2 to change roles through the third link 215 . When the second device 202-2 receives a signal instructing to change the role, in the third transmission/reception section (not shown) subsequent to the second transmission/reception section T2, the second device 202-2 transmits audio data and/or to transmit additional data.

With reference to FIG. 12 , it has been described that data is acquired centering on the first microphone and the second microphone of the first device 202-1, but embodiments of the present document are not limited thereto. When the first device 202-1 includes a plurality of microphones, the first device 202-1 may acquire audio data and/or additional data based on various microphone combinations. For example, the second data 1202 is obtained by using the first microphone of the first device 202-1, and the fourth data 1204 is obtained by using the second microphone and the third microphone of the first device 202-1. It can be obtained using a microphone. As another example, the second data 1202 is obtained by using the first microphone and the second microphone of the first device 202-1, and the fourth data 1204 is obtained by using the first microphone 202-1 of the first device 202-1. It may be obtained using a third microphone.

12 , it has been described that only the first device 202-1 transmits additional data, but embodiments of the present document are not limited thereto. According to an embodiment, the user device 201 may also be configured to transmit additional data. In this case, the third data 1203 may include additional data for improving the sound quality of the first data 1201 . The seventh data 1207 transmitted in the third time slot S3 of the second transmission/reception period T2 may include additional data for improving the sound quality of the fifth data 1205 .

In the example of FIG. 12 , the first device 202-1 is illustrated as transmitting the acquired audio data and additional data, but embodiments of the present document are not limited thereto. For example, as described below with respect to FIGS. 19 and 20 , the second device 202 - 2 may transmit audio data and additional data. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

13 illustrates packet exchange by transmission of additional data of a second device according to an embodiment.

In the example of FIG. 13 , the second device 202 - 2 may be configured to transmit additional data within the retransmission interval. For example, the user device 201 and the first device 202-1 may be configured not to transmit additional data. The second device 202 - 2 may transmit additional data using a time slot allocated for transmission of the first device 202 - 1 . In this case, additional data may be transmitted/received as described above with reference to FIG. 8A . Hereinafter, a data retransmission method of a method different from that of FIG. 8A may be described with reference to FIG. 13 .

In FIG. 13 , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) (eg, T1 or T2) of 16 slots, and retransmission of 4 slots. It can be set to have a section (WeSCO) (eg, W1 or W2). Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto. Also, in FIG. 13 , it is assumed that the user device 201 is the master device of the eSCO link, but various embodiments of the present document are not limited thereto.

For example, in the first time slot S1 of the first transmission/reception period T1, the user device 201 transmits the first data 1301 to the first device 202-1 through the generated eSCO link. It can transmit to one device 202-1. In the second time slot S2 of the first transmission/reception period T1, the first device 202-1 transmits the second data 1302 including audio data acquired by the first device 202-1. may be transmitted to the user device 201 via the eSCO link. In one example, the second data 1302 may further include ACK information for the first data 1301 . In the second time slot S2 , the user device 201 may fail to receive the second data 1302 . In this case, in the third time slot S3 of the first transmission/reception period T1 , the user device 201 may transmit the third data 1303 indicating NACK to the first device 202-1. .

In the example of FIG. 13 , despite the reception of the third data 1303 indicating NACK, the second device 202-2 transmits additional data in the fourth time slot S4 of the first transmission/reception period T1. The included fourth data 1304 may be transmitted to the user device 201 . In the first retransmission period W1 of the first transmission/reception period T1, the second device 202-2 receives the fourth data 1304 including additional data regardless of the ACK/NACK of the user device 201 can be sent. For example, the additional data may include information for enhancing the audio data of the second data 1302 . For example, the fourth data 1304 may include audio data obtained by the second device 202 - 2 . As another example, the fourth data 1304 may include a sound quality improvement parameter obtained by the second device 202 - 2 .

In the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 retransmits the third data 1303 to the first device 202-1 according to not receiving the second data 1302 . can do. The first device 202-1 may retransmit the second data 1302 to the user device 201 after the second device 202-2 transmits the additional data. For example, the first device 202-1 may retransmit the second data 1302 in the sixth time slot S6 of the first transmission/reception period T1. According to an embodiment, the user device 201 includes the second data 1302 and the second device ( ) transmitted by the first device 202-1 in the second time slot S2 of the first transmission/reception period T1 . Even when 202-2 fails to receive the fourth data 1304 transmitted in the fourth time slot S4 of the first transmission/reception interval T1, the first device 202-1 performs the first transmission/reception interval T1. ), the second data 1302 retransmitted in the sixth time slot S6 may be received and processed.

For example, in the first time slot S1 of the second transmission/reception period T2, the user device 201 transmits the fifth data 1305 to the first device 202-1 through the generated eSCO link. It can transmit to one device 202-1. In the second time slot S2 of the second transmission/reception period T2, the first device 202-1 transmits the sixth data 1306 including the audio data acquired by the first device 202-1. may be transmitted to the user device 201 via the eSCO link. For example, the sixth data 1306 may include audio data subsequent to the audio data of the second data 1302 in the time domain. In the third time slot S3 of the second transmission/reception period T2, the user device 201 transmits the seventh data 1307 indicating NACK in response to non-reception of the sixth data 1306 to the first device 202 -1) can be sent. Similar to the first transmission/reception period T1, in the fourth time slot S4 of the second transmission/reception period T2, the second device 202-2 transmits the eighth data 1308 including additional data to the user. may transmit to device 201 . In an embodiment, even if the additional data transmitted by the second device 202 - 2 is successfully received, the user device 201 performs the second transmission/reception period T2 for retransmission of the sixth data 1306 . In the fifth time slot S5, the seventh data 1307 may be transmitted again. For example, when creating the first link 205 with the first device 202-1, the user device 201 may know whether the first device 202-1 supports additional data transmission/reception, and thus the first device 202-1. The seventh data 1307 may be transmitted to (202-1). In response to the reception of the seventh data 1307 , the first device 202-1 transmits the sixth data 1306 to the user device 201 in the sixth time slot S6 of the second transmission/reception period T2. can be resent. In the embodiment of FIG. 13 , the user device 201 may not receive the sixth data 1306 retransmitted by the first device 202-1.

According to an embodiment, the user device 201 performs the first device 202-1 and/or the second device ( 202-1) can receive and process the transmitted data or additional data. For example, in the first transmission/reception period T1 , the user device 201 may generate audio data using only the successfully received second data 1302 . In the second transmission/reception period T2 , the user device 201 may generate audio data using only the successfully received eighth data 1308 .

Although it has been described with reference to FIG. 13 that only the second device 202 - 2 transmits the additional data, embodiments of the present document are not limited thereto. According to an embodiment, the user device 201 may also be configured to transmit additional data. In this case, the third data 1303 may include additional data for improving the sound quality of the first data 1301 , and the seventh data 1307 may include additional data for improving the sound quality of the fifth data 1305 . can

In the example of FIG. 13 , the first device 202-1 is shown to transmit acquired audio data (eg, the second data 1302 and/or the sixth data 1306), but in the practice of this document, Examples are not limited thereto. For example, as described below with reference to FIGS. 19 and 20 , the second device 202 - 2 may transmit audio data. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

14 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.

In FIG. 14 , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) of 16 slots (eg, T1 or T2), and 6-slot retransmission. It can be set to have a section (WeSCO) (eg, W1 or W2). Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto. In this example, the retransmission period (eg, W1 or W2) is a third time slot (S3), a fourth time slot (S4), a fifth time slot (S5), a sixth time slot (S6), and a seventh time slot (S7) and an eighth time slot (S8). Also, in FIG. 14 , it is assumed that the user device 201 is the master device of the eSCO link, but various embodiments of the present document are not limited thereto.

According to an embodiment, the first device 202-1 and the user device 201 may be configured to transmit additional data. In the first time slot S1 of the first transmission/reception period T1 , the user device 201 may transmit the first data 1401 to the first device 202-1. For example, for more robust data transmission/reception, the first data 1401 may include audio data acquired in two time intervals preceding the first transmission/reception interval T1 . For example, the first data 1401 may include audio data V0 and audio data V1 subsequent to the audio data V0 in the time domain. Each size of the audio data V0 and the audio data V1 may correspond to one transmission/reception period T1 or T2. For example, when the size of data (eg, payload) transmitted by the user device 210 is 60 bytes, the first data 1401 may include 30 bytes of audio data V0 and 30 bytes of audio data V1.

In the second time slot S2 of the first transmission/reception period T1 , the first device 202-1 may transmit the second data 1402 . In order to increase a reception probability through retransmission of data, for example, the second data 1402 may include NACK information. For example, the first device 202-1 may transmit the second data 1402 including NACK information even if the first data 1401 is received. As another example, the user device 201 may be configured to repeatedly transmit data a specified number of times even if the second data 1402 includes ACK information.

For example, the second data 1402 may include audio data Vm1 and audio data Vs0. For example, the audio data Vm1 may include audio data acquired by the first microphone of the first device 202-1. The audio data Vs0 is obtained by the second microphone of the first device 202-1 and may include audio data that is earlier than the audio data Vm1 in the time domain.

In the third time slot S3 and the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 may retransmit the first data 1401 . In a fourth time slot ( S4 ), a sixth time slot ( S6 ), and an eighth time slot ( S8 ), the first device 202-1 includes a fourth data corresponding to the second data 1402 . Data 1404 may be transmitted. For example, the fourth data 1404 may include additional data for audio data Vm1 and additional data for audio data Vs0.

In the seventh time slot S7 of the first transmission/reception period T1 , the user device 201 may transmit the third data 1403 including additional data for the first data 1401 . For example, the third data 1403 may include additional data for audio data V0 and/or additional data for audio data V1 .

Data transmission/reception in the second transmission/reception period T2 may be referred to by data transmission/reception in the first transmission/reception interval T1. For example, the fifth data 1405 may include audio data V1 and audio data V2 subsequent to the audio data V1 in the time domain. The seventh data 1407 may include additional data for the audio data V1 and additional data for the audio data V2. The sixth data may include audio data Vm2 and audio data Vs1. For example, the audio data Vm2 may follow the audio data Vm1 and include audio data acquired by the first microphone of the first device 202-1. The audio data Vs1 may be obtained by the second microphone of the first device 202-1, and may include audio data in the time domain corresponding to the audio data Vm1. The eighth data 1408 may include additional data for the sixth data 1406 . For example, the eighth data 1408 may include additional data for audio data Vm2 and additional data for audio data Vs1.

According to an embodiment, when there is no additional data for the first data 1401 (eg, audio data V0, audio data V2), the user device 201 performs the first data 1401 in the seventh time slot S7. ) can be retransmitted. For example, the user device 201 may repeatedly retransmit the first data 1401 in a transmission slot (eg, S3, S5, S7) of the first retransmission period W1. According to an embodiment, when there is no additional data for the second data 1402 , the user device 201 may repeatedly retransmit the first data 1401 . For example, the user device 201 may repeatedly retransmit the first data 1401 in a transmission slot (eg, S4, S6, S8) of the first retransmission period W1.

14 , it has been described that the first device 202-1 and the user device 201 transmit additional data, but embodiments of the present document are not limited thereto. For example, transmission of additional data (eg, the third data 1403 and the seventh data 1407 ) of the user device 201 may be omitted. As another example, the second device 202 - 2 may be configured to transmit additional data using at least one time slot of the retransmission interval, as will be described later with reference to FIG. 16 .

In the example of FIG. 14 , the first device 202-1 is shown to transmit acquired audio data (eg, the second data 1402 and/or the sixth data 1406), but in the practice of this document Examples are not limited thereto. For example, as described below with reference to FIGS. 19 and 20 , the second device 202 - 2 may transmit audio data. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

15 illustrates packet exchange by transmission of additional data of the first device according to an embodiment.

A method in which the first device 202-1 transmits two audio channels and audio data of two time intervals in one packet has been described with reference to FIG. 14 . According to an embodiment, the first device 202-1 may transmit audio data of two time sections of one audio channel as one packet in one packet. For example, the first device 202-1 may include at least two or more microphones. The at least two microphones may include a first microphone and/or a second microphone.

In FIG. 15 , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) (eg, T1 or T2) of 16 slots, and It may be configured to have a retransmission interval (WeSCO) (eg, W1 or W2). Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto. In this example, the retransmission period (eg, W1 or W2) is a third time slot (S3), a fourth time slot (S4), a fifth time slot (S5), a sixth time slot (S6), and a seventh time slot (S7) and an eighth time slot (S8). Also, in FIG. 15 , it is assumed that the user device 201 is the master device of the eSCO link, but various embodiments of the present document are not limited thereto.

In the first time slot S1 of the first transmission/reception period T1 , the user device 201 may transmit the first data 1501 . For example, for more robust data transmission/reception, the first data 1501 may include audio data acquired in two time intervals preceding the first transmission/reception interval T1 . For example, the first data 1501 may include audio data V0 and audio data V1 subsequent to the audio data V0 in the time domain. Each of the audio data V0 and the audio data V1 may have a length corresponding to one transmission/reception period T1 or T2.

In the second time slot S2 of the first transmission/reception period T1 , the first device 202-1 may transmit the second data 1502 . For example, the second data 1502 may include NACK information.

For example, the second data 1502 may include audio data Vm1 and audio data Vm0. For example, the audio data Vm1 may include audio data acquired by the first microphone of the first device 202-1. The audio data Vm0 may be acquired by the first microphone of the first device 202-1, and may include audio data that is earlier than the audio data Vm1 in the time domain.

In the third time slot S3 and the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 may retransmit the first data 1501 . In the fourth time slot S4 of the first transmission/reception period T1 , the first device 202-1 may transmit the fourth data 1504 . For example, the fourth data 1504 may include audio data Vs1 and audio data Vs0 as additional data to the second data 1502 . For example, the audio data Vs1 may be audio data acquired by the second microphone of the first device 202-1 on the same time domain as the audio data Vm1. The audio data Vs0 may be audio data obtained by the second microphone of the first device 202-1 and precede the audio data Vs1 in the time domain.

In the sixth time slot S6 and the eighth time slot S8 of the first transmission/reception period T1 , the first device 202-1 includes a sixth time slot including additional data for the second data 1502 . Data 1506 may be transmitted. For example, the sixth data 1506 includes additional data for the audio data Vm1 (eg, audio enhancement parameters or audio data acquired through an audio channel different from the audio data Vm1) and additional data for the audio data Vm0 (eg: audio enhancement parameters or audio data obtained through an audio channel different from the audio data Vm0).

In the seventh time slot S7 of the first transmission/reception period T1 , the user device 201 may transmit the third data 1503 including additional data for the first data 1501 . For example, the third data 1503 may include additional data for the audio data V0 and additional data for the audio data V1 (eg, an audio enhancement parameter).

Data transmission/reception in the second transmission/reception period T2 may be referred to by data transmission/reception in the first transmission/reception interval T1. For example, the fifth data 1505 may include audio data V1 and audio data V2 subsequent to the audio data V1 in the time domain. The seventh data 1507 may include additional data for the audio data V1 and additional data for the audio data V2. The eighth data 1508 may include audio data Vm2 and audio data Vm1. For example, the audio data Vm2 may follow the audio data Vm1 and include audio data acquired by the first microphone of the first device 202-1. The tenth data 1510 may include audio data Vs1 and audio data Vs2. For example, the audio data Vs2 may be audio data obtained by the second microphone of the first device 202-1 and subsequent to the audio data Vs1 in the time domain. The twelfth data 1512 may include additional data for the eighth data 1508 . For example, the twelfth data 1512 may include additional data for the audio data Vm1 and additional data for the audio data Vm2.

It has been described with reference to FIG. 15 that the first device 202-1 transmits audio data of two time sections of one audio channel in one packet as one packet, but embodiments of the present document are limited thereto. it is not Hereinafter, the first device 202-1 may be configured to transmit audio data of one channel corresponding to one time interval in one packet. In this case, instead of one packet including audio data of a plurality of time sections, the additional data packet may include audio data corresponding to other time sections. For example, the second data 1502 may include only the audio data Vm1, and the fourth data 1504 may include only the audio data Vs0. Also, the sixth data 1506 may include additional data for the second data 1502 (eg, additional data for the audio data Vm1). As another example, the eighth data 1508 may include only the audio data Vm2 , and the tenth data 1510 may include only the audio data Vs1 . Also, the twelfth data 1512 may include additional data for the audio data Vm2.

15 , it has been described that the first device 202-1 and the user device 201 transmit additional data, but embodiments of the present document are not limited thereto. For example, transmission of additional data (eg, the third data 1503 and the seventh data 1507 ) of the user device 201 may be omitted. As another example, the second device 202 - 2 may be configured to transmit additional data using at least one time slot of the retransmission interval, as will be described later with reference to FIG. 16 .

In the example of FIG. 15 , the first device 202-1 is shown to transmit acquired audio data (eg, the second data 1502 and/or the eighth data 1508 ), but in the practice of this document Examples are not limited thereto. For example, as described below with reference to FIGS. 19 to 22 , the second device 202 - 2 may transmit audio data. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

16 illustrates packet exchange by transmission of additional data of a second device according to an embodiment.

In FIG. 16 , the eSCO link between the user device 201 and the first device 202-1 has, for example, a transmit/receive interval (TeSCO) of 16 slots (eg, T1 or T2), and 6-slot retransmission. It can be set to have a section (WeSCO) (eg, W1 or W2). The user device 201, the first device 202-1, and the second device 202-2 are illustrated as exchanging data using a single slot, but embodiments of the present document are not limited thereto. Also, in FIG. 16 , it is assumed that the user device 201 is the master device of the eSCO link, but embodiments of the present document are not limited thereto.

In the examples of FIG. 16 , the first device 202-1, the second device 202-2, and the user device 201 may be configured to transmit additional data. Hereinafter, three examples may be described with reference to FIG. 16 for convenience of description.

In the first example, the first device 202-1, the second device 202-2, and the user device 201 transmit audio data of a plurality of time intervals for one audio channel in one packet. can be set.

The first data 1601 may include audio data obtained in two time sections preceding the first transmission/reception section T1 . For example, the first data 1501 may include audio data V1 following audio data V0 and V0 in the time domain.

In the second time slot S2 of the first transmission/reception period T1 , the first device 202-1 may transmit the second data 1602 . For example, the second data 1602 may include NACK information. The second data 1602 may include audio data Vm1 and audio data Vm0. For example, the audio data Vm1 may include audio data acquired by the first microphone of the first device 202-1. The audio data Vm0 may be obtained by the first microphone of the first device 202-1, and may include audio data that is earlier than the audio data Vm1 in the time domain.

In the third time slot S3 and the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 may retransmit the first data 1601 .

In the fourth time slot S4 of the first transmission/reception period T1 , the second device 202 - 2 may transmit the fourth data 1604 . The fourth data 1602 may include audio data Vm1' and audio data Vm0'. For example, the audio data Vm1 ′ may include audio data acquired by the first microphone of the second device 202 - 2 . The audio data Vm0' may be acquired by the first microphone of the second device 202-2 and may include audio data that is earlier than the audio data Vm1' in the time domain.

In the sixth time slot S6 and the eighth time slot S8 of the first transmission/reception period T1 , the first device 202-1 may transmit the sixth data 1606 . The sixth data 1606 may include additional data for audio data Vm1 and additional data for audio data Vm0 included in the second data 1602 .

For example, the fifth data 1605 of the second transmission/reception period T2 may include audio data V1 and audio data V2 subsequent to the audio data V1 in the time domain. The eighth data 1608 may include audio data Vm1 and audio data Vm2. The audio data Vm2 may be audio data obtained by the first microphone of the first device 202-1 and subsequent to the audio data Vm1. The seventh data 1607 may include additional data for the audio data V1 and additional data for the audio data V2. The tenth data 1610 may include audio data Vm1' and audio data Vm2'. For example, the audio data Vm2' may be audio data obtained by the first microphone of the second device 202-2 and subsequent to the audio data Vm1'. The twelfth data 1612 may include additional data for the audio data Vm1 and additional data for the audio data Vm2 included in the eighth data 1608 . According to an embodiment, the user device 201 includes the second data 1602 , the fourth data 1604 , the sixth data 1606 of the first transmission/reception period T1 and the tenth data of the second transmission/reception period T2 Audio data may be generated based on the data 1610 . For example, the user device 201 transmits data in different transmission/reception periods (eg, T1 or T2) and different electronic devices (eg, the first device 202-1 or the second device 202-2). Robust audio data may be generated based on the data.

In the second example, the user device 201 may be configured to transmit audio data of a plurality of time sections for one audio channel in one packet. The first device 202-1 and the second device 202-2 may be configured to transmit audio data of one time interval for one audio channel as one packet. In this case, data transmitted by the first device 202-1 and the second device 202-2 in one time section may be audio data corresponding to different time sections.

In this case, the data transmitted by the user device 201 may be the same as in the first example. In the second example, the second data 1602 may include audio data Vm1, and the fourth data 1604 may include audio data Vm0'. The sixth data 1606 may include additional data for the audio data Vm1 included in the second data 1602 . For example, the eighth data 1608 may include audio data Vm2, and the tenth data 1610 may include audio data Vm1'. The twelfth data 1612 may include additional data for the audio data Vm2 included in the eighth data 1608 . According to an embodiment, the user device 201 is configured based on the second data 1602, the sixth data 1606 of the first transmission/reception period T1, and the tenth data 1610 of the second transmission/reception period T2. Audio data can be created. For example, the user device 201 transmits data in different transmission/reception periods (eg, T1 or T2) and different electronic devices (eg, the first device 202-1 or the second device 202-2). Robust audio data may be generated based on the data.

In a third example, the user device 201 may be configured to transmit audio data of a plurality of time sections for one audio channel in one packet. The first device 202-1 and the second device 202-2 may be configured to transmit audio data of a plurality of time sections for a plurality of audio channels in one packet.

In this case, the data transmitted by the user device 201 may be the same as in the first example. In a third example, the second data 1602 may include audio data Vm1 and audio data Vs0. The audio data Vs0 may be audio data obtained by using the second microphone of the first device 202-1 that precedes the audio data Vm1 in the time domain by using the first microphone. The fourth data 1604 may include Vm1' and Vs0'. The audio data Vm1 ′ may be audio data acquired by the first microphone of the second device 202 - 2 in the same time domain as the audio data Vm1 . The audio data Vs0' may be audio data acquired by the second microphone of the second device 202 - 2 in the same time domain as the audio data Vs0. For example, in the third example, one packet transmitted by the first device 202-1 or the second device 202-2 includes not only audio data of two time domains, but also audio data Each may correspond to a different audio channel. The sixth data 1606 may include additional data for audio data Vm1 and additional data for audio data Vs0.

For example, the eighth data 1608 may include audio data Vm2 and audio data Vs1, and the tenth data 1610 may include audio data Vm2' and audio data Vs1'. The twelfth data 1612 may include additional data for the audio data Vm2 and additional data for the audio data Vs1.

According to an embodiment, the user device 201 includes the second data 1602, the fourth data 1604, the sixth data 1606 of the first transmission/reception period T1, and the eighth data of the second transmission/reception period T2. Audio data may be generated based on the data 1608 , the tenth data 1610 , and the twelfth data 1612 . For example, the user device 201 transmits data in different transmission/reception periods (eg, T1 or T2) and different electronic devices (eg, the first device 202-1 or the second device 202-2). Robust audio data may be generated based on the data.

In the example of FIG. 16 , the first device 202-1 is shown to transmit acquired audio data (eg, the second data 1602 and/or the eighth data 1608), but in the practice of this document Examples are not limited thereto. For example, as described below with reference to FIGS. 19 to 22 , the second device 202 - 2 may transmit audio data. User device 201 , first device 202-1 , and/or second device 202-2 may dynamically determine and/or negotiate a device to transmit audio data and/or additional data to.

17 is a flowchart 1700 of a method for transmitting audio data by a user device according to an embodiment.

In operation 1705 , the user device 201 may connect to the first device 202-1 through the first link 205 . The user device 201 may create an extended synchronous oriented (eSCO) link based on a synchronous connection protocol through the first link 205 .

In operation 1710, the user equipment 201 may transmit a first packet in a first time slot among a plurality of time slots of one transmission/reception interval of the eSCO link. For example, the first packet may include first audio data.

In operation 1715 , the user device 201 may receive a second packet including second audio data from the first device 202-1 in a second time slot among the plurality of time slots. If the second packet is not received in operation 1715 , the user device 201 may transmit information indicating NACK in a third time slot subsequent to the second time slot in response to non-reception of the second packet.

In operation 1720 , the user device 201 may determine whether third audio data is received within at least one retransmission time slot. For example, the user device 201 may attempt to receive the third audio data within at least one retransmission time slot among the plurality of time slots. For example, the third audio data may be audio data of an audio channel different from that of the second audio data. For example, the third audio data may be audio data obtained by a second device different from the first device. For example, the third audio data may be audio data of a different section from the second audio data in a time domain.

When the third audio data is received (eg, in operation 1720-Y), in operation 1725, the user device 201 transmits the second audio data and audio data generated based on the third audio data to an external electronic device. can do. The user device 201 may generate the audio data by improving the sound quality of the second audio data by using the third audio data. As another example, when reception of the second packet fails in operation 1715 and reception of the second packet fails even within the retransmission period, the user device 201 transmits audio data generated based only on the third audio data to an external electronic device. can be sent to the device.

If the third audio data is not received (eg, in operation 1720 -N), in operation 1730 , the user device 201 may transmit audio data generated based on the second audio data to an external electronic device. As another example, if reception of the second packet fails in operation 1715 and reception of the second packet succeeds within the retransmission period, the user device 201 transmits audio data generated based only on the second audio data to the outside. It can be transmitted to an electronic device.

18 is a flowchart 1800 of a method of changing an audio data transmission apparatus of a user equipment according to an embodiment.

According to an embodiment, the user device 201 performs a retransmission interval (WeSCO) before the retransmission interval (WeSCO) between the first device 202-1 and the second device 202-2 (eg, FIGS. 8A, 8B, 12, 13, 14, A device (hereinafter referred to as an audio data transmission device) to transmit audio data in the second time slots S2 of 15 and 16 may be determined. For example, when negotiating an additional data transfer method (eg, operation 920 of FIG. 9 ), the user device 201 may determine a device to transmit audio data. The user device 201 may periodically or dynamically determine an audio data transmission device during connection with the first device 202-1 and/or the second device 202-2.

In operation 1805 , the user device 201 may receive first audio data from the first device 202-1. The first audio data may be audio data obtained by using at least one microphone (eg, the audio receiving circuit 481) of the first device 202-1. The first audio data may be audio data having excellent quality among audio data acquired using a plurality of microphones of the first device 202-1. The first audio data may be audio data whose sound quality is improved by using audio data obtained using a plurality of microphones of the first device 202-1. The first audio data may include quality information (eg, noise level) of audio data acquired using at least one microphone of the first device 202-1. The user device 201 may receive the first audio data through the first link 205 .

In operation 1810 , the user device 201 may receive second audio data from the second device 202 - 2 . The second audio data may be audio data acquired using a microphone (eg, the audio receiving circuit 482 ) of the second device 202 - 2 . The third audio data may be audio data having excellent quality among audio data acquired using a plurality of microphones of the second device 202 - 2 . The second audio data may be audio data whose sound quality is improved by using audio data obtained using a plurality of microphones of the second device 202 - 2 . The second audio data may include quality information (eg, noise level) of the audio data acquired using at least one microphone of the second device 202 - 2 . The user device 201 may receive the second audio data through the first link 205 or the second link 210 .

In operation 1815 , the user device 201 may determine an audio data transmission device based on the first audio data and the second audio data. Instead of determining the transmission device, the user device 201 may determine audio data having superior quality among the first audio data and the second audio data. The user device 201 may transmit the determined audio data transmission device or audio data information to the first device 202-1 and/or the second device 202-2.

For example, the user device 201 may determine an audio data transmission device or audio data based on a level of noise (eg, wind noise). Since wind noise is generally directional, the user device 201 may determine the audio data transmission device or the audio data experiencing relatively low wind noise based on the noise level of the audio data.

The user device 201 may determine an audio data transmission device (or audio data) by comparing the noise with a threshold value. For example, when the noise level of the first audio data is less than the threshold value and the noise level of the second audio data is greater than or equal to the threshold value, the user device 201 determines that the first device 201-1 receives the audio data. transmit, and the second device 202 - 2 may determine to transmit the additional data. As another example, when the noise level of the first audio data is greater than or equal to the threshold value and the noise level of the second audio data is less than the threshold value, the user device 201 determines that the second device 201 - 2 transmits the audio data. transmit, and the first device 202-1 may determine to transmit additional data. In another example, when the level of noise of both the first audio data and the second audio data is equal to or greater than the threshold value, the user device 201 is configured as a designated device (eg, the first device 202-1 or the second device 202 ). -2)) may decide to transmit audio data. In another example, when the level of noise of both the first audio data and the second audio data is less than a threshold value, the user device 201 is a designated device (eg, the first device 202-1 or the second device 202 ). -2) may determine to transmit audio data As another example, when the level of noise in only the first audio data is less than a threshold value, the user device 201 determines that the first device 202-1 transmits the audio data. , and the second device 202 - 2 may decide not to transmit additional data and audio data.

When the audio data transmission device (or audio data) is determined, the user device 201 may transmit a signal indicating the audio data transmission device (or audio data) through the first link 205 .

When the audio data transmission device is changed according to the decision of the audio data transmission device, the user device 201 may transmit a signal instructing the change of the audio data transmission device through the first link 205 . The first device 202-1 and/or the second device 202-2 may change a device for transmitting audio data in response to receiving the signal. For example, the first device 202-1 and the second device 202-2 may perform a role change.

In the example of FIG. 18 , it has been described that the user device 201 determines the audio data transmission device based on the noise level, but embodiments of the present document are not limited thereto. For example, the user device 201 may determine an audio data transmission device based on battery states of the first device 202-1 and the second device 202-2. If the battery state of the first device 202-1 is less than the threshold level, the user device 201 may determine the second device 202-2 as the audio data transmission device. If the battery state of the second device 202 - 2 is less than the threshold level, the user device 201 may determine the first device 202 - 1 as the audio data transmission device. As another example, the user device 201 may determine whether to transmit additional data as well as the audio data transmission device. The user device 201 may determine whether to transmit the audio data transmission device and additional data based on the battery state and the noise level.

In the example of FIG. 18 , it may be assumed that the first device 202-1 and the second device 202-2 are worn by the user. For example, when only the first device 202-1 is worn by the user, the user device 201 may determine a microphone to be used for audio data transmission among a plurality of microphones of the first device 202-1. have. The user device 201 provides the first audio data (eg, data acquired through the first microphone of the first device 202-1) and the second audio data (eg, the first A microphone to be used for transmitting audio data may be determined by comparing the data acquired through the second microphone of the device 202 - 2 .

19 is a flowchart 1900 of a method of changing the audio data transmission apparatus of the first apparatus according to an exemplary embodiment.

According to an embodiment, the first device 202-1 is configured before the retransmission interval (WeSCO) between the first device 202-1 and the second device 202-2 (eg, FIGS. 8A, 8B, 12, 13 ). , 14, 15, and 16 in the second time slot (S2)) may determine a device (hereinafter, referred to as an audio data transmission device) to transmit audio data. For example, the first device 202-1 may determine an audio data transmission device when negotiating an additional data transmission method (eg, operation 1035 of FIG. 10 ). The first device 202-1 may periodically or dynamically determine an audio data transmission device during connection with the user device 201 .

In operation 1905 , the first device 202-1 may activate a microphone (eg, the audio receiving circuit 481 of FIG. 4 ). The first device 202-1 may determine whether the first device 202-1 is worn by the user using a sensor (eg, a proximity sensor). The first device 202-1 may activate the microphone when the first device 202-1 is worn by the user. The first device 202-1 may activate a microphone when connected to the user device 201 based on a specified service (eg, hands free profile). The first device 202-1 may activate the microphone when the first device 202-1 is worn by the user and connected to the user device 201 based on a specified service.

In operation 1910, the first device 202-1 may acquire first audio data using the activated microphone. The first device 202-1 may acquire the first audio data for data transmission to the user device 201 or acquire the first audio data for the determination of the audio data transmission device. The first audio data may be audio data obtained by using at least one microphone (eg, the audio receiving circuit 481) of the first device 202-1. The first audio data may be audio data having excellent quality among audio data acquired using a plurality of microphones of the first device 202-1. The first audio data may be audio data whose sound quality is improved by using audio data obtained using a plurality of microphones of the first device 202-1. The first audio data may include quality information (eg, noise level) of audio data acquired using at least one microphone of the first device 202-1.

In operation 1915 , the first device 202-1 may receive second audio data from the second device 202-2. For example, the first device 202-1 may receive the second audio data through the third link 215 . As another example, the first device 202-1 may receive the second audio data transmitted by the second device 202-2 to the user device 201 through the first link 205 . The second audio data may be audio data acquired using a microphone (eg, the audio receiving circuit 482 ) of the second device 202 - 2 . The second audio data may be audio data obtained using at least one microphone (eg, the audio receiving circuit 481 ) of the second device 202 - 2 . The second audio data may be audio data having excellent quality among audio data acquired using a plurality of microphones of the second device 202 - 2 . The second audio data may be audio data whose sound quality is improved by using audio data obtained using a plurality of microphones of the second device 202 - 2 . The second audio data may include quality information (eg, noise level) of the audio data acquired using at least one microphone of the second device 202 - 2 .

In operation 1920, the first device 202-1 may determine an audio data transmission device based on the first audio data and the second audio data. For example, the first device 202-1 may determine an audio data transmission device based on the level of noise (eg, wind noise). When the first audio data and the second audio data include noise level information, the first device 202-1 may determine an audio data transmission device by comparing the noise level information. The first device 202-1 may determine the audio data transmission device in a method similar to the method described above with respect to operation 1815 of FIG. 18 .

The first device 202-1 may transmit information indicating the determined audio data transmission device through the first link 205 or the third link 215 . The first device 202-1 and/or the second device 202-2 may change a device for transmitting audio data in response to receiving the signal. For example, the first device 202-1 and the second device 202-2 may perform a role change.

In the example of FIG. 19 , it has been described that the first device 202-1 determines the audio data transmission device based on the noise level, but embodiments of the present document are not limited thereto. For example, as described above with reference to FIG. 18 , the first device 202-1 is an audio data transmission device based on the battery states of the first device 202-1 and the second device 202-2. can be decided The first device 202-1 may determine whether to transmit the audio data transmission device and additional data based on the battery state and the noise level.

20 is a flowchart 2000 of a method of changing an audio data transmission apparatus of a second apparatus according to an exemplary embodiment.

According to an embodiment, the second device 202 - 2 is configured before the retransmission interval (WeSCO) between the first device 202-1 and the second device 202-2 (eg, FIGS. 8A, 8B, 12, 13 ). , 14, 15, and 16 in the second time slot (S2)) may determine a device (hereinafter, referred to as an audio data transmission device) to transmit audio data. For example, the second device 202 - 2 may determine an audio data transmission device when negotiating an additional data transmission method (eg, operation 1035 of FIG. 10 ). The second device 202 - 2 may periodically or dynamically determine an audio data transmission device during connection with the user device 201 .

In operation 2005, the second device 202 - 2 may activate a microphone (eg, the audio receiving circuit 482 of FIG. 4 ). The second device 202 - 2 may determine whether the second device 202 - 2 is worn by the user using a sensor (eg, a proximity sensor). The second device 202 - 2 may activate the microphone when the second device 202 - 2 is worn by the user. The second device 202 - 2 may activate a microphone when connected to the user device 201 based on a specified service (eg, hands free profile). The second device 202 - 2 may activate the microphone when the second device 202 - 2 is worn by the user and connected to the user device 201 based on a specified service.

In operation 2010, the second device 202 - 2 may receive first audio data from the first device 202-1. For example, the second device 202 - 2 may receive the first audio data through the third link 215 . As another example, the second device 202-1 may receive the first audio data transmitted by the first device 202-1 to the user device 201 through the first link 205 . The first audio data may be audio data obtained using a microphone (eg, the audio receiving circuit 481) of the first device 202-1. The description of the first audio data may be referred to as described above with reference to FIG. 19 .

In operation 2015, the second device 202 - 2 may acquire second audio data using the activated microphone. The second device 202 - 2 may acquire the second audio data for data transmission to the user device 201 or acquire the second audio data for the determination of the audio data transmission device. The description of the second audio data may be referred to as described above with reference to FIG. 19 .

In operation 2020, the second device 202 - 2 may determine an audio data transmission device based on the first audio data and the second audio data. For example, the second device 201 may determine the audio data transmission device based on the level of noise (eg, wind noise). When the first audio data and the second audio data include noise level information, the second device 202 - 2 may determine the audio data transmission device by comparing the noise level information. The second device 202-1 may determine the audio data transmission device in a method similar to the method described above with respect to operation 1815 of FIG. 18 .

The second device 202 - 2 may transmit information indicating the determined audio data transmission device through the first link 205 or the third link 215 . The first device 202-1 and/or the second device 202-2 may change a device for transmitting audio data in response to receiving the signal. For example, the first device 202-1 and the second device 202-2 may perform a role change.

In the example of FIG. 20 , it has been described that the second device 202 - 2 determines the audio data transmission device based on the noise level, but embodiments of the present document are not limited thereto. For example, as described above with reference to FIG. 18 , the second device 202-2 is an audio data transmission device based on the battery states of the first device 202-1 and the second device 202-2. can be decided The second device 202 - 2 may determine whether to transmit the audio data transmission device and additional data based on the battery state and the noise level.

21 illustrates an example of packet exchange according to a change in an audio data transmission apparatus.

In the example of FIG. 21 , the first device 202-1 may be configured to transmit audio data, and the second device 202-2 may be configured to transmit additional data within a retransmission period.

The eSCO link (eg, the first link 205) between the user device 201 and the first device 202-1 uses, for example, a 16-slot transmit/receive interval (TeSCO) (eg, T1 or T2). It may be configured to have a 4-slot retransmission interval (WeSCO) (eg, W1 or W2). In this example, the retransmission period (eg, W1 or W2) may include a third time slot S3, a fourth time slot S4, a fifth time slot S5, and a sixth time slot S6. have. Although the user device 201 and the first device 202-1 are illustrated as exchanging data using a single slot, various embodiments of the present document are not limited thereto.

In an embodiment, in the first time slot S1 of the first transmission/reception period T1, the user device 201 transmits the first data 2101 to the first device 202-1 through the generated eSCO link. can send In the second time slot S2, the first device 202-1 transmits second data 2102 including the first audio data obtained by the first device 202-1 to the user device via the eSCO link. It can be sent to (201). In one example, the second data 2102 may further include ACK information for the first data 2101 . In the first time slot (eg, the third time slot S3 ) of the subsequent first retransmission period W1 , the user equipment 201 receives the third data 2103 including an ACK for the second data 2102 . ) to the first device 202-1 through the eSCO link.

In the fourth time slot S4 of the first transmission/reception period T1, the second device 202-2 transmits the fourth data 2104 including additional data (eg, second audio data) through the eSCO link. may be transmitted to the user device 201 . The additional data may include information for enhancing the first audio data of the second data 2102 . For example, the fourth data 2104 may include audio data of another channel acquired at the same time as the second audio data of the second data 2102 . For example, the fourth data 2104 may include second audio data acquired through the microphone of the second device 202 - 2 .

In the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 may transmit the fifth data 2105 through the eSCO link. The fifth data 2105 may include ACK information for the fourth data 2104 .

In the example of FIG. 21 , the first device 202-1, the second device 202-2, or the user device 201 may determine an audio data transmission device based on the first audio data and the second audio data. have. In the first transmission/reception period T1 , the second device 202 - 2 may be determined as an audio data transmission device. The first device 202-1 and the second device 202-2 may perform a roll change.

In the first time slot S1 of the second transmission/reception period T2, the user device 201 may transmit the sixth data 2106 through the eSCO link. The sixth data 2106 may be data contiguous with the first data 2101 stored in the transmission buffer to be transmitted to the first device 202-1 by the user device 201 . In the second time slot S2, the second device 202-2 may transmit the seventh data 2107 including the audio data obtained by the second device 202-2 via the eSCO link. . The seventh data 2107 may further include ACK information for the sixth data 2106 .

In response to receiving the seventh data 2107 , the user device 201 may transmit the eighth data 2108 including ACK information for the seventh data 2107 . In the fourth time slot S4 of the second transmission/reception period T2 , the first device 202-1 may transmit the ninth data 2109 including additional data to the user device 201 . The ninth data 2109 may include additional data for adjusting audio data included in the seventh data 2107 . In the fifth time slot S5 , the user device 201 may transmit the tenth data 2110 including ACK information for the ninth data 2109 .

22 illustrates another example of packet exchange according to a change in an audio data transmission device.

In the example of FIG. 22 , the first device 202-1 may be configured to transmit audio data, and the second device 202-2 may be configured to transmit additional data within a retransmission period. The setting of the eSCO link (eg, the first link 205 ) between the user device 201 and the first device 202-1 is as described above with reference to FIG. 21 .

In the first time slot S1 of the first transmission/reception period T1, the user device 201 may transmit the first data 2201 with the first device 202-1 through the generated eSCO link. In the second time slot S2, the first device 202-1 transmits second data 2202 including the first audio data obtained by the first device 202-1 to the user device via the eSCO link. It can be sent to (201). In one example, the second data 2202 may further include ACK information for the first data 2201 . In the first time slot (eg, the third time slot S3) of the first retransmission period W1, the user device 201 transmits the third data 2203 including the ACK for the second data 2202. It may transmit to the first device 202-1 through the eSCO link.

In the fourth time slot S4 of the first transmission/reception period T1, the second device 202-2 transmits the fourth data 2204 including additional data (eg, second audio data) through the eSCO link. may be transmitted to the user device 201 . For example, the fourth data 2204 may include second audio data obtained through the microphone of the second device 202 - 2 .

In the fifth time slot S5 of the first transmission/reception period T1 , the user device 201 may transmit the fifth data 2105 through the eSCO link. The fifth data 2205 may include ACK information for the fourth data 2204 .

In the example of FIG. 22 , the first device 202-1, the first device 202-1, or the user device 201 may determine an audio data transmission device based on the first audio data and the second audio data. have. The second device 202 - 2 may be determined as an audio data transmission device. The first device 202-1 and the second device 202-2 may perform a roll change. Also, the first device 202-1 may be determined not to transmit separate data (audio data or additional data).

In the first time slot S1 of the second transmission/reception period T2, the user device 201 may transmit the sixth data 2206 through the eSCO link. The sixth data 2206 may be data contiguous with the first data 2201 stored in the transmission buffer to be transmitted to the first device 202-1 by the user device 201 . In the second time slot S2, the second device 202-2 may transmit the seventh data 2207 including the audio data obtained by the second device 202-2 through the eSCO link. . The seventh data 2207 may further include ACK information for the sixth data 2206 . In response to receiving the seventh data 2207 , the user device 201 may transmit the eighth data 2208 including ACK information for the seventh data 2207 .

21 and 22 , a roll change between the first device 202-1 and the second device 202-2 has been described, but embodiments of the present document are not limited thereto. For example, similar to the examples of FIGS. 14 and 15 , a roll change may be performed between the plurality of microphones of the first device 202-1. For example, the second data 2102 and the ninth data 2109 of FIG. 21 are data acquired by the first microphone of the first device 202-1, and the fourth data 2104 and the seventh data Reference numeral 2107 may be data acquired by the second microphone of the first device 202-1. For example, the second data 2202 of FIG. 22 is data acquired by the first microphone of the first device 202-1, and the fourth data 2104 and the seventh data 2107 are data obtained by the first device 202-1. It may be data acquired by the second microphone of (202-1).

The electronic device (eg, the user device 201 of FIG. 4 ) according to an embodiment includes a first communication circuit supporting wireless communication (eg, the first communication circuit 391 of FIG. 4 ) and a first communication circuit supporting Bluetooth communication. 2 communication circuitry (eg, second communication circuitry 392 of FIG. 4 ), a processor operatively coupled with the first communication circuitry and the second communication circuitry (eg, processor 320 of FIG. 4 and working with the processor) It may include a memory (eg, the memory 330 of Fig. 3) that is coupled to the memory, wherein the memory, when executed, causes the processor to use the second communication circuit, and based on a synchronous connection protocol, a first device. Creates a link with (eg, the first device 202-1 of FIG. 4 ), and transmits first data through the link in a first time slot among a plurality of time slots in one transmission/reception section of the link transmit to a first device, receive second data including audio data obtained by the first device in a second time slot of the plurality of time slots, from the first device via the link, Receive third data including additional data for the second data within a retransmission interval set for data retransmission among time slots of , through the link, and generate based on the second data and the third data One or more instructions for transmitting the converted audio data to an external electronic device using the first communication circuit may be stored.

The one or more instructions, when executed, may cause the processor to transmit, to the first device, information indicating whether to support the additional data when the link is created with the first device.

For example, information indicating whether the additional data is supported may be indicated by codec information used for audio data of the link.

When the one or more instructions are executed, when the second data is not received in the second time slot or second data including a negative acknowledgment is received in the second time slot, the processor transmits the first data within the retransmission interval. can be retransmitted. For example, the third data may be audio data of an audio channel different from that of the second data. For example, the third data may be audio data obtained by a second device different from the first device. For example, the third data may be audio data of a time section at least partially different from the second data in a time domain.

When the one or more instructions are executed, the processor may transmit additional data for improving the sound quality of the first audio data included in the first data to the first device within the retransmission period.

For example, the protocol supporting the synchronous connection may be extended synchronous connection oriented (eSCO).

According to an embodiment, the electronic device (eg, the first device 202-1 of FIG. 4 ) includes an audio reception circuit (eg, the audio reception circuit 481 of FIG. 4 ) connected to at least one microphone, Bluetooth communication a wireless communication circuit (eg, communication circuit 491 of FIG. 4 ) configured to support a processor (eg, processor 421 of FIG. 4 ) operatively coupled to the audio receiving circuit and the wireless communication circuit, and the processor and a memory (eg, the memory 431 of FIG. 4 ) operatively connected to the . When the memory is executed, the processor connects to a first external electronic device (eg, the user device 201 of FIG. 4 ) through a first link using the wireless communication circuit, and the wireless communication circuit is connected to a second external electronic device (eg, the second device 202 - 2 of FIG. 4 ) through a second link, and includes channel information of the first link through the second link. 1 link information is transmitted to the second external electronic device, an extended synchronous connection oriented (eSCO) link is generated with the first external electronic device through the first link, and a plurality of transmission/reception sections of the eSCO link are provided. Receive first data from the first external electronic device in a first time slot of the time slots, and include audio data obtained using the audio receiving circuit in a second time slot of the plurality of time slots one or more instructions for transmitting the second data to the first external electronic device and transmitting additional data for improving the sound quality of the audio data in a retransmission interval set for data retransmission among the plurality of time slots; can

For example, the audio receiving circuit may be connected to a first microphone and a second microphone, the audio data may be obtained through the first microphone, and the additional data may include audio data obtained through the second microphone. can

For example, the second data and the additional data may be acquired in at least a partly different time domain.

The one or more instructions, when executed, cause the processor to transmit the additional data if the audio codec information associated with the eSCO link corresponds to a specified codec, and if the audio codec information associated with the eSCO link does not correspond to the specified codec The additional data may not be transmitted.

When the one or more instructions are executed, the processor may receive additional data for improving the sound quality of the data from the first external electronic device in the retransmission period.

The one or more instructions, when executed, cause the processor, based on the noise levels of the audio data and the additional data, to include, among the first device and the second device, a plurality of transmission/reception intervals following the one transmission/reception interval. It is possible to determine a device to transmit audio data in a second time slot among the time slots.

According to an embodiment, a method for transmitting audio data by an electronic device (eg, the user device 201 of FIG. 4 ) includes generating an extended synchronous oriented (eSCO) link with a first device through the first link; transmitting first data in a first time slot among a plurality of time slots of one transmission/reception interval of the eSCO link; In a second time slot among the plurality of time slots, receiving second data from a first device receiving; attempting to receive third data within at least one retransmission time slot of the plurality of time slots; and if the third data is received within the at least one retransmission time slot, the second and transmitting data and audio data generated based on the third data to an external electronic device.

For example, the method may further include, if the third data is not received within the at least one retransmission time slot, transmitting audio data generated based on the second data to an external electronic device. .

The method may further include generating the audio data by improving sound quality of the second data using the third data. For example, the third data may be audio data of an audio channel different from that of the second data. For example, the third data may be audio data obtained by a second device different from the first device. For example, the third data may be audio data of a section that is at least partially different from the second data in a time domain. The method includes, based on the noise levels of the second data and the third data, a second of a plurality of time slots of a transmission/reception interval subsequent to the one transmission/reception interval among the first device and the second device The method may further include determining a device to transmit audio data in a time slot.

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

The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more of the item, unless the relevant context clearly dictates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C” and “A, Each of the phrases "at least one of B, or C" may include any one of, or all possible combinations of, items listed together in the corresponding one of the phrases. Terms such as “first”, “second”, or “first” or “second” may simply be used to distinguish the component from other components in question, and may refer to components in other aspects (e.g., importance or order) is not limited. that one (eg first) component is “coupled” or “connected” to another (eg, second) component with or without the terms “functionally” or “communicatively” When referenced, it means that one component can be connected to the other component directly (eg by wire), wirelessly, or through a third component.

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

According to various embodiments of the present document, one or more instructions stored in a storage medium (eg, internal memory 136 or external memory 138) readable by a machine (eg, electronic device 101) may be implemented as software (eg, the program 140) including For example, the processor (eg, the processor 120 ) of the device (eg, the electronic device 101 ) may call at least one of one or more instructions stored from a storage medium and execute it. This makes it possible for the device to be operated to perform at least one function according to the at least one command called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

According to an embodiment, the method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or via an application store (eg Play Store™) or on two user devices ( It can be distributed (eg downloaded or uploaded) directly, online between smartphones (eg: smartphones). In the case of online distribution, at least a part of the computer program product may be temporarily stored or temporarily created in a machine-readable storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server.

According to various embodiments, each component (eg, a module or a program) of the above-described components may include a singular or a plurality of entities. According to various embodiments, one or more components or operations among the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg, a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component are executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations are executed in a different order, omitted, or , or one or more other operations may be added.

Claims (20)

In an electronic device,
a first communication circuit supporting wireless communication;
a second communication circuit supporting Bluetooth communication;
a processor operatively coupled with the first communication circuitry and the second communication circuitry; and
a memory operatively coupled to the processor;
The memory, when executed, causes the processor to:
using the second communication circuit to create a link with the first device based on a synchronous connection protocol;
transmit first data to the first device through the link in a first time slot among a plurality of time slots of one transmission/reception section of the link;
receiving second data including audio data obtained by the first device in a second time slot of the plurality of time slots from the first device through the link;
receiving, through the link, third data including additional data for the second data within a retransmission interval set for data retransmission among the plurality of time slots; and
and storing one or more instructions for transmitting audio data generated based on the second data and the third data to an external electronic device using the first communication circuit. The method of claim 1,
The one or more instructions, when executed, cause the processor to transmit, to the first device, information indicating whether to support the additional data when the link is created with the first device. 3. The method of claim 2,
The information indicating whether the additional data is supported is indicated by codec information used for audio data of the link. The method of claim 1,
When the one or more instructions are executed, when the second data is not received in the second time slot or second data including a negative acknowledgment is received in the second time slot, the processor receives the first data within the retransmission interval. An electronic device that causes retransmission. The method of claim 1,
and the third data is audio data of an audio channel different from the second data. 6. The method of claim 5,
and the third data is audio data obtained by a second device different from the first device. 6. The method of claim 5,
and the third data is audio data of a time section at least partially different from the second data in a time domain. The method of claim 1,
The one or more instructions, when executed, cause the processor to transmit, to the first device, additional data for improving sound quality of the first audio data included in the first data within the retransmission period. The method of claim 1,
The one or more instructions, when executed, cause the processor, based on the noise levels of the audio data and the additional data, to select a plurality of transmission/reception intervals following the one transmission/reception interval among the first device and the second device determine a device to transmit audio data in a second one of the time slots. In an electronic device,
an audio receiving circuit coupled to the at least one microphone;
a wireless communication circuit configured to support Bluetooth communication;
a processor operatively coupled to the audio receiving circuitry and the wireless communication circuitry; and
a memory operatively coupled to the processor;
The memory, when executed, causes the processor to:
using the wireless communication circuit to connect with a first external electronic device through a first link;
using the wireless communication circuit to connect with a second external electronic device through a second link;
transmitting first link information including channel information of the first link to the second external electronic device through the second link;
generating an extended synchronous connection oriented (eSCO) link with the first external electronic device through the first link;
receiving first data from the first external electronic device in a first time slot among a plurality of time slots of one transmission/reception section of the eSCO link;
In a second time slot among the plurality of time slots, transmit second data including audio data obtained using the audio receiving circuit to the first external electronic device;
and storing one or more instructions for transmitting additional data for improving sound quality of the audio data in a retransmission interval set for data retransmission among the plurality of time slots. 11. The method of claim 10,
The audio receiving circuit is connected to a first microphone and a second microphone,
The audio data is obtained through the first microphone,
The additional data includes audio data acquired through the second microphone. 12. The method of claim 11,
The electronic device of claim 1, wherein the second data and the additional data are obtained in at least partly different time domains. 11. The method of claim 10,
The one or more instructions, when executed, cause the processor to:
If the audio codec information associated with the eSCO link corresponds to a specified codec, transmit the additional data;
and not to transmit the additional data if the audio codec information associated with the eSCO link does not correspond to the specified codec. 11. The method of claim 10,
The one or more instructions, when executed, cause the processor to receive additional data for improving the sound quality of the audio data from the first external electronic device in the retransmission period. A method for transmitting audio data in an electronic device, the method comprising:
generating an extended synchronous oriented (eSCO) link through the first device and the first link;
transmitting first data in a first time slot among a plurality of time slots of one transmission/reception interval of the eSCO link;
receiving second data from a first device in a second one of the plurality of time slots;
attempting to receive third data within at least one retransmission time slot of the plurality of time slots; and
and transmitting the second data and audio data generated based on the third data to an external electronic device when the third data is received within the at least one retransmission time slot. 16. The method of claim 15,
If the third data is not received within the at least one retransmission time slot, transmitting audio data generated based on the second data to an external electronic device. 16. The method of claim 15,
The method further comprising generating the audio data by improving the sound quality of the second data by using the third data. 18. The method of claim 17,
and the third data is audio data of an audio channel different from the second data. 19. The method of claim 18,
and the third data is audio data obtained by a second device different from the first device. 20. The method of claim 19,
Based on the noise levels of the second data and the third data, among the first device and the second device, audio in a second time slot among a plurality of time slots in a transmission/reception interval subsequent to the one transmission/reception interval The method further comprising determining a device to transmit data to.

Images