WO2019144351A1 - 主从角色转换方法、芯片与数据传输系统 - Google Patents

主从角色转换方法、芯片与数据传输系统 Download PDF

Info

Publication number
WO2019144351A1
WO2019144351A1 PCT/CN2018/074164 CN2018074164W WO2019144351A1 WO 2019144351 A1 WO2019144351 A1 WO 2019144351A1 CN 2018074164 W CN2018074164 W CN 2018074164W WO 2019144351 A1 WO2019144351 A1 WO 2019144351A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
master
slave device
information
slave
Prior art date
Application number
PCT/CN2018/074164
Other languages
English (en)
French (fr)
Inventor
邹景华
郭仕林
Original Assignee
深圳市为通博科技有限责任公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市为通博科技有限责任公司 filed Critical 深圳市为通博科技有限责任公司
Priority to CN201880000275.1A priority Critical patent/CN108323241B/zh
Priority to PCT/CN2018/074164 priority patent/WO2019144351A1/zh
Publication of WO2019144351A1 publication Critical patent/WO2019144351A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H04W84/20—Master-slave selection or change arrangements

Definitions

  • the present application relates to the field of wireless network technologies, and in particular, to a master-slave role conversion method, a chip, and a data transmission system.
  • Wireless Personal Area Network refers to a wireless communication network composed of computing devices (such as computers, telephones, PDAs, digital cameras, etc.) in a personal range (with or without a meter). Wireless network data transmission has more and more applications in personal area network (PAN), such as wireless headsets, various wearable data sensors, etc. Universal wireless link bearer modes include WIFI, infrared or Bluetooth. Wait.
  • the master device in the wireless network communication model of the master-slave device, the master device is generally responsible for task scheduling, link maintenance, and the like until the entire system stops running, and the roles of the master device and the slave device remain. constant.
  • the purpose of some embodiments of the present application is to provide a master-slave role conversion method, a chip and a data transmission system, which realizes a role transition between a master device and a selected slave device; meanwhile, the entire role transition process does not have a data source device. Any impact, thus not affecting the transmission of application data.
  • the embodiment of the present application provides a master-slave role conversion method, which is applied to a master device, where the master device communicates with the data source device by using a first data link, and is connected to at least one slave device, and each slave device uses the second data.
  • the link is connected to the data source device; the method comprises: sending a role exchange request to the selected slave device, wherein the selected slave device is one of the at least one slave device connected to the master device; when the selected one is received After the response from the device includes the first information for the role transition, generating second information for role conversion; transmitting the second information to the selected slave device for the selected slave device to be based on the second information
  • the main device role is converted, and the data source device communicates with the first data link; the first information is converted into a slave device role, and the second data link is connected with the data source device.
  • the embodiment of the present application further provides a master-slave role conversion method, which is applied to a selected slave device, and the selected slave device is connected to the master device, and is connected to the data source device by using the second data link, the master device and the data.
  • the source device communicates with the first data link and is connected to the at least one slave device.
  • the method includes: after receiving the role exchange request sent by the master device, feeding back the response including the first information for the role transition to the master device. For the primary device to be converted into the slave device role according to the first information, and connected to the data source device by using the second data link; receiving the second information sent by the master device for role transition; and converting the master device role according to the second information Communicate with the data source device on the first data link.
  • the embodiment of the present application further provides a chip, which is disposed in a master device, where the master device communicates with the data source device by using a first data link, and is connected to at least one slave device, and each slave device uses a second data link.
  • the chip includes: a first sending module, configured to send a role exchange request to the selected slave device, wherein the selected slave device is one of the at least one slave device connected to the master device; a receiving module, configured to receive, by the selected slave device, a response including first information for role conversion; and a second information generating module, configured to generate a second role for role conversion after receiving the response
  • the first sending module is further configured to send the second information to the selected slave device, so that the selected slave device converts the master device role according to the second information, and performs the first data link with the data source device.
  • the first role conversion module is configured to convert to the slave device role according to the first information, and connect to the data source device by using the second data link.
  • the embodiment of the present application further provides a data transmission system, including: a data source device and a plurality of receiving devices, where the plurality of receiving devices include a master device and at least one slave device; the master device is connected to each slave device; the master device and the data
  • the source device communicates with the first data link and receives the application data from the data source device; the slave device and the data source device are connected to the data source device by using the second data link, and receive the application data from the data source device in a listening manner;
  • the master device includes the chip described above.
  • the embodiment of the present application further provides a chip, which is disposed in a selected slave device, and the selected slave device is connected to the master device, and is connected to the data source device by using a second data link, where the master device and the data source device are The first data link is connected to the at least one slave device, and the chip includes: a second receiving module, configured to receive a role exchange request sent by the master device; and a second sending module, configured to receive the role mutual After the request is exchanged, the response of the first information for the role transition is fed back to the master device, so that the master device converts to the slave device role according to the first information, and connects to the data source device with the second data link; the second receiving module And the second role conversion module is configured to receive the second information for the role conversion by the primary device, and the second role conversion module is configured to convert the primary device role according to the second information, and communicate with the data source device by using the first data link.
  • the embodiment of the present application further provides a data transmission system, including: a data source device and a plurality of receiving devices, where the plurality of receiving devices include a master device and at least one slave device; the master device is connected to each slave device; the master device and the data
  • the source device communicates with the first data link and receives the application data from the data source device; the slave device and the data source device are connected to the data source device by using the second data link, and receive the application data from the data source device in a listening manner;
  • the slave device includes the above chip.
  • the master device and the data source device communicate with the first data link and are connected to at least one slave device, and each slave device is connected to the data source device by using the second data link. Based on such networking mode, the master device sends a role exchange request to the selected slave device, and generates a role transition after receiving the response of the first information for role conversion fed back by the selected slave device.
  • the second information the primary device then sends the second information to the selected slave device, the master device converts to the slave device role according to the first information, and connects to the data source device with the second data link, and the slave device according to the second information
  • the conversion to the master device role, the data source device communicates with the first data link, that is, the role conversion between the master device and the selected slave device is realized; meanwhile, the entire role conversion process has no impact on the data source device. None affect the transmission of application data.
  • FIG. 1 is a schematic diagram of a data transmission system in a first embodiment according to the present application.
  • FIG. 2 is a specific flowchart of a master-slave role conversion method according to a first embodiment of the present application
  • FIG. 3 is a timing diagram of a master device and a slave device in a first embodiment according to the first embodiment of the present invention
  • FIG. 4 is a specific flowchart of a method for converting a master-slave role according to a second embodiment of the present application
  • FIG. 5 is a specific flowchart of a method for converting a master-slave role according to a third embodiment of the present application.
  • FIG. 6 is a specific flowchart of a method for converting a master-slave role according to a fourth embodiment of the present application.
  • FIG. 7 is a specific flowchart of a method for converting a master-slave role according to a fifth embodiment of the present application.
  • Figure 8 is a block diagram showing a chip in a sixth embodiment of the present application.
  • Figure 9 is a block diagram showing a chip in an eighth embodiment of the present application.
  • Figure 10 is a block diagram showing a chip in accordance with a ninth embodiment of the present application.
  • Figure 11 is a block schematic diagram of a chip in a tenth embodiment of the present application.
  • the first embodiment of the present application relates to a master-slave role conversion method, which is applied to a master device, where the master device communicates with the data source device by using a first data link, and is connected to at least one slave device, and each slave device is second.
  • the data link is connected to the data source device; the method includes: sending a role exchange request to the selected slave device, wherein the selected slave device is one of at least one slave device connected to the master device; when receiving the selected After the slave device feedbacks the response including the first information for the role transition, generating second information for the role transition; transmitting the second information to the selected slave device for the selected slave device according to the second
  • the information is converted into a master device role, and the data source device communicates with the first data link; the first information is converted into a slave device role, and the second data link is connected with the data source device.
  • the master device and the data source device communicate with each other on the first data link, and are connected to at least one slave device, and each slave device is connected to the data source device by using the second data link; Based on such a networking mode, the master device sends a role exchange request to the selected slave device, and after receiving the response of the first information for role transition fed back by the selected slave device, generates a role transition for role conversion.
  • the second information the primary device then sends the second information to the selected slave device, the master device converts to the slave device role according to the first information, connects to the data source device with the second data link, and the slave device converts according to the second information.
  • the data source device communicates with the first data link, that is, the role transition between the master device and the selected slave device is realized; at the same time, the entire role transition process has no impact on the data source device, thereby Does not affect the transmission of application data.
  • the master device applied by the master-slave role conversion method is located in a data transmission system; referring to FIG. 1, the data transmission system includes a data source device (Source device) and three receiving devices (Sink devices, with three The Sink device is used as an example.
  • the source device is used to send application data to the sink device, and the sink device is a device that uses the application data.
  • the Source device is, for example, a television set, and the sink device includes, for example, a main speaker, a surround sound, a center speaker, a subwoofer, etc., and the Source device and the Sink devices form a data transmission system.
  • the Source device is, for example, a mobile phone that stores music files, such as wireless headphones, wireless speakers, and the like.
  • the link between the source-Sink link and the local area network that is, the wireless network in the present application
  • the link between the source-Sink link and the local area network that is, the wireless network in the present application
  • the source-Sink link and the link inside the local area network may be based on different wireless communication standards, but not limited thereto, and may also be based on the same wireless communication standard; the wireless communication standard includes but is not limited to Bluetooth, WIFI, Zigbee, etc.
  • the Source-Sink link is initiated by the Source device and establishes a connection with one of the Sink devices.
  • the Source device is responsible for link creation, link parameter management, and application data interaction of the Source-Sink link.
  • the Master device receives application data from the Source device through the Source-Sink link.
  • the Sink device that is wirelessly connected to the Source device is the Master device in the LAN, and the other Sink devices are the Slave devices.
  • a Master-Slave link is established between the Master device and each Slave device.
  • the Master-Slave link can be a wireless link or a wired link.
  • the Master device manages the slave device that joins the LAN and passes the Source-Sink chain.
  • the road information is given to the slave device to help establish a Listen link between the slave device and the Source device.
  • the slave device obtains all Source-Sink link information through the master device, and a Listen link is established between the slave device and the source device.
  • the slave device receives application data from the source device in a listening manner.
  • the source-Sink link between the source devices of the master device is the first data link
  • the Listen link between the slave device and the source device is the second data link
  • the slave device when the slave device receives the application data from the source device in the interception mode, the slave device directly sends the retransmission request of the application data to the master device, and receives the request for retransmission sent by the master device through the master-Slave link. data.
  • a simple star network structure can be adopted inside the local area network, that is, there is one master device and several slave devices.
  • the local area network can also adopt a more complex structure of the scattering network, that is, a master device exists at the same time.
  • application data can be relayed through the network node (for example, the master device exists in the local area network formed by each sink device and exists in the local area network formed with the source device).
  • Step 101 Send a role exchange request to the selected slave device.
  • the Master device sends a role exchange request to the selected slave device through its internal Controller layer.
  • the selected slave device is one of each slave device connected to the master device, and is used for performing a master-slave role transition with the master device.
  • the Slave device can be selected in such a way that the Master device is selected according to a preset condition or manually selected by the user.
  • the master device and each slave device maintain a connection through a connection event. That is, the master device periodically initiates a connection event to each slave device through the Master-Slave link to always maintain a connection state with each slave device; During the period, the master device schedules each slave device in the agreed time sequence.
  • Step 102 Determine whether a response of the first information included in the selected slave device including the first information for role conversion is received. If yes, go to step 103; otherwise, go back to step 101.
  • the selected slave device receives the role exchange request, if the request is approved, a response including the first information for the role transition is fed back, and the first information is the slave device configuration information;
  • the device determines that the response of the slave device feedback received by the slave device is received, and proceeds to step 103; otherwise, returns to step 101, and the master device sends the role exchange request to the selected slave device again; preferably, the master
  • the preset number of query thresholds in the device when the number of queries reaches the threshold of the number of queries, discards the role exchange with the selected slave device.
  • the slave device configuration information includes the clock precision of the selected slave device.
  • Step 103 Generate second information for role conversion.
  • the master device generates second information for role conversion, and the second information includes the waiting time of the role exchange and the master device configuration information.
  • the master device configuration information includes the clock precision of the master device, and the link information between the master device and each slave device.
  • the link information includes the channel number of the master device and each link connected after the role is exchanged, and the role exchange. The time after which the master device and the first connection event on each link occur.
  • Step 104 Send the second information to the selected slave device, so that the selected slave device converts to the master device role according to the second information, and communicates with the data source device by using the first data link.
  • the master device integrates the waiting time of the role exchange with the master device configuration information into a protocol data unit (ie, the second information), and sends the protocol data unit to the selected slave device for the selected slave.
  • the device After the device waits for the role to be exchanged, the device performs role conversion based on the master device configuration information.
  • the master device configuration information is used to configure the system for the selected slave device during the last scheduling of the waiting time, and the system configuration takes effect at the start time of the first connection event after the waiting time to be converted into the master device role.
  • the new Master device (the selected Slave device is converted to the new Master device) will initiate a connection event to the new Slave device (the original Master device is converted to the new Slave device), the new Master The device communicates with the Source device on a Source-Sink link (first data link).
  • the second information may only include the master device configuration information, and the selected slave device performs system configuration during the last scheduling of the waiting time after receiving the second information, and is next time.
  • the system configuration of the start time of the connection event takes effect to be converted to the master device role.
  • Step 105 Convert the first information into a slave role, and connect to the data source device with the second data link.
  • the master device converts to the slave device role according to the slave device configuration information.
  • the master device configures itself according to the slave device configuration information (first information), and the system configuration takes effect at the start time of the first connection event after the waiting time, and is converted into the slave device role. Abandoning the management of the Master device in the LAN, it only needs to maintain a link between it and the selected Slave device, and connect to the Source device with the second data link (Listen link).
  • the selected slave device performs system configuration according to the master device configuration, and the system configuration takes effect at the start time of the first connection event after the waiting time, and is converted into the master device role, thereby selecting
  • the slave device can seamlessly connect to the original master device, start responsible for management within the LAN, and is responsible for maintaining the link between the source device and the source device.
  • the master device performs role conversion with the selected slave device at the start time of a connection event.
  • the master device predicts a connection event after the connection event. Start time, and stipulate this time as the time to perform role conversion (as an example, but not limited to this), since both the master device and the slave device use their respective clocks, the two parties have no physical connection and cannot synchronize, therefore,
  • the Master device calculates the time offset between the moment when the role is switched and the start time of the current connection event, and sets the time offset as the waiting time for the role swap.
  • the slave device After receiving the waiting time sent by the master device, the slave device obtains the start time of the connection event when the waiting time is received, and then adds the waiting time to the time to obtain the agreed time for the role transition.
  • the master device exchanges roles with the selected slave device at the moment of the scheduled role transition.
  • the connection event with the slave device is started.
  • the master device acquires the start time of the first connection event (ie, the agreed time of the role transition), and calculates the difference t1 between the start time and the previous clock boundary as the offset time; the new master device uses the local clock.
  • the boundary plus the offset time t1 is taken as the start time of the initiating connection event as the moment when the connection event is initiated on the Master-Slave link of this article.
  • the same calculation method is used to obtain the start time of the first connection event and the start time of the first connection event on each link after the role is exchanged according to the new master device. To calculate.
  • the slave device receives the application data from the source device in a listening manner, that is, the slave device has all the Source-Sink link information, and the Listen link is established with the Source device.
  • the link between the selected slave device and the source device is not disconnected, and the Listen link is converted to the Source-Sink link, that is, there is always a Sink.
  • the device is connected to the source device as the master device. Therefore, the entire role conversion process has no effect on the source device (that is, the source device is transparent), so that the transmission of application data is not affected.
  • the second embodiment of the present application relates to a master-slave role conversion method.
  • This embodiment is an improvement on the basis of the first embodiment.
  • the main improvement is that the master device negotiates with the selected slave device to determine the waiting time.
  • Step 202 is substantially the same as step 102, and step 205 to step 207 are substantially the same as steps 103 to 105. The main differences are:
  • the role exchange request sent by the master device to the selected slave device includes the number of cycles N, indicating the number of cycles of the connection event included from the start time of the current connection event to the start time of the Nth connection event.
  • the master device negotiates with the selected slave device in advance to perform role conversion at the beginning of the Nth connection event, where N is an integer greater than zero.
  • Steps 203 and 204 are added, as follows:
  • step 203 it is determined whether N is included in the response; if yes, the process proceeds to step 204; if not, the process returns to step 201.
  • determining whether the response includes N that is, determining whether the slave device allows role conversion after N connection events, and if the response includes N, the slave device agrees to perform role conversion after N connection events, and proceeds to the step. 204; otherwise, it indicates that the slave device does not agree to perform role conversion after N connection events, and returns to step 201, the master device sends a role exchange request to the selected slave device again, and replaces the number of cycles in the role exchange request. N.
  • Step 204 Set a waiting time for the role exchange according to N.
  • the period of one connection event is represented by T
  • the waiting time of the role exchange is N*T.
  • the master device estimates the start time of the third connection event, and calculates the time offset from the start time of the current connection event, and sets the time offset to the role mutual Waiting time for change.
  • the master device can negotiate with the selected slave device to determine the waiting time.
  • the third embodiment of the present application relates to a method for converting a master-slave role.
  • This embodiment is an improvement on the basis of the first embodiment.
  • the main improvement is that the performance indicators of the master device and the slave device are monitored, and the performance is based on the performance.
  • the indicator determines whether the role transition is triggered.
  • the specific process of the master-slave role conversion method of this embodiment is as shown in FIG. 5.
  • the steps 304 to 308 are substantially the same as the steps 101 to 105.
  • the main difference is that steps 301 to 303 are added, as follows:
  • Step 301 Receive at least one performance indicator from each slave device.
  • the master device is the maintainer of the link in the local area network.
  • Each slave device periodically reports at least one performance indicator to the master device.
  • the host protocol layer (Host layer) of each slave device is controlled by the host.
  • the interface (HCI) command sets the reporting period.
  • the control layer (Controller layer) of each slave device periodically obtains at least one performance indicator of its own and reports it to the master device through a protocol data unit (PDU).
  • PDU protocol data unit
  • Step 302 Determine whether to trigger a role transition according to the performance indicator. If yes, the role transition is triggered, then the process proceeds to step 303; if not, the process ends directly.
  • the master device determines the performance indicators reported by the slave devices and the corresponding performance indicators, that is, the master device needs to separately determine whether the master device needs role conversion. And whether there is a slave device that can perform role conversion with the master device; when it is determined that the performance indicator of the self and the performance indicator reported by the at least one slave device meet the preset condition, the process proceeds to step 303; otherwise, the process ends directly.
  • the master device can determine whether the master device needs role conversion, and then determine whether there is a slave device that can perform role conversion with the master device. However, the master device can also determine whether there is a role transition with the master device. The slave device determines whether the master device needs role conversion. This embodiment does not impose any restrictions.
  • step 303 a slave device is selected according to the performance indicator.
  • the Host layer of the master device initiates the HCI command for role conversion.
  • the Controller layer of the master device replies to the Host layer through the COMMAND STATUS, initiates the role conversion process, and according to the received performance indicators of each slave device. Choose a Slave device with better performance indicators to perform role conversion with it.
  • the embodiment monitors the performance index of the master device and the performance index of the slave device, determines whether the role transition is triggered according to the performance indicator, and selects a slave device according to the performance indicator, that is, performance.
  • the metrics determine the conversion of the master and slave devices, which can avoid the performance degradation of the current master device and affect the performance of the entire data transmission system, thereby improving the performance of the entire data transmission system. It should be noted that the present embodiment can also be used as an improvement on the basis of the second embodiment, and the same technical effects can be achieved.
  • the performance indicator is one or more of the remaining power, the wearing state, the packet loss rate, and the signal strength, and determining whether to trigger the role transition according to the performance indicator includes:
  • the role transition is triggered when the remaining power of the master device is less than the preset first power threshold, and the power difference between the remaining power of the slave device and the remaining power of the master device is greater than a preset second power threshold; or
  • the role transition is triggered when the master device is in an unworn state and at least one slave device is in the worn state; wherein the sink device (ie, the master device and the slave device) are both wearable devices, such as wireless headsets.
  • the master device and the slave device have sensors (for example, touch sensors) to detect whether they are in a wearing state, but the embodiment does not impose any restrictions on the specific detection manner; or,
  • the second packet loss rate threshold is less than or equal to the first
  • the role transition is triggered.
  • the master device and the slave device can calculate the packet loss rate in real time. Specifically, the slave device calculates the packet loss rate based on the number of times the slave device requests the master device to retransmit the application data. The master device calculates the packet loss rate according to the number of times the source device requests the source device to retransmit the application data; or
  • the role transition is triggered.
  • the Master device and the Slave device can calculate the signal strength when acquiring application data from the Source device.
  • the priority of the judgment may be: the remaining power, the wearing state, and the packet loss rate. , signal strength. Among them, for the entire LAN, the endurance is crucial, so the remaining power is taken as the first priority.
  • the slave device with the most power is used as the selected slave device, and the role is exchanged with the master device, thereby improving the battery life of the entire wireless network, and avoiding the power consumption of the master device and the slave device being inconsistent. Causes the battery loss of the Master device to be more serious.
  • the wearing state When the wearing state is used for judgment, the roles of the master device and the slave device implemented according to the wearing state are interchanged, and the power consumption of the master device in the unworn state can be reduced.
  • the slave device with the smallest packet loss rate is used as the selected slave device to exchange roles with the master device; thus, the packet loss rate of the application data transmission between the master device and the source device can be reduced.
  • the number of times that the master device requests the source device to retransmit the application data can be reduced, thereby reducing the power consumption of the master device and improving the endurance of the entire data transmission system.
  • the slave device with the highest signal strength is used as the selected slave device to perform role exchange with the master device; thereby improving the transmission quality of the application data between the master device and the source device.
  • the fourth embodiment of the present invention relates to a master-slave role conversion method, which is applied to a slave device selected for role exchange with a master device in a wireless network, and the selected slave device is connected to the master device, and the second data is
  • the link (Listen link) is connected to the Source device, and the Master device and the Source device communicate with the first data link (Source-Sink link) and are connected to at least one Slave device.
  • the specific flow of the master-slave role conversion method of this embodiment is as shown in FIG. 6.
  • Step 401 Determine whether a role exchange request sent by the master device is received. If yes, go to step 402; otherwise, go to step 401 again.
  • the master device uses one of the at least one slave device as the selected slave device, and sends a role exchange request to the selected slave device through the Controller layer.
  • the process proceeds to step 402; otherwise, step 401 is performed again until the role exchange request sent by the master device is received.
  • the master device and the at least one slave device maintain a connection through a connection event, that is, the master device periodically initiates a connection event to each slave device through the master-Slave link, so as to remain in a connected state with each slave device at all times; During the period of a connection event, the master device schedules each slave device in the agreed time sequence.
  • Step 402 Feed back, to the primary device, a response including the first information for role conversion, so that the primary device converts to the slave device role according to the first information, and connects to the data source device with the second data link.
  • the selected slave device receives the role exchange request, if the request is approved, a response including the first information for the role transition is fed back.
  • the master device receives the response including the first information fed back by the slave device, so that the first information is converted into a slave device role, and the second data link is connected to the source device.
  • the first information is a slave device configuration information
  • the slave device configuration information includes a clock precision of the selected slave device
  • the second data link is a listening link.
  • Step 403 Receive second information sent by the primary device for role conversion.
  • the Master device generates second information for role transitioning and sends the second information to the selected slave device.
  • the second information includes the waiting time of the role exchange and the configuration information of the master device.
  • the configuration information of the master device includes the clock precision of the master device and the link information between the master device and each slave device. The channel number of the Master device and each link connection, and the time when the Master device and the first connection event on each link occur after the role is exchanged.
  • Step 404 Convert the primary device role according to the second information, and communicate with the data source device by using the first data link.
  • the master device configuration information is converted into the master device role.
  • the selected slave device performs system configuration according to the master device configuration, and the system configuration takes effect at the start time of the first connection event after the waiting time, and is converted into the master device role, thereby
  • the selected slave device can seamlessly connect to the master's work, start responsible for management within the LAN, and is responsible for maintaining the link with the Source device.
  • the master device configures itself according to the slave device configuration information (first information), and the system configuration takes effect at the start time of the first connection event after the waiting time, and is converted into a slave device.
  • the role abandoning the management of the master device in the local area network, only needs to maintain a link between it and the selected slave device, and connect to the Source device with the second data link (Listen link).
  • the master device integrates the waiting time of the role exchange with the master device configuration information into a protocol data unit, and sends the protocol data unit to the selected slave device; wherein the master device configuration information is used for selection.
  • the slave device is configured after the waiting time to be converted to the master device role.
  • the system configuration is performed according to the configuration information of the master device, and is converted into the role of the master device. Specifically, the offset of the connection event corresponding to each link is calculated according to the time when the first connection event occurs on each link and the local clock. Time, at which the selected Slave device is converted to the Master device role and the moment when the connection event is initiated on each link.
  • the slave device after receiving the waiting time sent by the master device, acquires the start time of the connection event where the waiting time is received, and then adds the waiting time to the time to obtain the agreed role conversion.
  • the master device exchanges roles with the selected slave device at the moment of the scheduled role transition.
  • the connection event with the slave device is started.
  • the master device acquires the start time of the first connection event (ie, the agreed time of the role transition), and calculates the difference t1 between the start time and the previous clock boundary as the offset time; the new master device uses the local clock.
  • the boundary plus the offset time t1 is taken as the start time of the initiating connection event as the moment when the connection event is initiated on the Master-Slave link of this article.
  • the same calculation method is used to obtain the start time of the first connection event and the start time of the first connection event on each link after the role is exchanged according to the new master device. To calculate.
  • the slave device receives the application data from the source device in a listening manner, that is, the slave device has all the Source-Sink link information, and the Listen link is established with the Source device.
  • the link between the selected slave device and the source device is not disconnected, and the Listen link is converted to the Source-Sink link, that is, there is always a Sink.
  • the device is connected to the source device as the master device. Therefore, the entire role conversion process has no effect on the source device (that is, the source device is transparent), so that the transmission of application data is not affected.
  • the master device and the data source device communicate with each other on the first data link, and are connected to at least one slave device, and each slave device is connected to the data source device by using the second data link; Based on such a networking mode, the master device sends a role exchange request to the selected slave device, and after receiving the response of the first information for role transition fed back by the selected slave device, generates a role transition for role conversion.
  • the second information the primary device then sends the second information to the selected slave device, the master device converts to the slave device role according to the first information, connects to the data source device with the second data link, and the slave device converts according to the second information.
  • the data source device communicates with the first data link, that is, the role transition between the master device and the selected slave device is realized; at the same time, the entire role transition process has no impact on the data source device, thereby Does not affect the transmission of application data.
  • the fifth embodiment of the present application relates to a master-slave role conversion method.
  • This embodiment is an improvement on the basis of the fourth embodiment.
  • the main improvement is that the master device negotiates with the selected slave device to determine the waiting time.
  • the specific flow of the master-slave role conversion method of this embodiment is as shown in FIG. 7.
  • the steps 504 to 506 are substantially the same as the steps 402 to 404, and the main differences are as follows:
  • the selected slave device receives the role exchange request sent by the master device, including the number of cycles N, indicating the period of the connection event included from the start time of the current connection event to the start time of the Nth connection event.
  • the master device negotiates with the selected slave device in advance to perform role transition after N connection events, where N is an integer greater than zero. Therefore, the waiting time is the time difference between the start time of the Nth connection event and the start time of the current connection event.
  • Step 502 and step 503 are added, as follows:
  • Step 502 Identify N from the role exchange request, and determine whether to allow role exchange at the beginning of the Nth connection event. If yes, go to step 503; if no, end directly.
  • the slave device identifies the number of cycles N from the role exchange request and determines whether to allow role transition after N connection events. If the result of the determination is allowed, then go to step 503; if not, end directly.
  • step 503 N is integrated into the response.
  • the slave device integrates the cycle number N into the response of the first information for role transition, that is, integrates the cycle number N into the slave device configuration information.
  • the master device negotiates with the selected slave device to obtain the determined time.
  • the sixth embodiment of the present application relates to a chip, which is disposed in a master device, where the master device communicates with the source device by using a first data link, and is connected to at least one slave device, and each slave device has a second data link ( Listen link) Connect to the Source device.
  • the chip includes a first sending module 1 , a second information generating module 2 , a first receiving module 3 , and a first role converting module 4 .
  • the first sending module 1 is configured to send a role exchange request to the selected slave device, and the first receiving module 3 is configured to receive a response of the selected slave device that includes the first information for role conversion, wherein the selected The Slave device is one of at least one slave device connected to the master device; the master device and the at least one slave device remain connected through a connection event.
  • the second information generating module 2 is configured to generate second information for role conversion after receiving the response of the selected slave device including the first information for role conversion.
  • the second information includes the waiting time of the role exchange and the configuration information of the master device, so that the selected slave device is converted into the master device role according to the master device configuration information after the waiting time elapses.
  • the master device configuration information includes the clock precision of the master device and the link information between the master device and each slave device.
  • the link information includes the channel number of the Master device after the role exchange and the connection time of each slave device and the start time of the first connection event.
  • the first sending module 1 is further configured to send the second information to the selected slave device, so that the selected slave device converts to the master device role according to the second information, and the first data link with the source device (Source-Sink) Link) to communicate.
  • the first role conversion module 4 is configured to convert to a slave device role according to the first information, and connect to the source device by using the second data link.
  • the second data link is a Listen link.
  • the first information is the slave device configuration information
  • the first role conversion module 4 is specifically configured to convert to the slave device role according to the slave device configuration information after the waiting time elapses.
  • the slave device configuration information includes the clock precision of the selected slave device.
  • the master device and the data source device communicate with each other on the first data link, and are connected to at least one slave device, and each slave device is connected to the data source device by using the second data link; Based on such a networking mode, the master device sends a role exchange request to the selected slave device, and after receiving the response of the first information for role transition fed back by the selected slave device, generates a role transition for role conversion.
  • the second information the primary device then sends the second information to the selected slave device, the master device converts to the slave device role according to the first information, connects to the data source device with the second data link, and the slave device converts according to the second information.
  • the data source device communicates with the first data link, that is, the role transition between the master device and the selected slave device is realized; at the same time, the entire role transition process has no impact on the data source device, thereby Does not affect the transmission of application data.
  • the seventh embodiment of the present application relates to a chip.
  • the present embodiment is an improvement on the basis of the sixth embodiment.
  • the main improvement is that, referring to FIG. 8, the master device negotiates with the selected slave device to determine the waiting time.
  • the role exchange request sent by the first sending module 1 to the selected slave device includes the number of cycles N, indicating the connection included from the start time of the current connection event to the start time of the Nth connection event.
  • the second information generating module 2 is further configured to: after receiving the response that the selected slave device feeds back the first information for the role transition, determine whether the response includes N; if the determination result is included, the second information is generated. Module 2 sets the waiting time for role swapping according to N.
  • the master device negotiates with the selected slave device to determine the waiting time.
  • the eighth embodiment of the present application relates to a chip.
  • the present embodiment is an improvement based on the sixth embodiment.
  • the main improvement is that, referring to FIG. 9, the chip further includes a trigger module 5.
  • the first receiving module 3 receives at least one performance indicator from each slave device, and the triggering module 5 determines whether to trigger the role transition according to the performance indicator.
  • a slave device is selected according to the performance indicator.
  • the performance metric is one or more of remaining power, wearing status, packet loss rate, and signal strength.
  • the triggering module 5 is configured to: when the remaining power of the master device is less than a preset first power threshold, and the power difference between the remaining power of the at least one slave device and the remaining power of the master device is greater than a preset second power threshold; or When the master device is in the unworn state and at least one slave device is in the worn state; or when the packet loss rate of the master device is greater than the preset first packet loss rate threshold, and the packet loss rate of the at least one slave device is less than Or equal to the preset second packet loss rate threshold, where the second packet loss rate threshold is less than or equal to the first packet loss rate threshold; or when the signal strength of the master device is less than the preset first strength threshold, and at least one slave is present The signal strength of the device is greater than or equal to a preset second intensity threshold, and when the second intensity threshold is greater than or equal to the first intensity threshold, the role transition is triggered.
  • the present embodiment monitors the performance index of the master device and the performance index of the slave device, determines whether the role transition is triggered according to the performance indicator, and selects a slave device according to the performance indicator, that is, performance.
  • the metrics determine the conversion of the master and slave devices, which can avoid the performance degradation of the current master device and affect the performance of the entire data transmission system, thereby improving the performance of the entire data transmission system. It should be noted that the present embodiment can also be used as an improvement on the seventh embodiment, and the same technical effects can be achieved.
  • the ninth embodiment of the present application relates to a chip, which is disposed in a selected slave device, and the selected slave device is connected to the master device, and is connected to the source device by using the second data link, and the master device and the source device are first.
  • the data link communicates and is connected to at least one slave device.
  • the chip includes a second sending module 6, a second receiving module 7, and a second character conversion module 8.
  • the second receiving module 7 is configured to receive a role exchange request sent by the master device.
  • the second sending module 6 is configured to: after receiving the role exchange request sent by the master device, feed back, to the master device, a response including the first information used for role conversion, so that the master device converts to the slave device role according to the first information, Connect to the Source device with the second data link.
  • the second data link is a listening link.
  • the first information is the slave device configuration information, so that the master device connects to the source device with the second data link according to the slave device configuration information after the waiting time elapses.
  • the first information includes the clock accuracy of the selected slave device.
  • the master device and at least one slave device are kept connected through a connection event.
  • the second receiving module 7 is further configured to receive second information sent by the master device for role conversion.
  • the second role conversion module 8 is configured to convert to the master device role according to the second information, and communicate with the source device by using the first data link.
  • the second information includes the waiting time of the role exchange and the configuration information of the master device.
  • the second role conversion module 8 is specifically configured to convert the master device configuration information into the master device role after the waiting time elapses.
  • the waiting time is the time difference between the start time of the role transition and the start time of the current connection event.
  • the master device configuration information includes the clock precision of the master device and the link information between the master device and each slave device.
  • the link information includes the channel number of the master device and each slave device connected with the role and the start time of the first connection event. .
  • the master device and the data source device communicate with each other on the first data link, and are connected to at least one slave device, and each slave device is connected to the data source device by using the second data link; Based on such a networking mode, the master device sends a role exchange request to the selected slave device, and after receiving the response of the first information for role transition fed back by the selected slave device, generates a role transition for role conversion.
  • the second information the primary device then sends the second information to the selected slave device, the master device converts to the slave device role according to the first information, connects to the data source device with the second data link, and the slave device converts according to the second information.
  • the data source device communicates with the first data link, that is, the role transition between the master device and the selected slave device is realized; at the same time, the entire role transition process has no impact on the data source device, thereby Does not affect the transmission of application data.
  • the tenth embodiment of the present application relates to a chip.
  • the embodiment is an improvement based on the ninth embodiment.
  • the main improvement is that the first information generating module 9 is further included.
  • the master device and the selected device are selected.
  • the slave device negotiates to determine the waiting time.
  • the role exchange request sent by the master device received by the selected slave device includes a cycle number N, indicating the number of cycles of the connection event included from the start time of the current connection event to the start time of the Nth connection event, where N Is an integer greater than zero.
  • the first information generating module 9 After receiving the role exchange request sent by the master device, the first information generating module 9 identifies N from the role exchange request, and determines whether to allow role exchange at the start time of the Nth connection event; To allow, then integrate N into the response.
  • the master device negotiates with the selected slave device to determine the waiting time.
  • one chip can have the Master device function and the Slave device function in the sixth embodiment to the tenth embodiment at the same time, so as to implement different functions in different scenarios.
  • the eleventh embodiment of the present application relates to a data transmission system.
  • the data transmission system includes a Source device and a plurality of receiving devices (equivalent to a Sink device, three of which are exemplified in the figure), and the multiple receiving devices include Master device and at least one slave device (two in the figure); the master device is wirelessly connected to each slave device;
  • the Master device and the Source device are wirelessly connected.
  • the Master device and the Source device communicate with the first data link and receive application data from the Source device.
  • the Slave device wirelessly connects with the Source device and receives application data from the Source device in a listening manner.
  • the Master device includes the chips in the sixth to eighth embodiments.
  • the Slave device and the Source device are connected to the Source device by using the second data link, and receive application data from the Source device in a listening manner.
  • the slave device sends a retransmission request of the application data to the master device when the application data is received by the source device in a listening manner; when receiving the retransmission request, the master device sends the application data to the slave device to provide the A remedy for the Slave device to receive application data errors.
  • the master device further receives link establishment information from the source device, and sends the link establishment information to the slave device.
  • the slave device establishes a listening link with the source device according to the link establishment information, and listens from the source device.
  • the source device receives the application data, that is, the slave device and the source device have established a Listen link.
  • the source device does not need to know the role transition between the master device and the slave device, thereby not affecting the transmission of application data.
  • the data transmission system includes a Source device and a plurality of receiving devices (equivalent to a Sink device, three of which are exemplified in the figure), and the plurality of receiving devices include Master device and at least one slave device (two in the figure); the master device is wirelessly connected to each slave device;
  • the Master device and the Source device are wirelessly connected.
  • the Master device and the Source device communicate with the first data link and receive application data from the Source device.
  • the Slave device wirelessly connects with the Source device and receives application data from the Source device in a listening manner.
  • the Slave device and the Source device are connected to the Source device by using the second data link, and receive application data from the Source device in a listening manner.
  • the Slave device includes the chip in the ninth embodiment or the tenth embodiment.
  • the slave device sends a retransmission request of the application data to the master device when the application data is received by the source device in a listening manner; when receiving the retransmission request, the master device sends the application data to the slave device to provide the A remedy for the Slave device to receive application data errors.
  • the master device further receives link establishment information from the source device, and sends the link establishment information to the slave device.
  • the slave device establishes a listening link with the source device according to the link establishment information, and listens from the source device.
  • the source device receives the application data, that is, the slave device and the source device have established a Listen link.
  • the source device does not need to know the role transition between the master device and the slave device, thereby not affecting the transmission of application data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及无线网络技术领域，提供了一种主从角色转换方法、芯片与数据传输系统。方法包括向选定的从设备发送角色互换请求，其中，选定的从设备为与主设备连接的至少一从设备中的一个；当接收到选定的从设备反馈的包括用于角色转换的第一信息的应答后，生成用于角色转换的第二信息；将第二信息发送至选定的从设备，以供选定的从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信；根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。本申请还提供了一种芯片与数据传输系统。本申请中，实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。

