WO2022155862A1

WO2022155862A1 - Synchronization method and synchronization device

Info

Publication number: WO2022155862A1
Application number: PCT/CN2021/073163
Authority: WO
Inventors: 董建利
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-01-21
Filing date: 2021-01-21
Publication date: 2022-07-28
Also published as: CN116349258A

Abstract

The present application relates to a synchronization method and a synchronization device. The synchronization method comprises: a controller switches, on the basis of a broadcast isochronous group (BIG) creation and synchronization request, a synchronized broadcast isochronous stream (BIS) to a target BIS. In embodiments of the present application, a controller switches, on the basis of a BIG creation and synchronization request, a synchronized BIS to a target BIS, thereby reducing the power consumption of synchronous reception in a BIS synchronous switching process and reducing the synchronous switching time.

Description

Synchronization Methods and Synchronization Devices

technical field

The present application relates to the field of communications, and more particularly, to a synchronization method and a synchronization device.

Background technique

Bluetooth Low Energy (BLE), also known as Bluetooth Low Energy, is a personal area network technology that can be used in fields such as healthcare, sports and fitness, beacons, security, and home entertainment. In the Bluetooth Core Specification (Core Spec), a Broadcast Isochronous Group (BIG) is included, and a BIG may include one or more Broadcast Isochronous Streams (BIS). It is necessary to consider how to reduce the power consumption and time during the BIS synchronous handover process.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a synchronization method and a synchronization device, which can reduce power consumption and reduce switching time during a BIS synchronization switching process.

The embodiment of the present application provides a synchronization method, including:

The controller creates a synchronization request based on the broadcast synchronization group BIG, and switches the synchronized broadcast synchronization stream BIS to the target BIS.

The host sends a BIG create synchronization request to the controller to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG create synchronization request.

An embodiment of the present application provides a synchronization device, including:

The control unit is configured to create a synchronization request based on the broadcast synchronization group BIG, and switch the synchronized broadcast synchronization stream BIS to the target BIS.

A sending unit, configured to send a BIG creation synchronization request to the controller, so as to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request.

An embodiment of the present application provides a synchronization device, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the synchronization device executes the above synchronization method.

An embodiment of the present application provides a chip for implementing the above synchronization method.

Specifically, the chip includes: a processor for calling and running a computer program from the memory, so that the device on which the chip is installed executes the above synchronization method.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program, which, when the computer program is run by a device, causes the device to execute the above synchronization method.

An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the above synchronization method.

The embodiments of the present application provide a computer program, which, when running on a computer, enables the computer to execute the above synchronization method.

In the embodiment of the present application, the controller creates a synchronization request based on the BIG to switch the synchronized BIS to the target BIS, which can reduce the power consumption of synchronization reception and reduce the synchronization switching time during the BIS synchronization switching process.

Description of drawings

FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

FIG. 2 is a flowchart of a synchronization receiver initiating a BIS handover.

FIG. 3 is a schematic diagram of determining BIS/BIG timing using periodic broadcast.

FIG. 4 is a schematic flowchart of a synchronization method according to an embodiment of the present application.

FIG. 5 is a schematic flowchart of a synchronization method according to another embodiment of the present application.

FIG. 6 is a schematic diagram of the process of the controller completing the BIS switching in Example 1. FIG.

FIG. 7 is a schematic flowchart of BIS switching in Example 1. FIG.

FIG. 8 is a schematic diagram of the process of the controller completing the BIS switching in Example 2. FIG.

FIG. 9 is a schematic flowchart of BIS switching in Example 2. FIG.

FIG. 10 is a schematic block diagram of a synchronization device according to an embodiment of the present application.

FIG. 11 is a schematic block diagram of a synchronization device according to another embodiment of the present application.

FIG. 12 is a schematic block diagram of a synchronization device according to another embodiment of the present application.

FIG. 13 is a schematic block diagram of a synchronization device according to another embodiment of the present application.

FIG. 14 is a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 15 is a schematic block diagram of a chip according to an embodiment of the present application.

FIG. 16 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship. For example, if A indicates B, it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, which belong to the embodiments of the present application. protected range.

In the BLE scenario, BIG can be carried over Bluetooth Periodic Advertising (PA). You need to start the periodic broadcast first and then start the BIG. When synchronizing BIG, broadcast synchronizers (such as synchronous broadcasters and/or synchronous receivers) should also synchronize to Bluetooth periodic broadcast, and then synchronize to BIG/BIS through periodic broadcast. For example, a BIG can contain up to 31 BISs, each BIS can be used to transmit the corresponding audio stream, and BIG/BIS can provide a new audio broadcast function for Bluetooth. As shown in FIG. 1 , a master (Master) device starts a BIG, and the BIG includes two BISs, and the two BISs transmit the left channel and the right channel of the audio respectively. Two slave (Slave) devices can synchronize to the BIG/BIS at the same time and receive the audio stream in the BIS.

Usually broadcast senders can be called Isochronous Broadcasters (or broadcast senders), and broadcast synchronous receivers can be called Synchronized Receivers (or synchronous receivers, synchronous broadcast receivers, etc.).

A typical application scenario of Bluetooth broadcast audio is the support of multilingual audio streams. For example, suppose a BIG contains 4 BISs. Among them, BIS1 and BIS2 respectively transmit the left and right channels of Spanish, and BIS3 and BIS4 respectively transmit the left and right channels of English. Users may need to switch languages while enjoying audio. For example, switch from Spanish to English. At this time, the BIS synchronized by the user's Bluetooth headset device (that is, the Synchronized Receiver) needs to be switched from BIS1 and BIS2 to BIS3 and BIS4.

