A communication system, a translation machine, and a communication method among accessory devices

Abstract

This application discloses a communication method between a communication system, a translator, and accessory devices. Data transmission between the translator and accessory devices is achieved via a Type-C interface, eliminating the need for public wireless frequency bands and completely avoiding interference from the 2.4GHz Bluetooth band. The transmission latency is significantly lower than Bluetooth, ensuring efficient real-time transmission of translated audio, text, and other data, meeting the smooth translation needs in various scenarios. The translator and accessory devices establish a direct data transmission channel (SBU1 and SBU2) through the SBU pins of the Type-C interface, eliminating the need for a Bluetooth module for wireless transmission and reception. This avoids the high power consumption associated with continuous Bluetooth RF operation, reduces device power consumption, and extends the battery life of both the translator and accessory devices.

Description

Technical Field

[0001] This application relates to the field of device-to-device communication technology, and more specifically, to a communication system, a translator, and a communication method between accessory devices. Background Technology

[0002] Currently, translation devices and accessories on the market typically use Bluetooth for communication. Accessories mainly come in two forms: one is as a standalone device, connecting directly to the translator via a built-in Bluetooth module, such as Bluetooth wireless headsets, Bluetooth microphones, and Bluetooth button controllers; the other is as an external device, powered via a USB interface and interacting with the translator via Bluetooth, such as USB portable subtitle printers and USB Bluetooth extended button panels. In different application scenarios, accessories, in addition to basic data transmission functions, can also provide extended functions such as audio playback, subtitle display, voice recognition assistance, or user interaction to meet diverse usage needs.

[0003] Bluetooth connectivity typically uses Bluetooth Low Energy or Bluetooth Classic. However, Bluetooth technology primarily relies on the 2.4GHz public frequency band for data transmission. This band is occupied by various devices such as Wi-Fi devices and microwave ovens, easily leading to signal overlap and interference. Furthermore, when translation devices and accessories transmit data via Bluetooth, both devices must maintain a Bluetooth connection. In scenarios with high-frequency data interaction, this increases power consumption for both devices, shortening their usage time. In terms of data transmission, Bluetooth requires protocol processing, which also incurs overhead, resulting in slow data transmission.

[0004] Therefore, there is an urgent need for a two-line communication solution for translation devices and their accessories that can effectively solve the problems existing in the current technology. Summary of the Invention

[0005] In view of the above problems, this application is proposed to provide a communication method between a communication system, a translator, and accessory devices, to solve at least some of the defects existing in data transmission between existing translator devices and their accessory devices via Bluetooth connection. The specific solution is as follows:

[0006] In a first aspect, a communication system is provided, including a translator and an accessory device, wherein the translator and the accessory device each have a Type-C interface;

[0007] After the accessory device is connected to the translator via the Type-C interface, the translator switches its SBU2 pin to the transmit channel TX and its SBU1 pin to the receive channel RX; the accessory device switches its SBU1 pin to TX and its SBU2 pin to RX, thereby establishing the SBU1 and SBU2 channels between the translator and the accessory device and entering the interactive mode.

[0008] In interactive mode, the translator and the accessory device exchange data through the established SBU1 and SBU2 channels.

[0009] In one possible design, in another implementation of the first aspect of the embodiments of this application, the process of the translator and the accessory device switching SBU1 and SBU2 pins to establish SBU1 and SBU2 channels includes:

[0010] After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin.

[0011] In response to the authorization request signal, the translator triggers the opening of the VBUS channel to power the accessory device, and switches the SBU2 pin of the translator to the transmit channel TX and the SBU1 pin to the receive channel RX, and sends a handshake signal to the accessory device through the SBU2 channel;

[0012] After the accessory device is powered on via the VBUS channel, it triggers the switching of the SBU2 pin to RX. After receiving the handshake signal through the SBU2 channel, it verifies the handshake signal. If the verification is successful, the accessory device switches the SBU1 pin to TX and sends an acknowledgment signal to the translator through the SBU1 channel. After the translator receives the acknowledgment signal, it enters the interactive mode.

[0013] In one possible design, in another implementation of the first aspect of the embodiments of this application, after the accessory device disconnects the Type-C connection with the translator, the translator closes the VBUS channel and notifies the SBU1 and SBU2 pins on the translator side to switch to the default idle state; after the VBUS pin of the accessory device is powered off, it notifies the SBU2 pin on the accessory device side to enter a timeout waiting state, and after not receiving a message from the translator within a set time, it switches the SBU2 and SBU1 pins on the accessory device side to the default idle state.