Description

主从角色转换方法、芯片与数据传输系统 技术领域
本申请涉及无线网络技术领域，特别涉及一种主从角色转换方法、芯片与数据传输系统。
背景技术
无线个人局域网(Wireless Personal Area Network，WPAN)，指个人范围(随身携带或数米之内)的计算设备(如计算机、电话、掌上电脑、数码相机等)组成的无线通信网络。无线网络数据传送在个人局域网中(Personal Area Network，PAN)有着越来越多的应用，比如：无线耳机、各种穿戴式的数据传感器等，通用的无线链路承载方式包括WIFI、红外或蓝牙等。
发明人发现现有技术至少存在以下问题：在主从设备的无线网络通讯模型中，一般由主设备负责任务调度、链路维系等工作，直至整个系统停止运行，主设备以及从设备的角色保持不变。
发明内容
本申请部分实施例的目的在于提供一种主从角色转换方法、芯片与数据传输系统，实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
本申请实施例提供了一种主从角色转换方法，应用于主设备，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；方法包括：向选定的从设备发送角色互换请求，其中，选定的从设备为与主设备连接的至少一从设备中的一个；当接收到选定的从设备反馈的包括用于角色转换的第一信息的应答后，生成用于角色转换的第二信息；将第二信息发送至选定的从设备，以供选定的从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信；根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。
本申请实施例还提供了一种主从角色转换方法，应用于选定的从设备，选定的从设备与主设备连接，且以第二数据链路与数据源设备连接，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接；方法包括：当接收到主设备发送的角色互换请求后，向主设备反馈包括用于角色转换的第一信息的应答，以供主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接；接收主设备发送的用于角色转换的第二信息；根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信。
本申请实施例还提供了一种芯片，设置于主设备中，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；芯片包括：第一发送模块，用于向选定的从设备发送角色互换请求，其中，选定的从设备为与主设备连接的至少一从设备中的一个；第一接收模块，用于接收所述选定的从设备反馈的包括用于角色转换的第一信息的应答；第二信息生成模块，用于在接收到应答后，生成用于角色转换的第二信息；第一发送模块，还用于将第二信息发送至选定的从设备，以供选定的 从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信；第一角色转换模块，用于根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。
本申请实施例还提供了一种数据传输系统，包括：数据源设备和多个接收设备，多个接收设备包括主设备和至少一个从设备；主设备与每个从设备连接；主设备与数据源设备以第一数据链路进行通信，并从数据源设备接收应用数据；从设备与数据源设备以第二数据链路与数据源设备连接，以侦听方式从数据源设备接收应用数据；主设备包括上述的芯片。
本申请实施例又提供了一种芯片，设置于选定的从设备中，选定的从设备与主设备连接，且以第二数据链路与数据源设备连接，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，芯片包括：第二接收模块，用于接收所述主设备发送的角色互换请求；第二发送模块，用于在接收到角色互换请求后，向主设备反馈包括用于角色转换的第一信息的应答，以供主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接；第二接收模块，还用于接收主设备发送的用于角色转换的第二信息；第二角色转换模块，用于根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信。
本申请实施例又提供了一种数据传输系统，包括：数据源设备和多个接收设备，多个接收设备包括主设备和至少一个从设备；主设备与每个从设备连接；主设备与数据源设备以第一数据链路进行通信，并从数据源设备接收应用数据；从设备与数据源设备以第二数据链路与数据源设备连接，以侦听方式从数据源设备接收应用数据；从设备包括上述的芯片。
本申请实施例相对于现有技术而言，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；基于这样的组网方式，主设备向选定的从设备发送角色互换请求，并在接收到选定的从设备反馈的用于角色转换的第一信息的应答后，生成用于角色转换的第二信息，随后主设备将第二信息发送至选定的从设备，主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接，从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信，即实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是根据本申请第一实施例中的数据传输系统的示意图；
图2是根据本申请第一实施例中的主从角色转换方法的具体流程图；
图3是根据本申请第一实施例中的Master设备与Slave设备互换角色前后的时序示意图；
图4是根据本申请第二实施例中的主从角色转换方法的具体流程图；
图5是根据本申请第三实施例中的主从角色转换方法的具体流程图；
图6是根据本申请第四实施例中的主从角色转换方法的具体流程图；
图7是根据本申请第五实施例中的主从角色转换方法的具体流程图；
图8是根据本申请第六实施例中的芯片的方框示意图；
图9是根据本申请第八实施例中的芯片的方框示意图；
图10是根据本申请第九实施例中的芯片的方框示意图；
图11是根据本申请第十实施例中的芯片的方框示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请部分实施例进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请第一实施例涉及一种主从角色转换方法，应用于主设备，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；方法包括：向选定的从设备发送角色互换请求，其中，选定的从设备为与主设备连接的至少一从设备中的一个；当接收到选定的从设备反馈的包括用于角色转换的第一信息的应答后，生成用于角色转换的第二信息；将第二信息发送至选定的从设备，以供选定的从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信；根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。
本实施例相对于现有技术而言，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；基于这样的组网方式，主设备向选定的从设备发送角色互换请求，并在接收到选定的从设备反馈的用于角色转换的第一信息的应答后，生成用于角色转换的第二信息，随后主设备将第二信息发送至选定的从设备，主设备根据第一 信息转换为从设备角色，以第二数据链路与数据源设备连接，从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信，即实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
下面对本实施方式的主从角色转换方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。
本实施例中，主从角色转换方法所应用的主设备位于一个数据传输系统中；请参考图1，数据传输系统包括数据源设备(Source设备)与三个接收设备(Sink设备，以三个Sink设备为例)，Source设备用于向sink设备下发应用数据，Sink设备为使用这些应用数据的设备。在一个例子中，Source设备例如为电视机等，Sink设备例如包括主音箱、环绕音响、中置音箱、低音音箱等，该Source设备和该些Sink设备形成一个数据传输系统。在另一个例子中，Source设备例如为存储有音乐文件的手机，sink设备例如为无线耳机、无线音箱等。
本实施例的数据传输系统中存在三种链路：Source-Sink链路、Sink设备之间的局域网(即本申请中的无线网络)内部的链路、Sink设备和Source设备之间的侦听(Listen)链路；其中，Source-Sink链路与局域网内部的链路可以基于不同的无线通信标准，然不限于此，也可以基于相同的无线通信标准；无线通信标准包括但不限于蓝牙、WIFI、Zigbee等。下面对三种链路进行具体介绍：
Source-Sink链路由Source设备发起，和各Sink设备中的一个建立连接，Source设备负责Source-Sink链路的链路创建、链路参数管理以及应用数据交互。 Master设备通过Source-Sink链路从Source设备接收应用数据
与Source设备无线连接的Sink设备为局域网中的Master设备，其他的Sink设备均为Slave设备。Master设备和各Slave设备之间建立有Master-Slave链路，Master-Slave链路可以为无线链路，也可以为有线链路；Master设备负责管理加入局域网的Slave设备，并传递Source-Sink链路信息给Slave设备，以帮助Slave设备和Source设备之间建立Listen链路。
Slave设备通过Master设备获得所有的Source-Sink链路信息，与Source设备之间建立有Listen链路，Slave设备以侦听方式从Source设备接收应用数据。
本实施例中，Master设备Source设备之间的Source-Sink链路，即为第一数据链路；Slave设备与Source设备之间的Listen链路，即为第二数据链路。
较佳的，当Slave设备以侦听方式从Source设备接收应用数据发生错误时，直接向Master设备发送应用数据的重传请求，并通过Master-Slave链路接收Master设备发送的请求重传的应用数据。
需要说明的是，局域网内部可以采用简单的星型网络结构，即存在一个Master设备和若干个Slave设备，然不限于此，局域网也可以采用结构更复杂的散射网结构，即一个Master设备同时存在于多个微微网中，可以通过网络节点中继传输应用数据(如Master设备即存在于各sink设备形成的局域网中，又存在于和source设备形成的局域网中)。
本实施例的主从角色转换方法的具体流程如图2所示。
步骤101，向选定的从设备发送角色互换请求。
具体而言，Master设备通过其内部的Controller层向选定的Slave设备发 送角色互换请求。其中，选定的Slave设备为与Master设备连接的各Slave设备中的一个，用于与Master设备进行主从角色转换。Slave设备的选定方式可为：Master设备按照预设条件选定，或者由用户手动选定。
其中，Master设备与各Slave设备通过连接事件保持连接，即，Master设备会通过Master-Slave链路向各Slave设备定时发起连接事件，以始终与各Slave设备保持在连接状态；在一次连接事件的周期内，Master设备按约定的时间顺序分别调度各Slave设备。
步骤102，判断是否接收到选定的从设备反馈的包括用于角色转换的第一信息的应答。若是，则进入步骤103；否则，则回到步骤101。
具体而言，选定的Slave设备在接收到角色互换请求时，若同意该请求，则会反馈一个包括用于角色转换的第一信息的应答，第一信息为Slave设备配置信息；若Master设备判定接收到Slave设备反馈的包括Slave设备配置信息的应答，则进入步骤103；否则，则回到步骤101，Master设备再次向选定的Slave设备发送角色互换请求；较佳的，在Master设备中预设询问次数阈值，当询问次数达到该询问次数阈值时，放弃与该选定的Slave设备互换角色。其中，Slave设备配置信息包括选定的Slave设备的时钟精度。
步骤103，生成用于角色转换的第二信息。
具体而言，Master设备生成用于角色转换的第二信息，第二信息包括角色互换的等待时间和Master设备配置信息。其中，Master设备配置信息包括Master设备的时钟精度、Master设备与每个Slave设备的链路信息，链路信息中包括角色互换后Master设备和每条链路连接的信道编号，以及角色互换后Master设备和每条链路上首次连接事件的发生时间。
步骤104，将第二信息发送至选定的从设备，以供选定的从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信。
具体而言，Master设备将角色互换的等待时间与Master设备配置信息整合成协议数据单元(即第二信息)，并将该协议数据单元发送到选定的Slave设备，以供选定的Slave设备在经过角色互换的等待时间后，根据Master设备配置信息进行角色转换。其中，Master设备配置信息用于供选定的Slave设备在等待时间内的最后一次调度时进行系统配置，并在等待时间后的首次连接事件的开始时间系统配置生效，以转换为Master设备角色；进行角色互换时，新的Master设备(选定的Slave设备转换成新的Master设备)就会向新的Slave设备(原来的Master设备转换成新的Slave设备)发起一次连接事件，新的Master设备与Source设备以Source-Sink链路(第一数据链路)进行通信。需要说明的是，本实施例中，第二信息也可以只包括Master设备配置信息，选定的Slave设备在接收到第二信息后在等待时间内的最后一次调度时进行系统配置，并在下一次连接事件的开始时间系统配置生效，以转换为Master设备角色。
步骤105，根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。
具体而言，在经过等待时间后，Master设备根据Slave设备配置信息转换为Slave设备角色。在等待时间内的最后一次调度时，Master设备根据Slave设备配置信息(第一信息)对自身进行系统配置，并在等待时间后的首次连接事件的开始时间系统配置生效，转换为Slave设备角色，放弃作为Master设备在局域网中的管理工作，只需维系其与选定的Slave设备之间的一条链路，并以第二数据链路(Listen链路)与Source设备连接。同时，在等待时间内的最 后一次调度时，选定的Slave设备根据Master设备配置进行系统配置，并在等待时间后的首次连接事件的开始时间系统配置生效，转换为Master设备角色，从而选定的Slave设备能够无缝的衔接原master设备的工作，开始负责局域网内的管理工作，并负责与Source设备之间的链路维系工作。
本实施例中，Master设备在某次连接事件的开始时间与选定的Slave设备进行角色转换，以图3为例，在当前连接事件的开始时间，Master设备会预估之后某一次连接事件的开始时间，并约定这个时间作为进行角色转换的时刻(以此为例，然不以此为限)，由于Master设备与Slave设备均使用各自的时钟，双方没有物理连接，无法进行同步，因此，Master设备要计算进行角色转换的时刻与当前连接事件的开始时间之间的时间偏移，并将该时间偏移设定为角色互换的等待时间。Slave设备接收到Master设备发送的等待时间后，获取接收到该等待时间所在连接事件的开始时刻，然后将该时刻加上等待时间即可得到约定的进行角色转换的时刻。
在经过等待时间后，到达约定的进行角色转换的时刻，Master设备与选定的Slave设备进行角色互换，选定的Slave设备转换为Master设备后，开始发起与slave设备的连接事件，新的Master设备获取首次连接事件的开始时间(即，约定的进行角色转换的时刻)，并计算该开始时间与上一个时钟边界之间的差值t1作为偏移时间；新的Master设备以本地的时钟边界加上偏移时间t1作为发起连接事件的开始时间，作为在本条Master-Slave链路上发起连接事件的时刻。对于其他的Master-Slave链路上发起连接事件的时刻，则采用相同的计算方法，根据新的Master设备获取首次连接事件的开始时间以及角色互换后每条链路上首次连接事件的开始时间来计算。
在本实施例中，Slave设备以侦听方式从Source设备接收应用数据，即Slave设备拥有所有的Source-Sink链路信息，与Source设备之间已建立有Listen链路，在这种架构下，选定的Slave设备转换为Master设备的过程中，选定的Slave设备与Source设备之间的链路不会被断开，由Listen链路转换为Source-Sink链路，即，始终存在一Sink设备作为Master设备与Source设备连接，因此，整个角色转换过程对Source设备没有任何影响(即实现对Source设备的透明化)，从而不影响应用数据的传输。
本申请第二实施例涉及一种主从角色转换方法，本实施例是在第一实施例基础上的改进，主要改进之处在于：Master设备与选定的Slave设备协商确定等待时间。
本实施例的主从角色转换方法的具体流程如图4所示。
其中，步骤202与步骤102大致相同，步骤205至步骤207与步骤103至步骤105大致相同，主要不同之处在于：
步骤201中，Master设备向选定的从设备发送的角色互换请求中，包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，Master设备预先与选定的Slave设备协商在第N个连接事件的开始时刻进行角色转换，N为大于零的整数。
增加了步骤203、步骤204，具体如下：
步骤203，判断应答中是否包含N；若是，则进入步骤204；若否，则回到步骤201。
具体而言，判断应答中是否包含N，即判断Slave设备是否允许在N个连接事件后进行角色转换，若应答中包含N，则说明Slave设备同意在N个连 接事件后进行角色转换，进入步骤204；否则，则说明Slave设备不同意在N个连接事件后进行角色转换，回到步骤201，Master设备再次向选定的Slave设备发送角色互换请求，并更换角色互换请求中的周期数N。
步骤204，根据N设定角色互换的等待时间。
具体而言，以T表示一次连接事件的周期，则角色互换的等待时间为N*T。例如，周期数N为3，则Master设备会预估第三次连接事件的开始时间，并计算与当前连接事件的开始时间之间的时间偏移，并将该时间偏移设定为角色互换的等待时间。
本实施例相对于第一实施例而言，Master设备可以与选定的Slave设备协商确定等待时间。
本申请第三实施例涉及一种主从角色转换方法，本实施例是在第一实施例基础上的改进，主要改进之处在于：对Master设备与Slave设备的性能指标进行监控，并根据性能指标判断是否触发角色转换。
本实施例的主从角色转换方法的具体流程如图5所示。
其中，步骤304至步骤308与步骤101至步骤105大致相同，主要不同之处在于，增加了步骤301至步骤303，具体如下：
步骤301，分别从每个从设备接收至少一性能指标。
具体而言，Master设备作为局域网中链路的维系者，各Slave设备会周期性向Master设备报告自身的至少一项性能指标；具体的，每个Slave设备的主机协议层(Host层)通过主机控制接口(HCI)命令设置报告周期，每个Slave设备的控制层(Controller层)周期性获取自身的至少一项性能指标，并通过协议数据单元(Protocol Data Unit，PDU)报告到Master设备。
步骤302，根据性能指标判断是否触发角色转换。若是，则触发角色转换，则进入步骤303；若否，则直接结束。
具体而言，Master设备在接收到的各Slave设备报告的性能指标后，对各Slave设备报告的性能指标以及自身对应的性能指标进行判断，即，Master设备需要分别判断Master设备是否需要角色转换，以及是否存在可以与Master设备进行角色转换的slave设备；当判定自身的性能指标与至少一Slave设备报告的性能指标满足预设条件时，进入步骤303；否则，则直接结束。其中，Master设备可以先判断Master设备是否需要角色转换，再判断是否存在可以与Master设备进行角色转换的slave设备；然不限于此，Master设备也可以先判断是否存在可以与Master设备进行角色转换的slave设备，再判断Master设备是否需要角色转换，本实施例对此不作任何限制。
步骤303，根据性能指标选定一个从设备。
具体而言，Master设备的Host层发起角色转换的HCI命令，Master设备的Controller层通过命令状态栏(COMMAND STATUS)回复Host层，启动角色转换流程，并根据接收到的各Slave设备的性能指标，从中选定一个性能指标较好的Slave设备，以与之进行角色转换。
本实施例相对于第一实施例而言，对主设备的性能指标与从设备的性能指标进行监控，根据性能指标判断是否触发角色转换，并根据性能指标选定一个从设备，即，由性能指标来决定进行主从设备的转换，可以避免由于当前的主设备的性能下降而影响整个数据传输系统的性能，从而可以提高整个数据传输系统的性能。需要说明的是，本实施例也可以作为在第二实施例基础上的改进，可以达到同样的技术效果。
本实施例中，性能指标为剩余电量、佩戴状态、丢包率和信号强度中的一个或多个，根据性能指标判断是否触发角色转换，具体包括：
当主设备的剩余电量小于预设的第一电量阈值，且存在至少一个从设备的剩余电量与主设备的剩余电量的电量差值大于预设的第二电量阈值时，触发角色转换；或者，
当主设备处于未佩戴状态，且存在至少一个从设备处于已佩戴状态时，触发角色转换；其中，Sink设备(即Master设备与Slave设备)均为可穿戴的设备，例如无线耳机。Master设备与Slave设备具有传感器(例如触摸传感器)来检测是否处于佩戴状态，然本实施例对具体的检测方式不作任何限制；或者，
当主设备的丢包率大于预设的第一丢包率阈值，且存在至少一个从设备的丢包率小于或等于预设的第二丢包率阈值，第二丢包率阈值小于或者等于第一丢包率阈值时，触发角色转换；其中，Master设备与Slave设备可以实时计算自身的丢包率，具体来说，Slave设备根据自身向Master设备请求重传应用数据的次数来计算丢包率；Master设备根据自身向Source设备请求重传应用数据的次数来计算丢包率；或者，
当主设备的信号强度小于预设的第一强度阈值，且存在至少一个从设备的信号强度大于或等于预设的第二强度阈值，第二强度阈值大于或者等于第一强度阈值时，触发角色转换；其中，Master设备与Slave设备从Source设备获取应用数据时，可以计算信号强度的大小。
当性能指标同时包括剩余电量、佩戴状态、丢包率以及信号强度时，在根据性能指标判断是否触发角色转换时，判断的优先级由高到低可以为：剩余电量、佩戴状态、丢包率、信号强度。其中，对于整个局域网而言，续航能力 至关重要，所以将剩余电量作为第一优先级。
当利用剩余电量进行判断时，将电量最多的Slave设备作为选定的Slave设备，与Master设备进行角色互换，从而可以提升整个无线网络的续航能力，避免Master设备与Slave设备的功耗不对等造成Master设备电池损耗更严重的情况。
利用佩戴状态进行判断时，根据佩戴状态实现的Master设备与Slave设备的角色互换，可以降低处于未佩戴状态的Master设备的功耗。
利用丢包率进行判断时，将丢包率最小的Slave设备作为选定的Slave设备，与Master设备进行角色互换；从而可以减小Master设备与Source设备之间的应用数据传输的丢包率，即可以减少Master设备向Source设备请求重传应用数据的次数，从而可以降低Master设备的功耗，提升整个数据传输系统的续航能力。
利用信号强度进行判断时，将信号强度最大的Slave设备作为选定的Slave设备，与Master设备进行角色互换；从而可以提升Master设备与Source设备之间的应用数据的传输质量。
本申请第四实施例涉及一种主从角色转换方法，应用于无线网络中的被选定与Master设备进行角色互换的Slave设备，选定的Slave设备与Master设备连接，且以第二数据链路(Listen链路)与Source设备连接，Master设备与Source设备以第一数据链路(Source-Sink链路)进行通信，且与至少一Slave设备连接。
本实施例的主从角色转换方法的具体流程如图6所示。
步骤401，判断是否接收到主设备发送的角色互换请求。若是，则进入 步骤402；否则，则再次执行步骤401。
具体而言，Master设备将至少一Slave设备中的一个作为选定的Slave设备，并通过Controller层向选定的Slave设备发送角色互换请求。当判定接收到Master设备发送的角色互换请求时，进入步骤402；否则，则再次执行步骤401，直至接收到Master设备发送的角色互换请求。
本实施例中，Master设备与至少一Slave设备通过连接事件保持连接，即，Master设备会通过Master-Slave链路向各Slave设备定时发起连接事件，以始终与各Slave设备保持在连接状态；在一次连接事件的周期内，Master设备按约定的时间顺序分别调度各Slave设备。
步骤402，向主设备反馈包括用于角色转换的第一信息的应答，以供主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接。
具体而言，选定的Slave设备在接收到角色互换请求时，若同意该请求，则会反馈一个包括用于角色转换的第一信息的应答。Master设备接收到Slave设备反馈的包括第一信息的应答，从而可以根据第一信息转换为Slave设备角色，以第二数据链路与Source设备连接。其中，第一信息为Slave设备配置信息，Slave设备配置信息包括选定的Slave设备的时钟精度；第二数据链路为侦听链路。
步骤403，接收主设备发送的用于角色转换的第二信息。
具体而言，Master设备生成用于角色转换的第二信息，并将第二信息发送至选定的Slave设备。其中，第二信息包括角色互换的等待时间和Master设备配置信息；Master设备配置信息包括Master设备的时钟精度和Master设备与每个Slave设备的链路信息，链路信息中包括角色互换后Master设备和每条 链路连接的信道编号，以及角色互换后Master设备和每条链路上首次连接事件的发生时间。
步骤404，根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信。
具体而言，在经过等待时间后，根据Master设备配置信息转换为Master设备角色。详细的说，在等待时间内的最后一次调度时，选定的Slave设备根据Master设备配置进行系统配置，并在等待时间后的首次连接事件的开始时间系统配置生效，转换为Master设备角色，从而选定的Slave设备能够无缝的衔接master的工作，开始负责局域网内的管理工作，并负责与Source设备之间的链路维系工作。同时，在等待时间内的最后一次调度时，Master设备根据Slave设备配置信息(第一信息)对自身进行系统配置，并在等待时间后的首次连接事件的开始时间系统配置生效，转换为Slave设备角色，放弃作为Master设备在局域网中的管理工作，只需维系其与选定的Slave设备之间的一条链路，并以第二数据链路(Listen链路)与Source设备连接。
本实施例中，Master设备将角色互换的等待时间与Master设备配置信息整合成协议数据单元，并将该协议数据单元发送到选定的Slave设备；其中，Master设备配置信息用于供选定的Slave设备在经过等待时间后进行系统配置，以转换为Master设备角色。
其中，根据Master设备配置信息进行系统配置，以转换为Master设备角色，具体为：根据每条链路上的首次连接事件的发生时间与本地时钟计算出每条链路对应的连接事件的偏移时间，以供选定的Slave设备转换成Master设备角色后确定在每条链路上发起连接事件的时刻。
具体而言，请参考图3，Slave设备接收到Master设备发送的等待时间后，获取接收到该等待时间所在连接事件的开始时刻，然后将该时刻加上等待时间即可得到约定的进行角色转换的时刻。在经过等待时间后，到达约定的进行角色转换的时刻，Master设备与选定的Slave设备进行角色互换，选定的Slave设备转换为Master设备后，开始发起与slave设备的连接事件，新的Master设备获取首次连接事件的开始时间(即，约定的进行角色转换的时刻)，并计算该开始时间与上一个时钟边界之间的差值t1作为偏移时间；新的Master设备以本地的时钟边界加上偏移时间t1作为发起连接事件的开始时间，作为在本条Master-Slave链路上发起连接事件的时刻。对于其他的Master-Slave链路上发起连接事件的时刻，则采用相同的计算方法，根据新的Master设备获取首次连接事件的开始时间以及角色互换后每条链路上首次连接事件的开始时间来计算。
在本实施例中，Slave设备以侦听方式从Source设备接收应用数据，即Slave设备拥有所有的Source-Sink链路信息，与Source设备之间已建立有Listen链路，在这种架构下，选定的Slave设备转换为Master设备的过程中，选定的Slave设备与Source设备之间的链路不会被断开，由Listen链路转换为Source-Sink链路，即，始终存在一Sink设备作为Master设备与Source设备连接，因此，整个角色转换过程对Source设备没有任何影响(即实现对Source设备的透明化)，从而不影响应用数据的传输。
需要说明的是，现有架构中，Slave设备与Source设备之间没有建立Listen链路，Master设备接收应用数据后再发送至各Slave设备；因此，如果以现有的构架来实现Master设备与Slave设备的角色转换，则转换时首先Master设备会与Source设备断开连接，然后新的Master设备要重新与Source设备连线， 才能继续传输应用数据，用户体验不佳。
本实施例相对于现有技术而言，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；基于这样的组网方式，主设备向选定的从设备发送角色互换请求，并在接收到选定的从设备反馈的用于角色转换的第一信息的应答后，生成用于角色转换的第二信息，随后主设备将第二信息发送至选定的从设备，主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接，从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信，即实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
本申请第五实施例涉及一种主从角色转换方法，本实施例是在第四实施例基础上的改进，主要改进之处在于：Master设备与选定的Slave设备协商确定等待时间。
本实施例的主从角色转换方法的具体流程如图7所示。
其中，步骤504至步骤506与步骤402至步骤404大致相同，主要不同之处在于：
步骤501中，选定的Slave设备接收到Master设备发送的角色互换请求中，包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，Master设备预先与选定的Slave设备协商在N个连接事件后进行角色转换，N为大于零的整数。因此，等待时间为第N次连接事件的开始时刻与当前连接事件的开始时刻的时间差。
增加了步骤502、步骤503，具体如下：
步骤502，从角色互换请求中识别出N，并判断是否允许在第N次连接事件的开始时刻进行角色互换。若是，则进入步骤503；若否，直接结束。
具体而言，Slave设备从角色互换请求中识别出周期数N，并判断是否允许在N个连接事件后进行角色转换。若判断结果是允许，则进入步骤503；若否，直接结束。
步骤503，将N整合入应答中。
具体而言，Slave设备将周期数N整合入用于角色转换的第一信息的应答，即，将周期数N整合入Slave设备配置信息。
本实施例相对于第四实施例而言，Master设备与选定的Slave设备协商获取确定时间。
本申请第六实施例涉及一种芯片，设置于Master设备中，Master设备与Source设备以第一数据链路进行通信，且与至少一Slave设备连接，每个Slave设备以第二数据链路(Listen链路)与Source设备连接。请参考图8，芯片包括第一发送模块1、第二信息生成模块2、第一接收模块3以及第一角色转换模块4。
第一发送模块1用于向选定的Slave设备发送角色互换请求，第一接收模块3用于接收选定的Slave设备反馈的包括用于角色转换的第一信息的应答其中，选定的Slave设备为与Master设备连接的至少一Slave设备中的一个；Master设备与至少一Slave设备通过连接事件保持连接。
第二信息生成模块2用于当接收到选定的Slave设备反馈的包括用于角色转换的第一信息的应答后，生成用于角色转换的第二信息。
本实施例中，第二信息包括角色互换的等待时间和Master设备配置信 息，以供选定的Slave设备在经过等待时间后，根据Master设备配置信息转换为Master设备角色。其中，Master设备配置信息包括Master设备的时钟精度和Master设备与每个Slave设备的链路信息。链路信息包括角色互换后的Master设备和每个Slave设备连接的信道编号和首次连接事件的开始时刻。
第一发送模块1还用于将第二信息发送至选定的Slave设备，以供选定的Slave设备根据第二信息转换为Master设备角色，与Source设备以第一数据链路(Source-Sink链路)进行通信。
第一角色转换模块4用于根据第一信息转换为Slave设备角色，以第二数据链路与Source设备连接。其中，第二数据链路为Listen链路。
本实施例中，第一信息为Slave设备配置信息，第一角色转换模块4具体用于在经过等待时间后，根据Slave设备配置信息转换为Slave设备角色。其中，Slave设备配置信息包括选定的Slave设备的时钟精度。
本实施例相对于现有技术而言，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；基于这样的组网方式，主设备向选定的从设备发送角色互换请求，并在接收到选定的从设备反馈的用于角色转换的第一信息的应答后，生成用于角色转换的第二信息，随后主设备将第二信息发送至选定的从设备，主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接，从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信，即实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
本申请第七实施例涉及一种芯片，本实施例是在第六实施例基础上的改 进，主要改进之处在于：请参考图8，Master设备与选定的Slave设备协商确定等待时间。
本实施例中，第一发送模块1向选定的从设备发送的角色互换请求中，包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中N为大于零的整数。
第二信息生成模块2还用于在接收到选定的从设备反馈的包括用于角色转换的第一信息的应答后，判断应答中是否包含N；若判断结果为包含，则第二信息生成模块2根据N设定角色互换的等待时间。
本实施例相对于第六实施例而言，Master设备与选定的Slave设备协商确定等待时间。
本申请第八实施例涉及一种芯片，本实施例是在第六实施例基础上的改进，主要改进之处在于：请参考图9，芯片还包括触发模块5。
在第一发送模块1向选定的Slave设备发送角色互换请求之前，第一接收模块3分别从每个Slave设备接收至少一性能指标，触发模块5根据性能指标判断是否触发角色转换。
若触发模块5判定触发角色转换，根据性能指标选定一个Slave设备。
在一个例子中，性能指标为剩余电量、佩戴状态、丢包率和信号强度中的一个或者多个。
触发模块5用于当Master设备的剩余电量小于预设的第一电量阈值，且存在至少一个Slave设备的剩余电量与Master设备的剩余电量的电量差值大于预设的第二电量阈值时；或者当Master设备处于未佩戴状态，且存在至少一个Slave设备处于已佩戴状态时；或者当Master设备的丢包率大于预设的第一 丢包率阈值，且存在至少一个Slave设备的丢包率小于或等于预设的第二丢包率阈值，第二丢包率阈值小于或者等于第一丢包率阈值时；或者当Master设备的信号强度小于预设的第一强度阈值，且存在至少一个Slave设备的信号强度大于或等于预设的第二强度阈值，第二强度阈值大于或者等于第一强度阈值时，触发角色转换。
本实施例相对于第六实施例而言，对主设备的性能指标与从设备的性能指标进行监控，根据性能指标判断是否触发角色转换，并根据性能指标选定一个从设备，即，由性能指标来决定进行主从设备的转换，可以避免由于当前的主设备的性能下降而影响整个数据传输系统的性能，从而可以提高整个数据传输系统的性能。需要说明的是，本实施例也可以作为在第七实施例基础上的改进，可以达到同样的技术效果。
本申请第九实施例涉及一种芯片，设置于选定的Slave设备中，选定的Slave设备与Master设备连接，且以第二数据链路与Source设备连接，Master设备与Source设备以第一数据链路进行通信，且与至少一Slave设备连接。请参考图10，芯片包括第二发送模块6、第二接收模块7以及第二角色转换模块8。
第二接收模块7用于接收所述主设备发送的角色互换请求。第二发送模块6用于在接收到Master设备发送的角色互换请求后，向Master设备反馈包括用于角色转换的第一信息的应答，以供Master设备根据第一信息转换为Slave设备角色，以第二数据链路与Source设备连接。其中，第二数据链路为侦听链路。其中，第一信息为Slave设备配置信息，以供Master设备在经过等待时间后，根据Slave设备配置信息为Slave设备角色，以第二数据链路与Source设 备连接。第一信息包括选定的Slave设备的时钟精度。
本实施例中，Master设备与至少一Slave设备通过连接事件保持连线。
第二接收模块7还用于接收Master设备发送的用于角色转换的第二信息。
第二角色转换模块8用于根据第二信息转换为Master设备角色，与Source设备以第一数据链路进行通信。
本实施例中，第二信息包括角色互换的等待时间和Master设备配置信息；第二角色转换模块8具体用于在经过等待时间后，根据Master设备配置信息转换为Master设备角色。其中，等待时间为角色转换的开始时刻与当前连接事件的开始时刻的时间差。Master设备配置信息包括Master设备的时钟精度和Master设备与每个Slave设备的链路信息，链路信息包括角色互换后的Master设备和每个Slave设备连接的信道编号和首次连接事件的开始时刻。
本实施例相对于现有技术而言，主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与数据源设备连接；基于这样的组网方式，主设备向选定的从设备发送角色互换请求，并在接收到选定的从设备反馈的用于角色转换的第一信息的应答后，生成用于角色转换的第二信息，随后主设备将第二信息发送至选定的从设备，主设备根据第一信息转换为从设备角色，以第二数据链路与数据源设备连接，从设备根据第二信息转换为主设备角色，与数据源设备以第一数据链路进行通信，即实现了主设备与选定的从设备之间的角色转换；同时，整个角色转换过程对数据源设备没有任何影响，从而不影响应用数据的传输。
本申请第十实施例涉及一种芯片，本实施例是在第九实施例基础上的改 进，主要改进之处在于：还包括第一信息生成模块9，请参考图11，Master设备与选定的Slave设备协商确定等待时间。
选定的Slave设备接收到的Master设备发送的角色互换请求中包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中N为大于零的整数。
在接收到Master设备发送的角色互换请求后，第一信息生成模块9从角色互换请求中识别出N，并判断是否允许在第N次连接事件的开始时刻进行角色互换；若判断结果为允许，则将N整合入应答中。
本实施例相对于第九实施例而言，Master设备与选定的Slave设备协商确定等待时间。
需要说明的是，一颗芯片可以同时具有第六实施例至第十实施例中的Master设备功能与Slave设备功能，以便于在不同的场景中实现不同的功能。
本申请第十一实施例涉及一种数据传输系统，请参考图1，数据传输系统包括Source设备和多个接收设备(相当于Sink设备，图中以三个为例)，多个接收设备包括Master设备和至少一个Slave设备(图中以两个为例)；Master设备与每个Slave设备无线连接；
Master设备与Source设备无线连接，Master设备与Source设备以第一数据链路进行通信，并从Source设备接收应用数据；Slave设备与Source设备无线连接，并以侦听方式从Source设备接收应用数据。Master设备包括第六实施例至第八实施例中的芯片。
Slave设备与Source设备以第二数据链路与Source设备连接，以侦听方式从Source设备接收应用数据。
较佳的，Slave设备在以侦听方式从Source设备接收应用数据发生错误时，向Master设备发送应用数据的重传请求；Master设备接收到重传请求时，将应用数据发送至Slave设备，提供了Slave设备接收应用数据出错时的一种补救方式。
在一个例子中，Master设备还从Source设备接收链路建立信息，并将链路建立信息发送至Slave设备；Slave设备根据链路建立信息与Source设备建立侦听链路，并以侦听方式从Source设备接收应用数据，即Slave设备与Source设备已建立有Listen链路，在这种构架下，Source设备不需要得知Master设备与Slave设备的角色转换，从而不影响应用数据的传输。
本申请第十二实施例涉及一种数据传输系统，请参考图1，数据传输系统包括Source设备和多个接收设备(相当于Sink设备，图中以三个为例)，多个接收设备包括Master设备和至少一个Slave设备(图中以两个为例)；Master设备与每个Slave设备无线连接；
Master设备与Source设备无线连接，Master设备与Source设备以第一数据链路进行通信，并从Source设备接收应用数据；Slave设备与Source设备无线连接，并以侦听方式从Source设备接收应用数据。
Slave设备与Source设备以第二数据链路与Source设备连接，以侦听方式从Source设备接收应用数据。
Slave设备包括第九实施例或第十实施例中的芯片。
较佳的，Slave设备在以侦听方式从Source设备接收应用数据发生错误时，向Master设备发送应用数据的重传请求；Master设备接收到重传请求时，将应用数据发送至Slave设备，提供了Slave设备接收应用数据出错时的一种补 救方式。
在一个例子中，Master设备还从Source设备接收链路建立信息，并将链路建立信息发送至Slave设备；Slave设备根据链路建立信息与Source设备建立侦听链路，并以侦听方式从Source设备接收应用数据，即Slave设备与Source设备已建立有Listen链路，在这种构架下，Source设备不需要得知Master设备与Slave设备的角色转换，从而不影响应用数据的传输。
本领域的普通技术人员可以理解，上述各实施例是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (36)

  1. 一种主从角色转换方法，其特征在于，应用于主设备，所述主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与所述数据源设备连接；所述方法包括：
    向选定的从设备发送角色互换请求，其中，所述选定的从设备为与所述主设备连接的至少一从设备中的一个；
    当接收到所述选定的从设备反馈的包括用于角色转换的第一信息的应答后，生成用于角色转换的第二信息；
    将所述第二信息发送至所述选定的从设备，以供所述选定的从设备根据所述第二信息转换为主设备角色，与所述数据源设备以所述第一数据链路进行通信；
    根据所述第一信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接。
  2. 如权利要求1所述的主从角色转换方法，其特征在于，所述第二数据链路为侦听链路。
  3. 如权利要求1或者2所述的主从角色转换方法，其特征在于，所述第二信息包括角色互换的等待时间和主设备配置信息，以供所述选定的从设备在经过所述等待时间后，根据所述主设备配置信息转换为主设备角色；
    所述第一信息为从设备配置信息，所述根据所述第一信息转换为从设备角色具体包括：
    在经过所述等待时间后，根据所述从设备配置信息转换为从设备角色。
  4. 如权利要求3所述的主从角色转换方法，其特征在于，所述主设备与所述至少一从设备通过连接事件保持连接；
    所述角色互换请求中包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中所述N为大于零的整数；
    在接收到所述选定的从设备反馈的包括用于角色转换的第一信息的应答后，且在所述生成用于角色转换的第一信息之前，还包括：
    判断所述应答中是否包含所述N；
    若判断结果为包含，则根据所述N设定角色互换的所述等待时间。
  5. 如权利要求1-4任一项所述的主从角色转换方法，其特征在于，所述第一信息包括所述选定的从设备的时钟精度。
  6. 如权利要求1-5任一项所述的主从角色转换方法，其特征在于，所述第二信息包括所述主设备的时钟精度和主设备与每个从设备的链路信息。
  7. 如权利要求6所述的主从角色转换方法，其特征在于，所述链路信息包括角色互换后的主设备和每个从设备连接的信道编号和首次连接事件的开始时刻。
  8. 如权利要求1-7任一项所述的主从角色转换方法，其特征在于，在所述向选定的从设备发送角色互换请求之前，还包括：
    分别从每个从设备接收至少一性能指标；
    根据所述性能指标判断是否触发角色转换；
    若触发角色转换，根据所述性能指标选定一个从设备。
  9. 如权利要求8所述的主从角色转换方法，其特征在于，所述性能指标为剩余电量、佩戴状态、丢包率和信号强度中的一个或者多个。
  10. 如权利要求8或者9所述的主从角色转换方法，其特征在于，所述根据所述性能指标判断是否触发角色转换具体包括：
    当所述主设备的剩余电量小于预设的第一电量阈值，且存在至少一个从设备的剩余电量与所述主设备的剩余电量的电量差值大于预设的第二电量阈值时；或者
    当所述主设备处于未佩戴状态，且存在至少一个从设备处于已佩戴状态时；或者
    当所述主设备的丢包率大于预设的第一丢包率阈值，且存在至少一个从设备的丢包率小于或等于预设的第二丢包率阈值，所述第二丢包率阈值小于或者等于所述第一丢包率阈值时；或者
    当所述主设备的信号强度小于预设的第一强度阈值，且存在至少一个从设备的信号强度大于或等于预设的第二强度阈值，所述第二强度阈值大于或者等于所述第一强度阈值时，触发角色转换。
  11. 一种主从角色转换方法，其特征在于，应用于选定的从设备，所述选定的从设备与主设备连接，且以第二数据链路与数据源设备连接，所述主设备与所述数据源设备以第一数据链路进行通信，且与至少一从设备连接；所述方法包括：
    当接收到所述主设备发送的角色互换请求后，向所述主设备反馈包括用于角色转换的第一信息的应答，以供所述主设备根据所述第一信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接；
    接收所述主设备发送的用于角色转换的第二信息；
    根据所述第二信息转换为主设备角色，与所述数据源设备以所述第一数据链路进行通信。
  12. 如权利要求11所述的主从角色转换方法，其特征在于，所述第二数据链路为侦听链路。
  13. 如权利要求11或者12所述的主从角色转换方法，其特征在于，所述第二信息包括角色互换的等待时间和主设备配置信息；
    所述根据所述第二信息转换为主设备角色具体包括：
    在经过所述等待时间后，根据所述主设备配置信息转换为主设备角色；
    所述第一信息为从设备配置信息，以供所述主设备在经过所述等待时间后，根据所述从设备配置信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接。
  14. 如权利要求13所述的主从角色转换方法，其特征在于，所述主设备与所述至少一从设备通过连接事件保持连线；
    所述角色互换请求中包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中所述N为大于零的整数；
    在接收到所述主设备发送的角色互换请求后，且在向所述主设备反馈包括用于角色转换的第一信息的应答之前，还包括：
    从所述角色互换请求中识别出所述N，并判断是否允许在所述第N次连接事件的开始时刻进行角色互换；
    若判断结果为允许，将所述N整合入所述应答中；
    所述等待时间为所述第N次连接事件的开始时刻与当前连接事件的开始时刻的时间差。
  15. 如权利要求11-14任一项所述的主从角色转换方法，其特征在于，所述第一信息包括所述选定的从设备的时钟精度。
  16. 如权利要求11-15任一项所述的主从角色转换方法，其特征在于，所述第二信息包括所述主设备的时钟精度和主设备与每个从设备的链路信息。
  17. 如权利要求16所述的主从角色转换方法，其特征在于，所述链路信息包括角色互换后的主设备和每个从设备连接的信道编号和首次连接事件的开始时刻。
  18. 一种芯片，其特征在于，设置于主设备中，所述主设备与数据源设备以第一数据链路进行通信，且与至少一从设备连接，每个从设备以第二数据链路与所述数据源设备连接；所述芯片包括：
    第一发送模块，用于向选定的从设备发送角色互换请求，其中，所述选定的从设备为与所述主设备连接的至少一从设备中的一个；
    第一接收模块，用于接收所述选定的从设备反馈的包括用于角色转换的第一信息的应答；
    第二信息生成模块，用于在接收到所述应答后，生成用于角色转换的第二信息；
    第一发送模块，还用于将所述第二信息发送至所述选定的从设备，以供所述选定的从设备根据所述第二信息转换为主设备角色，与所述数据源设备以所述第一数据链路进行通信；
    第一角色转换模块，用于根据所述第一信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接。
  19. 如权利要求18所述的芯片，其特征在于，所述第二数据链路为侦听链路。
  20. 如权利要求18或者19所述的芯片，其特征在于，所述第二信息包括角色互换的等待时间和主设备配置信息，以供所述选定的从设备在经过所述等待时间后，根据所述主设备配置信息转换为主设备角色；
    所述第一信息为从设备配置信息，所述第一角色转换模块具体用于在经过所述等待时间后，根据所述从设备配置信息转换为从设备角色。
  21. 如权利要求20所述的芯片，其特征在于，所述主设备与所述至少一从设备通过连接事件保持连接；
    所述角色互换请求中包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中所述N为大于零的整数；
    在接收到所述应答后，所述第二信息生成模块还用于判断所述应答中是否包含所述N；若判断结果为包含，则根据所述N设定角色互换的所述等待时间。
  22. 如权利要求18-21任一项所述的芯片，其特征在于，所述第一信息包括所述选定的从设备的时钟精度。
  23. 如权利要求18-22任一项所述的芯片，其特征在于，所述第二信息包括所述主设备的时钟精度和主设备与每个从设备的链路信息。
  24. 如权利要求23所述的芯片，其特征在于，所述链路信息包括角色互换后的主设备和每个从设备连接的信道编号和首次连接事件的开始时刻。
  25. 如权利要求18-24任一项所述的芯片，其特征在于，所述芯片还包括触发模块，在所述第一发送模块向选定的从设备发送角色互换请求之前，所述第一接收模块用于分别从每个从设备接收至少一性能指标，所述触发模块根据所述性能指标判断是否触发角色转换；若触发角色转换，根据所述性能指标选定一个从设备。
  26. 如权利要求25所述的芯片，其特征在于，所述性能指标为剩余电量、佩戴状态、丢包率和信号强度中的一个或者多个。
  27. 如权利要求25或者26所述的芯片，其特征在于，所述触发模块用于根据所述性能指标判断是否触发角色转换，具体为：
    所述触发模块用于当所述主设备的剩余电量小于预设的第一电量阈值，且存在至少一个从设备的剩余电量与所述主设备的剩余电量的电量差值大于预设的第二电量阈值时；或者
    当所述主设备处于未佩戴状态，且存在至少一个从设备处于已佩戴状态时；或者
    当所述主设备的丢包率大于预设的第一丢包率阈值，且存在至少一个从设备的丢包率小于或等于预设的第二丢包率阈值，所述第二丢包率阈值小于或者等于所述第一丢包率阈值时；或者
    当所述主设备的信号强度小于预设的第一强度阈值，且存在至少一个从设备的信号强度大于或等于预设的第二强度阈值，所述第二强度阈值大于或者等于所述第一强度阈值时，触发角色转换。
  28. 一种芯片，其特征在于，设置于选定的从设备中，所述选定的从设备与主设备连接，且以第二数据链路与数据源设备连接，所述主设备与所述数据源设备以第一数据链路进行通信，且与至少一从设备连接，所述芯片包括：
    第二接收模块，用于接收所述主设备发送的角色互换请求；
    第二发送模块，用于在接收到所述角色互换请求后，向所述主设备反馈包括用于角色转换的第一信息的应答，以供所述主设备根据所述第一信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接；
    第二接收模块，还用于接收所述主设备发送的用于角色转换的第二信息；
    第二角色转换模块，用于根据所述第二信息转换为主设备角色，与所述数据源设备以所述第一数据链路进行通信。
  29. 如权利要求28所述的芯片，其特征在于，所述第二数据链路为侦听链路。
  30. 如权利要求28或者29所述的芯片，其特征在于，所述第二信息包括角色互换的等待时间和主设备配置信息；
    所述第二角色转换模块具体用于在经过所述等待时间后，根据所述主设备配置信息转换为主设备角色；
    所述第一信息为从设备配置信息，以供所述主设备在经过所述等待时间后，根据所述从设备配置信息转换为从设备角色，以所述第二数据链路与所述数据源设备连接。
  31. 如权利要求30所述的芯片，其特征在于，所述主设备与所述至少一从设备通过连接事件保持连线；
    所述角色互换请求中包括周期数N，表示从当前连接事件的开始时刻到第N次连接事件的开始时刻所包含的连接事件的周期数，其中所述N为大于零的整数；
    还包括第一信息生成模块；
    在接收到所述角色互换请求后，所述第一信息生成模块用于从所述角色互换请求中识别出所述N，并判断是否允许在所述第N次连接事件的开始时刻进行角色互换；若判断结果为允许，则将所述N整合入包括用于角色转换的第一信息的应答中；
    所述等待时间为所述第N次连接事件的开始时刻与当前连接事件的开始时刻的时间差。
  32. 如权利要求28-31任一项所述的芯片，其特征在于，所述第一信息包括所述选定的从设备的时钟精度。
  33. 如权利要求28-32任一项所述的芯片，其特征在于，所述第二信息包括所述主设备的时钟精度和主设备与每个从设备的链路信息。
  34. 如权利要求33所述的芯片，其特征在于，所述链路信息包括角色互换后的主设备和每个从设备连接的信道编号和首次连接事件的开始时刻。
  35. 一种数据传输系统，其特征在于，包括：数据源设备和多个接收设备，所述多个接收设备包括主设备和至少一个从设备；所述主设备与每个从设备连接；
    所述主设备与所述数据源设备以第一数据链路进行通信，并从所述数据源设备接收应用数据；
    所述从设备与所述数据源设备以第二数据链路与所述数据源设备连接，以侦听方式从所述数据源设备接收所述应用数据；
    所述主设备包括如权利要求18至27中任一项所述的芯片。
  36. 一种数据传输系统，其特征在于，包括：数据源设备和多个接收设备，所述多个接收设备包括主设备和至少一个从设备；所述主设备与每个从设备连接；
    所述主设备与所述数据源设备以第一数据链路进行通信，并从所述数据源设备接收应用数据；
    所述从设备与所述数据源设备以第二数据链路与所述数据源设备连接，以侦听方式从所述数据源设备接收所述应用数据；
    所述从设备包括如权利要求28至34任一项所述的芯片。