In an example, the synchronization of the BIS can be initiated by the Low Energy (LE) BIG Create Sync command, and the number of BISs to be synchronized and the target BIS index ( Index).

See Table 1 for an example of a LEBIG Create Sync command:

Table 1

If the command sent by the host carries an allocated (allocated) BIG_Handle (BIG handle), the controller will return an error code: Command Disallowed (0x0C)).

Because the Synchronized Receiver needs to terminate the synchronization of the current BIS when it initiates a BIS synchronization switch, and then re-initiate the synchronization of the new target BIS. FIG. 2 is a schematic flowchart of a BIS handover initiated by a Synchronized Receiver. The synchronization receiver may include a host (Host) and a controller (Controller). The host may include an application layer, and the controller may include a link layer (LL). Specifically, the process of the BIS handover may include:

S11. Isochronous Broadcaster starts periodic broadcast (Start PA).

S12. Isochronous Broadcaster (Isochronous Broadcaster) starts BIG (Start BIG) associated with the periodic broadcast. For example: BIS 1, BIS 2, BIS 3, BIS 4 are included in the activated BIG.

S13. The Synchronized Receiver Host sends an instruction to scan (Scan) PA to the controller, and the controller executes the scan.

S14. The Synchronized Receiver Controller (Synchronized Receiver Controller) receives the periodic broadcast from the synchronous broadcaster. For example, ACAD in periodic broadcast AUX_SYNC_IND carries BIG information (BIGInfo) (AUX_SYNC_IND ACAD with BIGInfo).

S15. The sync receiver host sends a LE BIG Create Sync cmd to the sync receiver controller, so that the sync receiver synchronizes to BIS1/BIS2 (sync to BIS1/BIS2).

In this way, the synchronous receiver can scan to the PA of the synchronous broadcaster (Sync to PA), and use the PA to synchronize to the BIS (Sync with BIG) such as BIS1/BIS2.

S16. BIS handover may be initiated by the sync receiver host.

S17. The sync receiver host sends a LE BIG stop sync command (Terminate Sync cmd) to the sync receiver controller.

S18. The synchronous receiver controller returns a host controller interface (Host Controller interface, HCI) command completion event (Command Complete event) to the synchronous receiver host. In this case, the sync receiver stops syncing to BIS1/BIS2.

If the sync receiver has stopped synchronizing with the PA of the sync broadcaster, S19 and S20 can be performed to synchronize to the PA again. If the sync receiver does not stop synchronizing with the PA of the sync broadcaster, S21 may be performed.

S19. The sync receiver host scans the PA.

S20. The sync receiver controller receives periodic broadcasts from the sync broadcaster. For example, periodic broadcast: ACAD in AUX_SYNC_IND carries BIGInfo.

S21. The sync receiver host sends a LE BIG Create Sync cmd to the sync receiver controller, so that the sync receiver synchronizes to BIS3/BIS4 (sync to BIS3/BIS4).

In this way, the synchronous receiver can scan again to the PA of the synchronous broadcaster (Sync to PA), and synchronize with the BIG such as BIS3/BIS4 by means of the PA.

As shown in Figure 3, the timing of BIG/BIS can be obtained through BIGInfo carried in periodic broadcast. For example, by periodically broadcasting the BIGInfo carried by the ACAD in the AUX_SYNC_IND, the BIG event (event) x+1 in the next cycle of the BIG event x can be determined. The BIGInfo may include a BIG offset (BIG_Offset), a BIG anchor point (BIG Anchor Point), and the like. For example, the offset unit (Offset Unit) can be 30 μs (microseconds) or 300 μs. The BIG anchor is after the time indicated by the BIG offset (Time indicated by BIG_Offset). The BIG anchor point may be the start of BIG 1 in BIG event x+1. In addition, BIGInfo may also include time information for determining BIS events such as the BIS spacing (BIS_Spacing) of BIS1 and BIS2.

Referring to the BIS switching process, the Synchronized Receiver device needs to terminate the currently established BIS before switching the BIS, and then resynchronize the new BIS. This process requires the periodic broadcast of the Synchronized Receiver device and the Isochronous Broadcaster device to maintain a synchronized state, resulting in a waste of power consumption of the Receiver device. Moreover, if the Synchronized Receiver device stops synchronizing with the periodic broadcast of the Isochronous Broadcaster device, it will first rescan and synchronize to the periodic broadcast of the Broadcaster device, and then synchronize to the new BIS. The process of scanning the synchronous periodic broadcast is a time-consuming process, which leads to a long time for BIS switching, resulting in poor user experience.

FIG. 4 is a schematic flowchart of a synchronization method 200 according to an embodiment of the present application. The method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least some of the following.

S210. The controller creates a synchronization request based on the broadcast synchronization group BIG, and switches the synchronized broadcast synchronization stream BIS to the target BIS.

Exemplarily, the controller may be the controller of the synchronization receiver, see FIG. 2 . The controller may create a synchronization request based on the BIG from the host of the synchronization receiver to switch the synchronized broadcast synchronization stream BIS to the target BIS. The synchronized broadcast synchronization stream BIS may include one or more BISs in a BIG, and may specifically include one or more BISs that have been synchronized between the synchronization receiver and the synchronization broadcaster. The target BIS may also include one or more BISs, and may specifically include the BISs that need to be switched to be synchronized with the synchronization receiver.

Optionally, the method further includes: the controller receives the BIG creation synchronization request from the host.