[0014] In one possible design, in another implementation of the first aspect of the embodiments of this application, in interactive mode, when the translator needs to go into sleep mode, it sends a sleep command to the accessory device through the SBU2 channel. After receiving the sleep command, the accessory device enters a sleep state and returns a response message indicating successful reception to the translator through the SBU1 channel.

[0015] After receiving the response information, the translator controls the SBU1 pin to enter the listening mode, which is used to wait for wake-up in sleep mode.

[0016] In one possible design, in another implementation of the first aspect of the embodiments of this application, when the accessory device determines that it needs to switch to a wake-up state, it sends a wake-up command to the translator through the SBU1 channel. After receiving the wake-up command, the translator enters the wake-up state and returns wake-up confirmation information to the accessory device through the SBU2 channel.

[0017] In one possible design, in another implementation of the first aspect of the embodiments of this application, in interactive mode, when the accessory device needs to go into sleep mode, it sends a sleep command to the translator through the SBU1 channel. After receiving the sleep command, the translator enters the sleep state and returns a response message indicating successful reception to the accessory device through the SBU2 channel.

[0018] Upon receiving the response information, the accessory device controls the SBU2 pin to enter listening mode, which is used to wait for wake-up from sleep mode.

[0019] In one possible design, in another implementation of the first aspect of the embodiments of this application, the accessory device is provided with a sleep button; the translator is provided with a sleep button;

[0020] When the sleep button on the accessory device is triggered, the accessory device is controlled to enter sleep mode, and the SBU2 pin of the accessory device is controlled to enter listening mode, which is used to wait for wake-up in sleep mode;

[0021] When the sleep button on the translator is triggered, the translator is controlled to enter sleep mode, and the SBU1 pin of the translator is controlled to enter listening mode, which is used to wait for wake-up in sleep mode.

[0022] Secondly, a communication method between a translator and an accessory device is provided, wherein the translator and the accessory device each have a Type-C interface, and the communication method includes:

[0023] In response to the authorization request signal received on the CC pin, the translator triggers the opening of the VBUS channel to power the accessory device, switches the SBU2 pin to the transmit channel TX and the SBU1 pin to the receive channel RX, and sends a handshake signal to the accessory device through the SBU2 channel. The authorization request signal is a signal sent by the accessory device to the translator through the CC pin after it is connected to the translator via the Type-C interface.

[0024] After receiving an acknowledgment signal through the SBU1 channel, the translator enters the interactive mode. The acknowledgment signal is a signal sent by the accessory device to the translator through the SBU1 channel after the accessory device has successfully verified the handshake signal, switching the accessory device's SBU1 pin to TX.

[0025] In interactive mode, the translator sends interactive data to the accessory device through the SBU2 channel and receives interactive data sent by the accessory device through the SBU1 channel.

[0026] In one possible design, in another implementation of the second aspect of the embodiments of this application, the communication method further includes:

[0027] In interactive mode, when the translator needs to go into sleep mode, it sends a sleep command to the accessory device through the SBU2 channel to instruct the accessory device to enter sleep mode.

[0028] The translator receives a response message indicating successful reception from the accessory device via the SBU1 channel, and controls the SBU1 pin to enter listening mode, which is used to wait for wake-up in sleep mode.

[0029] Thirdly, another communication method between a translator and an accessory device is provided, wherein both the translator and the accessory device have a Type-C interface, and the communication method includes:

[0030] After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin.

[0031] After detecting that the VBUS pin is powered on, the accessory device triggers the switching of the SBU2 pin to the receive channel RX. After receiving the handshake signal sent by the translator through the SBU2 channel, it verifies the handshake signal. If the verification is successful, it switches the SBU1 pin to the transmit channel TX, sends an acknowledgment signal to the translator through the SBU1 channel, and enters the interactive mode. The handshake signal is the signal sent by the translator to the accessory device through the SBU2 channel after switching its own SBU2 pin to TX and SBU1 pin to RX.

[0032] In interactive mode, the accessory device sends interactive data to the translator through the SBU1 channel and receives interactive data sent by the translator through the SBU2 channel.

[0033] In one possible design, in another implementation of the third aspect of the embodiments of this application, the communication method further includes:

[0034] In interactive mode, when the accessory device needs to go into sleep mode, it sends a sleep command to the translator through the SBU1 channel to instruct the translator to enter sleep mode.

[0035] The accessory device receives a response message indicating successful reception from the translator via the SBU2 channel and controls the SBU2 pin to enter listening mode, which is used to wait for wake-up from sleep mode.

[0036] Using the above technical solution, the translator and accessory devices of this application achieve data transmission via a Type-C interface, eliminating the need to rely on public wireless frequency bands and completely avoiding the interference problem of the Bluetooth 2.4GHz band. The transmission latency is significantly lower than Bluetooth, ensuring efficient real-time transmission of translated audio, text, and other data, meeting the smooth translation needs in various scenarios. The translator and accessory devices establish a direct data transmission channel (SBU1 and SBU2) through the SBU pins of the Type-C interface, eliminating the need for a Bluetooth module for wireless transmission and reception. This avoids the high power consumption caused by continuous Bluetooth RF operation, reduces device power consumption, and extends the battery life of both the translator and the accessory.

[0037] In addition, the Type-C interface adopts a reversible plug design, avoiding damage caused by incorrect plugging and unplugging of traditional interfaces. The interface has strong contact stability and is not easily interrupted by vibration or slight pulling in mobile scenarios such as outdoor walking and handheld communication. The Type-C interface has strong universality and is compatible with most accessories on the market that support Type-C (such as headphones, speakers, and tablets), without the need for additional dedicated accessories, thus expanding the boundaries of usage scenarios. Attached Figure Description

[0038] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0039] Figure 1 A schematic diagram of a Type-C interface pinout provided in an embodiment of this application;

[0040] Figure 2 A timing diagram illustrating the interaction between a translator and its accessories is provided in an embodiment of this application.

[0041] Figure 3 Another timing diagram of the interaction between a translator and accessories provided in this application embodiment;

[0042] Figure 4 A schematic diagram illustrating the pin connection relationship between a translator and its accessory devices in a separated state, as provided in an embodiment of this application;

[0043] Figure 5 This is a schematic diagram of the pin connection relationship between a translator and an accessory device after being connected via Type-C, as provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] It is understood that before using the technical solutions disclosed in the various embodiments of this application, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this application in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0046] With the rapid development of artificial intelligence and internet technology, translation machines have achieved a leap from basic word matching to accurate and fluent translation of entire sentences and even paragraphs. Today, thanks to powerful cloud computing capabilities, translation machines can update language models in real time, covering hundreds of languages ​​and dialects worldwide, and are widely used in scenarios such as business negotiations, travel, and academic exchanges.

[0047] In the current market, Bluetooth connectivity is one of the main ways that translation devices and their various accessories work together. Translation devices can communicate with various accessories via Bluetooth, creating a diverse interconnected device system. Accessories can include: Bluetooth wireless headsets, Bluetooth microphones, Bluetooth button controllers, USB portable subtitle printers, USB Bluetooth extended button panels, etc. In different application scenarios, in addition to basic data transmission functions, accessories can also provide extended functions such as audio playback, subtitle display, voice recognition assistance, and user interaction to meet diverse usage needs.

[0048] Currently, translators and accessories connect via Bluetooth. However, Bluetooth relies on the 2.4GHz public frequency band, which is susceptible to interference from Wi-Fi and wireless peripherals in environments with dense electronic devices, such as airports and exhibitions. This can cause audio stuttering, delays, or even connection interruptions, resulting in gaps in the translated content during real-time communication and failing to meet the need for continuous and smooth dialogue. Furthermore, Bluetooth has a limited transmission rate. When accessories need to simultaneously receive multiple types of data, such as translated text, voice, and language configuration, data transmission congestion can easily occur. In addition, Bluetooth connections consume a lot of power, which can shorten the battery life of both the translator and accessories with continuous use.

[0049] Therefore, this application provides a new communication method between a translator and accessory devices. This application customizes the pins of the Type-C interface between the translator and accessory devices, and uses custom pins SBU1 and SBU2 to perform bidirectional communication between the devices.

[0050] Reference Figure 1 This example illustrates a pinout of a Type-C interface. The functions of each pin are described in Table 1 below:

[0051] Table 1

[0052]

[0053] Explain why the high-speed differential channel TX / RX provided by the Type-C interface is not used directly, but instead the SBU pin is used for communication.