PCT/CN2018/074164 2018-01-25 2018-01-25 主从角色转换方法、芯片与数据传输系统 WO2019144351A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880000275.1A CN108323241B (zh) 2018-01-25 2018-01-25 主从角色转换方法、芯片与数据传输系统
PCT/CN2018/074164 WO2019144351A1 (zh) 2018-01-25 2018-01-25 主从角色转换方法、芯片与数据传输系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/074164 WO2019144351A1 (zh) 2018-01-25 2018-01-25 主从角色转换方法、芯片与数据传输系统

Publications (1)

Publication Number Publication Date
WO2019144351A1 true WO2019144351A1 (zh) 2019-08-01

Family

ID=62896671

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074164 WO2019144351A1 (zh) 2018-01-25 2018-01-25 主从角色转换方法、芯片与数据传输系统

Country Status (2)

Country Link
CN (1) CN108323241B (zh)
WO (1) WO2019144351A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019144351A1 (zh) * 2018-01-25 2019-08-01 深圳市为通博科技有限责任公司 主从角色转换方法、芯片与数据传输系统
CN110266547B (zh) * 2019-07-02 2022-05-24 普联技术有限公司 一种组网方法及设备
CN111107526B (zh) * 2019-10-08 2023-05-02 珠海市杰理科技股份有限公司 标准时隙的双无线蓝牙设备主从切换方法、设备和系统
CN111225437A (zh) * 2019-11-29 2020-06-02 博微宇空(重庆)科技有限公司 一种地基基站接收信号的增益控制方法
CN111475484A (zh) * 2020-03-26 2020-07-31 平安银行股份有限公司 一种数据源切换方法、装置、计算机设备及存储介质
CN112672290B (zh) * 2020-12-02 2022-05-31 无锡中感微电子股份有限公司 一种在无线通信系统进行主从切换的方法、装置及设备
CN112788494A (zh) * 2021-02-09 2021-05-11 维沃移动通信有限公司 耳机控制方法、装置、设备及介质
CN115412952B (zh) * 2021-05-27 2024-06-14 成都极米科技股份有限公司 一种无线感知控制方法、设备和计算机存储介质
CN113890144A (zh) * 2021-09-29 2022-01-04 青岛海信移动通信技术股份有限公司 一种充放电控制方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103731294A (zh) * 2013-03-28 2014-04-16 深圳市金溢科技有限公司 一种双机热备通信方法和设备及系统
CN104335642A (zh) * 2012-05-26 2015-02-04 高通股份有限公司 用于音频设备的智能电池耗损均衡
CN106535057A (zh) * 2016-12-07 2017-03-22 歌尔科技有限公司 一种主设备与从设备的运行切换方法和系统
CN108323241A (zh) * 2018-01-25 2018-07-24 深圳市为通博科技有限责任公司 主从角色转换方法、芯片与数据传输系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20002860A (fi) * 2000-12-27 2002-06-28 Nokia Corp Laiteroolit ja pikoverkkoyhteydet
CN105787344A (zh) * 2016-03-25 2016-07-20 江苏惠通集团有限责任公司 一种从设备及其与主设备建立连接的方法
CN106535081A (zh) * 2016-12-20 2017-03-22 建荣半导体（深圳）有限公司 蓝牙模式切换方法、装置、通信系统及立体声音频传输方法
CN106878926B (zh) * 2017-02-08 2020-11-06 泰凌微电子（上海）有限公司 一种基于低功耗蓝牙的数据传输方法、从主设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104335642A (zh) * 2012-05-26 2015-02-04 高通股份有限公司 用于音频设备的智能电池耗损均衡
CN103731294A (zh) * 2013-03-28 2014-04-16 深圳市金溢科技有限公司 一种双机热备通信方法和设备及系统
CN106535057A (zh) * 2016-12-07 2017-03-22 歌尔科技有限公司 一种主设备与从设备的运行切换方法和系统
CN108323241A (zh) * 2018-01-25 2018-07-24 深圳市为通博科技有限责任公司 主从角色转换方法、芯片与数据传输系统