Illustratively, a user may initiate a BIS handover through the host of the synchronization receiver. The host sends a BIG create synchronization request to the controller. When the controller receives a BIG creation synchronization request from the host, it switches the synchronized broadcast synchronization stream BIS to the target BIS.

Optionally, the BIG creation synchronization request includes a BIG handle BIG_Handle, and the method further includes:

In the case that the BIG_Handle has been used by the create BIG command, the controller returns an error message to the host.

Illustratively, the BIG_Handle included in the BIG create synchronization request may be used by a create BIG command such as a LE Create BIG command. The LE Create BIG command is the command used by the synchronous broadcaster to create a BIG. If a synchronous broadcaster has already created a BIG with this BIG_Handle, and the synchronous receiver requests to continue to use the same BIG_Handle to synchronize the BIGs created by other synchronous broadcasters, the synchronous receiver controller will return an error message to the synchronous receiver host.

Optionally, the BIG creation synchronization request also includes target BIS information, and the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, including:

When the BIG_Handle is not used by the create BIG command, the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS.

Optionally, the target BIS information includes: the quantity and/or parameter description of the target BIS.

Exemplarily, the number of target BISs included in the target BIS information may be N, and the target BIS information may further include parameter descriptions of the N BISs.

Optionally, the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, including:

The controller obtains the target BIS set based on the target BIS information included in the BIG creation synchronization request;

The controller obtains a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein, the first BIS set includes existing in the target BIS set but not in the BIS information of a synchronized BIS set, the second BIS set includes BIS information that exists in the synchronized BIS set but does not exist in the target BIS set;

The controller stops synchronizing the BIS identified by the BIS information of the second BIS set, and starts to establish synchronization with the BIS identified by the BIS information of the first BIS set.

In mode 1, the controller can trigger a new switching logic based on the BIG creation synchronization request, compare the BISs that need to stop synchronization and those that need to establish synchronization, and then complete the BIS switching.

Exemplarily, the BIS information included in the synchronized BIS sets of the synchronization receiver and the synchronization broadcaster are BIS1 and BIS2. The target BIS information included in the BIG creation synchronization request is BIS3 and BIS4, and the target BIS set includes BIS3 and BIS4. The controller compares the synchronized BIS set and the target BIS set, records the BIS information BIS3 and BIS4 existing in the target BIS set but not in the synchronized BIS set into the first BIS set, and records the BIS information BIS3 and BIS4 that exist in the synchronized BIS set But BIS information BIS1 and BIS2 that do not exist in the target BIS set are recorded in the second BIS set. Then, the controller stops synchronizing BIS1 and BIS2 of the synchronous broadcaster in the second BIS set, and starts to establish synchronization with BIS3 and BIS4 of the synchronous broadcaster in the first BIS set.

Exemplarily, the BIS information included in the synchronized BIS sets of the sync receiver and the sync broadcaster are BIS1, BIS2 and BIS3. The target BIS information included in the BIG creation synchronization request is BIS3, BIS4, BIS5, and BIS6. The controller compares the synchronized BIS set and the target BIS set, records the BIS information BIS4, BIS5 and BIS6 that exist in the target BIS set but do not exist in the synchronized BIS set into the first BIS set, and will exist in the synchronized BIS set. The BIS information BIS1 and BIS2 of the BIS set but not present in the target BIS set are recorded in the second BIS set. Then, the controller stops synchronizing BIS1 and BIS2 of the synchronous broadcaster in the second BIS set and starts to establish synchronization with BIS4, BIS5 and BIS6 of the synchronous broadcaster in the first BIS set.

Optionally, the BIG creation synchronization request further includes BIS information for which synchronization needs to be stopped.

Optionally, the information of the BISs whose synchronization needs to be stopped includes the number and/or parameter description of the BISs whose synchronization needs to be stopped.

Optionally, the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, including: the controller stops synchronizing the BIS identified by the BIS information for which synchronization needs to be stopped, and starts to synchronize the BIS based on the synchronization. The BIS identified by the target BIS information establishes synchronization.

In the second mode, the controller can stop synchronizing the BIS identified by the BIS information that needs to stop synchronization included in the BIG creation synchronization request, and establish synchronization with the BIS identified by the target BIS information included in the BIG creation synchronization request, and then Complete the BIS switch.

Optionally, the BIG creation synchronization request is a low-power LE BIG creation synchronization command.

Exemplarily, in mode 1, the BIG create synchronization request may be a LE BIG Create Sync command (LE BIG Create Sync command), or an Enhanced LE BIG Create Sync command (Enhanced LE BIG Create Sync command). For example, HCI_LE_BIG_Create_Sync. Create Sync Commands based on LE BIG or Enhanced LE BIG Create Sync Commands to change the switching logic of the controller. In the new switching logic, the controller can compare and obtain the BIS information that needs to stop synchronization and the BIS information that needs to establish synchronization, and then complete the BIS switching.

Optionally, the BIG creation synchronization request is an LE BIG creation synchronization command including BIS information that needs to stop synchronization.

Exemplarily, in the second manner, the BIG create synchronization request may create a modified version of the synchronization command for LE BIG (LE BIG Create Sync command V2). For example HCI_LE_BIG_Create_Sync v2. The modified version of the LE BIG create synchronization command can add parameters related to the BIS information that needs to be stopped, such as the number of BISs that need to be stopped and the parameter description of the BISs that need to be stopped. The switching logic of the controller can be changed to complete the BIS switching based on the number of BISs that need to stop synchronization and the parameter description of the BISs that need to stop synchronization.

Optionally, the method further includes:

The controller sends a BIG synchronization result to the host, where the BIG synchronization result includes the information of the out-of-sync BIS set.