[0054] Because the existing differential signal pins TX / RX of the Type-C interface require the USB protocol stack to run, the protocol is complex and consumes a lot of power. In this case, the translator and accessory devices typically only transmit small data such as audio, text, and control commands, making differential signal pins unsuitable. The SBU pin of the Type-C interface is suitable for low-speed control communication, and its UART protocol is simpler and consumes less power. Therefore, this application customizes the custom pins SBU1 and SBU2 provided by the Type-C interface to achieve communication between the translator and accessory devices.

[0055] This application provides a communication system, including a translator and accessory devices.

[0056] Both the translator and accessory devices have a Type-C interface.

[0057] After the accessory device is connected to the translator via the Type-C interface, the translator switches the SBU2 pin on its side to the transmit channel TX and the SBU1 pin to the receive channel RX.

[0058] The accessory device switches its SBU1 pin to TX and its SBU2 pin to RX to complete the initialization interaction, establishes the SBU1 and SBU2 channels between the translator and the accessory device, and enters the normal interaction mode.

[0059] In interactive mode, the translator and accessory devices exchange data through the established SBU1 and SBU2 channels.

[0060] If the translator needs to control accessory functions, such as triggering audio input, display output, or extended application operations, it can send control commands to the accessory device through the SBU2 channel. The accessory device will then execute the corresponding operation and provide feedback through the SBU1 channel.

[0061] The communication system provided in this application embodiment enables data transmission between the translator and accessory devices via a Type-C interface. This eliminates the need to rely on public wireless frequency bands, completely avoiding interference from the Bluetooth 2.4GHz band. The transmission latency is significantly lower than Bluetooth, ensuring efficient real-time transmission of translated audio, text, and other data, meeting the smooth translation needs in various scenarios. The translator and accessory devices establish a direct data transmission channel (SBU1 and SBU2) through the SBU pins of the Type-C interface, eliminating the need for a Bluetooth module for wireless transmission and reception. This avoids the high power consumption associated with continuous Bluetooth RF operation, reducing device power consumption and extending the battery life of both the translator and accessory devices.

[0062] In addition, the Type-C interface adopts a reversible plug design, avoiding damage caused by incorrect plugging and unplugging of traditional interfaces. The interface has strong contact stability and is not easily interrupted by vibration or slight pulling in mobile scenarios such as outdoor walking and handheld communication. The Type-C interface has strong universality and is compatible with most accessories on the market that support Type-C (such as headphones, speakers, and tablets), without the need for additional dedicated accessories, thus expanding the boundaries of usage scenarios.

[0063] In some embodiments of this application, combined with Figure 2 The process of switching SBU pins and establishing SBU channels for translators and accessory equipment is explained.

[0064] After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin.

[0065] In response to the authorization request signal, the translator triggers the opening of the VBUS channel to power the accessory device, and switches the translator's SBU2 pin to the transmit channel (TX) and the SBU1 pin to the receive channel (RX), sending a handshake signal to the accessory device through the SBU2 channel.

[0066] After the accessory device is powered on via the VBUS channel, it triggers the switching of its SBU2 pin to RX. After receiving the handshake signal through the SBU2 channel, it verifies the handshake signal. If the verification is successful, the accessory device switches its SBU1 pin to TX and sends an acknowledgment signal to the translator through the SBU1 channel. After the translator receives the acknowledgment signal, it completes the initialization interaction, establishes the SBU1 and SBU2 channels between the translator and the accessory device, and then enters the normal interaction mode.

[0067] Combination Figure 2 As shown, in interactive mode, the translator can transmit data to the accessory device via the SBU2 channel. The accessory device can transmit data to the translator via the SBU1 channel, enabling bidirectional communication.

[0068] Furthermore, after the accessory device disconnects from the translator via Type-C, the translator closes the VBUS channel and notifies the translator's SBU1 and SBU2 pins to switch to the default idle state. After power failure, the accessory device's VBUS pin notifies its SBU2 pin to enter a timeout waiting state. If no message is received from the translator within the set time, the accessory device's SBU2 and SBU1 pins are switched to the default idle state.

[0069] Combination Figure 2 As shown, in one optional scenario, when the accessory device is unplugged from the translator (the Type-C connection is disconnected), the translator's CC pin triggers a removal interrupt. At this time, the translator shuts down the VBUS pin and stops supplying power. Simultaneously, it notifies the translator's SBU1 and SBU2 pins to switch to the default idle state.