Also Published As

Publication number Publication date
CN108323241A (zh) 2018-07-24
CN108323241B (zh) 2021-01-29

Similar Documents

Publication Publication Date Title
WO2019144351A1 (zh) 主从角色转换方法、芯片与数据传输系统
US10206084B2 (en) Power-efficient, balanced, and reliable true wireless bluetooth stereo audio solution
WO2020132922A1 (zh) 一种连接蓝牙设备方法及设备
WO2021129892A1 (zh) 用于无线通信的设备主从角色切换系统及方法
JP6625887B2 (ja) 無線システム、無線機器、通信プログラム、および通信方法
JP5873476B2 (ja) 異種ネットワークを介した患者のモニタリング
TWI339042B (en) Communication methods and apparatus relating to cooperative and non-cooperative modes of operation
CA3067279A1 (en) Communication processing method and communications apparatus
JP6772330B2 (ja) マルチ構成要員型ブルートゥース装置におけるブルートゥース副回路
WO2021175126A1 (zh) 一种测量方法、装置及系统
TWI430631B (zh) 無線通訊系統及其相關方法
WO2020164534A1 (zh) 辅助信息上报方法及装置、通信设备
JP2015534413A (ja) ワイヤレス通信における省電力のためのシステムおよび方法
JP2008541641A5 (zh)
CN111698794B (zh) 一种无线音频共享方法
JP5964737B2 (ja) 通信端末
JP6772329B2 (ja) 信号途切れを回避可能なマルチ構成要員型ブルートゥース装置
WO2011097893A1 (zh) 一种e1双向环网络的数据传输方法、装置及系统
WO2022052129A1 (zh) 一种可靠性测量方法、装置及系统
CN109587666A (zh) 蓝牙设备、系统及调度方法
TWI789236B (zh) 可避免聲音中斷的藍牙通信系統及相關的藍牙設備群
WO2021092839A1 (zh) 数据传输方法、电子设备、系统及存储介质
CN103220775A (zh) 一种实现数据同步的方法、装置和系统
KR100636527B1 (ko) 블루투스 시스템에서의 전력 관리 장치 및 그 방법
JP2020127238A (ja) 無線システム、無線機器、通信プログラム、および通信方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18902255

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18902255

Country of ref document: EP

Kind code of ref document: A1