Optionally, the information of the out-of-synchronization BIS set includes the number of out-of-synchronization BISs and/or the connection handle corresponding to the out-of-synchronization BIS.

Optionally, the BIG synchronization result is a host controller interface (HCI) LE BIG synchronization establishment and update event, and the HCI LE BIG synchronization establishment and update event includes the information of the out-of-synchronization BIS set.

Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment event including the information of the out-of-synchronization BIS set.

Exemplarily, the manner in which the controller sends the BIG synchronization result to the host may include various manners. One way is to modify the parameters in the HCI LE BIG synchronization establishment event, and carry the number of out-of-sync BIS and /Or information about the out-of-sync BIS set, such as the connection handle corresponding to the out-of-sync BIS. Another way is to add a new HCI LE BIG synchronization establishment update event (LE BIG Sync Established update event), and carry the number of out-of-sync BISs and/or the connection corresponding to the out-of-sync BIS in the HCI LE BIG synchronization establishment update event Information about out-of-sync BIS collections such as handles.

FIG. 5 is a schematic flowchart of a synchronization method 300 according to another embodiment of the present application. The method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least some of the following.

S310. The host sends a BIG creation synchronization request to the controller to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request.

Optionally, the BIG creation synchronization request includes a BIG handle BIG_Handle, and the method further includes: in the case that the BIG_Handle has been used by the BIG creation command, the host receives error information from the controller.

Optionally, the BIG creation synchronization request further includes target BIS information.

Optionally, the method further includes: receiving, by the host, a BIG synchronization result from the controller, the BIG synchronization result including information on a BIS set that is out of synchronization.

Optionally, the BIG synchronization result is an HCI LE BIG synchronization establishment update event, and the HCI LE BIG synchronization establishment update event includes the information of the out-of-synchronization BIS set.

For a specific example of the host execution method 300 in this embodiment, reference may be made to the relevant description about the host of the synchronization receiver in the foregoing method 200, which is not repeated here for brevity.

The embodiment of the present application provides a synchronization method based on BLE BIS, which can enhance the LE BIG Create Sync command, so that when the device has been synchronized to BIG/BIS, it does not need to terminate the synchronization of BIG/BIS first, and directly completes the new synchronization. Synchronous handover of the BIS.

Example 1:

1. Enhance LE BIG Create Sync command. For example, to set an Enhanced LE BIG Create Sync command:

(1) Make the controller check the BIG_Handle when it receives the command. If the BIG_Handle has been used by the LE Create BIG command, the controller returns an error code (error code): invalid HCI command parameters (INVALID HCI COMMAND PARAMETERS) (0x12 );

The controller checks the BIS(es) described by the Num_BIS, BIS[i] parameters:

Num_BIS, BIS[i] parameter description BIS set marked as BIS_Set_req,

The controller marks the currently existing BIS set for which synchronization has been established as BIS_Set_synced, and can perform the following steps:

(a) If the BIS of the two sets are exactly the same or BIS_Set_req is included in BIS_Set_synced, the Controller returns an error code (error code): Command Disallowed (0x0C);

(b) If the BIS of the two sets are not the same:

Mark the BIS set that exists in BIS_Set_req but does not exist in BIS_Set_synced as BIS_Set_a;

Mark the BIS set that exists in BIS_Set_synced but does not exist in BIS_Set_req as BIS_Set_b;

The controller terminates the synchronization of the BIS contained in the BIS_Set_b set (if any) and starts to establish synchronization with the BIS contained in the BIS_Set_a set.

2. Added the LE BIG synchronization establishment update event (Sync Established update event) or the v2 version of the LE BIG step establishment event (HCI_LE_BIG_Sync_Established[v2]). The parameters in the event can be found in Table 2:

Table 2

In the above table, Num_BIS_Lost, Connection_Handle_Lost[i] represent the set of out-of-sync BISs. Num_BIS_Lost is the number of out-of-sync BISs, and Connection_Handle_Lost[i] is an array of connection handles, representing the connection handles corresponding to out-of-sync BISs.

FIG. 6 is a schematic diagram of the process of the controller completing the BIS switching, taking the BIG including two BISs as an example. If the controller of the sync receiver is in sync with BIS1, and the controller receives the enhanced LE BIG create sync command, a BIS handover begins. In this example, the switch is from BIS1 to BIS2. Specifically, the anchor point of the BIS event of the next cycle x+1 of x can be determined based on the ISO interval. The controller performs BIS switching based on the BIG anchor point (Anchor Point) according to the enhanced LE BIG Create Sync command (Enhanced LE BIG Create Sync command): HCI_LE_BIG_Create_Sync. After the controller performs synchronous switching, it returns the HCI LE BIG synchronization establishment event (HCI_LE_BIG_Sync_Established event) v2 version: HCI_LE_BIG_Sync_Established[v2] to the host.

As shown in Figure 7, the overall process of BIS handover includes:

S31. The synchronous broadcaster (Isochronous Broadcaster) starts periodic broadcast (Start PA).

S32. The synchronous broadcaster starts BIG (Start BIG) associated with the periodic broadcast. For example, start 4 BISs: BIS1, BIS2, BIS3 and BIS4.

S33. The Synchronized Receiver Host sends an instruction to scan (Scan) PA to the synchronous receiver controller, and the synchronous receiver controller executes the scan.

S34. The Synchronized Receiver Controller (Synchronized Receiver Controller) receives the periodic broadcast from the synchronous broadcaster. For example, ACAD in periodic broadcast AUX_SYNC_IND carries BIG information (AUX_SYNC_INDACAD with BIGInfo).