[0070] After power failure, the VBUS pin of the accessory device notifies the SBU1 pin to confirm whether the connection with the translator has been disconnected. The SBU1 pin can notify the SBU2 pin to enter a timeout waiting state. If the SBU2 pin does not receive a message from the translator within the set time, it switches to the idle state and notifies the SBU1 pin to time out and enter the default idle state. The SBU1 pin then switches to the idle state.

[0071] In other optional scenarios, if the translator or the user actively terminates the interaction, the translator sends a disconnect command to the accessory device via the SBU2 channel and shuts down the VBUS pin, ceasing external power supply. Upon detecting a power failure on the VBUS pin, the accessory device switches the SBU1 and SBU2 pins to the default idle state.

[0072] In some embodiments of this application, the process of the translator and accessory device switching to sleep mode and waking up in normal interaction mode is further described.

[0073] First scenario: The translator triggers a sleep mode.

[0074] Combination Figure 3 As shown, in interactive mode, when the translator needs to go into sleep mode, it sends a sleep command (notification to enter sleep mode) to the accessory device through the SBU2 channel. After receiving the sleep command, the accessory device enters sleep mode and returns a response message indicating successful reception to the translator through the SBU1 channel.

[0075] After receiving the response information, the translator controls the SBU1 pin to enter the listening mode (IRQ state) to wait for wake-up from sleep mode.

[0076] When the accessory device determines that it needs to switch to the wake-up state, it can send a wake-up command to the translator through the SBU1 channel. After receiving the wake-up command, the translator enters the wake-up state and returns wake-up confirmation information to the accessory device through the SBU2 channel.

[0077] The second scenario: The accessory device triggers the entry into sleep mode.

[0078] Combination Figure 3 As shown, in interactive mode, when the accessory device needs to go into sleep mode, it sends a sleep command (notification to enter sleep mode) to the translator through the SBU1 channel. After receiving the sleep command, the translator enters sleep mode and returns a response message indicating successful reception to the accessory device through the SBU2 channel.

[0079] After receiving the response information, the accessory device controls the SBU2 pin to enter the listening mode (IRQ state) to wait for wake-up from sleep mode.

[0080] The third scenario: Entering sleep mode via a physical button.

[0081] Combination Figure 3 As shown, both the accessory device and the translator can be equipped with a sleep button.

[0082] When the sleep button on the accessory device is triggered, the accessory device is controlled to enter sleep mode, and the SBU2 pin of the accessory device is controlled to enter listening mode (IRQ state) to wait for wake-up in sleep mode.

[0083] When the sleep button on the translator is triggered, the translator is controlled to enter sleep mode, and the SBU1 pin of the translator is controlled to enter listening mode (IRQ state) to wait for wake-up in sleep mode.

[0084] In this embodiment, the translator and accessory devices can switch from the normal interaction mode to a sleep mode, thereby further reducing power consumption. They can also be woken up from the sleep mode when communication is needed to ensure normal communication functions.

[0085] In some embodiments of this application, the states of the translator and accessory devices before and after the Type-C interface connection are further described.

[0086] Reference Figure 4 It illustrates the pin connection diagram when the translator and accessory devices are separated (i.e., the Type-C connection is disconnected).

[0087] Before the accessory device is connected to the translator, the SBU1 pin of the translator is connected to the UART_RX pin of the translator chip, and the SBU2 pin is connected to the GPIO_INPUT pin of the translator chip. This means that the SBU2 pin is in a state of waiting for an input signal, and the VBUS of the translator is in a state of no output.

[0088] At this time, the SBU1 and SBU2 pins of the accessory device are both connected to the GPIO_INPUT pin of the accessory chip, meaning that the SBU1 and SBU2 pins of the accessory device are both in a state of waiting for input signals.

[0089] Reference Figure 5 It illustrates the pin connection relationship between the translator and accessory devices after they are connected via Type-C.

[0090] When the accessory device is connected to the translator via Type-C, the translator's INT pin receives an interrupt signal, triggering the translator to enter the insertion process.

[0091] The translator controls the VBUS pin for power supply, triggering an interrupt on the accessory device side (or triggering the power-on logic if the device is not powered on).

[0092] The translator switches the SBU2 pin to the UART_TX pin and keeps the SBU1 pin to the UART_RX pin. The translator sends a handshake signal through the SBU2 and waits for the accessory device to return an acknowledgment signal until the connection is successful or a timeout occurs.

[0093] When the accessory device's SBU2 receives the handshake signal, it performs verification. If the verification is successful, it switches SBU1 to the UART_TX pin and sends an acknowledgment message through SBU1.

[0094] After receiving the confirmation message, the SBU1 on the translator side completes the initialization process and enters the normal interactive mode.

[0095] In normal interactive mode, SBU1 on the translator side holds the UART_RX pin, and SBU2 holds the UART_TX pin; SBU1 on the accessory device holds the UART_TX pin, and SBU2 holds the UART_RX pin.

[0096] The translator and accessory devices transmit data through the SBU1 and SBU2 channels.

[0097] Reference Figure 5 As shown, a control switch (software-controlled electronic switch) and a physical button switch can also be installed on the accessory side. Both switches are connected to the SBU1 communication channel in parallel.

[0098] In normal communication mode:

[0099] The switch is closed and the physical button is off (not pressed).

[0100] At this point, on the translator side, the pin map switches to UART_TX mode, and on the accessory side, the pin map switches to UART_RX mode, controlling the switch to close and enabling the SBU1 channel to conduct. The UART signal controls the switch → SBU1 pin → peer, achieving bidirectional serial communication.

[0101] In hibernation mode:

[0102] The switch is disconnected, and the physical button is also disconnected (not pressed).

[0103] At this point, after the translator sends the "enter sleep" command, the software-controlled switch disconnects. Both the translator and accessory pin maps switch to GPIO_INPUT mode (high impedance), the SBU1 channel is physically disconnected, no current flows, and the device enters a low-power sleep state.

[0104] In button wake-up mode:

[0105] The switch is disconnected and the physical button is closed (pressed).

[0106] In sleep mode, when a user presses a physical button, the SUB1 pin momentarily conducts, generating a voltage level change. The peer GPIO_INPUT detects this level change and triggers an interrupt. The interrupt wakes the device, and the software executes the wake-up process:

[0107] Reclose the control switch, switch the pin map back to UART_TX / RX mode, and restore normal communication mode.

[0108] The above-mentioned control involves the interaction of a switch (software-controlled electronic switch) and a physical button switch. The software-controlled electronic switch is responsible for "active on / off" switching, closing during normal communication (channel conduction) and opening when entering sleep mode (channel disconnection for power saving). The physical button is responsible for "passive wake-up." Although the software channel is disconnected during sleep mode, the physical button can still generate a signal. Pressing the button results in a level change, a GPIO interrupt, and wake-up of the device.

[0109] The parallel design of the two ensures that power can be saved during hibernation (i.e., software disconnection) and that the device can be woken up at any time.

[0110] In some embodiments of this application, a communication method between a translator and an accessory device is also provided. Both the translator and the accessory device have a Type-C interface. From the perspective of the translator, this communication method may include the following steps:

[0111] Step S11: In response to the authorization request signal received on the CC pin, the translator triggers the opening of the VBUS channel to power the accessory device, switches the SBU2 pin to the transmit channel TX, switches the SBU1 pin to the receive channel RX, and sends a handshake signal to the accessory device through the SBU2 channel.

[0112] The authorization request signal is a signal sent by the accessory device to the translator via the CC pin after the accessory device is connected to the translator through the Type-C interface.

[0113] Step S12: After receiving the confirmation signal through the SBU1 channel, the translator enters the interactive mode. The confirmation signal is the signal sent by the accessory device to the translator through the SBU1 channel after the accessory device has successfully verified the handshake signal.

[0114] Step S13: In interactive mode, the translator sends interactive data to the accessory device through the SBU2 channel and receives the interactive data sent by the accessory device through the SBU1 channel.

[0115] Furthermore, after detecting that the Type-C connection is disconnected, the translator shuts down the VBUS channel and notifies the SBU1 and SBU2 pins on the translator side to switch to the default idle state.

[0116] Furthermore, in interactive mode, when the translator needs to go into sleep mode, it sends a sleep command to the accessory device via the SBU2 channel to instruct the accessory device to enter sleep mode. The translator receives a response message indicating successful reception from the accessory device via the SBU1 channel and controls the SBU1 pin to enter listening mode, which is used to wait for wake-up while in sleep mode.

[0117] After receiving the wake-up command sent by the accessory device through the SBU1 channel, the translator enters the wake-up state and returns wake-up confirmation information to the accessory device through the SBU2 channel.