S35. The host sends an enhanced LE BIG creation synchronization command to the controller, which can carry: Num_BIS: 2, [BIS1, BIS2], etc. Num_BIS: 2 indicates that the number of BISs is 2, and [BIS1,BIS2] indicates the parameter descriptions of BIS1 and BIS2 that need to be synchronized.

In this way, the Synchronized Receiver (Synchronized Receiver) scans the PA of the synchronous broadcaster and synchronizes to the BIS (Sync with BIG) via the PA, for example: BIS1/BIS2.

S36. The application initiates a BIS handover request.

S37. The parameters carried by the synchronous receiver host sending the Enhanced LE BIG Create Sync command to the synchronous receiver controller may include BIS3/BIS4 information. For example, this command can carry: Num_BIS:2,[BIS3,BIS4], etc. Num_BIS: 2 indicates that the number of BISs is 2, and [BIS3, BIS4] indicates the parameter descriptions of BIS1 and BIS2 that need to be synchronized.

S38. After receiving the command, the controller performs processing according to the description of the command. For example, stop syncing BIS1/BIS2 and start syncing to BIS3/BIS4.

Note: BIS switching can be completed according to the schematic diagram of the controller to complete the BIS switching process, that is, Figure 6.

S39. The controller returns the v2 version of the HCI LE BIG step establishment event (HCI_LE_BIG_Sync_Established[v2]) to the host. The Num_BIS and Connection_Handle[i] included in this event are the set of BIS3/BIS4 newly established synchronization, and Num_BIS_Lost and Connection_Handle_Lost[i] are the set of BIS1/BIS2 whose synchronization is stopped.

Example 2:

This example is applicable to the situation where the Synchronized Receiver (Synchronized Receiver) device continues to synchronize with the periodic broadcast of the Isochronous Broadcaster (Isochronous Broadcaster) device after establishing synchronization with BIG/BIS.

1. Added LE BIG Create Sync command v2 version:

(1) In this command, the parameters Num_BIS_Lost and BIS_Lost[i] are added, indicating the set of BISs that the host (Host) requests the controller (Controller) to stop synchronizing. See Table 3.

table 3

Based on the parameters in the above table, when the controller receives the command, it checks the BIG handle (BIG_Handle), if the BIG_Handle has been used by the LE Create BIG command (Create BIG command), the controller returns an invalid error code (error code) HCI command parameters (INVALID HCI COMMAND PARAMETERS) (0x12);

The controller stops synchronizing the BIS information that needs to stop synchronization: Num_BIS_Lost, the multiple BIS indicated by the BIS_Lost[i] parameter, and initiates synchronization for the BIS information that needs to be synchronized: Num_BIS, and the multiple BIS indicated by the BIS[i] parameter.

In addition, the LE BIG Sync Established update event or the LE BIG Sync Established event v2 version (HCI_LE_BIG_Sync_Established[v2]) is added. For parameters in the event, see Table 2 in Example 1, and details are not repeated here. In Table 2, Num_BIS_Lost and Connection_Handle_Lost[i] represent the set of BISs out of synchronization. Num_BIS_Lost is the number of out-of-sync BISs, and Connection_Handle_Lost[i] is an array of connection handles, representing the connection handles corresponding to out-of-sync BISs.

FIG. 8 is a schematic diagram of the process of the controller completing the BIS switching, taking the BIG including two BISs as an example. If the controller of the sync receiver is in sync with BIS1, and the controller receives the enhanced LE BIG create sync command, a BIS handover begins. In this example, the switch is from BIS1 to BIS2. Specifically, the anchor point of the BIS event of the next cycle x+1 of x can be determined based on the ISO interval. The controller performs BIS switching based on the BIG anchor point (Anchor Point) according to the Enhanced LE BIG Create Sync command (Enhanced LE BIG Create Sync command) v2 version: HCI_LE_BIG_Create_Sync[v2]. After the controller performs synchronous switching, it returns the HCI LE BIG synchronization establishment event (HCI_LE_BIG_Sync_Established event) v2 version: HCI_LE_BIG_Sync_Established[v2] to the host.

As shown in Figure 7, the overall flow of BIS handover includes: the BIS handover flow diagram may include:

S41. The synchronous broadcaster (Isochronous Broadcaster) starts periodic broadcast (Start PA).

S42. The synchronous broadcaster starts the BIG to associate with the periodic broadcast. For example, start 4 BISs: BIS1, BIS2, BIS3 and BIS4.

S43. The Synchronized Receiver Host (Synchronized Receiver Host) sends an instruction to scan (Scan) PA to the synchronous receiver controller, and the synchronous receiver controller executes the scan.

S44. The Synchronized Receiver Controller (Synchronized Receiver Controller) receives the periodic broadcast from the synchronous broadcaster. For example, ACAD in periodic broadcast AUX_SYNC_IND carries BIG information (AUX_SYNC_INDACAD with BIGInfo).

S45. The host sends an enhanced LE BIG create sync command or LE BIG create sync command v2 version (HCI_LE_BIG_Create_Sync[v2]) to the controller. Which can carry: Num_BIS: 2, [BIS1, BIS2], etc. Num_BIS: 2 indicates that the number of BISs is 2, and [BIS1,BIS2] indicates the parameter descriptions of BIS1 and BIS2 that need to be synchronized.

S46. The application initiates sending of a BIS handover request.

S47. The synchronous receiver host sends the HCI_LE_BIG Create Sync command[v2] to the synchronous receiver controller, carrying parameters Num_BIS:2, [BIS3/BIS4], Num_BIS:2, [BIS1/BIS2].