[0118] In another optional scenario, in interactive mode, the translator can receive a sleep command sent by the accessory device through the SBU1 channel, enter sleep mode upon receiving the sleep command, and return a response message indicating successful reception to the accessory device through the SBU2 channel.

[0119] In another optional scenario, when the sleep button on the translator is triggered, the translator is controlled to enter sleep mode, and the SBU1 pin of the translator is controlled to enter listening mode, which is used to wait for wake-up in sleep mode.

[0120] In some embodiments of this application, from the perspective of accessory equipment, the communication method may include the following steps:

[0121] Step S21: After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin.

[0122] Step S22: After detecting that the VBUS pin is powered on, the accessory device triggers the switching of the SBU2 pin to the receive channel RX. After receiving the handshake signal sent by the translator through the SBU2 channel, the handshake signal is verified. After successful verification, the SBU1 pin is switched to the transmit channel TX. An acknowledgment signal is sent to the translator through the SBU1 channel, and the device enters the interactive mode.

[0123] The handshake signal is a signal sent by the translator to the accessory device through the SBU2 channel after the translator switches the SBU2 pin to TX and the SBU1 pin to RX on its own side.

[0124] Step S23: In interactive mode, the accessory device sends interactive data to the translator through the SBU1 channel and receives interactive data sent by the translator through the SBU2 channel.

[0125] Furthermore, after detecting a power failure on the VBUS pin, the accessory device notifies the SBU2 pin on the accessory device side to enter a timeout waiting state. If no message is received from the translator within the set time, the SBU2 and SBU1 pins on the accessory device side are switched to the default idle state.

[0126] Furthermore, in interactive mode, after receiving the sleep command sent by the translator through the SBU2 channel, the accessory device enters sleep mode and returns a response message indicating successful reception to the translator through the SBU1 channel, so that the translator can control the SBU1 pin to enter listening mode, which is used to wait for wake-up in sleep mode.

[0127] When the accessory device determines that it needs to switch to the wake-up state, it sends a wake-up command to the translator through the SBU1 channel and receives the wake-up confirmation information returned by the translator through the SBU2 channel.

[0128] In an alternative scenario, in interactive mode, when the accessory device needs to enter sleep mode, it sends a sleep command to the translator via the SBU1 channel to instruct the translator to enter sleep mode, and obtains a response message from the translator indicating successful reception via the SBU2 channel. After receiving the response message, the accessory device controls the SBU2 pin to enter listening mode, which is used to wait for wake-up while in sleep mode.

[0129] In another optional scenario, when the sleep button on the accessory device is triggered, the accessory device is controlled to enter sleep mode, and the SBU2 pin of the accessory device is controlled to enter listening mode, so as to wait to be woken up in sleep mode.

[0130] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0132] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0133] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0134] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.

Claims

1. A communication system, characterized in that, It includes a translator and accessory devices, each of which has a Type-C interface; After the accessory device is connected to the translator via the Type-C interface, the translator switches its SBU2 pin to the transmit channel TX and its SBU1 pin to the receive channel RX; the accessory device switches its SBU1 pin to TX and its SBU2 pin to RX, thereby establishing the SBU1 and SBU2 channels between the translator and the accessory device and entering the interactive mode. In interactive mode, the translator and the accessory device exchange data through the established SBU1 and SBU2 channels.

2. The communication system according to claim 1, characterized in that, The process by which the translator and the accessory device switch SBU1 and SBU2 pins to establish SBU1 and SBU2 channels includes: After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin. In response to the authorization request signal, the translator triggers the opening of the VBUS channel to power the accessory device, and switches the SBU2 pin of the translator to the transmit channel TX and the SBU1 pin to the receive channel RX, and sends a handshake signal to the accessory device through the SBU2 channel; After the accessory device is powered on via the VBUS channel, it triggers the switching of the SBU2 pin to RX. After receiving the handshake signal through the SBU2 channel, it verifies the handshake signal. If the verification is successful, the accessory device switches the SBU1 pin to TX and sends an acknowledgment signal to the translator through the SBU1 channel. After the translator receives the acknowledgment signal, it enters the interactive mode.

3. The communication system according to claim 2, characterized in that, After the accessory device disconnects from the translator via Type-C, the translator closes the VBUS channel and notifies the translator's SBU1 and SBU2 pins to switch to the default idle state. After power failure, the accessory device's VBUS pin notifies the accessory device's SBU2 pin to enter a timeout waiting state. If no message is received from the translator within a set time, the accessory device's SBU2 and SBU1 pins are switched to the default idle state.