S48. After receiving the command, the controller performs processing according to the description of the command, for example, stops synchronizing BIS1/BIS2, and starts synchronizing to BIS3/BIS4.

In this example, the BIS switching can be completed according to the schematic diagram of the process of completing the BIS switching by the controller, that is, FIG. 8 .

S49. The controller returns the v2 version of the HCI LE BIG step establishment event (HCI_LE_BIG_Sync_Established[v2]) to the host. The Num_BIS and Connection_Handle[i] included in this event are the set of BIS3/BIS4 newly established synchronization, and Num_BIS_Lost and Connection_Handle_Lost[i] are the set of BIS1/BIS2 whose synchronization is stopped.

The embodiment of the present application supports the synchronized receiver (Synchronized Receiver) device to directly complete the switching between different BISs under the condition of keeping synchronization with the BIG/BIS, shortening the time for the host (Host) to initiate the BIS switching, and enhancing the user experience , Shorten the delay of different audio switching. In addition, after the Synchronized Receiver device is synchronized with the BIG/BIS, it can terminate the synchronization of the periodic broadcast, and the BIS switching process does not depend on the periodic broadcast, which effectively reduces the power consumption of the Synchronized Receiver device and increases the use time of the device.

FIG. 10 is a schematic block diagram of a synchronization device 400 according to an embodiment of the present application. The synchronization device 400 may include:

The control unit 410 is configured to create a synchronization request based on the broadcast synchronization group BIG, and switch the synchronized broadcast synchronization stream BIS to the target BIS.

Optionally, as shown in FIG. 11 , the synchronization device further includes: a receiving unit 420, configured to receive the BIG creation synchronization request from the host.

Optionally, the BIG creation synchronization request includes a BIG handle BIG_Handle, and the synchronization device further includes: a first sending unit 430, configured to return error information to the host when the BIG_Handle has been used by the BIG creation command .

Optionally, the BIG creation synchronization request further includes target BIS information, the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, and the control unit is further configured to create a BIG when the BIG_Handle has not been created. When the command is used, a synchronization request is created based on the BIG, and the synchronized BIS is switched to the target BIS.

Optionally, the control unit is also used for:

Obtain the target BIS set based on the target BIS information included in the BIG creation synchronization request;

Based on the target BIS set and the synchronized BIS set, a first BIS set and a second BIS set are obtained; wherein the first BIS set includes the BIS that exists in the target BIS set but does not exist in the synchronized BIS The BIS information of the set, the second BIS set includes the BIS information that exists in the synchronized BIS set but does not exist in the target BIS set;

Stop synchronizing the BIS identified by the BIS information of the second BIS set, and start to establish synchronization with the BIS identified by the BIS information of the first BIS set.

Optionally, the control unit is further configured to stop synchronizing the BIS identified by the BIS information whose synchronization needs to be stopped, and start synchronizing the BIS identified based on the target BIS information.

Optionally, the synchronization device further includes: a second sending unit 440, configured to send a BIG synchronization result to the host, where the BIG synchronization result includes information about a BIS set that is out of synchronization.

Optionally, the BIG synchronization result is a host controller interface HCI LE BIG synchronization establishment and update event, and the HCI LE BIG synchronization establishment and update event includes the information of the out-of-synchronization BIS set.

The synchronization device 400 in this embodiment of the present application can implement the corresponding functions of the controller of the synchronization receiver in the foregoing method embodiments. For the corresponding processes, functions, implementations, and beneficial effects of each module (sub-module, unit, or component, etc.) in the synchronization device 400, reference may be made to the corresponding descriptions in the above method embodiments, which are not repeated here. It should be noted that the functions described by each module (submodule, unit, or component, etc.) in the synchronization device 400 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or may be implemented by the same Module (submodule, unit or component, etc.) implementation.

FIG. 12 is a schematic block diagram of a synchronization device 500 according to another embodiment of the present application. The synchronization device 500 may include:

The sending unit 510 is configured to send a BIG creation synchronization request to the controller, so as to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request.

Optionally, the BIG creation synchronization request includes a BIG handle BIG_Handle. As shown in FIG. 13 , the synchronization device further includes: a first receiving unit 520, configured to be used when the BIG_Handle has been used by the BIG creation command , to receive an error message from the controller.

Optionally, the synchronization device further includes: a second receiving unit 530, configured to receive a BIG synchronization result from the controller, where the BIG synchronization result includes information about a BIS set that is out of synchronization.

The synchronization device 500 in the embodiment of the present application can implement the corresponding function of the host of the synchronization receiver in the foregoing method embodiments. For the corresponding processes, functions, implementations, and beneficial effects of each module (submodule, unit, or component, etc.) in the synchronization device 500, reference may be made to the corresponding descriptions in the above method embodiments, which are not repeated here. It should be noted that the functions described by each module (submodule, unit, or component, etc.) in the synchronization device 500 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or by the same Module (submodule, unit or component, etc.) implementation.

FIG. 14 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so that the communication device 600 implements the methods in the embodiments of the present application.

Optionally, the communication device 600 may also include a memory 620 . The processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices .

Among them, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 600 may be the host of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the host in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the communication device 600 may be the controller of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the controller in each method of the embodiment of the present application, which is not repeated here for brevity.

FIG. 15 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the methods in the embodiments of the present application.

Optionally, the chip 700 may further include a memory 720 . The processor 710 may call and run a computer program from the memory 720 to implement the method executed by the controller or the host in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may further include an input interface 730 . The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740 . The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the host in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the host in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the chip can be applied to the controller in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the controller in each method of the embodiment of the present application, which is not repeated here for brevity.

The chips applied to the host and controller can be the same chip or different chips.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.

The memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM).

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

FIG. 16 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a controller 810 and a host 820 .

The controller 810 is configured to create a synchronization request based on the BIG, and switch the synchronized broadcast synchronization stream BIS to the target BIS.

The host 820 is configured to send a BIG creation synchronization request to the controller, so as to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request.

Wherein, the controller 810 can be used to implement the corresponding functions implemented by the controller in the above method, and the host 820 can be used to implement the corresponding functions implemented by the host in the above method. For brevity, details are not repeated here.

Alternatively, the controller 810 and the host 820 may be provided in the same synchronization device such as a synchronization receiver.

Optionally, the system may further include: a synchronization broadcaster, which establishes synchronization with the host of the synchronization receiver through the controller of the synchronization receiver.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. 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 on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art who is familiar with the technical scope disclosed in the present application can easily think of changes or substitutions. Covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A synchronization method that includes:

The controller creates a synchronization request based on the broadcast synchronization group BIG, and switches the synchronized broadcast synchronization stream BIS to the target BIS.
The method of claim 1, wherein the method further comprises:

The controller receives the BIG create synchronization request from the host.
The method according to claim 1 or 2, wherein the BIG creation synchronization request includes a BIG handle BIG_Handle, and the method further comprises:

In the case that the BIG_Handle has been used by the create BIG command, the controller returns an error message to the host.
The method according to claim 3, wherein the BIG creation synchronization request further includes target BIS information, and the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, comprising:

When the BIG_Handle is not used by the create BIG command, the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS.
The method according to claim 4, wherein the target BIS information comprises: quantity and/or parameter description of the target BIS.
The method according to any one of claims 1 to 5, wherein the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, comprising:

The controller obtains the target BIS set based on the target BIS information included in the BIG creation synchronization request;

The controller obtains a first BIS set and a second BIS set based on the target BIS set and the synchronized BIS set; wherein, the first BIS set includes existing in the target BIS set but not in the BIS information of a synchronized BIS set, the second BIS set includes BIS information that exists in the synchronized BIS set but does not exist in the target BIS set;

The controller stops synchronizing the BIS identified by the BIS information of the second BIS set, and starts to establish synchronization with the BIS identified by the BIS information of the first BIS set.
The method according to any one of claims 1 to 5, wherein the BIG creation synchronization request further includes BIS information for which synchronization needs to be stopped.
The method according to claim 7, wherein the information of the BISs whose synchronization needs to be stopped includes the number and/or parameter description of the BISs whose synchronization needs to be stopped.
The method according to claim 7 or 8, wherein the controller creates a synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, comprising:

The controller stops synchronizing the BIS identified by the BIS information whose synchronization needs to be stopped, and starts to establish synchronization with the BIS identified based on the target BIS information.
The method of any one of claims 1 to 6, wherein the BIG create synchronization request is a low power LE BIG create synchronization command.
The method according to any one of claims 1 to 5, 7 to 9, wherein the BIG create synchronization request is an LE BIG create synchronization command including BIS information that needs to stop synchronization.
The method of any one of claims 1 to 11, wherein the method further comprises:

The controller sends a BIG synchronization result to the host, where the BIG synchronization result includes the information of the out-of-sync BIS set.
The method according to claim 12, wherein the information of the out-of-synchronization BIS set includes the number of out-of-synchronization BISs and/or the connection handle corresponding to the out-of-synchronization BIS.
The method according to claim 12 or 13, wherein the BIG synchronization result is a host controller interface HCI LE BIG synchronization establishment and update event, and the HCI LE BIG synchronization establishment and update event includes the information of the out-of-synchronization BIS set .
The method of claim 12 or 13, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-sync BIS set.
A synchronization method that includes:

The host sends a BIG create synchronization request to the controller to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG create synchronization request.
The method according to claim 16, wherein the BIG creation synchronization request includes a BIG handle BIG_Handle, and the method further comprises:

The host receives an error message from the controller in case the BIG_Handle has been used by the create BIG command.
The method according to claim 16 or 17, wherein the BIG creation synchronization request further includes target BIS information.
The method according to claim 18, wherein the target BIS information comprises: quantity and/or parameter description of the target BIS.
The method according to any one of claims 16 to 19, wherein the BIG creation synchronization request further includes BIS information for which synchronization needs to be stopped.
The method according to claim 20, wherein the information of the BISs whose synchronization needs to be stopped includes the number and/or parameter description of the BISs whose synchronization needs to be stopped.
19. The method of any of claims 16 to 19, wherein the BIG create synchronization request is a low power LE BIG create synchronization command.
The method of any one of claims 16 to 22, wherein the BIG create synchronization request is an LE BIG create synchronization command that includes BIS information for which synchronization needs to be stopped.
The method of any one of claims 16 to 23, wherein the method further comprises:

The host receives a BIG synchronization result from the controller, the BIG synchronization result including information on out-of-sync BIS sets.
The method according to claim 24, wherein the information of the set of out-of-synchronization BISs includes the number of out-of-synchronization BISs and/or the connection handles corresponding to the out-of-synchronization BISs.
The method according to claim 24 or 25, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment update event, and the HCI LE BIG synchronization establishment update event includes the information of the out-of-synchronization BIS set.
The method of claim 24 or 25, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-sync BIS set.
A synchronization device comprising:

The control unit is configured to create a synchronization request based on the broadcast synchronization group BIG, and switch the synchronized broadcast synchronization stream BIS to the target BIS.
The synchronization device of claim 28, wherein the synchronization device further comprises:

A receiving unit, configured to receive the BIG creation synchronization request from the host.
The synchronization device according to claim 28 or 29, wherein the BIG creation synchronization request includes a BIG handle BIG_Handle, and the synchronization device further comprises: a first sending unit, configured to be used when the BIG_Handle has been created by the BIG command In the case of , an error message is returned to the host.
The synchronization device according to claim 30, wherein the BIG creation synchronization request further includes target BIS information, the controller creates the synchronization request based on the BIG, and switches the synchronized BIS to the target BIS, and the control unit is further configured to In the case that the BIG_Handle is not used by the create BIG command, a synchronization request is created based on the BIG, and the synchronized BIS is switched to the target BIS.
The synchronization device according to claim 31, wherein the target BIS information comprises: the number and/or parameter description of the target BIS.
The synchronization device of any one of claims 28 to 32, wherein the control unit is further adapted to:

Obtain the target BIS set based on the target BIS information included in the BIG creation synchronization request;

Based on the target BIS set and the synchronized BIS set, a first BIS set and a second BIS set are obtained; wherein the first BIS set includes the BIS that exists in the target BIS set but does not exist in the synchronized BIS The BIS information of the set, the second BIS set includes the BIS information that exists in the synchronized BIS set but does not exist in the target BIS set;

Stop synchronizing the BIS identified by the BIS information of the second BIS set, and start to establish synchronization with the BIS identified by the BIS information of the first BIS set.
The synchronization device according to any one of claims 28 to 32, wherein the BIG creation synchronization request further includes BIS information for which synchronization needs to be stopped.
The synchronization device according to claim 34, wherein the information of the BISs whose synchronization needs to be stopped includes the number and/or parameter description of the BISs whose synchronization needs to be stopped.
The synchronization device according to claim 34 or 35, wherein the control unit is further configured to stop synchronizing the BIS identified by the BIS information for which synchronization needs to be stopped, and start synchronizing the BIS identified based on the target BIS information BIS establishes synchronization.
The synchronization device of any one of claims 28 to 33, wherein the BIG create synchronization request is a low power LE BIG create synchronization command.
The synchronization device according to any one of claims 28 to 32, 34 to 36, wherein the BIG create synchronization request is a LE BIG create synchronization command including BIS information that needs to stop synchronization.
The synchronization device according to any one of claims 28 to 38, wherein the synchronization device further comprises: a second sending unit, configured to send a BIG synchronization result to the host, where the BIG synchronization result includes a BIS set that is out of synchronization Information.
The synchronization device according to claim 39, wherein the information of the set of out-of-synchronization BISs includes the number of out-of-synchronization BISs and/or the connection handles corresponding to the out-of-synchronization BISs.
The synchronization device according to claim 39 or 40, wherein the BIG synchronization result is a host controller interface HCI LE BIG synchronization establishment update event, and the HCI LE BIG synchronization establishment update event includes the out-of-synchronization BIS set information.
The synchronization device of claim 39 or 40, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-sync BIS set.
A synchronization device comprising:

A sending unit, configured to send a BIG creation synchronization request to the controller, so as to instruct the controller to switch the synchronized BIS to the target BIS based on the BIG creation synchronization request.
The synchronization device according to claim 43, wherein the BIG creation synchronization request includes a BIG handle BIG_Handle, and the synchronization device further comprises: a first receiving unit, configured to be used when the BIG_Handle has been used by the BIG creation command Next, receive an error message from the controller.
The synchronization device according to claim 43 or 44, wherein the BIG creation synchronization request further includes target BIS information.
The synchronization device according to claim 45, wherein the target BIS information comprises: the number and/or parameter description of the target BIS.
The synchronization device according to any one of claims 43 to 46, wherein the BIG creation synchronization request further includes BIS information for which synchronization needs to be stopped.
The synchronization device according to claim 47, wherein the information of the BISs whose synchronization needs to be stopped includes the number and/or parameter description of the BISs whose synchronization needs to be stopped.
46. The synchronization device of any one of claims 43 to 46, wherein the BIG create synchronization request is a low power LE BIG create synchronization command.
The synchronization device according to any one of claims 43 to 49, wherein the BIG create synchronization request is an LE BIG create synchronization command including BIS information for which synchronization needs to be stopped.
The synchronization device according to any one of claims 43 to 50, wherein the synchronization device further comprises: a second receiving unit for receiving a BIG synchronization result from the controller, wherein the BIG synchronization result includes out-of-synchronization Information about the BIS collection.
The synchronization device according to claim 51, wherein the information of the out-of-synchronization BIS set includes the number of out-of-synchronization BISs and/or the connection handle corresponding to the out-of-synchronization BIS.
The synchronization device according to claim 51 or 52, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment update event, and the HCI LE BIG synchronization establishment update event includes the information of the out-of-synchronization BIS set.
The synchronization device according to claim 51 or 52, wherein the BIG synchronization result is an HCI LE BIG synchronization establishment event including information of the out-of-sync BIS set.
A synchronizing device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, so that the synchronizing device executes as claimed in claims 1 to 15 The method of any of the above.
A synchronization device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, so that the synchronization device executes as claimed in claims 16 to 27 The method of any of the above.
A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 15.
A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method as claimed in any one of claims 16 to 27.
A computer-readable storage medium for storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 15.
A computer-readable storage medium for storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 16 to 27.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 15.
A computer program product comprising computer program instructions that cause a computer to perform the method of any of claims 16 to 27.
A computer program that causes a computer to perform the method of any one of claims 1 to 15.
A computer program that causes a computer to perform the method of any one of claims 16 to 27.