4. The communication system according to claim 1, characterized in that, In interactive mode, when the translator needs to go into sleep mode, it sends a sleep command to the accessory device through the SBU2 channel. After receiving the sleep command, the accessory device enters sleep mode and returns a response message indicating successful reception to the translator through the SBU1 channel. After receiving the response information, the translator controls the SBU1 pin to enter the listening mode, which is used to wait for wake-up in sleep mode.

5. The communication system according to claim 4, characterized in that, When the accessory device determines that it needs to switch to a wake-up state, it sends a wake-up command to the translator through the SBU1 channel. After receiving the wake-up command, the translator enters the wake-up state and returns wake-up confirmation information to the accessory device through the SBU2 channel.

6. The communication system according to claim 1, characterized in that, In interactive mode, when the accessory device needs to go into sleep mode, it sends a sleep command to the translator through the SBU1 channel. After receiving the sleep command, the translator enters sleep mode and returns a response message indicating successful reception to the accessory device through the SBU2 channel. Upon receiving the response information, the accessory device controls the SBU2 pin to enter listening mode, which is used to wait for wake-up from sleep mode.

7. The communication system according to claim 1, characterized in that, The accessory device is equipped with a sleep button; the translator is equipped with a sleep button. When the sleep button on the accessory device is triggered, the accessory device is controlled to enter sleep mode, and the SBU2 pin of the accessory device is controlled to enter listening mode, which is used to wait for wake-up in sleep mode; When the sleep button on the translator is triggered, the translator is controlled to enter sleep mode, and the SBU1 pin of the translator is controlled to enter listening mode, which is used to wait for wake-up in sleep mode.

8. A communication method between a translator and an accessory device, characterized in that, The translator and the accessory device each have a Type-C interface, and the communication method includes: In response to the authorization request signal received on the CC pin, the translator triggers the opening of the VBUS channel to power the accessory device, switches the SBU2 pin to the transmit channel TX and the SBU1 pin to the receive channel RX, and sends a handshake signal to the accessory device through the SBU2 channel. The authorization request signal is a signal sent by the accessory device to the translator through the CC pin after it is connected to the translator via the Type-C interface. After receiving an acknowledgment signal through the SBU1 channel, the translator enters the interactive mode. The acknowledgment signal is a signal sent by the accessory device to the translator through the SBU1 channel after the accessory device has successfully verified the handshake signal, switching the accessory device's SBU1 pin to TX. In interactive mode, the translator sends interactive data to the accessory device through the SBU2 channel and receives interactive data sent by the accessory device through the SBU1 channel.

9. The method according to claim 8, characterized in that, The communication method further includes: In interactive mode, when the translator needs to go into sleep mode, it sends a sleep command to the accessory device through the SBU2 channel to instruct the accessory device to enter sleep mode. The translator receives a response message indicating successful reception from the accessory device via the SBU1 channel, and controls the SBU1 pin to enter listening mode, which is used to wait for wake-up in sleep mode.

10. A communication method between a translator and an accessory device, characterized in that, The translator and the accessory device each have a Type-C interface, and the communication method includes: After the accessory device is connected to the translator via the Type-C interface, it sends an authorization request signal to the translator via the CC pin. After detecting that the VBUS pin is powered on, the accessory device triggers the switching of the SBU2 pin to the receive channel RX. After receiving the handshake signal sent by the translator through the SBU2 channel, it verifies the handshake signal. If the verification is successful, it switches the SBU1 pin to the transmit channel TX, sends an acknowledgment signal to the translator through the SBU1 channel, and enters the interactive mode. The handshake signal is the signal sent by the translator to the accessory device through the SBU2 channel after switching its own SBU2 pin to TX and SBU1 pin to RX. In interactive mode, the accessory device sends interactive data to the translator through the SBU1 channel and receives interactive data sent by the translator through the SBU2 channel.

11. The method according to claim 10, characterized in that, The communication method further includes: In interactive mode, when the accessory device needs to go into sleep mode, it sends a sleep command to the translator through the SBU1 channel to instruct the translator to enter sleep mode. The accessory device receives a response message indicating successful reception from the translator via the SBU2 channel and controls the SBU2 pin to enter listening mode, which is used to wait for wake-up from sleep mode.

Images